There was some previous discussion in the community (I don't remember when) about a dedicated notification API for Billing and Charging systems. Nothing came of that, and it seems that the Product Order API is being used, as per Sebastian's answer.
Specifically for Charging, as Claudia pointed out, rating information is needed also at Service level, e.g. to cover the case of monetary allowances that apply to multiple service types (voice, data, message). The OCS needs to rate the events in real time at service level to ensure that the money quota is not exceeded. This has been discussed in the ODA use case team, as it relates to UC009 - perhaps @Elisabeth Andersson can relate to this, as the lead for UC009.
------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------
Original Message:
Sent: Feb 28, 2024 06:16
From: Waseem GREISS
Subject: Intrgration with Billing System
Hello,
Sending PO 622 to the billing system has additional benifit that to send the PO 622, the master core commerce catlaogue is consulted while respecting its commercial rules, so in this case the billing and its catalogue will be a slave and following the main core commerce catalogue that was used in the ordering and delivery.
------------------------------
Waseem GREISS
TO BE VERIFIED
Original Message:
Sent: Feb 27, 2024 15:15
From: Claudia Ivette Falcon Mata
Subject: Intrgration with Billing System
Hello:
I have a doubt If my billing system has is own Product Catalog in order it can generate the invoices, how I need to communicate every service and its prices (usages, recurring or OTC), is below RFSS of each CFS, what are the APIs to be used? Any documentation about this integration?
------------------------------
Claudia Ivette Falcon Mata
Thinkskink
------------------------------