Hi Bhavik,
If I understand your concern correctly, if 1 Quote with multiple line items is present then 1 single service agreement should be created with all line items. Each product instance can have its own terms and conditions.
For point#2, ideally a new product shouldn't be added to an existing agreement unless it is an associated product or a VAS offering. Addition of a sub-product (like VAS) if added should result in new contract version.
------------------------------
Rupen Dewan
Tata Consultancy Services
------------------------------
Original Message:
Sent: Mar 16, 2025 09:51
From: Bhavik Parekh
Subject: TMF651 Agreement API to create service contract
Hi,
For a B2B customer, we need to create either a MSA or a Service Contract based on the quote. The quote could be multi-site multi-product , for example SD-WAN service spread across multiple sites and Internet with CPE and managed service , professional services. The offers are modeled using modular approach to allow soft bundling. CPQ will need to invoke 651 to create the contract.
- As a principle, does 651 recommend creating one service contract from one quote or multiple service contracts and hence CPQ to create multiple API requests?
- For MACD quotes, in case a new Internet service is added along with modify on an existing SD-WAN service, is the recommendation to create a new service contract for Internet?
Since the API allows creation of one agreement , CPQ has to have the logic to maintain these rules.
------------------------------
Bhavik Parekh
Infosys
------------------------------