Skip to Content
avatar image
Former Member

IDoc-Adapter Monitoring

Hi,

I know the transaction "IDX5". There are sender-information and receiver-information from the xml-message. In this monitoring the settings are correct but when I look in R/3 for example the sender-information of the message are different in comparison to the sender-information from the transaction "IDX5".

Is there a IDoc-Adapter Monitoring that shows the sender- and receiver-information which arrived to the R/3-System??

Thanks.

Regards.

Stefan

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • Best Answer
    avatar image
    Former Member
    Nov 22, 2006 at 01:11 PM

    You can do a end- end monitoring in Runtime work bench and also can go for Message monitoring -

    http://<host>:<port>/MessagingSystem/monitor/monitor.jsp

    which will provide you with more details.

    Nanda

    Add comment
    10|10000 characters needed characters exceeded

  • Nov 22, 2006 at 01:08 PM

    hi,

    the data for EDI_DC40 segment can be filled by the IDOC adapter

    so you will not see it in the message monitoring I guess

    but why do you need it?

    it can be also harcoded (in receiver agreement)

    Regards,

    michal

    -


    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

    Add comment
    10|10000 characters needed characters exceeded

  • Nov 22, 2006 at 01:13 PM

    in IDX5 for the IDocs of type inbound, select the message and press F5 or double click it, it will take you to the message in sxmb_moni. There in the inbound message -> payload -> main document you can see the control record of the Idoc filled.

    In case of outbound Idocs in IDX5, only in case you filled the control records in mapping, it would be displayed.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Nov 22, 2006 at 01:32 PM

    Is an IDoc actually coming into the R/3 system? If it is, then you can run transaction we02 and open the IDoc that you are interested in. Then expand it's status records to get more information about it

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi,

      For IDocs, to trace Idoc error the transaction you can use is IDX5, SM58 in the XI systema nd SM58, We02 in the R/3 system.

      If you see the outbound Idoc in the IDX5 and not in R/3 that means either the RFC destination is wrong or the Control record data is wrong.

      You can check for error in SM58. If no error then there is something wrong with control record data

      Regards

      Vijaya