Skip to Content

Purpose

The purpose of the blog is to get the feedback from the fellow SDN members on using this IDOC Error Segment Detail ALV Report tool for supporting the day to day IDOC monitoring activities in the SAP support landscape.


Source code and deployment instructions

Please refer  to the blog IDOC Error Segment Detail ALV Tool Deployment Instructions.

Background

In the era of cloud computing/web services, it may not be very stimulating to blog about IDOC ALV reports but I believe there are many organizations which still rely on that technology. I think there are still many global business teams supporting SAP who didn’t yet catch up with the emerging technologies.

I am sure that the headline of blog will leave many of us mulling over why we need to use this bespoke tool when SAP provides standard idoc error reporting and monitoring transactions. I am going to explain the gap and how the tool fills the gap for the business/technical ALE support teams in the next few sections.

Problem

Imagine you work in a big warehouse where stock keeps changing every second and it is important to determine the stock levels accurately for staying cut-throat in the market.  We had to build a goods movement ALE IDOC MBGMCR03 interface between legacy warehouse system and SAP ERP system that processes high volumes of goods movements to align the stocks and determine the stock levels accurately for running the business efficiently.

However things are not easy as they are said, the legacy systems as you expect are so fragile and hence the interface always had few hundreds of errors that needs to be resolved by the support teams. While the legacy teams are working hard to resolve the interface defects, the business teams have to resolve the IDOC errors manually and align missing stocks between the legacy warehouse and SAP system.

It was quite laborious and time consuming for the support team to drill down each goods movement IDOC and segments to identify the stocks that are misaligned via the transactions WE02 and WE09 and align the stocks manually between the legacy warehouse and SAP ERP system.

Solution

I thought the solution to the problem is ideally to provide the business with an IDOC ALV error report that displays IDOC Number, IDOC Status, IDOC Status Text and IDOC Segment Field and the value in the IDOC Segment Field. It will be more useful for the business users if he has an option to choose the IDOC segment fields and the filter the IDOCS based on the values in the segments.

I had done some research on the internet to check whether there are any blogs or SAP transactions that will do this but unfortunately found none. I found the standard report RSECHK05 but it doesn’t either give you a list of error IDOCS for a message type or an option to the user to select the IDOC segment fields or filter the IDOC content that he is interested to see in the ALV output.

The program RSECHK05 provided me a good starting point to develop a tool that works for any IDOC message type.

IDOC Error Segment Detail ALV Report Selection Screen

If you are a support user who wants to select the goods movement IDOCS between 2032 and 3045 with status error ‘51’ and want to display the IDOC segment fields material, plant, storage location, movement types and filter the IDOCS based on movement types from 201 to 501 then you enter parameters in the selection screen as shown below:


Please  click on the image for clarity

IDOCT.JPG

IDOC Error Segment Detail ALV Report Output

The tool filters the IDOCS and displays the IDOC segments that match the selection criteria as shown below. Please note that the tool filtered the IDOCS that has a segment with movement types between 201 and 501 for the given IDOC number and status range. You can also suppress segment fields with empty values in the ALV output by not clicking the checking box “Also Output Empty Fields’ in the selection screen of the tool.

Please  click on the image for clarity

IDOCO.JPG

Do you think that tool will be useful in your landscape?

To report this post you need to login first.

10 Comments

You must be Logged on to comment or reply to a post.

  1. Jelena Perfiljeva

    Can’t see the images…

    I had to write a similar report long time ago and was actually thinking about resurrecting it recently. Although we don’t get hundreds of errors, the standard transactions are not very user-friendly, so a simple report wuld be much more helpfull. Were you planning to post the code?

    (0) 
      1. Jelena Perfiljeva

        Nope, sorry, still no images. Right click -> show image (IE) doesn’t work either. I’ve seen the same thing in one other blog recently. Not sure if there is some SCN bug…

        (0) 
  2. Thomas Zloch

    I also remember this gap from my times in IDoc development, my first IDoc error report was still using classic interactive reporting (WRITE and HIDE statements…), but the business users could adjust specific values (e.g. customer orders with misspelled article numbers) and then re-post right from the list.

    I bet a lot of these were written all over the world, same thing with the transport request dependency checks.

    Sometimes I’m wondering if SAP is deliberately missing out on some crucial functionality, in order to give third party solutions some chance…

    Please keep the blogs coming, and maybe add the source code for this blog as an attachment.

    Thomas

    (0) 

Leave a Reply