Open APIs

Hi,

Can TMF648 Quote Management refer to Frame agreement to get the special prices or terms and then we can go ahead with contracting using TMF651, does in this case we are going to have two references of Agreement Items on Quote Item level? How can we drive the frame agreements auto application with Contracting?

Hi Ameenuddin Mohammed,

APIs are for specific objects. 

648 is used for creating and managing a Quote. 

651 is for creating and managing agreements (contracts)

If during the quotation process that was created and managed via 648 (owned by the Quote object), the customer specific pricing , terms and conditions are to be referred to or fetched, then 651(owned by the Agreement object) should be invoked and the contract  /agreement terms of that customer need to be fetched and updated into the quote.

Regards,

Jag

Hi,

Can TMF648 Quote Management refer to Frame agreement to get the special prices or terms and then we can go ahead with contracting using TMF651, does in this case we are going to have two references of Agreement Items on Quote Item level? How can we drive the frame agreements auto application with Contracting?

Thanks Jag for response!

Here i mean if i have a Quote with three Quote Line Items

• Customer Quote# Quote123
  • Quote Line 1 - Postpaid 50
  • Quote Line 2 - Landline 100
  • Quote Line 3 - Satellite connection 900

and Postpaid 50 i have a frame agreement to give 30% discount discount for a period of 1 year.

• MSA123
  • MSALine#88828282 - Postpaid 50 - 30% Discount from 1st Jan 2024 to 31st Dec 2024

Now my Quote will be like this. 

• Customer Quote# Quote123
  • Quote Line 1 - Postpaid 50 - Linked to MSALine#88828282
  • Quote Line 2 - Landline 100
  • Quote Line 3 - Satellite connection 900

with this quote i will go for contract then a new contract will be generated as below.

• Contract#8937893903
  • AgreementLine1 - Postpaid 50 - Linked to MSALine#88828282
  • AgreementLine2 - Landline 100
  • AgreementLine3 - Satellite connection 900

However the Quote will have two references now like below.

• Customer Quote# Quote123
  • Quote Line 1 - Postpaid 50 - Linked to MSALine#88828282 and AgreementLine1
  • Quote Line 2 - Landline 100 - Linked to AgreementLine2
  • Quote Line 3 - Satellite connection 900  - Linked to AgreementLine3

So i want to understand this scenario presented valid per TMF651 and TMF648 and same would be send to TMF622 for order processing, 

Questions

1. Final Quote send to TMF622 is correct wrt to multiple agreement line linkages ?
2. How OM will process these Quotes, Do they query TMF651 and get the understanding of contract terms and conditions to apply in billing or do we need to integrate the MSA and Contracts first in billing before sending Order?
3. How does the amendment should work here? we take Contract#8937893903 and amend for any changes in future or remove the MSA if the product characteristics are getting changed or MSA is inactivated?

Hi Ameenuddin Mohammed,

APIs are for specific objects. 

648 is used for creating and managing a Quote. 

651 is for creating and managing agreements (contracts)

If during the quotation process that was created and managed via 648 (owned by the Quote object), the customer specific pricing , terms and conditions are to be referred to or fetched, then 651(owned by the Agreement object) should be invoked and the contract  /agreement terms of that customer need to be fetched and updated into the quote.

Regards,

Jag

Hi,

Can TMF648 Quote Management refer to Frame agreement to get the special prices or terms and then we can go ahead with contracting using TMF651, does in this case we are going to have two references of Agreement Items on Quote Item level? How can we drive the frame agreements auto application with Contracting?

Thanks Jag for response!

Here i mean if i have a Quote with three Quote Line Items

• Customer Quote# Quote123
  • Quote Line 1 - Postpaid 50
  • Quote Line 2 - Landline 100
  • Quote Line 3 - Satellite connection 900

and Postpaid 50 i have a frame agreement to give 30% discount discount for a period of 1 year.

• MSA123
  • MSALine#88828282 - Postpaid 50 - 30% Discount from 1st Jan 2024 to 31st Dec 2024

Now my Quote will be like this. 

• Customer Quote# Quote123
  • Quote Line 1 - Postpaid 50 - Linked to MSALine#88828282
  • Quote Line 2 - Landline 100
  • Quote Line 3 - Satellite connection 900

with this quote i will go for contract then a new contract will be generated as below.

• Contract#8937893903
  • AgreementLine1 - Postpaid 50 - Linked to MSALine#88828282
  • AgreementLine2 - Landline 100
  • AgreementLine3 - Satellite connection 900

However the Quote will have two references now like below.

• Customer Quote# Quote123
  • Quote Line 1 - Postpaid 50 - Linked to MSALine#88828282 and AgreementLine1
  • Quote Line 2 - Landline 100 - Linked to AgreementLine2
  • Quote Line 3 - Satellite connection 900  - Linked to AgreementLine3

