Idoc monitoring

[former_member186099]

Dear Experts,

Is there any report or a way to get the list of idocs in error into a file at SAP server level.

Also kindly let us know the best way to monitor the idocs in production system.

Regards,

Prasanna

[former_member376453]

go to transaction BD87. This is the monitoring tool for IDOC

[Former Member]

BD87 is the TCode from where you can get this report, in addition you can also try WE02/WE05.

Regards

Shital

[former_member186099]

Guys, mainly i need a report by executing which i can get a file at SAP server level with the idocs in error. Thanks for the inputs on idocs monitoring transactions..

[former_member376453]

Hi - I am not sure about your exact requirement, you can have a try with RSEIDOCC. This gives Error History.

Kuntal

[former_member186099]

Hi Nandi,

okay let me explain what i am looking for... see when u execute transaction WE02 or WE05, you can see all the idocs depending the selection criteria you have mentioned on next screen.

I want the same idoc list for same selection criteria in a file on my application server folder (AL11) and not on to local system folder.

Is there any standard transaction which does this function?

Cheers.

Prasanna

[Former Member]

I am skeptical about such Utility.

But it would be great to know if any such thing exists

Regards

Shital

[Former Member]

Hi Prasanna,

As far as I know there is NO such report.

Only thing is you got to create one by creating internal tables for the standard tables EDIDC,EDIDS,EDID4 and capture the errored Idocs by their status values.

Use Dataset concept and try to generate a file in the required Application Server folder and log all the errored Idocs.

Note: For Inbound Idocs, you can write this piece of code in the FM of the process code.

Hope the guidline is useful

[uwe_schieferstein]

Hello Prasanna

On SAP releases >= 6.20 you have the standard report RSEIDOCA available. However, this only can trigger SAP workflow in case of IDoc errors (which I do not really like).

Therefore I created a custom report ZRSEIDOCA which has an e-mail interface as well. You could create your own report for your specific requirements.

For more details please refer to thread

Regards

Uwe

[former_member186099]

hi Uwe,

There are two custom declaration which you have made in your custom program, and information is not provided for the same. Those are as below. Could you please share this information, otherwise i cant make use of the code you have shared, Thanks for the inputs which you have given, actually its meeting my exact requirement.

lo_idoc TYPE REF TO zcl_idoc,

lif_idoc TYPE REF TO zif_idoc,

Regards,

Prasanna

[uwe_schieferstein]

Hello Prasanna

The class ZCL_IDOC just collects useful data of the affected IDoc (like the IDoc data itself, links of the IDoc to business objects, etc.).

Below I mention a few standard functions that I have added to this class:

METHOD constructor.


  CREATE OBJECT me->mo_idoc_xml1    " TYPE REF TO cl_idoc_xml1
    EXPORTING
      docnum = id_docnum
    EXCEPTIONS
      error_loading_idoc = 1
      error_building_xml = 2
      others             = 3.
  CASE syst-subrc.
    WHEN '0'.
    WHEN '1'.
      MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
              WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4
              RAISING error_loading_idoc.
    WHEN OTHERS.
      MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
      WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4
      RAISING error_building_xml.
  ENDCASE.

  me->md_docnum   = id_docnum.
  me->md_port     = id_port.
  me->md_released = id_released.
  me->md_external = id_external.  " external representation of outbound
  me->md_include_empty_fields = id_include_empty_fields.
*
  me->ms_control_record = me->mo_idoc_xml1->get_controlrecord( ).



  CALL METHOD me->read_idoc_completely( ).  " calls fm IDOC_READ_COMPLETELY
**  CALL METHOD me->get_external_view_for_outbound( ).
**  CALL METHOD me->process_data_records( ).


  CALL METHOD me->get_next_relations( ).


  call method me->get_next_neighbors( ).  " calls fm SREL_GET_NEXT_NEIGHBORS

ENDMETHOD.

Instead of having multiple functions floating around I just gathered them together into a useful class.

Regards

Uwe

[Former Member]

Hi,

Apart from the suggestions given above you can also use WE09 which is also an IDoc montioring tool but it has a detailed selection criteria.

Thanks

Krithika