Hi Ludovic, all,I think the first step is to define the business scope of "billing item". TMF620 is managing the lifecyle of product catalogue items - i.e. product offerings, product specifications and product offering prices.BR,Dirk
Hi Ludovic, all,I think the first step is to define the business scope of "billing item".TMF620 is managing the lifecyle of product catalogue items - i.e. product offerings, product specifications and product offering prices.BR,Dirk
Yes, in line with other responses, to manage complete commercial product offering into billing system it involves several APIs, creation of customer entity is pre-requisite and then we need to pass through the commercial product eligibility, consider the managing life cycle of resource, consider the managing life cycle of service and other aspects, so it will be a complete product management followed by shopping cart and ordering process.
From TMF Open API table point of view I think we need to use several APIs to solve this requirement. For instance TMF 633 Service Catalog API to manage life cycle of service, TMF634 Resource Catalog Management API to manage life cycle of resource, for product eligibility check TMF679 Product Offering Qualification API, for shopping cart TMF663 Shopping Cart API and for ordering TMF622 Product Ordering API.
We in Ericsson introduced uniform TMF Open API Exposure Layer for digital front ends facilitates the backend functionality through native interfaces, so to manage product offering, we are in discussion to use the approach of extending TMF620 Product Catalog Management API and add the capabilities of TMF633, TMF634 so in this way we can minimize using of several APIs and on top of that we will use TMF679, TMF663, TMF622 to complete the order process.
Customer creation, our model follows to acquire party, party role first and then create customer, further billing account to be created followed by commercial product offering service order APIs which will create contract agreements and then associate the products in our Digital Monetization Platform (DMP). So the set of APIs could be, TMF 632 Party Management API, TMF 629 Customer Management API, TMF 666 Account Management API along with product offering APIs mentioned above in addition to these APIs we also need to use TMF670 Payment Methods API to read type of payments available and chose for customer payment method.
Coming to product/customer change requirement, Ericsson TMF Open API Exposure Layer facilitates the backend functionality through native interfaces in order to manage such operations.