Your customer has different technical services in place. Which of the following processes are supported by SAP Convergent Mediation? Note: There are 3 correct answers to this question.

The correct answer is A. Validate transactions B. Collect transactions D. Aggregate transactions. SAP Convergent Mediation acts as a data pipeline layer between raw technical systems (networks, IoT devices, etc.) and downstream billing processes. Its job is to handle usage data before it reaches rating or billing - specifically by collecting raw transactions (B) from…

Rating and Charging Integration

Question

Options

AValidate transactions
BCollect transactions
CInvoice transactions
DAggregate transactions
ERate transactions

How the community answered

(23 responses)

A
87% (20)
C
9% (2)
E
4% (1)

Explanation

SAP Convergent Mediation acts as a data pipeline layer between raw technical systems (networks, IoT devices, etc.) and downstream billing processes. Its job is to handle usage data before it reaches rating or billing - specifically by collecting raw transactions (B) from disparate sources, validating them for completeness and accuracy (A), and aggregating them into consolidated records (D). These three functions define the mediation layer's scope.

C (Invoice) is wrong because invoicing is a downstream process handled by SAP Convergent Invoicing or a billing engine - mediation never generates customer bills. E (Rate) is wrong because applying pricing/tariffs to usage is the responsibility of SAP Convergent Charging, a separate component in the BRIM stack.

Memory tip: Think of mediation as a "CAV filter" - Collect → Aggregate → Validate. Anything that happens after the data is clean (rating, invoicing) belongs to a different SAP component downstream.

Topics

#Convergent Mediation#transaction collection#transaction validation#transaction aggregation

Community Discussion

No community discussion yet for this question.

Full C_BRSOM_2020 Practice