Open APIs

Hi All.

We are exploring the feasibility of "TMF 679 - Product offering qualification" API to identify products eligible for B2B customers.
Eligibility is based on party and channel. Price of a product offer could differ for each customer based on price negotiations in the agreement.
In this context,  request your feedback to the following questions.

• Does "TMF 679 - Product offering qualification" API a suitable candidate to return eligible product offerings along with prices?
• If yes,  current resource data model suggests prices can be returned for Products. For a provide use case ( action = add),  would it be possible to return negotiated prices without product?

 If this API is not suitable to return negotiated prices for eligible product offers, could you please suggest the suitable one for this requirement ? 

 Thanks in advance for your feedback.

Hi ,

While ProductPrice sub-resource does offer productOfferingPrice within which price might be placed for a specific product, I feel price is something that varies as there could be different pricelist for different CPs based on the markets served in and discounts that could be offered specific to some, and in some cases it gets decided based on various factors. (say, if the Provider is further relying on their Supplier etc.)

And CP contracts with their Suppliers also are something that would have got some agreements on the pricing and maintained internally as part of the product model.

But technically, it does look possible.

Hi All.

We are exploring the feasibility of "TMF 679 - Product offering qualification" API to identify products eligible for B2B customers.
Eligibility is based on party and channel. Price of a product offer could differ for each customer based on price negotiations in the agreement.
In this context,  request your feedback to the following questions.

• Does "TMF 679 - Product offering qualification" API a suitable candidate to return eligible product offerings along with prices?
• If yes,  current resource data model suggests prices can be returned for Products. For a provide use case ( action = add),  would it be possible to return negotiated prices without product?

 If this API is not suitable to return negotiated prices for eligible product offers, could you please suggest the suitable one for this requirement ? 

 Thanks in advance for your feedback.

1. the pricing depends on the channel
2. the pricing depends on discounts from an agreement
3. the discounts are negotiated for a particular deal

Hi ,

While ProductPrice sub-resource does offer productOfferingPrice within which price might be placed for a specific product, I feel price is something that varies as there could be different pricelist for different CPs based on the markets served in and discounts that could be offered specific to some, and in some cases it gets decided based on various factors. (say, if the Provider is further relying on their Supplier etc.)

And CP contracts with their Suppliers also are something that would have got some agreements on the pricing and maintained internally as part of the product model.

But technically, it does look possible.

Hi All.

We are exploring the feasibility of "TMF 679 - Product offering qualification" API to identify products eligible for B2B customers.
Eligibility is based on party and channel. Price of a product offer could differ for each customer based on price negotiations in the agreement.
In this context,  request your feedback to the following questions.

• Does "TMF 679 - Product offering qualification" API a suitable candidate to return eligible product offerings along with prices?
• If yes,  current resource data model suggests prices can be returned for Products. For a provide use case ( action = add),  would it be possible to return negotiated prices without product?

 If this API is not suitable to return negotiated prices for eligible product offers, could you please suggest the suitable one for this requirement ? 

 Thanks in advance for your feedback.

Hi All.

We are exploring the feasibility of "TMF 679 - Product offering qualification" API to identify products eligible for B2B customers.
Eligibility is based on party and channel. Price of a product offer could differ for each customer based on price negotiations in the agreement.
In this context,  request your feedback to the following questions.

• Does "TMF 679 - Product offering qualification" API a suitable candidate to return eligible product offerings along with prices?
• If yes,  current resource data model suggests prices can be returned for Products. For a provide use case ( action = add),  would it be possible to return negotiated prices without product?

 If this API is not suitable to return negotiated prices for eligible product offers, could you please suggest the suitable one for this requirement ? 

 Thanks in advance for your feedback.

Eligibility

Prices

Hi All.

We are exploring the feasibility of "TMF 679 - Product offering qualification" API to identify products eligible for B2B customers.
Eligibility is based on party and channel. Price of a product offer could differ for each customer based on price negotiations in the agreement.
In this context,  request your feedback to the following questions.

