E2E Monitor - ABAP Cloud Development Project

Project Overview

A custom ‘End-2-End’ monitor framework to support business users and the integration team in following up ‘E2E’ messaging within the SAP landscape and to external partners.

Technical B2B messages are being processed by the SAP CPI system and received, mapped and delivered from and towards SAP systems and external partners.

The E2E monitor allows the follow up of the status of such messages by the business users and the technical integration team members.

Business users can find messages using their business related values (like for example order numbers), directly see the delivery status, exchanged payloads and IDOC / ABAP Proxy processing status (and details) in the backend SAP system.

Integration team members can additionally see technical information, received events, logs and history of processing.

Concepts

• Multi-environment solution allowing messages from various integration systems. Currently a 2-tier landscape supporting ‘Development’, ‘Test’ and ‘Acceptance’ on 1 ABAP cloud instance and ‘Production’ on a second.
• Customizing driven solution allowing easy maintenance of new E2E messaging flows.
• A CPI system will send various E2E registration events via a JMS queue towards the ABAP Cloud system during the life cycle of a message - typically a ‘START’, ‘PROCESSING’ and ‘END’ event, including details about the status, payload, etc.
• E2E registration events are queued on ABAP cloud as well and regularly processed based upon priority by various background jobs.
• The registration events are validated for correctness and converted into new E2E messages or added to existing ones. Thus the status of an E2E message changes during the processing life cycle.
• E2E messages become available for display in the E2E monitor and cockpit for business users based upon their authorization for the determined business domain of that message.
• E2E messages become available for follow up by the integration team in the technical monitors as well.
• During processing, configured business key values are extracted from the payloads and made available for searching.
• Once delivered to SAP backend systems, end status processing of IDOC and ABAP PROXY messages are checked via the SAP cloud connector and made visible in the monitor as well.
• Automated reprocessing for messages in Error in CPI via background jobs checks and/or via manual button actions in the UI.
• Regular cleanup of older messages data like payloads, history and registration events in order to keep the HANA database size in check.

Applications

• Business User Cockpit - consolidated business overview of messaging, with click through towards ‘message monitor’
• Business User Message Monitor - detailed overview of messaging and status, including extracted payload business values, End-2-End status details from IDOCs & proxies, payload details
• Technical User Cockpit - consolidated technical overview of messaging, with click through towards ‘message monitor’
• Technical User Message Monitor - detailed overview of messaging and status, including extracted payload business values, End-2-End status details from IDOCs & proxies, payload details, received events, history, etc
• Registration Events Monitor - overview of received messaging registration events
• Business Configuration - maintenance of business and technical configuration
• Application Log - display of custom application logs of all the framework components

Technologies Used

Modern ABAP Cloud development project implementing:

• RAP (RESTful Application Programming) - Modern ABAP framework
• CDS Views - Core Data Services for data modeling
• ABAP OO - Modern ABAP OO design & development including unit test classes
• OData V4 - RESTful API exposure
• SAP Fiori Elements - Auto-generated UI using SAP Fiori floorplans
• SAP Fiori Flexible Programming - custom extensions on standard Fiori applications
• SAP Business Customizing - standard business customizing apps framework supporting 20+ configuration tables
• ABAP Unit - Test-driven development
• ABAP Cloud - Clean core development approach
• ABAP Cloud business roles - authorization of messages based upon custom business domains
• Integration - Providing API’s for integration with SAP CPI and other systems via communication arrangements
• SAP Cloud Connector - Providing access to SAP backend systems (SAP Rise) via SAP Cloud Connector
• SAP Cloud Identity Services - Using SAP CIS (IAS) with Corporate IDP Azure AD for user access validation
• ABAP Cloud Business Roles - ABAP Cloud business roles for authorizations

Used Tools

• Eclipse ABAP Development Toolkit for modern ABAP development
• SAP Business Aplication Studio for Fiori Apps generation and custom extensions
• POSTMAN for API testing
• ABAP Cloud Management for various ABAP cloud administration like communication management, users & roles, etc
• SAP BTP Cloud Management for subaccount management and SAP cloud connector destinations
• SAP Cloud Connector Admin for SAP CC managenment
• SAP IAS Admin for SAP IAS & IPS managenment
• SAP Fiori Theme Editor for building custom Fiori Themes

Development Team

My Role(s)

• Lead Developer (full stack )
• Technical Architect
• Technical Specs
• Visual Designer
• Unit Tester
• Documentation

Members

• Only me