Excerpt: How a Mediation Engine Prepares and Connects Data Among Multiple Applications on the SAP NetWeaver Platform

by Scott Priest, Editorial Director

October 7, 2011

The following is an excerpt from the SAP Professional Journal article, "How a Mediation Engine Prepares and Connects Data Among Multiple Applications on the SAP NetWeaver Platform," by Abdelmorhit El Rhazi, Narendar Akula, and Martin Donovan of SAP Labs Canada. For the full article, SAP Professional Journal subscribers can go here.

Mediation Engine Basics and Requirements

The mediation engine has to handle a hug e volume of data. The provisioning system provides several million records a day and this number is expected to increase on a monthly basis. In general, the mediation engine has to:

  • Read the CDRs
  • Validate the CDR content based on business rules
  • Maintain a mediation database that has tables representing the statuses of services on specific devices
  • Log the exceptions and errors, and send the alerts
  • Allow reprocessing for the corrected records

Figure 1 shows the business process of the mediation engine at a conceptual level. Five systems are involved in this business process: the provisioning system, SAP ERP Central Component (SAP ECC), SAP CC, a reporting system (e.g., SAP NetWeaver Business Warehouse [SAP NetWeaver BW]), and a mediation engine. Let’s look into those in more detail:

  • Provisioning system: This is the source system of the main transactional data — the CDRs. The provisioning system should be designed to provide a set of new records periodically. For example, it produces around 30,000 new CDRs every 15 minutes. It should also be designed to create these new CDRs in a separate table (or file). This table later acts as a queue of CDRs. 
  • SAP ECC: This is the system for master data and configuration data. The customer and service information have to be replicated to the mediation database. The mediation engine uses this data to implement the CDR processing logic.
  • SAP CC: SAP CC provides a rating and charging solution for high-volume processing in service industries. It delivers pricing design capabilities, high-performance rating, and convergent balance management. It provides a Java API that allows the mediation engine to rate the service uses (e.g., number of bi llable hours or days).
  • Reporting system (e.g., SAP NetWeaver BW): This retrieves the transactional and master data for reporting purposes.
  • Mediation engine: This component is the main subject of this article. It represents the role of a mediator among the provisioning system, SAP CC, and the reporting system. Its main role is to prepare and manage the data for SAP CC, the invoicing module, and the reporting system.


An email has been sent to:

More from SAPinsider


Please log in to post a comment.

No comments have been submitted on this article. Be the first to comment!