Work order object
The MXWO object structure allows for bidirectional synchronization of exporting work order information and supports status changes.
Purpose
The system first sends out a work order when it reaches the status in the WOSTART control, then on all updates thereafter. The entire work order document is always sent.
The work order interface contains all the information defined by system on the work order, but it does not provide additional information about projects or financial control data, equipment, and locations that is not part of the standard work order. If necessary, you can add the additional information via user fields.
The system treats work order tasks as work orders. Both have similar properties and they are stored in the same table. If a user creates a work order, adds tasks/child work orders to the work order, and then approves the work order, the Inherit Status Changes flag on the work order indicates whether approval of the work order also results in approval of all the tasks/child work orders of that particular work order. The default is Y, so when a work order is approved, any child tasks or work orders that inherit the parent's approval based on this flag are also approved.
The outbound event listener on the work order MBO receives multiple independent events, one for each work order, and they are processed and sent out independently. Therefore, a work order with three tasks and two child work orders results in six independent outbound work orders.
Outbound integration processing
The following table shows the predefined values used in outbound integration processing.
Predefined integration components | Value and description |
---|---|
Object structure definition class functionality | None |
Publish channel | MXWOInterface - Uses processing rules, the complete work order document is sent only for status changes. |
Processing rules | SKIPWO – Skips the sending of the document
if both of the following conditions are true:
|
Integration controls | WOSTART |
Inbound integration processing
The following table shows the preconfigured values used in inbound integration processing.
Predefined integration components | Value and description |
---|---|
Object structure processing class functionality | StatefulMicSetIn - Generic class that supports status changes. |
Publish channel | MXWOInterface |
Processing rules | None |
Integration controls | None |