Sample Deal Return to Submitter Request and Response in the JSON Format

Using the below example, you can return to submit the deal 0786194281.

Sample Deal Return Submitter Request in the JSON Format 

{
    "C1-DealCreationUpdateIWS":
    {
        "actionFlag" :"UPD",
        "dealOperation"
        {
            "operationFlag" :"RETN",
            "dealId" :"0786194281",
            "modelId" :"9319862860",
            "comments" :"insufficient sqi"
            "rejectReasonCode" :"R04",
        }
    }
}

Sample Deal Return Submitter Response in the JSON Format 

{
    "C1-DealCreationUpdateIWS":
    {
        "actionFlag" :"UPD",
        "dealResponse"
        {
        message" :"Deal Returned to Submitter Successfully",
        }
        "dealOperation"
        {
            "operationFlag" :"RETN",
            "dealIdentifier" :"",
            "dealId" :"0786194281",
            "modelId" :"9319862860",
            "dealAcceptEffStartDate" :"",
            "dealAcceptEffEndDate" :"",
            "comments" :"insufficient sqi",
            "rejectReasonCode" :"R04",
        }
        "dealDetails"
        {
            "dealIdentifier" :"",
            "dealInformation" :"",
            "dealId" :"",
            "modelId" :"",
            "dealEntityType" :"",
            "customerSegment" :"",
            "customerTier" :"",
            "division" :"",
            "accessGrp" :"",
            "dealEntityId" :"",
            "contractedDealFlag" :"false",
            "currency" :"",
            "dealTypeCode" :"",
            "startDate" :"",
            "endDate" :"",
            "simulationTypeFlag" :"",
            "reviewFrequency" :"",
            "dealDescription" :"",
            "longDescription" :"",
            "dealVersionDescription" :"",
            "dealFrequency" :"",
            "skipReferenceFlag" :"false",
            "priceSelectionDate" :"",
            "usagePeriod" :"",
            "includeHierarchyFlag" :"false",
            "status" :"",
            "dealVersionStatus" :"",
            "templateFlag" :"false",
            "createdDate" :"",
            "acceptanceDate" :"",
            "finalizedDate" :"",
            "effectiveStartDate" :"",
            "effectiveEndDate" :"",
            "reviewedDate" :"",
        }
        "templateReferenceDetails"
        {
            "templateDealId" :"",
            "templateDealIdentifier" :"",
            "templateModelId" :"",
            "copyBasicDetailsFlag" :"false",
            "copyPricingFlag" :"false",
            "copyUsageFlag" :"false",
        }
        "referenceDetails"
        {
            "referenceTypeFlg" :"",
            "refPersonIdentifierType" :"",
            "refPersonIdentifier" :"",
            "referPersonId" :"",
            "refAccountIdentifierType" :"",
            "refAccountIdentifier" :"",
            "referAccountId" :"",
            "referDealIdentifier" :"",
            "referenceDealId" :"",
            "referenceModelId" :"",
            "referUsageSw" :"false",
            "referPriceSw" :"false",
            "includeChildHierarchy" :"false",
            "division" :"",
        }
    }
}
Note: We have given the above request and response samples to illustrate how the attribute value pairs should be structured while sending a deal return to submitter 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 update request and response attribute/value pairs in the JSON format Deal Update Request and Response - Attribute/Value Pairs in the JSON Format