Inventory issues object
The MXINVISSUE object structure provides for the bidirectional synchronization of inventory (storeroom) issues and returns.
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 | MoutISUProcess - Skips reservations that are for direct issues. |
| Publish Channel | MXINVISSUEInterface - Filters out direct issues from MATUSETRANS (PONUM is not null and ISSUETYPE is ISSUE or RETURN) because they are handled by the receipts (MXRECEIPTInterface) object structure. Filters out variance transactions that are written to MATUSETRANS by the invoice approval process. |
| Processing Rules | None |
| Integration Controls | None |
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 | MaxISUProcess - If the action provided is not an Add action, then an exception is generated. Validates ISSUETYPE to ensure that it is ISSUE, RETURN, or null. If it is any other value, an error is reported. If it is null, the value is set to ISSUE by default. |
| Enterprise Service | MXINVISSUEInterface |
| Processing Rules | None |
| Integration Controls | None |