Hello,
I'd like to understand in a better way the existing Product Offering Price (POP)
modeling for TMF620 because in latest TMF620 version, it became a separated resource
rather than a Product Offering sub-resource.
Therefore, a POP can exist on its own and, we don't have a direct link points an
association towards a PO or even a PS but, we still have these elements:
- ProductOfferingTerm
- ProductSpecificationCharacteristicValueUse
So, questions are:
1) How do we create a POP element and, fulfill these two particular sub-elements if,
we don't have a field to indicate an association towards a particular PO or PS?
In other words, if this is a unique resource, (that can be created without association
towards PO or PS), how can we populate these two sub-elements?
2) Why don't we have a Characteristic field dedicated to POP element?
(i.e.: being a separated resource, can't we have new price related characteristics
associated to it?)
3) Suppose that we have two POs connected to the same POP and, suppose this POP is configured
initially with recurring charge as U$ 10 per month. How can an user change the PO
associated price details (e.g.: change the recurrency frequency or even the price)
without affecting the other PO?
Thanks and Regards,
------------------------------
Marcos Donato da Silva
Ericsson Inc.
------------------------------