Sample Deal Commitments Add Request and Response in the JSON Format
Using the below example, you can add commitments for the deal.
Sample Deal Commitments Add Request in the JSON Format
{
"C1-DealPriceAsgnCommitmentBS"
{
"modelId" :"8447774739",
"inquiryModeflag" :"COMT",
"pricingcmtmntdtls"
{
"entityId" :"2797545007",
"entityType" :"PERS",
"commitmentDetails"
{
"priceItemCode" :"DEAL_PRERANA3",
"priceItemDescription" :"DealPrerana3",
"parameterDetails"
{
"parameterCode" :"COUNTRY",
"parameterValue" :"IND",
}
"SQIDetails"
{
"serviceQuantityIdentifier" :"BK-NBR",
"sqiValue" :"12.000000000000000000",
"sqiTypeFlg" :"PRPD",
"actionFlag" :"ADD",
}
}
}
}
}
Note: If you do not want to enter the data in the list attributes
(i.e. attributes where the type is set to list), you should not include
them in the request. Adding empty list attributes will give erroneous
results.
Sample Deal Commitments Add Response in the JSON Format
{
"C1-DealPriceAsgnCommitmentBS"
{
"dealId" :"5593158511",
"modelId" :"8447774739",
"pricingcmtmntdtls"
{
"entityId" :"2797545007",
"entityType" :"PERS",
"commitmentDetails"
{
"priceItemCode" :"DEAL_PRERANA3",
"priceItemDescription" :"DealPrerana3",
"parameterDetails"
{
"parameterCode" :"COUNTRY",
"parameterValue" :"IND",
}
"SQIDetails"
{
"serviceQuantityIdentifier" :"BK-NBR",
"sqiValue" :"12.000000000000000000",
"sqiTypeFlg" :"PRPD",
"actionFlag" :"ADD",
}
}
}
}
}
Note: We have given the above request and response samples to illustrate
how the attribute value pairs should be structured while sending deal
commitments add request from the external system. However, you should
not seamlessly use this request sample in your environment because
the required pre-requisite data may not be available in your environment.
In such case, the system will give erroneous results.
Related Topics
For more information on... | See... |
---|---|
Deal commitments add request and response attribute/value pairs in the JSON format | Deal Commitments Add Request and Response - Attribute/Value Pairs in the JSON Format |