h3. Introduction Once I was asked: “Hey Alex, is there a standard way we can use for searching XI messages in SXMB_MONI given the SAP IDoc number?”. So I looked a little bit around in the XI ABAP stack, without success. That’s a why I decided to enhance the message monitor and make this and other search ways possible. This weblog assumes you are a little bit familiar with ABAP coding, but I will try – as usual – to keep so simple that even without this knowledge one should be able to replicate it! By the way, if you have a look at this forum thread (Creating/Modifying adapter?), you’ll see that the need for ABAP skill in XI it’s still a matter of deep controversy, partially deriving from the stimulating ABAP/Java+ war+, and you could also read a couple of opinions o’ mine, for what it’s worth. I think the job I’m about to describe here it’s kinda proof for my (and others’) position, but this is another story. Let’s get built our XI Super Message Monitor! *When you’ll be finished coding up (approx. time needed 60 minutes), you’ll be able to search XI messages for IDoc number and IDoc type both sender and receiver, and – believe to the unbelievable – even for message content (payload)!! *This first version only searches the Inbound payload, that is before mapping takes place, but I will soon release a new one with the ability to choose it. No standard code will be opened to changes, just a copy it’s made, so don’t worry about it. 🙂 h3. Let’s go First of all your user needs to be registered as a developer in XI ABAP stack: check out SCCR (http://service.sap.com/sscr)for this purpose. Now that you have the power of building ABAP stuff, go to ABAP Developmemt Workbench (trx SE80) and create a new package that will contain all our custom objects. You’ll be asked for a workbench change request (which is basically a container for things we’ll create that you will use when you want to transport everything to consolidation and production box): I suggest you create a new one, give it a meaningful name (such as “XI Super Monitor”) and choose it. It will be automatically proposed afterwards. The big ABAP program behind trx SXMB_MONI is RSXMB_SELECT_MESSAGES, which we need (along with other includes) to duplicate. To do this – always from SE80: we’ll never move from here more or less! – choose +Program +from the upper left combo, type RSXMB_SELECT_MESSAGES in the edit box below it and press enter. Now right click on the program name, choose Copy… and a popup will ask you the name of your new program. Choose a suitable prefix for all the objects, +ZXIMONI+ could be a good choice as it also reflects the package name (a warning will popup: if you don’t like its message choose somthing else like +ZMONI+, otherwise just confirm). In the next popup you’re asked for which components of the program you’d like to copy: flag everything and confirm. In the next popup you’re asked to give new names to include programs: we need to duplicate only 2 of them actually (flagged in the picture below), but if you feel more confortable by working on custom objects only, just copy all of them and give them the same name with the above said prefix (+ZXIMONI_+ or +ZMONI_+).