Hi Sweety
The Open API model is a work in progress. There are various examples of entity refs that are not backed by a managed entity, such as Channel, Constraint, and more.
New APIs are introduced on demand, based on member feedback and availability of resources to do the API design.
I am not currently aware of plans to create an API that manages Constraint.
Regarding your question about alteration, yes a price alteration is just another ProductOfferingPrice - in earlier API releases (some years back) the alteration was an object embedded in the price but the model was refactored for R19.0 to recognize that alterations (such as discounts) are first-class price definitions.
Hope it helps.
------------------------------
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 05, 2020 01:54
From: Sweety Nagpal
Subject: ConstraintRef in ProductOfferingPrice (TMF620_Product_Catalog_Management)
Hello TMF Community,
I see a reference to Constraint resource in the ConstraintRef relationship defined in ProductOfferingPrice.
Do we have Constraint resource type defined in any other TMF specification. I do see few references of this in TMF 662 Entity Catalog Management, with referredType as EligibilityConstraint and AvailabilityConstraint.
Example of it given in ProductOfferingPrice has referredType as 'PriceConstraint'. But I couldn't figure out the TMF spec where the base type 'Constraint' is defined. Also, looking for some examples on 'PriceConstraint' from Pricing modeling perspective.
I have another question on ProductOfferPriceAlteration. My current understanding is that, its not a separate resource/entity, but a variation of ProductOfferingPrice only with priceType as 'discount' possibly. Is this understanding correct?
Thanks.
------------------------------
Sweety Nagpal
Oracle Corporation
------------------------------