Project and task component

This project and task component provides for inbound synchronization of project and task data.

Table 1. Project and task component

Name

Description

Object Structure

MXPROJ

Interface Table

MXPROJ_IFACE

Integration Controls
  • FCSTATUSXREF
  • ORGXREF
  • SITEXREF

Oracle Integration Controls

FCEXTRACTDATE

Oracle Open Interface Table

None

User Action

(in Oracle Project Accounting)
  1. Create or update work breakdown structure and project costs in Oracle Project Accounting.
  2. Run the following programs:
    • PRC: Distribute Labor Cost
    • PRC: Distribute Usage and Miscellaneous Costs
    • PRC: Update Project Summary Amounts
    • PRC: Maximo® Asset Management Financial Update from Oracle

Conditions
  • If a user enters the following optional parameters, the data must match the specified values:
    • Operating Unit ID
    • Project Number
    • Budget Type
    • Start Date

    The current operating unit is the default operating unit ID.

    If you enter a budget type, the process passes all budget amounts for that budget type to Maximo Asset Management.

    If you do not enter a budget type and the project has one budget type, the process passes the budget amount for that type to Maximo Asset Management. If the project has multiple budget types, the process sets the budget amount in Maximo Asset Management to null.

    The process extracts records updated on or after the start date. If you do not enter a start date, the screen displays the date in the Oracle FCEXTRACTDATE control. If you erase that value, the process extracts all projects that meet the project number and operating unit ID criteria.

  • The current project accounting period must be open.
  • The budget associated with the project or task must be base‐lined and valid.
Integration Action The Maximo Asset Management Financial Control Update from Oracle concurrent process extracts updated the work breakdown structure and summarized cost data.
  1. The integration framework calls the MOF_USR_FC_SP user exit procedure.
  2. The integration framework writes the extracted data to the MXPROJ_IFACE table and updates the MXIN_INTER_TRANS queue table.
  3. The IFACETABLECONSUMER cron task polls the MXIN_INTER_TRANS table for new records, retrieves the MXPROJ_IFACE record, and writes it to the inbound JMS queue.
  4. The integration framework calls the following procedures:
    1. User exit procedure preprocessing method (optional)
    2. ERP exit procedure ProjInExt
    3. User exit procedure postprocessing method (optional)
  5. The integration framework applies any processing rules to the object structure.
  6. The adapter builds the FINCTRLID business object from the object structure, and assigns a unique financial control ID to every new project and task.
  7. The integration framework passes the business object to Maximo Asset Management for standard processing.