• Does "TMF 679 - Product offering qualification" API a suitable candidate to return eligible product offerings along with prices?
• If yes,  current resource data model suggests prices can be returned for Products. For a provide use case ( action = add),  would it be possible to return negotiated prices without product?

 If this API is not suitable to return negotiated prices for eligible product offers, could you please suggest the suitable one for this requirement ? 

 Thanks in advance for your feedback.

Hi Matthieu Hattab,

     you said "TMF651 (agreement where customer negotiated prices are stored) " but I cannot find this in the user guide. Could you please be more specific here? thanks

Eligibility

Prices

Hi All.

We are exploring the feasibility of "TMF 679 - Product offering qualification" API to identify products eligible for B2B customers.
Eligibility is based on party and channel. Price of a product offer could differ for each customer based on price negotiations in the agreement.
In this context,  request your feedback to the following questions.

• Does "TMF 679 - Product offering qualification" API a suitable candidate to return eligible product offerings along with prices?
• If yes,  current resource data model suggests prices can be returned for Products. For a provide use case ( action = add),  would it be possible to return negotiated prices without product?

 If this API is not suitable to return negotiated prices for eligible product offers, could you please suggest the suitable one for this requirement ? 

 Thanks in advance for your feedback.

the resource model is incomplete. under agreementItem, you need to add a sub-resource that connect a POP and the PO for each agreement Item.

what is also missing is product group. We use a productgroup entity so instead of managing 50 product offerings, we only manage a group of product offerings and then specify a discount/price override that applies to all product offerings that are member of this ProductGroup.

Hi Matthieu Hattab,

     you said "TMF651 (agreement where customer negotiated prices are stored) " but I cannot find this in the user guide. Could you please be more specific here? thanks

Eligibility

Prices

Hi All.

We are exploring the feasibility of "TMF 679 - Product offering qualification" API to identify products eligible for B2B customers.
Eligibility is based on party and channel. Price of a product offer could differ for each customer based on price negotiations in the agreement.
In this context,  request your feedback to the following questions.

• Does "TMF 679 - Product offering qualification" API a suitable candidate to return eligible product offerings along with prices?
• If yes,  current resource data model suggests prices can be returned for Products. For a provide use case ( action = add),  would it be possible to return negotiated prices without product?

 If this API is not suitable to return negotiated prices for eligible product offers, could you please suggest the suitable one for this requirement ? 

 Thanks in advance for your feedback.

Thanks Matthieu Hattab

      we should create an enhancement request to TMF responsible of this API? Do you know how? so I can create it if you want.

the resource model is incomplete. under agreementItem, you need to add a sub-resource that connect a POP and the PO for each agreement Item.

what is also missing is product group. We use a productgroup entity so instead of managing 50 product offerings, we only manage a group of product offerings and then specify a discount/price override that applies to all product offerings that are member of this ProductGroup.

Hi Matthieu Hattab,

     you said "TMF651 (agreement where customer negotiated prices are stored) " but I cannot find this in the user guide. Could you please be more specific here? thanks

Eligibility

Prices

Hi All.

We are exploring the feasibility of "TMF 679 - Product offering qualification" API to identify products eligible for B2B customers.
Eligibility is based on party and channel. Price of a product offer could differ for each customer based on price negotiations in the agreement.
In this context,  request your feedback to the following questions.

• Does "TMF 679 - Product offering qualification" API a suitable candidate to return eligible product offerings along with prices?
• If yes,  current resource data model suggests prices can be returned for Products. For a provide use case ( action = add),  would it be possible to return negotiated prices without product?

 If this API is not suitable to return negotiated prices for eligible product offers, could you please suggest the suitable one for this requirement ? 

 Thanks in advance for your feedback.

Many API owners have left their job (the last one to go was Jonathan Goldberg).

I tried many times to contact various API owners, through their employer email, TMF email, this community, linkedin, TMF wiki, some TMF email and most of the time, I got not reply.

------------------------------
Kind regards,

Matthieu Hattab
Lyse Platform

Original Message:
Sent: Oct 07, 2024 11:02
From: Santiago Lorente
Subject: TMF 679 - Product Offering Qualification for eligible product offers with negotiated prices.

Thanks Matthieu Hattab

      we should create an enhancement request to TMF responsible of this API? Do you know how? so I can create it if you want.

