Hi Prakash
From Open API perspective, I suggest you take a look at the Product Order API specification (
TMF622_Product_Ordering_Management). You will see the OrderPrice entity there, which includes the possibility of Price Alterations to be applied to the price during the ordering process. These alterations would then be made permanent in Product Inventory (
TMF637_Product_Inventory_Management), which has ProductPrice and PriceAlteration.
An alteration might be due to a discount, an ad-hoc reduction given by an authorized CSR, or an agreed reduction as part of an enterprise sales process.
But the API model does appear to be is missing a pointer to Agreement, which would be relevant for the enterprise situation (your use case), and I suggest you take this with the team lead for the API
@Ludovic Robert.
From SID perspective, if you look at PartyOrderItem (for example in the figure PO.04 - Party Order Item detailed view), you will see that a Party Order Item has a specific price and an agreement (both of these through the parent Business Interaction Item). But in the final instantiation of the Product, the ProductPriceAlteration does not appear to have a direct relationship to agreement, so maybe there is work to do here.
@Cecile Ludwichowski and
@Michel Besson (SID team leads) may be interested in hearing from you on this.
Hope it helps
------------------------------
Jonathan Goldberg
Amdocs Management Limited
------------------------------
Original Message:
Sent: Aug 13, 2018 05:43
From: Prakash Ranjan
Subject: Product Offering Price for Customer Agreement
posted to Frameworx Community , It can be ignored here (no option to move )
----------------------------------------------------------------------------
Hi ,
This is more data modeling clarification and than API Clarification. (to be moved to Frameworx topic if appropriate)
We were looking at Entity Product Offering Price and looking how following use case for Enterprise business can be supported.
For a Product the standard Price (any type of charge) is X . For Each customer ( Agreement) this can be negotiated to different value Y1 , Y2 and so on.
a) In Data model I don't find link to persist these price values . precisely I think something on this line should be available : Link from Engaged Party Domain :Agreement ABE ->Product Domain : Product Offering Price ( or alteration)
b) how API on top of such data model can be built to maintain life-cycle of such prices separately for each Customer Agreement and consumed in Billing. ( separate from Standard catalog)
Me and my team are looking this valid use case for one of project , would be helpful to receive generic guideline from SID OR if its not available happy to contribute back to SID . We see more value in creating another Entity for Amount which can have different values for agreement and also can support quantity based pricing.
Regards,
Prakash Ranjan
------------------------------
Prakash Ranjan
Infosys Ltd.
------------------------------