From the Project Archives
This project showcases earlier work using technologies from a previous era of SAP development. It is preserved here for historical reference and to illustrate the breadth of experience built up over the years.
Project Overview
SAP PI/XI sits at the heart of large SAP landscapes, processing B2B messages between the company and its external partners. When something goes wrong, business users need to investigate — but the standard SAP PI monitoring tools are designed for technical integration teams, not for business staff.
This WebDynpro application gives business users a self-service monitor. Instead of technical interface names and party IDs, users search by business unit, partner name (configured aliases), interface alias, and business identifiers — data values extracted from the message content itself, such as order numbers or invoice references. This makes it possible to find a specific message without knowing anything about SAP PI internals.
Features
- Business-user-friendly search with non-technical criteria
- Business unit scoping — users only see messages relevant to their area
- Partner aliases — PI party names replaced with human-readable names
- Interface aliases — PI interface names replaced with business-friendly labels
- Business identifiers — search by order number, invoice number, etc. (extracted during message processing)
- Period-based search (day, week, month) for normal usage
- Expert mode for technical users: advanced date ranges, archived message search
- Message detail view with acknowledgement status
- Business-friendly message content display using custom XSLT stylesheets per interface
- Raw XML content display for technical investigation
Technical Implementation
The application runs on the SAP PI ABAP stack as a set of WebDynpro components. Configuration tables allow the integration team to:
- Link PI parties and interfaces to business-friendly names
- Define business identifier extraction rules per interface (XSLT-based)
- Map users to business units using standard SAP authorisation
Business identifiers are extracted during message processing by custom ABAP ICF handlers that intercept the message, parse the content, and store the extracted values alongside the PI message ID. At search time, the monitor queries both the PI message log and these extracted identifier values.
Message content is rendered for business users using per-interface XSLT stylesheets, transforming raw XML into a readable tabular view.
Technologies Used
- SAP ABAP WebDynpro
- SAP ABAP OO
- SAP HTTP ICF Handlers
- XSLT Stylesheets (message content rendering)
- SAP PI Runtime APIs
Project Gallery
Technologies Used
All showcased content, designs, and solutions remain the intellectual property of the respective clients. For any copyright inquiries, please contact us.