------------------------------
Santiago Lorente
Salesforce

Original Message:
Sent: Oct 07, 2024 10:15
From: Matthieu Hattab
Subject: TMF 679 - Product Offering Qualification for eligible product offers with negotiated prices.

the resource model is incomplete. under agreementItem, you need to add a sub-resource that connect a POP and the PO for each agreement Item.

what is also missing is product group. We use a productgroup entity so instead of managing 50 product offerings, we only manage a group of product offerings and then specify a discount/price override that applies to all product offerings that are member of this ProductGroup.

------------------------------
Kind regards,

Matthieu Hattab
Lyse Platform

Original Message:
Sent: Oct 04, 2024 06:53
From: Santiago Lorente
Subject: TMF 679 - Product Offering Qualification for eligible product offers with negotiated prices.

Hi Matthieu Hattab,

     you said "TMF651 (agreement where customer negotiated prices are stored) " but I cannot find this in the user guide. Could you please be more specific here? thanks

------------------------------
Santiago Lorente
Salesforce

Original Message:
Sent: Mar 15, 2022 12:36
From: Matthieu Hattab
Subject: TMF 679 - Product Offering Qualification for eligible product offers with negotiated prices.

Hi Uma,

My 2 cents,

Eligibility

The word "eligibility" is an umbrella term.

I would not use TMF679 for your stated requirement because TMF620 already supports your requirement by using a GET with filter criteria. you can add multiple criteria in the request, e.g.
GET /tmf-api/productCatalogManagement/v4/productOffering?channel=Web
There are some examples in the TMF620 documentation.

It is still possible to use TMF679 to embed TMF620 (illustrated in IG1228) in case you have real qualification rules but that's an implementation choice and it has its caveats. Since you'll need a backend for Frontech or use the process API, you can design your own overall process and use the Api in the sequence you want.

Prices

Another umbrella word!
The product Catalogue Component (which exposes TMF620) has all the prices (one-time, recurring, usage as well as price policies and price algorithms, characters value based prices etc) applicable to a product offering.
But not the contractual prices as these are stored in what I call a framework agreement (a B2B or B2C contract between the customer and the enterprise where all negotiated prices, discount, policies etc are stored).

