Purchase contracts object

The MXPC object structure allows for bidirectional synchronization of exporting purchase contract information. This object structure currently only supports the purchase contracts types of blanket and price.

Outbound integration processing

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

Table 1. Purchase contracts object predefined components for outbound integration processing

Predefined integration components	Value and description
Object structure processing class functionality	MoutPCProcess - Skips reservations that are for direct issues.
Publish channel	MXPCInterface - Uses processing rules so that the complete purchase contract document is sent only for a status change.
Processing rules	SKIPPC - 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 PCSEND control. SKIPPCUPDATE -Skips the sending of the document when updated but no status change. SETSTATUSIFACE - Sets the value of the STATUSIFACE field to 0 (false) for all status values except those listed in the PCSEND control. CHECKSTATUS - Sends only the purchase contract header data if status changes and the new status is not in the PCSEND control. (In this case, the full document was previously sent and this is sending only the status change notification).
Integration controls	PCSEND

Inbound integration processing

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

Table 2. Purchase contracts object predefined components for inbound integration processing

Predefined integration components	Value and description
Object structure processing class functionality	MaxPCProcess - Supports status changes. Creates a new revision when the purchase contract already exists and the revision does not. Only supports contract types of blanket and price.
Publish channel	MXPCInterface
Processing rules	None
Integration controls	None