Maximo Open Forum

 View Only

 Mas 9 SOAP Synchronous Web Service

Jump to  Best Answer
  • Integrations
Stephen Santoro's profile image
Stephen Santoro posted 09-29-2025 10:28

I have created an inbound Synchronous SOAP web Service for Work Orders with BY PASS Queue checked. When I generate the WDL, Schema and View XML the response XML does not contain the key values WONUM & SITIED.

The Work Order is created but there is no WONUM & SITEID in the Response 

See below. When an external SOAPUI App executes the response is:

SOAPUI Response

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
   <soap:Body>
      <SyncABS_VXCISSO2WOOS1Response creationDateTime="2025-09-25T20:19:28+00:00" transLanguage="EN" baseLanguage="EN" messageID="4875117588315687234990" xmlns="http://www.ibm.com/maximo" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
   </soap:Body>
</soap:Envelope>

 My question is why is this happening? The Primary Keys in the DB are WONUM & SITIED

Response XML

<?xml version="1.0" encoding="UTF-8"?>
<max:SyncABS_VXCISSO2WOOS1Response xmlns:max="http://www.ibm.com/maximo" creationDateTime="2008-09-29T01:49:45" baseLanguage="string" transLanguage="string" messageID="string" maximoVersion="string" />

A second question: The generated XML shows the following. Why is the action = Delete? How is this set?

maximoVersion="string">
  <max:ABS_VXCISSO2WOOS1Set>
    <max:WORKORDER action="Delete" relationship="string" deleteForInsert="string" transLanguage="string">

Thanks

Steven Shull's profile image
Steven Shull posted 09-29-2025 15:14  Best Answer

The first one about not seeing the wonum/siteid in the response you can get the primary keys back by enabling the system property mxe.int.keyresponse. 

Regarding the action="Delete", that's something you could send in a message to delete the workorder (or if referenced on a child object, the child object on the workorder). It's not too common to do in integrations and there are a lot of business rules around work orders that would prevent deletion. For example, once a WO has been approved it cannot be deleted.

Stephen Santoro's profile image
Stephen Santoro posted 10-02-2025 09:26

Thanks Steven! That change in properties worked. The interesting thing about this is I created another Synchronous  with Operation = "CREATE" and before I adjusted the mxe.int.keyresponse property, the response was present. After updating the property sync & Create have a response. I knew or did not remember the property but got confused when it worked in one case but not the other. All work now Thanks

As far as the delete in the generated schema I don't allow delete in security. If you have time can you point me in a direction to modify the Response as I would like to add an attribute.. Thanks again

Related Content