Idoc status records

can any one tell me what I have to do when getting
idoc status as 29, 56, 64,65,31,27 explain briefly?

Hi,
These IDOC status are because of many reasons. There are many reports and transaction codes for the same Based on the error you can reprocess the idoc etc. You can check the transaction codes in SE93 and type BD* & F4..
For reports SE38--> RBD*
http://help.sap.com/erp2005_ehp_02/helpdata/en/78/217e2951ce11d189570000e829fbbd/content.htm
Hope this helps,
Rgds,
Moorthy

Similar Messages

  • Idoc status record

    hi,
      How idoc status records are filled when it comes to inbound side ?
    Ganesh

    Hi,
    Please try to test using this FM to check whether your ALE distribution model has been setup correctly or not for the message type.
    ALE_MODEL_INFO_GET
    ALE_MODEL_AUTH_INFO_GET
    If not, yo need to maintain distribution model (t/code BD64).
    <b>Reward points</b>
    Regards

  • Idocs status records!!!

    Hi,
    We have a requirement in which the status records need to be added in the inbound Idoc.
    In the present scenario, Idoc status records are being created like : status 52 Inbound delivery/deliveries are created(no's are 000001 to 000005). This is current scenario.
    Requirement is like :
    we need to have the number of status records depends on Inbound deliveries created.
    For ex : If two inbound deliveries gets created in an Inbound Idoc, then In Idoc status records should be like :
    Status 52 Inbound delivery created ( no 0000001 to 0000001)
    Status 52 Inbound delivery created ( no 0000002 to 0000002)
    Status 52 Inbound delivery created ( no 0000003 to 0000003).
    and so on.......
    Please let us know how can we acheive the above scenario?
    Thanks in advance.
    Ramesh.

    The inputs to the IDoc processing function are:
    *"*"Local interface:
    *"  IMPORTING
    *"     REFERENCE(INPUT_METHOD) TYPE  BDWFAP_PAR-INPUTMETHD
    *"     REFERENCE(MASS_PROCESSING) TYPE  BDWFAP_PAR-MASS_PROC
    *"  EXPORTING
    *"     VALUE(WORKFLOW_RESULT) LIKE  BDWFAP_PAR-RESULT
    *"     VALUE(APPLICATION_VARIABLE) LIKE  BDWFAP_PAR-APPL_VAR
    *"     VALUE(IN_UPDATE_TASK) LIKE  BDWFAP_PAR-UPDATETASK
    *"     VALUE(CALL_TRANSACTION_DONE) LIKE  BDWFAP_PAR-CALLTRANS
    *"  TABLES
    *"      IDOC_DATA STRUCTURE  EDIDD
    *"      IDOC_CONTRL STRUCTURE  EDIDC
    *"      *IDOC_STATUS STRUCTURE  BDIDOCSTAT*
    *"      RETURN_VARIABLES STRUCTURE  BDWFRETVAR
    *"      SERIALIZATION_INFO STRUCTURE  BDI_SER
    *"  EXCEPTIONS
    *"      WRONG_FUNCTION_CALLED
    The status records are returned from the processing function via the parameter IDOC_STATUS which is an internal table so you can append multiple entries to it.
    The only restriction is that all records must have the same status code (ex. all must be 51 is there is an error, or all must be 53 if there are no errors).  An IDoc processing function executes as a single DB transaction so it is all or nothing.
    ~Ian

  • How to handle idoc status record.

    Hi expert,
    We have configure custom idoc, the status of inbound custom idoc when posting by process code is 64 (Ready to posting), How we can post with status 54, have any idea ?
    When I am using report RBDAPP01, it is in status 51 (Error),
    How I can change the idoc status with 54 (Successful).
    Please help,
    Regards,
    study sap

    hi,
    Retrigger from here
    Try with tcode BD87 For Inbound IDOCS.
    or BD88 for outbound IDOCs.
    Refer these links
    http://sap.ittoolbox.com/groups/technical-functional/sap-interfaces/idoc-status-64-1258234
    http://help.sap.com/saphelp_sm32/helpdata/en/52/16adef543311d1891c0000e8322f96/content.htm
    Cheers
    Mohinder Singh Chauhan
    Edited by: Mohinder Singh Chauhan on Jul 21, 2008 8:08 AM

  • How to create customized long text in IDOC status record in WE02?

    Hi,
    In WE02 you can see the status of the idoc. If you double click on the short text that is coming in the status, you can see the long text. How do i customized my long text to that screen?

    To create a message long text in SE91:
        1. Place the cursor on the corresponding message.
        2. Click the Long text pushbutton.
        3. Enter the long text.
        4. Save the data.
    Edited by: YTL on Jun 27, 2011 5:51 PM

  • Hii Inbound idoc status

    Hii
    i have a requirement where when an Zidoc is being process if a certain condition is met we should insert in a custom table and not process the IDOC
    What status should i put the IDOC in a sort of stand by process so that the user can process it later on with either BD87 or a FM IDOC_INPUT??
    I have try putting in a sort of warning message but neither BD87 or the FM can process idoc with status 52
    i have put it status 64 but client won't accept it since he recognise idoc comming from external system as 64.

    Hi,
    use my form for finishing IDOC processing from the time I did not uses OO...
    *&      Form  append_idoc_status
    *       Create IDOC status record from system message fields
    *       This is always the last action for processing one single
    *       IDOC
    FORM append_idoc_status
      USING    ps_edidc        TYPE edidc
      CHANGING pt_idoc_status  TYPE ty_t_bdidocstat.
      DATA:
        ls_bdidocstat TYPE bdidocstat.
    * this Routine must be called only once per IDOC
      MOVE-CORRESPONDING ps_edidc TO ls_bdidocstat.
    * transfer message data
      ls_bdidocstat-msgty    = sy-msgty.
      ls_bdidocstat-msgid    = sy-msgid.
      ls_bdidocstat-msgno    = sy-msgno.
      ls_bdidocstat-msgv1    = sy-msgv1.
      ls_bdidocstat-msgv2    = sy-msgv2.
      ls_bdidocstat-msgv3    = sy-msgv3.
      ls_bdidocstat-msgv4    = sy-msgv4.
      ls_bdidocstat-repid    = sy-repid.
    * update IDOC status
      CASE ls_bdidocstat-msgty.
        WHEN 'S' OR 'I'.
          ls_bdidocstat-status = c_idoc_posted_ok.
        WHEN 'W'.
          ls_bdidocstat-status = c_idoc_not_fully_posted.
        WHEN 'E' OR 'A'.
          ls_bdidocstat-status = c_idoc_not_posted .
      ENDCASE." ls_bdidocstat-msgty.
      APPEND ls_bdidocstat TO pt_idoc_status.
    ENDFORM.                    " append_idoc_status
    A precondition is that your processing issues a MESSAGE ... INTO lv_dummy with lv_dummy of TYPE STRING.
    Regards,
    Clemens

  • Updating IDoc Status through PI

    Hello Experts,
    We are sending an IDoc to a third party system through PI 7.1. From there we are planning that they will send a acknowledgement. It will contain the Idoc number and its status (whether it got processed at their end or not).
    The requirement is that according to the status we have to update the IDoc status in R/3 system through PI 7.1.
    Kindly elaborate on how to do this? Are there some scenarios done like this?
    Thanks in advance,
    Suraj Sawarkar

    Hi Suraj,
    Check this: call the RFC 'WDLD_EDI_STATUS_SET'. Pass it the Idoc number(s) and status.
    Another alternative is given here
    http://sap.ittoolbox.com/groups/technical-functional/sap-dev/post-idoc-status-record-using-an-rfc-2539010
    Regards
    Suraj

  • Error in idoc status

    hI all,
    can any one tell me "ERROR_WRITING_IDOC_STATUS " why this exception will raise.
    Thanks,
    Prakash .S

    Just check this.
    CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
            EXPORTING
                 VALUE(MASTER_IDOC_CONTROL) LIKE  EDIDC STRUCTURE  EDIDC
                   " Control record of master IDoc
                 VALUE(OBJ_TYPE) LIKE  SERIAL-OBJ_TYPE DEFAULT ''
                 VALUE(CHNUM) LIKE  SERIAL-CHNUM DEFAULT ''
           TABLES
                  COMMUNICATION_IDOC_CONTROL STRUCTURE  EDIDC
                   "  Control records of created comm. IDocs
                  MASTER_IDOC_DATA STRUCTURE  EDIDD
                   " Data records of master IDoc
           EXCEPTIONS
                  ERROR_IN_IDOC_CONTROL
                   " Incorrect entry in IDoc control record
                  ERROR_WRITING_IDOC_STATUS
                   " Error when writing IDoc status records 
                  ERROR_IN_IDOC_DATA
                   " Incorrect entry in IDoc data records
                  SENDING_LOGICAL_SYSTEM_UNKNOWN
                   " Own logical system unknown

  • Outbound IDoc status set as 31

    Hi Friends,
    I am working on the outbound IDoc interface IDOC_OUTPUT_ORDRSP. I modify/add few segments based on the business conditions using the user-exit EXIT_SAPLVEDC_003 (ZXVEDU15). According to the business need, I have to set the IDoc status record as 31. Now IDoc is being created with status record as 30. Is there any way to set the status record with status 31 within the scope of this IDoc interface IDOC_OUTPUT_ORDRSP.
    Pls let me know if any user exit for this same purpose. If not possible to set status explain me the reason for that.
    Thanks
    Hari

    Hi,
    You can use this standard program RC1_IDOC_SET_STATUS to change IDoc status 30 to another status.
    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.
    <b>Reward points</b>
    Regards
    Message was edited by:
            skk

  • Error while updating the status record of IDOC in SAP

    Hi All,
    I am facing this problem. I have done outbound processing and IDOC was sent successfully from SAP to EDI system and it was processed in EDI and now EDI system wants to send the status back to SAP with a status message and the status number that we are using is '24' and we have mapped all the fields in the status table EDIDS and made sure that EDI system sends all those and I think Counter field can not be determined by EDI system so EDI system used the counter '1' since it can not determine how many counters are already there in SAP and unless we pass the value to this counter field we were getting the error. After passing all the values the status of the IDOC is updated with the status '00' instead of '24' and we do not know why it is happened and I would like to know how SAP converts the status record that is received from the EDI system.
    Please let me know how the status record will be translated into SAP from EDI system and I ahve followed basically EDIDS structure and the IDOC status is updating in SAP but with wrong status number and the alignemnt also missing in SAP fields like if I give some text in the EDI it is splitting and storing in 2 fields.
    Please help me in this and I think I have explained the problem in a detail manner.
    Thanks,
    Ramesh.

    Hi Naresh,
    Thanks for the reply and my question is since EDI system is able to send the status back to SAP from EDI system and only problem is it is updatinf the status wrong and I have checked the EDIDS table also and the entry is creating with another counter and please confirm me that it is because of EDI does not support the status record update so that I can confirm to the client that there is nothing wrong in the way SAP functions and EDI system can not update the status code in the SAP.
    Thanks,
    Ramesh.

  • Question on the status record of Idocs.

    Hi all,
    Where does the status of the idoc update::
    1) In the idoc in the sap system/Idoc Archive
    OR
    2)The one we transfer to the OS as a flat file (for the translators(EDI subsystem) to work on)?
    OR
    both of the above?
    Thanks,
    Charles.

    Hi,
    Whenever the IDOC is generated there are one to many status record updated to idoc depending on it is inbound / outbound and various process / system is goes through.
    Check transaction <b>WE47</b> to see all IDOC related status.
    This is the range of status for IDOC.
    OUTBOUND Idoc - Status between 1 to 49
    INBOUND Idoc  - Status between 50 to 74
    Also you can check the View <b>V_STACUST</b>. If you want to check status(s) of any idoc check table EDIDS.
    Regarding two scenario you are talking about.
    1. In the idoc in the sap system/Idoc Archive.
    - When IDOC is generated, it get status record
    - When you archive already created IDOC, the neither the status records are updated / changed or new status record are created
    2. The one we transfer to the OS as a flat file (for the translators(EDI subsystem) to work on)?
    - If you mean that you are sending IDOC to fine port then yes in that case also IDOC has status records.
    Can you explain your second question in more detail?
    Let me know if you have any other question.
    Regards,
    RS

  • Report to display all the status records of an Idoc

    Hi,
      I need to find out all the status records for an idoc and display them as a report. Is there any existing SAP Report that does that. I checked in table edids and all the status records of the idoc are not stored in the status text which is empty althogh there are 12 counters for the idoc.
    regards
    Aveek

    Hey Aveek;
       Try this, which will get the most recent one.  You would just need to change it to loop at the edids records to get at them all...
          TABLES: *edidc, *edids, *t100.
          DATA: wf_string type string.
          CLEAR *edids.
          SELECT SINGLE *
             INTO *edids
             FROM edids
             WHERE docnum = *edidc-docnum
               AND status = '51'.
          SELECT SINGLE text
             INTO *t100-text
             FROM t100
             WHERE sprsl = 'EN'
               AND arbgb = *edids-stamid
               AND msgnr = *edids-stamno.
             CLEAR wf_string.
          MOVE *edids-stapa1 TO wf_string.
          REPLACE '&' WITH wf_string INTO *t100-text.
          IF sy-subrc EQ 0.
            CLEAR wf_string.
            MOVE *edids-stapa2 TO wf_string.
            REPLACE '&' WITH wf_string INTO *t100-text.
            IF sy-subrc EQ 0.
              CLEAR wf_string.
              MOVE *edids-stapa3 TO wf_string.
              REPLACE '&' WITH wf_string INTO *t100-text.
              IF sy-subrc EQ 0.
                CLEAR wf_string.
                MOVE *edids-stapa4 TO wf_string.
                REPLACE '&' WITH wf_string INTO *t100-text.
              ENDIF.
            ENDIF.
          ENDIF.
          A little sloppy (OK, alot!), but it gets the job done...
    Cheers,
    John

  • IDOC inbound ....Status record !

    IDOC_STATUS-MSGID = 'YM'.
    What is the above variable means ?
    Where from i will be able to know what is the MSGID of my  IDOC  which i have created ...using we31 ,we30 ,we81, we82.

    Hi Friend,
    Go to transaction WE02 and execute with IDOC number.
    Doubel click IDCO number on list, expand the status records.
    Double click on any status number, in STS DETAILS table you will get the message ID.
    Hope it will solbe the probelm.
    Regards
    Krishnendu

  • Inbund IDOC error: Status records with status 51 after status 53

    Hi all,
    I'm looking to resolve an issue related to posting an inbound IDOC. when I process inbound IDOC created from report prg I'm getting a status message: "Status records with status 51 after 53" .
    Functionality: I'm creating an IDOC from flat file and processing it to post Customer master data into SAP. During this process creation of IDOC is successful but when I'm changing the existing data record (customer master data) IDOC is throwing this error.
    Changing data: For changing existing data I'm passing KUNNR field and overwriting the remaining data. Even though the idoc status is 51 the changed data is getting posted in to SAP. Here my concern is to see IDOC status as 53.
    Regards,
    Ganesh.
    Edited by: Ganesh Sunkara on Aug 1, 2009 3:45 AM

    Hi all,
    I solved this issue by myself. There is an error in the user exit code.
    regards,
    Ganesh.

  • Some question on IDOC (Control Record/Data Record/Status Record)

    Dear all,
    I am new in this area, and would like to enquire some question on this topic.
    When I view a IDOC via WE02, each of the IDOC record will consist of Control Record/Data Record/Status Record).
    Questions:
    I notice that the data records consists of many segment (i.e. E1EDK01, etc) which are use to store application data.
    1 - My question is do I have to manually create all these segment and do a mapping to my application field one by one (i.e. that is when I want to create a brand new message type from scratch)?
    2 - If question no. 1 is Yes, how to do it, what are the transaction code to create it? can you show me the step by step.
    3 - I don't have to create the Control record and the status record for my new message type right ? because those field value will automatically pull out from partner profile and system status message, am I correct?
    Thanks.
    Tuff

    Hi Tuff,
    As everything in SAP, with IDOCs too there are
    1) Standard IDOCs
    2) Standard IDOCs(Extending - Enhancement to an IDOC, to accomodate for custom values)
    3) Custom IDOCs
    And every IDOC has,
    Control record - EDIDC Structure - This mostly reflects the partner profile information, along with few more details which are used for IDOC extension, Sequencing etc
    Data Records - EDID4 Structure - These records contain the actual business data of the document in concern. So for ORDERS05 it would contain order details, INVOIC02 - Invoice details so on...
    Status Records - These records capture the status of an IDOC from the time it is received/sent from your system and a corresponding business document is created/changed. So this will have messages like "IDOC sent to the port OK" etc which are status from the communication layer(ALE) to application specific messages like "Sales Order XXX created" or "Invalid Material" etc.
    You would have noticed something called as Process code in the partner profile, this is associated with a FM(or work flow task etc) which has the business logic coded in.
    So in case of an Inbound IDOC, the sending system updates the IDOC - Control and Data records, and sends it to the receiving system. On the receiving system the IDOC's control record is validated against the partner profiles set, if an entry is found then using the process code it finds the associated FM which will decode the data from the IDOC data records as per the IDOC type and then use it to post data into SAP (VIA BDC, Batch Input, BAPI etc).
    And all this while the Status records are being updated accordingly.
    So with the above context will try to answer your questions,
    1 - My question is do I have to manually create all these segment and do a mapping to my application field one by one (i.e. that is when I want to create a brand new message type from scratch)?
    In case of a custom IDOC, yes you will have  to.
    In case of a standard IDOC, you wouldn't have you just have set up the necessary configuration (Partner Profile, Process code etc)
    In case of a standard IDOC extended to accommodate for some custom values(for which there are no fields in standard IDOC - Let us say you have added some new fields on VA01) - In this case you can still use the standard Process code and Standard FM associated with it, SAP provides several Function exits in these FM's which you can leverage to add your custom logic.
    2 - If question no. 1 is Yes, how to do it, what are the transaction code to create it? can you show me the step by step.
    There are several documents available on the net and on SDN detailing step by step approach for all the above three cases,
    just search for step by step guide for IDOCS - sap.
    3 - I don't have to create the Control record and the status record for my new message type right ? because those field value will automatically pull out from partner profile and system status message, am I correct?
    Again it depends, in case of using a standard IDOC you wouldn't have to. But in case you have some customizations/enhancements then you might have to.
    For Ex: updating the control record accordingly for indicating that you have extended the standard IDOC. Or append custom messages to the status record as per the business logic.
    Try out the examples you find on the net and post any specific questions you might have.
    Regards,
    Chen

Maybe you are looking for

  • Schedule Lines and Confirmation on Sales orders.

    Hi all, here is a teaser for you to think about and comment. Ok we have a order line for a material that needs to be ordered into stock so we use the Item Cat TAB, this in turmn gives me a schedule line of CB. How ever as we do not use leadtime for m

  • Can I exchange my MacBook for a new one?

    Ok, so my Dad bought a MacBook for me yesterday, and he wants it now. But he doesn't want mine, he wants a new one. He wants to exchange my one-day old MacBook for a new MacBook that is exactly like mine, cept still in the box. Is this possible? Or w

  • What are the recovery files in the trash

    I like to keep the trach taken out and notice every now and then their has been something put in it that I did not move there.  It is a file called Recovery and has some sub folders in the main one and one of the documents seems to be witten in code.

  • Storing in Aperture Library

    If I import a huge folder of photos into Aperture, and I just use the default "Store Files in Aperture Library", does Aperture copy the photos imported into the library, or does it move them? By using this defaulted selection, the "Move Files" and "C

  • Frozen 4GS

    My iPhone 4GS all of a sudden FROZE.....I tried Turning it off.  It is showing that circle against a black background, but, the circle isn't rotating..It is FROZEN..........