Purchase requisitions object

The MXPR object structure allows for bidirectional synchronization of exporting purchase requisition information and supports status changes.

Outbound integration processing

The following table shows the predefined values used in outbound integration processing.

Table 1. Purchase requisitions object predefined components for outbound integration processing
Predefined integration components Value and description
Object structure definition class functionality None
Publish channel MXPRInterface – Uses the processing rules. The complete purchase request document is sent only for status changes.
Processing rRules
  1. SKIPPR - Skips the sending of the document if both of the following conditions are true:
    • The document has not been sent out before.
    • The new status is not listed in the PRSEND control.
  2. SKIPPRUPDATE - Skips the sending of the document when updated but the status is not changed.
  3. SETSTATUSIFACE - Sets the value of the STATUSIFACE field to 0 (false) for all status values except those listed in the PRSEND control.
  4. CHECKSTATUS - Sends only the purchase requisition header data if status changes and the new status is not in the PRSEND control. (In this case, the full document was previously sent and this is sending only the status change notification).
Integration controls PRSEND

Inbound integration processing

The following table shows the preconfigured values used in inbound integration processing.

Table 2. Purchase requisitions object predefined components for inbound integration processing
Predefined integration components Value and description
Object structure processing class functionality MaxPRProcess – Supports status changes. If the current status of the purchase requisition is approved, to support updates the processing class will change the status back to waiting for approval, perform updates and then return the status to what is identified in the XML message.
Publish channel MXPRInterface
Processing rules None
Integration controls None