QDoc Specifications and Standards > QDoc Examples > QAD Enterprise Applications QDoc Response (1.1)
  
QAD Enterprise Applications QDoc Response (1.1)
This is a sample partial QDoc response based on the API method maintainItemMaster. The QDoc message envelope is omitted, as it is described elsewhere. See QDoc Message Envelope.
 
<soapenv:Body>
<ns1:maintainItemMasterResponse xmlns="urn:schemas-qad-com:xml-services" xmlns:ns1="urn:schemas-qad-com:xml-services">
<ns1:result>error</ns1:result>
<ns2:dsSessionContext xmlns:ns2="urn:schemas-qad-com:xml-services:common">
<ns2:ttContext>
<ns2:propertyQualifier>QAD</ns2:propertyQualifier>
<ns2:propertyName>domain</ns2:propertyName>
<ns2:propertyValue>QP</ns2:propertyValue>
</ns2:ttContext>
<ns2:ttContext>
<ns2:propertyQualifier>QAD</ns2:propertyQualifier>
<ns2:propertyName>scopeTransaction</ns2:propertyName>
<ns2:propertyValue>false</ns2:propertyValue>
</ns2:ttContext>
<ns2:ttContext>
<ns2:propertyQualifier>QAD</ns2:propertyQualifier>
<ns2:propertyName>version</ns2:propertyName>
<ns2:propertyValue>eB2_2</ns2:propertyValue>
</ns2:ttContext>
<ns2:ttContext>
<ns2:propertyQualifier>QAD</ns2:propertyQualifier>
<ns2:propertyName>mnemonicsRaw</ns2:propertyName>
<ns2:propertyValue>true</ns2:propertyValue>
</ns2:ttContext>
<ns2:ttContext>
<ns2:propertyQualifier>QAD</ns2:propertyQualifier>
<ns2:propertyName>username</ns2:propertyName>
<ns2:propertyValue />
</ns2:ttContext>
<ns2:ttContext>
<ns2:propertyQualifier>QAD</ns2:propertyQualifier>
<ns2:propertyName>password</ns2:propertyName>
<ns2:propertyValue />
</ns2:ttContext>
</ns2:dsSessionContext>
<ns2:dsExceptions xmlns:ns2="urn:schemas-qad-com:xml-services:common">
<ns2:temp_err_msg>
<ns2:tt_level />
<ns2:tt_msg_context>itemMaster#1(ptPart-02-0001) field(ptDesc1)</ns2:tt_msg_context>
<ns2:tt_msg_data />
<ns2:tt_msg_datetime>2007-08-02T10:43:23+1000</ns2:tt_msg_datetime>
<ns2:tt_msg_desc>Submitted data was truncated</ns2:tt_msg_desc>
<ns2:tt_msg_field />
<ns2:tt_msg_index>0</ns2:tt_msg_index>
<ns2:tt_msg_keys />
<ns2:tt_msg_keys />
<ns2:tt_msg_keys />
<ns2:tt_msg_keys />
<ns2:tt_msg_keys />
<ns2:tt_msg_keys />
<ns2:tt_msg_nbr>MfgProWarningMessage</ns2:tt_msg_nbr>
<ns2:tt_msg_processed>false</ns2:tt_msg_processed>
<ns2:tt_msg_sev>warning</ns2:tt_msg_sev>
</ns2:temp_err_msg>
<ns2:temp_err_msg>
<ns2:tt_level />
<ns2:tt_msg_context>itemMaster#1(ptPart-02-0001)</ns2:tt_msg_context>
<ns2:tt_msg_data />
<ns2:tt_msg_datetime>2007-08-02T10:43:23+1000</ns2:tt_msg_datetime>
<ns2:tt_msg_desc>ERROR: INVALID SITE. Please re-enter.</ns2:tt_msg_desc>
<ns2:tt_msg_field />
<ns2:tt_msg_index>0</ns2:tt_msg_index>
<ns2:tt_msg_keys />
<ns2:tt_msg_keys />
<ns2:tt_msg_keys />
<ns2:tt_msg_keys />
<ns2:tt_msg_keys />
<ns2:tt_msg_keys />
<ns2:tt_msg_nbr>MfgProErrorMessage</ns2:tt_msg_nbr>
<ns2:tt_msg_processed>false</ns2:tt_msg_processed>
<ns2:tt_msg_sev>error</ns2:tt_msg_sev>
</ns2:temp_err_msg>
<ns2:temp_err_msg>
<ns2:tt_level />
<ns2:tt_msg_context>itemMaster#1(ptPart-02-0001) field(ptSite)</ns2:tt_msg_context>
<ns2:tt_msg_data />
<ns2:tt_msg_datetime>2007-08-02T10:43:23+1000</ns2:tt_msg_datetime>
<ns2:tt_msg_desc>Error processing data. See Context for details.</ns2:tt_msg_desc>
<ns2:tt_msg_field />
<ns2:tt_msg_index>0</ns2:tt_msg_index>
<ns2:tt_msg_keys />
<ns2:tt_msg_keys />
<ns2:tt_msg_keys />
<ns2:tt_msg_keys />
<ns2:tt_msg_keys />
<ns2:tt_msg_keys />
<ns2:tt_msg_nbr>EventExceptionex001</ns2:tt_msg_nbr>
<ns2:tt_msg_processed>false</ns2:tt_msg_processed>
<ns2:tt_msg_sev>error</ns2:tt_msg_sev>
</ns2:temp_err_msg>
</ns2:dsExceptions>
<ns1:dsItemMasterResponse>
<ns1:itemMaster>
<ns1:ptPart>02-0001</ns1:ptPart>
</ns1:itemMaster>
</ns1:dsItemMasterResponse>
</ns1:maintainItemMasterResponse>
</soapenv:Body>