So i want to understand this scenario presented valid per TMF651 and TMF648 and same would be send to TMF622 for order processing, 

Questions

1. Final Quote send to TMF622 is correct wrt to multiple agreement line linkages ?
2. How OM will process these Quotes, Do they query TMF651 and get the understanding of contract terms and conditions to apply in billing or do we need to integrate the MSA and Contracts first in billing before sending Order?
3. How does the amendment should work here? we take Contract#8937893903 and amend for any changes in future or remove the MSA if the product characteristics are getting changed or MSA is inactivated?

------------------------------
Ameenuddin Mohammed
Saudi Telecom Company

Original Message:
Sent: Aug 19, 2024 02:38
From: Jag Baddukonda
Subject: TMF651 agreement: Semantical Meaning?

Hi Ameenuddin Mohammed,

APIs are for specific objects. 

648 is used for creating and managing a Quote. 

651 is for creating and managing agreements (contracts)

If during the quotation process that was created and managed via 648 (owned by the Quote object), the customer specific pricing , terms and conditions are to be referred to or fetched, then 651(owned by the Agreement object) should be invoked and the contract  /agreement terms of that customer need to be fetched and updated into the quote.

Regards,

Jag

------------------------------
Jag Baddukonda
Deutsche Telekom AG

Original Message:
Sent: Aug 18, 2024 16:10
From: Ameenuddin Mohammed
Subject: TMF651 agreement: Semantical Meaning?

Hi,

Can TMF648 Quote Management refer to Frame agreement to get the special prices or terms and then we can go ahead with contracting using TMF651, does in this case we are going to have two references of Agreement Items on Quote Item level? How can we drive the frame agreements auto application with Contracting?

------------------------------
Ameenuddin Mohammed
Saudi Telecom Company

Original Message:
Sent: Jan 31, 2021 07:20
From: Jonathan Goldberg
Subject: TMF651 agreement: Semantical Meaning?

Hi
Definitely agree with Alexis that the Agreement resource can cover any type of agreement.
There is perhaps a case to be made for producing an API for the specialization of Framework Agreements in the business/corporate world, to capture the specific aspects of negotiation of such agreements and their impact on ordering and assurance processes.
The Open API team is always open (subject to priorities) to community contributions :) .
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: Jan 29, 2021 08:12
From: Alexis de Peufeilhoux
Subject: TMF651 agreement: Semantical Meaning?

Hi Thomas,

Sure. Agreements are not restricted to frame contract and the polymorphic mechanisms can be used to extend the Agreement resource to model further types of business agreements.

Regards

Alexis

------------------------------
Alexis de Peufeilhoux
Deutsche Telekom AG

Original Message:
Sent: Jan 29, 2021 07:54
From: Thomas Dupré
Subject: TMF651 agreement: Semantical Meaning?

Hi,

sporadically, there are some rumours that TMF651 agreement resource should only be used for frame contracts, e.g. as applicable in the large business customer segment.

However, in TMF651 OpenAPI itself, I cannot find such semantical restrictions. Instead, TMF651 indicates that this "agreement" resource can be used in a very broad context: "An agreement represents a contract or arrangement, either written or verbal and sometimes enforceable by law, such as a service level agreement or a customer price agreement."
Using the type / baseType mechanism I would expect that one could derive special agreements (such as frame contracts or other agreements) from this general base resource - whilst not restricting the agreement resource to frame contracts only.

Could you pls shortly comment on this?​​ Thx.

BR Thomas

------------------------------
Thomas Dupré
Deutsche Telekom AG
------------------------------

what's a "frame" agreement?

Could it be the same as "framework agreement"?

For B2C, TMF Product terms are enough to support most needs.

There are cases where - mostly with very large customers - no "standard" product offerings are sold, but for that one customer special solutions are defined. They can be documented as structures of ProductSpecifications and ProductOfferings, even with customer-specific ServiceSpecifications etc, and they are then agreed with the customer in form of a "Frame Contract" that defines which items that customer can order, probably also with adapted prices. The frame contract can also define that the customer can get reduced prices if he orders at least so and so many items, and much more. The Frame Contract may or may not cover the actual purchase, it only defines what the customer can order under the terms defined by the frame contract.

The above statement from 2021 originated in the fact that in a former version of SID there was no association between Agreement and Product, so that Agreement could not be used to buy a single Product; it only had a connection to ProductOffering, therfore it could be used to model a Frame Contract in the above sense. In a later version of SID, the connection to Product was added, so it is now possible to use Agreement also for simple purchases.

what's a "frame" agreement?

Could it be the same as "framework agreement"?

For B2C, TMF Product terms are enough to support most needs.