Contract component

This contract component allows for the synchronization of purchase contract data.

Table 1. Contract component

Name

Description

Object Structure

MXPC

Interface Table

MXPC_IFACE

Integration Controls
  • GENITEM
  • GENSTORE
  • GENUSR
  • GLCURNCYTYPE
  • LINETYPEXREF
  • OACATXREF
  • OAPCDEFORDERUNIT
  • ORGXREF
  • PCSEND
  • SITEXREF

Outbound Implementation Details

Table 2. Outbound implementation details
Name Description

Publish Channel

MXPC_TOOA12

Java Process

pc\MoutPCProcess

Processing Class

PCOutExt

PL/SQL Stored Procedure

MXE_PC_SP

PL/SQL User Exit Procedure
  • MXE_USR_PCH_SP
  • MXE_USR_PCL_SP
  • MXE_USR_PCT_SP

Oracle Open Interface Tables
  • PO_HEADERS_INTERFACE_ALL
  • PO_LINES_INTERFACE_ALL
  • PO_DISTRIBUTION_INTERFACE_ALL

Filtering

Bypass if either of the following conditions are true:

  • The status of the contract does not equal a status in the PCSEND integration control.
  • The contract is not a blanket contract.

Inbound Implementation Details

Table 3. Inbound implementation details
Name Description

Synchronization Script

None

Oracle Integration Control

PCIN

Triggering Tables
  • PO_ACTION_HISTORY
  • PO_HEADERS_ALL
  • PO_HEADERS_INTERFACE
  • PO_LINES_ALL

PL/SQL Stored Procedure
  • api_pc_sp
  • api_pcx_sp
  • api_polx_sp

PL/SQL User Exit Procedure
  • MOF_USR_PC_SP
  • MOF_USR_PCX_SP
  • MOF_USR_POLX_SP

Enterprise Service

MXPC_FROA12

Concurrent job request

<MAXORA_schema_name>: Maximo Requisitions & Purchase Documents

Processing Class

PCInExt

Java Process

pc\MaxPCProcess

Filtering

Bypass if any of the following conditions are true:

  • The value of the PCIN integration control is 0.
  • The contract is not a blanket purchase agreement, contract purchase agreement, or planned purchase order.
  • The status of the contract is not Approved.
Note: The inbound processing described here applies to the status change sent to the Maximo® Asset Management when the Oracle E‐Business Suite import process fails.