Sample Deal Return to Submitter Request and Response in the XML Format
Using the below example, you can return to submit the deal 0786194281.
Sample Deal Return Submitter Request in the XML Format
<C1-DealCreationUpdateIWS>
<actionFlag>UPD</actionFlag>
<dealOperation>
<operationFlag>RETN</operationFlag>
<dealId>0786194281</dealId>
<modelId>9319862860</modelId>
<comments>insufficient sqi</comments>
<rejectReasonCode>R04</rejectReasonCode>
</dealOperation>
</C1-DealCreationUpdateIWS>
Sample Deal Return Submitter Response in the XML Format
<C1-DealCreationUpdateIWS>
<actionFlag>UPD</actionFlag>
<dealResponse>
<message>Deal Returned to Submitter Successfully /message>
</dealResponse>
<dealOperation>
<operationFlag>RETN</operationFlag>
<dealId>0786194281</dealId>
<modelId>9319862860</modelId>
<comments>insufficient sqi</comments>
<rejectReasonCode>R04</rejectReasonCode>
</dealOperation>
<dealDetails>
<dealIdentifier></dealIdentifier>
<dealInformation></dealInformation>
<dealId></dealId>
<modelId></modelId>
<dealEntityType></dealEntityType>
<customerSegment></customerSegment>
<customerTier></customerTier>
<division></division>
<accessGrp></accessGrp>
<dealEntityId></dealEntityId>
<contractedDealFlag>false</contractedDealFlag>
<currency></currency>
<dealTypeCode></dealTypeCode>
<startDate></startDate>
<endDate></endDate>
<simulationTypeFlag></simulationTypeFlag>
<reviewFrequency></reviewFrequency>
<dealDescription></dealDescription>
<longDescription></longDescription>
<dealVersionDescription></dealVersionDescription>
<dealFrequency></dealFrequency>
<skipReferenceFlag>false</skipReferenceFlag>
<priceSelectionDate></priceSelectionDate>
<usagePeriod></usagePeriod>
<includeHierarchyFlag>false</includeHierarchyFlag>
<status></status>
<dealVersionStatus></dealVersionStatus>
<templateFlag>false</templateFlag>
<createdDate></createdDate>
<acceptanceDate></acceptanceDate>
<finalizedDate></finalizedDate>
<effectiveStartDate></effectiveStartDate>
<effectiveEndDate></effectiveEndDate>
<reviewedDate></reviewedDate>
</dealDetails>
<templateReferenceDetails>
<templateDealId></templateDealId>
<templateDealIdentifier></templateDealIdentifier>
<templateModelId></templateModelId>
<copyBasicDetailsFlag>false</copyBasicDetailsFlag>
<copyPricingFlag>false</copyPricingFlag>
<copyUsageFlag>false</copyUsageFlag>
</templateReferenceDetails>
<referenceDetails>
<referenceTypeFlg></referenceTypeFlg>
<refPersonIdentifierType></refPersonIdentifierType>
<refPersonIdentifier></refPersonIdentifier>
<referPersonId></referPersonId>
<refAccountIdentifierType></refAccountIdentifierType>
<refAccountIdentifier></refAccountIdentifier>
<referAccountId></referAccountId>
<referDealIdentifier></referDealIdentifier>
<referenceDealId></referenceDealId>
<referenceModelId></referenceModelId>
<referUsageSw>false</referUsageSw>
<referPriceSw>false</referPriceSw>
<includeChildHierarchy>false</includeChildHierarchy>
<division></division>
</referenceDetails>
</C1-DealCreationUpdateIWS>
Note: We have given the above request and response samples to illustrate
how the tags should be nested 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 tags in the XML format | Deal Update Request and Response - Tags in the XML Format |