Sample Deal Price Assignment Update Request and Response in the JSON Format
Using the below example, you can update the price assignment.
Sample Price Assignment Update Request in the JSON Format
{
"C1-DealPriceAsgnCommitmentBS"
{
"dealIdentifier" :"DEAL_EPER_PRIC_N_COMT_001_V1",
"inquiryModeflag" :"PRIC",
"pricingcmtmntdtls"
{
"entityId" :"2762026417",
"entityType" :"PERS",
"pricingdtls"
{
"priceAsgnId" :"6810091985",
"actionFlag" :"UPD",
"priceItemCode" :"DEAL_MULTIPARAM1",
"priceStatusFlag" :"PRPD",
"priceCurrencyCode" :"USD",
"rateSchedule" :"BK-THRES",
"startDate" :"2022-02-13",
"endDate" :"2023-02-12",
"isEligible" :"true",
"paTypeFlag" :"RGLR",
"printIfZero" :"Y",
"priceasgnchar"
{
"characteristicType" :"DEALID",
"effectiveDate" :"2022-04-05",
"characteristicValue" :"2520094042",
{
"characteristicType" :"C2CLTYPE",
"effectiveDate" :"2022-04-05",
"characteristicValue" :"2520094042",
}
"priceasgnparm"
{
"priceParmCode" :"COUNTRY",
"priceParmVal" :"BHARAT",
}
"txnDailyRatingCrt" :"DNRT",
"ignoreSw" :"N",
"doNotAggSw" :"N",
"scheduleCode" :"MONTHLY",
"pricecompdtls"
{
"priceCompTier"
{
"toVal" :"100",
"fromVal" :"1",
"priceCriteria" :"BK-NBR",
"tieSeqNum" :"10",
"priceparm" :"",
{
"parmCodeType" :"STATE",
"priceParmCode" :"MAHARASHTRA",
}
"priceCompElg"
{
"rhsPriceParmCd" :"ACCESSGRP",
"rhsPriceParmVal" :"System Default",
"lhsPriceParmCd" :"AGEBASED",
"rhsPriceParmTypeFlg" :"PRM",
"isInsufficientFlag" :"RLFS",
"isFalseFlag" :"RLFS",
"isTrueFlag" :"RLTR",
"operator" :"=",
"sequenceNumber" :"0",
}
"priceCompSequenceNo" :"20",
"priceCompDesc" :"No of transaction",
"valueAmt" :"45",
"priceComponentDisplay" :"true",
"rcMapId" :"3999784532",
"tieredFlag" :"THRS",
}
}
}
}
}
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 Price Assignment Update Response in the JSON Format
{
"C1-DealPriceAsgnCommitmentBS"
{
"dealIdentifier" :"RuleBUgFixing22",
"dealId" :"2510739370",
"modelId" :"9490517725",
"pricingcmtmntdtls"
{
"entityId" :"2762026417",
"entityType" :"PERS",
"entityIdentifierValue" :"123-12-1234",
"entityIdentifierType" :"Social security number",
"entityDivision" :"930-California",
"pricingdtls"
{
"priceAsgnId" :"6810091985",
"actionFlag" :"UPD",
"priceItemCode" :"DEAL_MULTIPARAM1",
"priceItemDescription" :"Deal_MultiParam",
"hierarchyDetails" :"RECMAVR,RECMAVR",
"priceStatusFlag" :"PRPD",
"priceCurrencyCode" :"USD",
"rateSchedule" :"BK-THRES",
"startDate" :"2022-02-13",
"endDate" :"2023-02-12",
"isEligible" :"true",
"assignmentLevel" :"CUPI",
"paTypeFlag" :"RGLR",
"printIfZero" :"Y",
"priceasgnchar"
{
"characteristicType" :"DEALID",
"effectiveDate" :"2022-04-05",
"characteristicValue" :"2520094042",
"priceasgnchar"
{
"characteristicType" :"C2CLTYPE",
"effectiveDate" :"2022-04-05",
"characteristicValue" :"2520094042",
}
"priceasgnparm"
{
"priceParmCode" :"COUNTRY",
"priceParmVal" :"BHARAT",
}
"txnDailyRatingCrt" :"DNRT",
"ignoreSw" :"N",
"doNotAggSw" :"N",
"scheduleCode" :"MONTHLY",
"pricecompdtls"
{
"priceCompTier"
{
"priceCompSequenceNo" :"20",
"toVal" :"100",
"fromVal" :"1",
"priceCriteria" :"BK-NBR",
"tieSeqNum" :"10",
"priceparm" :"",
{
"parmCodeType" :"STATE",
"priceParmCode" :"MAHARASHTRA",
}
"priceCompElg"
{
"rhsPriceParmCd" :"ACCESSGRP",
"rhsPriceParmVal" :"System Default",
"lhsPriceParmCd" :"AGEBASED",
"rhsPriceParmTypeFlg" :"PRM",
"isInsufficientFlag" :"RLFS",
"isFalseFlag" :"RLFS",
"isTrueFlag" :"RLTR",
"operator" :"=",
"sequenceNumber" :"0",
}
"priceCompSequenceNo" :"20",
"priceCompId" :"2341932341",
"priceCompDesc" :"No of transaction",
"valueAmt" :"45.000000000000000000",
"priceComponentDisplay" :"true",
"rcMapId" :"3999784532",
"tieredFlag" :"THRS",
}
}
}
}
}
Note: We have given the above request and response samples to illustrate
how the attribute value pairs should be structured while sending a
deal price assignment override 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 price assignment update request and response attribute/value pairs in the JSON format | Deal Price Assignment Update Request and Response - Attribute/Value Pairs in the JSON Format |