Open APIs

• Add a list of characteristics, and then set the characteristics to meet your requirements
• Add the fields explicitly (strongly named and typed)

I am not sure what you mean by proration at the level of the catalog. Typically proration would be done per individual customer invoice by the billing system. Unless you want to specify in the catalog if a particular price is prorated or not (i.e. to define a proration policy).

If you think that any of the above fields could be generally relevant, we could consider adding them to the core Open API model, this would require discussion.

Hope it helps
Jonathan

------------------------------
Jonathan Goldberg
Amdocs Management Limited

Original Message:
Sent: Jul 23, 2019 02:29
From: Anish Parekh
Subject: Queries for Product Offering Price from Product Catalog Management API


I have been referring to the document of TMF620_Product_Catalog_Management_API_REST_Specification_R17.5.0-1 where
I am unable to map some of the properties used in our system to ProductOfferingPrice resource in API:

1. "Revenue Code" at price level which is used by account receivable for accounting when the charges are billed
2. "Recurring Advance/Forward fee" and "Recurring Arrear fee" which is used during billing process to consider rental period in bill
3. "Proration" which is used during billing process to make sure the charges in the bill are prorated properly as per the configuration
4. If the operator wants bill to be generated with minimum of xx amount irrespctive of any product offering subscribed by the customer, then how to map "Minimum Bill Commitment Charge".

------------------------------
Anish Parekh
Sterlite Technologies Limited
------------------------------