Skip to Content

This blog explain about a tool developed for knowing the status of Inbound IDocs in an integration environment. From this we can view IDocs posted to SAP without using the SAP front end. I have developed this tool in Business Server Pages (BSP) to help middleware team to know about the IDocs status which came from different system. So middleware team can see IDocs status in any web browser which they have posted from different system.

The tool has a user friendly selection screen page where the criteria for searching the IDocs can be given. The user need not have to remember the Basic Message Type or Idoc Type. He can select the values from a list which pops up when he clicks on the button next to the input field. It is similar to the F4 help which we use in SAP.

The initial screen will have the following selection criteria which will help filter down the needs of the user Time created Date created IDoc Status IDoc number Basic type Logical Message type

image

Figure: Selection Screen

Above selection fields have the same functionality which is available in standard SAP like F4 helps values for date, IDoc status and etc. Implementing the F4 help values in selection field is done with Java Script (JS).

image

Figure: F4 Help

The above F4 help is for IDoc status. The user can select the status from the list and the selected value will be used for retrieving all the IDocs with status ’53’, based on which the result will be displayed.

Code for F4 help

image

When user clicks the execute button in the selection page the application will get into the next or result page. Result page will have the list of all the IDocs based on the Message type. This list will consider all the selection parameters which are available on the selection screen.

image

Figure: Result Page

This page will provide the complete information about the IDocs posted to the SAP system. This page has two parts for displaying the Message type tree on the left side and IDocs details (like IDoc number, Segment, Status, Status Group, Partner, Basic Type, Created date and time, Direction, Port, etc.) on the right side.

The result can spill to multiple pages. To navigate to the next page the user has to press the next page button and to navigate to the last page the last page button.

image

Figure: Navigation

Message tree will help user to find exact IDoc details which the user needs. Once user selects particular Message type from message tree, the right side IDoc list will display only the IDocs which are of the message type.

image

Figure: Selection based on Message Type

Enhancement

This tool can be improved by providing a further drill down level where the details regarding the selected IDoc is displayed. The Segment details for the particular IDoc number and the data in the segments.

To report this post you need to login first.

10 Comments

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

  1. One E
    Hello,

    Where is the Tool ? how do we use it or is it just an idea?
    Or somehting you worked on ?

    It would be good if you can help us do the same with a detailed blog.

    (0) 
  2. Krishnakumar Ramamoorthy
    Kannan
    I don’t see any benefit of developing such a tool. Such tool offers no business benefits but rather adds to your development and maintenance overhead.

    Why would an administrator/system monitor would like to have tool built in BSP instead of using standard SAP transactions. If viewing the data in a web browser instead of GUI is the only advantage, then there are easier ways to do this than developing a full fledged tool. For example, I don’t know which release of SAP you are in, but in current releases, you could invoke pretty much any transaction using ITS which is integrated in WAS. So, with a future upgrade, a tool like this looses more value.

    Thanks
    KK

    (0) 
    1. Kannan K Venkatachalam Post author
      Hi KK,

            This tool is not for the system administrator. It is in an environment where there is more than one team working on the project. The middleware (like Webmethods) team need to know the status of the IDocs posted and not the SAP people.
      When we are using ITS, we are exposing SAP to the people who don’t need any access to them. It is equal to giving access to SAP front end instead of give a URL and access to view this.

      (0) 
    2. Kannan K Venkatachalam Post author
      Hi KK,

           This tool is not for the system administrator. It is in an environment where there is more than one team working on the project. The middleware (like Webmethods) team need to know the status of the IDocs posted and not the SAP people.
           When we are using ITS, we are exposing SAP to the people who don’t need any access to them. It is equal to giving access to SAP front end instead of give a URL and access to view this.

      (0) 
      1. Michael Nicholls
        I think what KK is leading to is that starting transaction WE02 etc with webgui requires no development effort, especially with the newer ABAP releases (>=6.40) where ITS is integrated.

        The middleware people still need to be able to logon to the SAP system with a username and password (unless you have an SSO solution inplace, such as the SAP portal), and if they want to get low level details of errors etc, they may end up needing to access other SAP transactions.

        Cheers

        (0) 
    3. PRITI ROY
      hi
      i just saw ur profile on sdn about those idoc/edi

      first befre i start am sorry that i dunno you and am mailing you without your permission anyways

      i live in usa and well am a fresher and just got an interview call so they want a person to have

      a knowledge of

      inbound and outbound idocs to create and send 810,850,856,824,820 etc

      and also need a price catalog exp

      as am an sd consultant so it would be very nice of you if you can help me out with this situation and can send me the detail how to create and how to send each step by step procedure and can help me out how to face the interview on that

      thanks a lott in advance

      priti

      (0) 

Leave a Reply