To get customer-specific prices (as well as any other criteria such as channel, place etc) you need a pricing engine.
You'd call such component via an open API that doesn't exist today, inject the list (of filtered) product offering Ids.
such component would consume (at least) TMF620 (product catalogue), TMF651 (agreement where customer negotiated prices are stored) TMF637 (customer product inventory + terms and conditions), and calculate the relevant price per product offering for this customer, for this channel, etc
Then you can expose via (I'd assume) TMF620, the list of product offerings with applicable prices to your engaged party.

another option is you require the user (employee, customer) to put the product offering in a cart/quote/order first. Not a good customer experience, though.

------------------------------
Matthieu Hattab
Altibox AS

Original Message:
Sent: Mar 14, 2022 10:30
From: uma Maheswar
Subject: TMF 679 - Product Offering Qualification for eligible product offers with negotiated prices.

Hi All.

We are exploring the feasibility of "TMF 679 - Product offering qualification" API to identify products eligible for B2B customers.
Eligibility is based on party and channel. Price of a product offer could differ for each customer based on price negotiations in the agreement.
In this context,  request your feedback to the following questions.

• Does "TMF 679 - Product offering qualification" API a suitable candidate to return eligible product offerings along with prices?
• If yes,  current resource data model suggests prices can be returned for Products. For a provide use case ( action = add),  would it be possible to return negotiated prices without product?

 If this API is not suitable to return negotiated prices for eligible product offers, could you please suggest the suitable one for this requirement ? 

 Thanks in advance for your feedback.

------------------------------
Uma Maheswar
Tata Consultancy Services
------------------------------

Thanks Matthieu Hattab

      we should create an enhancement request to TMF responsible of this API? Do you know how? so I can create it if you want.

the resource model is incomplete. under agreementItem, you need to add a sub-resource that connect a POP and the PO for each agreement Item.

what is also missing is product group. We use a productgroup entity so instead of managing 50 product offerings, we only manage a group of product offerings and then specify a discount/price override that applies to all product offerings that are member of this ProductGroup.

Hi Matthieu Hattab,

     you said "TMF651 (agreement where customer negotiated prices are stored) " but I cannot find this in the user guide. Could you please be more specific here? thanks

Eligibility

Prices

Hi All.

We are exploring the feasibility of "TMF 679 - Product offering qualification" API to identify products eligible for B2B customers.
Eligibility is based on party and channel. Price of a product offer could differ for each customer based on price negotiations in the agreement.
In this context,  request your feedback to the following questions.

• Does "TMF 679 - Product offering qualification" API a suitable candidate to return eligible product offerings along with prices?
• If yes,  current resource data model suggests prices can be returned for Products. For a provide use case ( action = add),  would it be possible to return negotiated prices without product?

 If this API is not suitable to return negotiated prices for eligible product offers, could you please suggest the suitable one for this requirement ? 

 Thanks in advance for your feedback.

hi @Santiago Lorente please create a new feature request in the Open API project under the  AP-3398  TMF679 Product Offering Qualification v5.0.0 Epic and API Governance will review the request.

Thanks Matthieu Hattab

      we should create an enhancement request to TMF responsible of this API? Do you know how? so I can create it if you want.

the resource model is incomplete. under agreementItem, you need to add a sub-resource that connect a POP and the PO for each agreement Item.

what is also missing is product group. We use a productgroup entity so instead of managing 50 product offerings, we only manage a group of product offerings and then specify a discount/price override that applies to all product offerings that are member of this ProductGroup.

Hi Matthieu Hattab,

     you said "TMF651 (agreement where customer negotiated prices are stored) " but I cannot find this in the user guide. Could you please be more specific here? thanks

Eligibility

Prices

Hi All.

We are exploring the feasibility of "TMF 679 - Product offering qualification" API to identify products eligible for B2B customers.
Eligibility is based on party and channel. Price of a product offer could differ for each customer based on price negotiations in the agreement.
In this context,  request your feedback to the following questions.

• Does "TMF 679 - Product offering qualification" API a suitable candidate to return eligible product offerings along with prices?
• If yes,  current resource data model suggests prices can be returned for Products. For a provide use case ( action = add),  would it be possible to return negotiated prices without product?

 If this API is not suitable to return negotiated prices for eligible product offers, could you please suggest the suitable one for this requirement ? 

 Thanks in advance for your feedback.

Hi Heidi Lobecker

     the new feature request I was referring to, is not about TMF679 Product Offering Qualification v5.0.0 Epic but about TMF651.

Is there secuence of steps to access the right place to open the new feature request? BTW I cannot find a place to create the "new feature request". It is an issue that need to be created of type new feature request?

hi @Santiago Lorente please create a new feature request in the Open API project under the  AP-3398  TMF679 Product Offering Qualification v5.0.0 Epic and API Governance will review the request.

Thanks Matthieu Hattab

      we should create an enhancement request to TMF responsible of this API? Do you know how? so I can create it if you want.

the resource model is incomplete. under agreementItem, you need to add a sub-resource that connect a POP and the PO for each agreement Item.

what is also missing is product group. We use a productgroup entity so instead of managing 50 product offerings, we only manage a group of product offerings and then specify a discount/price override that applies to all product offerings that are member of this ProductGroup.

Hi Matthieu Hattab,

     you said "TMF651 (agreement where customer negotiated prices are stored) " but I cannot find this in the user guide. Could you please be more specific here? thanks

Eligibility

Prices

Hi All.

We are exploring the feasibility of "TMF 679 - Product offering qualification" API to identify products eligible for B2B customers.
Eligibility is based on party and channel. Price of a product offer could differ for each customer based on price negotiations in the agreement.
In this context,  request your feedback to the following questions.

• Does "TMF 679 - Product offering qualification" API a suitable candidate to return eligible product offerings along with prices?
• If yes,  current resource data model suggests prices can be returned for Products. For a provide use case ( action = add),  would it be possible to return negotiated prices without product?

 If this API is not suitable to return negotiated prices for eligible product offers, could you please suggest the suitable one for this requirement ? 

 Thanks in advance for your feedback.