Oracle 11i Financial Integer at Ion

Integration Guide
Oracle Financials 11i
Release 4.1.1
Copyright 2002, MRO Software, Inc.
1
This document and its publication do not constitute or create a contract. MRO Software, Inc.,
makes no warranties, express or implied, regarding the accuracy or completeness of this document
or of the related program material.
© 2001 MRO Software, Inc. All rights reserved. Contains confidential and trade secret information
of MRO Software, Inc. Use, transfer, disclosure, or copying without MRO Software, Inc.’s express
written permission is strictly forbidden.
United States Patent No. 6,325,522 B2
Restricted Rights - Use, duplication, and disclosure by the Government is subject to restrictions as
set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause
at DFARS 252.227-7013 (OCT 1998).
Trademarks: MAXIMO®, INTERMAT®, Struxure®, MAXIMO® Enterprise™, MAXIMO®

Extended Enterprise™, MAXIMO® for Integrated Supply™, MAXIMO® Scheduler™, MAXIMO®
Workflow™, MAXIMO® Analyzer™, MAXIMO® Buyer™, MAXIMO® Fleet Manager™,
MAXIMO® Aviation Manager™, MRO Online Commerce ServicesSM, MRO Software Operations
CenterSM, Supplier e-Commerce Adapter™, Illustrated Parts Catalog™, Collego™ Catalog
Manager™, Standard Modifier Dictionary™, and Autocon™ are trademarks of MRO Software,
Inc.
Other products and brand names are trademarks or registered trademarks of their respective
companies; some are noted below.
Third-Party Technology: Certain MRO Software, Inc., products contain technology provided under
license from third parties, as noted below:
MRO Software
Products Third-Party Technology Information
MAXIMO Portions © 2000 Brio Technology, Inc. Brio Report Builder™ provided by Brio
Technology, Inc. Portions © 1996 Centura Software Corporation. Portions © 1995-2000
Actuate Corporation.
All Products Portions © 1995-2000 BroadVision, Inc. BroadVision Business Commerce, BroadVision
One-to-One Enterprise, BroadVision One-to-One Publishing, BroadVision Tools provided
by BroadVision, Inc. Portions © 2000 webMethods, Inc. webMethods B2B Integrator™,
webMethods B2B Integration Server provided by webMethods, Inc.
AutoVue Portions © 1989-1998 Cimmetry Systems, Inc. AutoVue™, AutoVue Professional
provided by Cimmetry Systems, Inc.
MAXIMO Portions © 1998, 1999 NETRONIC Software GmbH.

Workflow
Illustrated Parts Portions © 1999-2001 Snowbound Software™ Corporation. RasterMaser™ provided by
Catalog Snowbound Software Corporation.
Online Portions © TAXWARE International, Inc. TAXWARE® VERAZIP™ Sales/User, STEP
Commerce provided by TAXWARE International, Inc.
Services
CONTENTS
CHAPTER 1: INTRODUCTION....................................................................................9
Overview...................................................................................................................10
Related Documentation.............................................................................................11
Integration Overview ................................................................................................13
CHAPTER 2: IMPLEMENTING THE SOFTWARE INTEGRATION...................17
Reconfiguring MAXIMO Table Columns ................................................................18
Modifying Integration API Control Codes............................................................19
Oracle Financials Control Codes ..........................................................................35
Customizing Integration Procedures .........................................................................47
CHAPTER 3: USING THE INTEGRATION MODULE ...........................................49
Inventory Ownership.................................................................................................50
Determining Inventory Ownership .......................................................................50
Viewing Inventory Ownership..............................................................................51
Changing Inventory Ownership ............................................................................51
Inventory Balance Transactions................................................................................52
APICTLs for Inventory Balance Transactions......................................................53
Importing and Exporting Inventory Balance Data ................................................56
Summary of Item Balance Transactions Using Default Settings of the APIs .......56
Recommended API Settings for Exchanging Item Balances ................................58
Purchasing Transactions ...........................................................................................61
Purchase Order Ownership ...................................................................................61
APICTLs for PO Ownership ......................................................................................62
Viewing PO Ownership..............................................................................................63
Changing PO Ownership............................................................................................63
3
Contents
Purchasing Configurations....................................................................................64
Comparison of APICTLs for the Configurations........................................................65
Configuration 1 ..........................................................................................................67
APICTL Control Values for Configuration 1 .............................................................68
Configuration 2 ..........................................................................................................69
Configuration 3 ..........................................................................................................71
Configuration 4 ..........................................................................................................73
Configuration 5 ..........................................................................................................75
Other Configurations..................................................................................................77
User Exit Procedures.................................................................................................78
External Procedures ..............................................................................................79
API Integration Points, Default Processes, and the UTRANSTYPE Control.......79
API Processing of Shared Information......................................................................80
Purchasing Data Transfers ....................................................................................80
Transferring Purchase Requisitions from MAXIMO to Oracle Financials ................80
Import errors...............................................................................................................82
Transferring Purchase Requisition Change of Status from Oracle Financials to
MAXIMO...................................................................................................................83
Transferring Purchase Orders from Oracle Financials to MAXIMO .........................84
Transferring Purchase Order Change of Status from Oracle Financials to MAXIMO85
Transferring Receipts from Oracle Financials to MAXIMO......................................86
Transferring Purchase Orders from MAXIMO to Oracle Financials..........................87
Transferring Receipts from MAXIMO to Oracle Financials......................................90
Inventory Ownership for Material Receipts Sent to Oracle Financials ......................91
Impact of Inventory Ownership on Material Receipts Imported into MAXIMO .......92
Loaded Costs for Material Receipts that are Imported into MAXIMO ......................92
Loaded Costs in MAXIMO ........................................................................................92
Loaded Cost in the APIs.............................................................................................93
Item Data Exchanges ............................................................................................94
Transferring Item Data from MAXIMO to Oracle Financials....................................94
Transferring Item Data from Oracle Financials to MAXIMO....................................96
Transferring Material Reservations/ Demands to Oracle Financials ..........................98
Inventory Ownership for Material Reservations Sent to Your System.......................99
Transferring Material Issues from Oracle Financials to MAXIMO .........................100
Inventory Ownership for Material Issues Sent to MAXIMO ...................................100
Transferring Item Balance Data from Oracle Financials to MAXIMO ....................101
4
Contents
Transferring Item Confirmations to MAXIMO........................................................103

Inventory Ownership with Item Confirmations Sent to MAXIMO..........................103
Vendors...............................................................................................................104
Transferring Vendor Data from Oracle Financials to MAXIMO .............................105
Accounts Payable Data Transfers .......................................................................106
Transferring Invoices from MAXIMO to Oracle Financials ....................................106
Transferring Invoices from Oracle Financials to MAXIMO ....................................107
General Ledger Data Exchanges.........................................................................109
Transferring Journal Entries from MAXIMO to Oracle Financials..........................110
Transferring Entries from INVTRANS to Oracle Financials ...................................112
Transferring Journal Entries from MATRECTRANS to Oracle Financials .............112
Transferring Journal Entries from MATUSETRANS to Oracle Financials .............114
Transferring Entries from SERVRECTRANS to Oracle Financials ........................115
Transferring Entries from LABTRANS to Oracle Financials ..................................116
Transferring Entries from TOOLTRANS to Oracle Financials................................117
Transferring Entries from INVOICETRANS to Oracle Financials ..........................118
Transferring Chart of Accounts Data from Oracle Financials to MAXIMO ............119
GL Synchronization Transformations ......................................................................120
Transferring Accounts from MAXIMO to Oracle Financials...................................120
Transferring Accounts from Oracle Financials to MAXIMO...................................121
MAXIMO Support for the Transformation of the GL Accounts..............................121
Cases Requiring Transformation of GL Accounts....................................................121
MAXIMO Interface Tables.....................................................................................125
Data Columns......................................................................................................125
User Columns......................................................................................................126
Batch Control Columns.......................................................................................126
The User Control Column...................................................................................126
Interface Control Columns..................................................................................127
Status Columns ...................................................................................................128
Error Messages........................................................................................................129
Purchasing Interface Tables ....................................................................................130
MOUT_PR_INTERFACE Table ........................................................................130
MAX_PRX_INTERFACE Table........................................................................142
MAX_PO_INTERFACE Table ..........................................................................152
MAX_POX_INTERFACE Table .......................................................................161
MAX_RCV_INTERFACE Table .......................................................................163
MOUT_PO_INTERFACE Table........................................................................175
MOUT_RCV_INTERFACE Table.....................................................................186
5
Contents
Item Interface Tables ..............................................................................................198

MAX_ITM_INTERFACE ..................................................................................198
MOUT_RSV_INTERFACE Table .....................................................................211
Inventory Confirmation Tables ...............................................................................220
MAX_ICF_INTERFACE Table .........................................................................220
Issues Data Tables...................................................................................................229
MAX_ISU_INTERFACE Table.........................................................................229
Vendor Interface Tables..........................................................................................235
MAX_COM_INTERFACE ................................................................................235
Accounts Payable Interface Tables .........................................................................242
MOUT_AP_INTERFACE..................................................................................242
MAX_AP_INTERFACE ....................................................................................252
General Ledger Interface Tables .............................................................................262
MOUT_GL_INTERFACE Table........................................................................262
MAX_COA_INTERFACE Table.......................................................................319
MAX_COAX_INTERFACE Table ....................................................................323
General Ledger Code Combinations from Oracle Financials .................................328
General Ledger Components from Oracle Financials .............................................331
Invoices from Oracle Financials .............................................................................335
Items from Oracle Financials ..................................................................................342
Issues from Oracle Financials .................................................................................349
Balances from Oracle Financials ............................................................................353
Reservations from MAXIMO .................................................................................366
Purchase Orders from Oracle Financials.................................................................375
Receipts from Oracle Financials .............................................................................382
Vendors from Oracle Financials .............................................................................386
Journal Transactions from MAXIMO.....................................................................390
Items from MAXIMO.............................................................................................395
Purchase Orders from MAXIMO with the CAI PO Interface Tables .....................404
Purchase Orders from MAXIMO to the Oracle Standard Purchasing Documents
Open Interface Tables .............................................................................................427
Receipt Transfer from MAXIMO to Oracle Financials ..........................................443
Purchase Requisition from MAXIMO ....................................................................450
Invoices from MAXIMO ........................................................................................460
6
Contents
CHAPTER 4: SYSTEM MAINTENANCE ................................................................465

Configuring the Database........................................................................................465
Customizing the Integration APIS ..........................................................................466
Using UTRANSTYPE Values with User Exit Procedures .................................467
Using Extra Tables in User Exits ........................................................................467
Using Batch Routines..............................................................................................468
The Batch Routine Process .................................................................................472
Maintaining the Batch Files ................................................................................473
Maintaining the Interface Tables ............................................................................474
Purging the Interface Tables ...............................................................................474
Running Reports .................................................................................................475
Troubleshooting ......................................................................................................476
General Troubleshooting Procedures ..................................................................476
MAXIMO Interface Log.....................................................................................477
Checking Status Columns ...................................................................................478
Debugging Errors Using MAXIMO Interface Flow ...........................................478
Error Messages....................................................................................................480
Transferring Purchase Requisition Changes into MAXIMO....................................480
Transferring Purchase Orders into MAXIMO..........................................................480
Transferring Purchase Order Changes into MAXIMO.............................................481
Transferring Receipts into MAXIMO ......................................................................481
Transferring Invoices into MAXIMO .................................................................482
Oracle Errors.......................................................................................................485
7
Contents
8
CHAPTER 1
INTRODUCTION
This manual provides information about the MAXIMO financial application

integration module. Use this integration module to exchange information
between Oracle Financials and MAXIMO.
This manual is intended for the following audience:
• System administrators
• Implementation team members
• MAXIMO users
MAXIMO and Oracle Financials users include people having many types of jobs,
including:
• Project manager
• Maintenance manager
• Accountant
• Industrial engineer
• Inventory manager
• Purchasing manager
• MIS specialist
9
Chapter 1
Overview
The information in this manual is presented in four sections, described below:
Chapter Description
1. Introduction Provides an overview of the MAXIMO

financial application integration
module.
2. Implementing the Software Integration Describes the system changes you need
to make in order to integrate MAXIMO
and Oracle Financials.
3. Using the Integration Module Explains how to use the integration

APIs in an integrated system, describes
the interface tables, and provides the
mappings between MAXIMO database
tables and the integration module
interface tables.
4. System Maintenance Describes how to maintain the interface

tables, run batch routines, and
troubleshoot the system. Details error
messages and error resolutions.
There is a separate installation manual that provides information on your system
requirements, preparatory procedures for a successful installation, and
installation instructions.
10
Introduction
Related Documentation
For a list of verification procedures to follow after you install the integration
module, see the file GENVERIF.DOC in the APIDOC directory.
For more information about using MAXIMO, refer to the following sources:
• The MAXIMO User’s Manual describes how to use the MAXIMO
maintenance system features. It provides a thorough overview of MAXIMO
features and relationships among modules.
• The online Help system provided with MAXIMO provides conceptual and
task-oriented information on using MAXIMO.
• The MAXIMO System Administrator’s Guide provides instructions on system
administrator functions such as managing the database and customizing the
system and the utilities that come with MAXIMO. It also gives instructions
for setting up general ledger accounting features within MAXIMO.
• The MAXIMO Finance Manager’s Guide describes both the GL accounts
used by MAXIMO as well as the processes involved in creating and using the
GL account fields. Processes and transactions are described from both a user
perspective and a database management perspective.
You will also need the relevant manuals for Oracle Financials.
By using the MAXIMO Oracle Financials integration module, you can create an
integrated system in which MAXIMO interfaces with Oracle Financials. Through
its application programming interfaces (APIs), this integration module facilitates
access to MAXIMO data and application functions. Therefore, the APIs improve
the efficiency of specific business functions performed by MAXIMO customers.
The standard MAXIMO APIs are transparent to users and designed for
flexibility. You can mix and match the documented integration points within the
limitations of Oracle Financials. However, please note that the standard
11
Chapter 1
MAXIMO APIs provide only the documented integration points, and not
unlimited integration points.
The integration module tracks events that cause data to be transferred between
systems, as well as the location of the data in each system. The integration
module manages the MAXIMO internal functions to ensure that transfers occur
smoothly and consistently.
Although a copy of the information is stored in both applications, you maintain it
in only one application. By eliminating duplicate functions and processes, the
integration module ensures users maximum efficiency.
The integration module processes are modeled after those in MAXIMO. Thus,
the module is synchronized with MAXIMO when MAXIMO is updated.
12
Introduction
Integration Overview
As shown below, there are five components in an integration between MAXIMO
and Oracle Financials.
• The MAXIMO application
• The MAXIMO APIs, a set of stored Oracle PL/SQL procedures which extract
data from MAXIMO and import data into MAXIMO from the related
financial system
• The integration portion, which passes and validates the data between the two
APIs
• Oracle Financials APIs, which extract data from the financial system and
import data into the financial system from MAXIMO
• Oracle Financials
MAXIMO MAXIMO Integration Oracle Oracle

API Applications Applications
API
The Oracle Financials integration API is an extension of the standard MAXIMO

API and is developed and supported jointly by MRO Software, Inc. and Oracle.
MRO Software is responsible for the MAXIMO API and integration components
while Oracle is responsible for support and changes to the external system API
Installation and upgrade of the Oracle Financials API will still require integration
work. Business practices will vary from site to site as will the complexity of the
integration. The APIs will, however, reduce the integration development life
cycle for the customer as well as expedite future MAXIMO upgrades.
Using the MAXIMO integration APIs, you can both coordinate processes and
exchange information between MAXIMO and Oracle Financials. Furthermore,
the APIs work “behind the scenes,” so that MAXIMO and Oracle Financials
work together seamlessly. The integration module keeps track of events that will
13
Chapter 1
cause data to be transferred between systems and where data is located in the
systems. It also manages the MAXIMO internal functions to ensure that transfers
occur smoothly and consistently.
The MAXIMO integration APIs transfer inbound and outbound data between
applications. The integration APIs move data from the source application to the
destination application by way of interface tables, which store the data and any
related processing information. MAXIMO provides the interface tables.
• As a destination application, MAXIMO receives data from the source
application, Oracle Financials, for further processing, storage, or both. The
data usually has completed its processing in Oracle Financials before being
passed to the destination.
• As a source application, MAXIMO sends processed data to the destination
application, Oracle Financials, for processing, storage, or both.
For example, you can coordinate the purchasing process between MAXIMO and
Oracle Financials. You can send an approved purchase requisition from
MAXIMO to Oracle Financials so that a purchase order can be generated in
Oracle Financials. The purchase requisition information is placed in an interface
table. An integration API sends the information from the interface table to Oracle
Financials. The purchase order is generated in Oracle Financials. When the
purchase order is approved, the information can be sent to MAXIMO via an
interface table. When Oracle Financials receives the item, it generates a receipt
record. The receipt information, for the item originally requested in MAXIMO,
can be sent back to MAXIMO using another interface table.
14
Introduction
The following diagram illustrates this exchange of purchasing information.
MAXIMO Oracle Financials
Approved MOUT_PR_INTERFACE PO_REQUISITIONS_INTERFACE

Requisition Table Table
MOUT_PO_INTERFACE Approved Purchase Order Oracle

MAXIMO
Table Financials
MOUT_RCV_INTERFACE Receipt
Table
For more information about transferring data between applications and the
interface tables, see Chapter 3, “Using the Integration Module.”
MAXIMO and Oracle Financials can share several types of information. In the
integrated system, you can:
• transfer purchase requisitions from MAXIMO to Oracle Financials
• transfer purchase orders from Oracle Financials to MAXIMO
• transfer receipts from Oracle Financials to MAXIMO
• transfer invoices between applications
• share item data
• share vendor data
• transfer MAXIMO general ledger journal entries to Oracle Financials
• update the MAXIMO Chart of Accounts application with data from Oracle
Financials
For details about how to use the integration module, see Chapter 3, “Using the
Integration Module.”
15
Chapter 1
16
CHAPTER 2
IMPLEMENTING THE SOFTWARE

INTEGRATION
This section describes the system changes necessary to integrate

MAXIMO and Oracle Financials. You should make these changes after
installing the integration APIs.
The integration team should include individuals that have an
understanding of the technical and functional capabilities of both
MAXIMO and Oracle Financials. At least one member of the team
should be familiar with your organization’s business processes,
especially those that affect multiple departments. The system or database
administrator should also be part of the team.
Implementing the integration of MAXIMO and Oracle Financials
consists of evaluating your integration requirements in each of several
areas shared between the products, and choosing the implementation
method that best suits your needs. Your choices affect how the two
applications will share certain information.
You must decide how to match the following information shared by the
two applications:
• financial calendars
• currencies
• tax rates
• units of measure
• user names
You do not have to match these settings if you are going to maintain the
data separately in the two applications. In this case, you will manually
add the information to each application.
17
Chapter 2
If the two applications will share data, you must decide how to make the
settings compatible. For example, if Oracle Financials defines currency
in terms of the British pound and MAXIMO is configured to use the U.S.
dollar, you must decide which currency definition to use and make it the
consistent definition for both applications.
The integration does not include a method for matching settings.
Reconfiguring MAXIMO Table Columns

You must reconfigure MAXIMO columns to be compatible with Oracle
Financials. You may reconfigure the columns either before or after data
transactions have occurred, depending on whether you process
transactions in real time or in batches.
If you will be using the software integration in real-time (data
transactions will occur in real-time, not in batch routines), table and
column mapping must be synchronized first. Otherwise, the transactions
will fail. If you will be using the software integration via batch routines,
and you do not reconfigure the table columns, then you can later use an
external process to transform the data to a compatible format.
Compare the MAXIMO tables to the tables in Oracle Financials.
Any columns containing data shared between MAXIMO and the
financial application must be compatible with respect to these
attributes: column length, data type, nulls setting.
You can look in the oramaxcf.sql file to see the fields that the adapter
configures during installation. For example, the following statement in
that file sets the COMPANY column in the COMPANIES record to a
length of 46 characters.
start &&md.maxconf COMPANIES COMPANY 46
If the installation has decreased the length of any of your MAXIMO
table columns, use the MAXIMO Database Configuration application to
reconfigure the length. Do this before selecting Configure Changes from
the Actions option of the Database Configuration Application.
18
Implementing the Software Integration
Modifying Integration API Control Codes

You can modify the integration API control codes and the Oracle
Financials control codes to configure the integration module for your
system needs. The control code settings regulate data transfers between
MAXIMO and Oracle Financials.
Most of the API control codes switch the API on or off. For example, if
you do not want to synchronize item data between MAXIMO and Oracle
Financials, set the ITMIN or ITMOUT controls to N. If the control code
for ITMIN is Y and if a new item is inserted into Oracle Financials, the
item data is entered into MAXIMO. To stop that transfer, set the code to
N. To stop the transfer of item data from MAXIMO to Oracle Financials,
set the control code for ITMOUT to N.
You can further modify some integration APIs with the API controls. For
example, you can do more than turn invoice transfers on or off with
APIN and/or APOUT. If invoice data is being transferred in, the
following control codes will further qualify the incoming data:
APINADJINV Adjusts inventory cost if there is variance.

APINADJDIRECT Adjusts direct cost if there is variance.
APINUPDTVND Updates vendor’s unit price.
APINAUTORCV Allows invoicing of services not yet received by
automatically recording receipt during invoicing.
Not all API control codes are on/off switches. Use the GLDELIMITER
control code to specify the general ledger account segment delimiter used
in Oracle Financials. The delimiter is a hyphen (-) by default. Use
PROLDSTAT and PRNEWSTAT control codes to specify the status of
purchase requisitions pending transfers. PROLDSTAT indicates the
status that a purchase requisition must be in prior to changing status.
PRNEWSTAT indicates the purchase requisition status that triggers the
data transfer, providing that the prior status is PROLDSTAT.
Refer to the following table for a complete list of external API control
codes that are installed with Oracle Financials API. As discussed at the
beginning of Chapter 3, there are two purchasing Configurations:
19
Chapter 2
Configuration 1 and Configuration 2. For some controls, the control

value in Configuration 2 must be the opposite of the default control value
in Configuration 1. For example, for APICTL, the value for APIN is Y
under Configuration 1, but N under Configuration 2. Thus, the cell in the
Control Value column reads “Y for Configuration 1, N for Configuration
2.”
The default values column shows the values as they are when the
external APIs are installed. The middle column in the following table
indicates whether the APICTL for that row has any impact on Oracle
Financials. For example, COMOUT is set to ‘N’, since Oracle Financials
will not accept updates for companies/vendors from MAXIMO.
API Control Applicable for Control Description

Control the Oracle Value
Group Financials API? Default
APICTL COA Y Y Receive chart of

accounts and
account segment
data from Oracle
Financials to
MAXIMO.
APICTL GLDELIMITER Y - GL account
segment delimiter
for GL data coming
from an Oracle
Financials. This GL
delimiter is used as
a placeholder
identifier for GL
processing (and
replaced with the
GL delimiter
specified in
MAXIMO if the
delimiter is to be
stored in the
database).
20

APICTL COMIN Y Y Receive companies

data from Oracle
Financials to
MAXIMO.
APICTL COMOUT N Y Send companies
data from
MAXIMO to
Oracle Financials.
APICTL ITMCATIN Y Y Receive item
catalog data from
Oracle Financials to
MAXIMO.
APICTL ITMCATOUT Y Y Send item catalog
data from
MAXIMO to
Oracle Financials.
Global switch.
APICTL ITMNOSTORE Y Y Send item without
storeroom
information from
MAXIMO to
Oracle Financials.
APICTL STOCKITEM Y Y Send stocked item
from MAXIMO to
Oracle Financials.
APICTL NONSTOCKITEM Y Y Send non-stocked
item from
MAXIMO to
Oracle Financials.
APICTL SPITEM Y Y Send special order
item from
MAXIMO to
Oracle Financials.
21
Chapter 2

APICTL ITMSTOREIN Y Y Receive item store

data from Oracle
Financials to
MAXIMO.
APICTL ITMSTOREOUT Y Y Send item store
data from
MAXIMO to
Oracle Financials.
APICTL ITMMFGIN N Y Receive item
manufacturer data
from Oracle
Financials to
MAXIMO.
APICTL ITMMFGOUT N Y Send item
manufacturer data
from MAXIMO to
Oracle Financials.
APICTL ITMVNDIN Y Y Receive item
vendor data from
MAXIMO.
APICTL ITMVNDOUT N Y Send item vendor
data from
MAXIMO to
Oracle Financials.
APICTL ITMBALXFROUT N N When Y, send item
balance data from
MAXIMO to
Oracle Financials
for MAXIMO-
owned inventory
only.
22

APICTL ITMBALXFRIN Y N When Y, receive

item balance data
from Oracle
Financials to
MAXIMO for
externally-owned
inventory only.
APICTL EXTRCVOUT Y N When Y, allow
receipts for
externally-owned
inventory to be sent
to Oracle
Financials.
APICTL EXTISSOUT N N When Y, allow
issues for
externally-owned
inventory to be sent
to Oracle
Financials.
APICTL MAXRCVIN Y N When Y, allow
receipts for
MAXIMO-owned
inventory to be
received into
MAXIMO.
APICTL MAXISSIN Y N When Y, allow
Issues for
MAXIMO-owned
inventory to be
received into
MAXIMO.
23
Chapter 2

APICTL RCVIBUPD Y Y When N, bypass the

inventory balance
and cost updates
associated with a
receipt transaction
for externally
owned inventory
coming into
MAXIMO. When
Y, all updates
occur.
APICTL ISSIBUPD Y Y When N, bypass the
inventory balance
and cost updates
associated with an
issue transaction for
externally owned
inventory coming
into
MAXIMO.When
Y, all updates
occur.
APICTL ISUIN Y Y Receive material
issue data from
MAXIMO.
APICTL JESERVREC Y Y Send service receipt
journal data from
MAXIMO to
Oracle Financials.
APICTL JEMATUSE Y Y Send item usage
journal data from
MAXIMO to
Oracle Financials.
24

APICTL JELABOR Y Y Send labor journal

data from
MAXIMO to
Oracle Financials.
APICTL JEMATREC Y Y Send item receipt
journal data from
MAXIMO to
Oracle Financials
for a receipt against
a MAXIMO-owned
PO.
APICTL EJEMATREC Y Y Send item receipt
journal data from
MAXIMO to
Oracle Financials
an Oracle-owned
PO.
APICTL JETOOL Y Y Send tool journal
data from
MAXIMO to
Oracle Financials.
APICTL JEINVOICE Y Y Send invoice
journal data from
MAXIMO to
Oracle Financials.
APICTL JEINVENTORY Y Y Send inventory
journal data from
MAXIMO to
Oracle Financials.
25
Chapter 2

APICTL APIN Y Y for Receive invoice

Config 1 data from Oracle
N for Financials to
MAXIMO (invoice
Config 2
details with
variance pre-
calculated. Global
switch
APICTL APINADJINV Y Y Adjust inventory
cost (when
required) for
invoice data
received by
MAXIMO from
Oracle Financials.
APICTL APINADJDIRECT Y Y Adjust direct cost
(when required) for
invoice data
received by
MAXIMO from
Oracle Financials.
APICTL APINCLOSEPO N Y Close PO on full
invoice (when
required) for
invoice data
received by
MAXIMO from
Oracle Financials.
APICTL APINUPDTVND Y Y Update vendor last
cost (when
required) for
invoice data
received by
MAXIMO from
Oracle Financials.
26

APICTL APINAUTORCV N Y Auto receipt on

invoice (when
required) for
invoice data
received by
MAXIMO from
Oracle Financials.
Auto receipt is for
service receipt only
(as in the
MAXIMO
application).
APICTL APOUT Y N for Send invoice data
Config 1 from MAXIMO to
Y for Oracle Financials.
Config 2
APICTL APDETAILS Y Y Send invoice detail
data from
MAXIMO to
Oracle Financials.
When set to N, only
invoice summary
information will be
sent.
APICTL APSTART Y APPR If invoice status is
equal or greater
than control value
and not previously
sent, invoice will be
sent to Oracle
Financials.
APICTL PROUT Y Y for Send PR data from
Config 1 MAXIMO to
N for Oracle Financials.
Config 2 Global switch.
27
Chapter 2

APICTL PRINT Y N Send internal PR

data from
MAXIMO to
Oracle Financials.
APICTL PRSERV Y N Send service PR
data from
MAXIMO to
Oracle Financials.
APICTL PRXIN Y Y for Receive PR status
Config 1 updates from
N for Oracle Financials to
Config 2 MAXIMO.
APICTL POIN Y Y for Receive PO data
Config 1 from Oracle
N for Financials to
Config 2 MAXIMO.
APICTL POOUT Y N Send PO data from
MAXIMO to
Oracle Financials.
APICTL RCVIN Y Y for Receive receipt
Config 1 data from Oracle
N for Financials to
MAXIMO.
Config 2
APICTL RCVINADJINV N (Y) Regardless of
control value,
adjust inventory
cost (when
required) for receipt
data received by
MAXIMO, from
Oracle Financials.
28

APICTL RCVINADJDIREC N (Y) Regardless of

T control value,
adjust direct cost
(when required) for
receipt data
received by
MAXIMO, from
Oracle Financials.
APICTL RCVINCLOSEPO Y (Y) Regardless of
control value, close
PO on full receipt
(when required) for
receipt data
received by
MAXIMO, from
Oracle Financials.
APICTL RCVINUPDTVND N (Y) Regardless of
control value,
update vendor last
cost (when
required) for receipt
data received by
MAXIMO, from
Oracle Financials.
APICTL RCVOUT Y Y for Send receipt data
Config 1 from MAXIMO to
N for Oracle Financials.
Config 2
APICTL PRGENITEM Y N Replace MAXIMO
item number with
“MAXITEM,” the
MAXIMO generic
value for
requisitioned items.
29
Chapter 2

APICTL RCVSVCAPPR Y Y Update Service

Receipts on a PO to
be approved at the
time of receipt.
APICTL PAYONRCPT Y N When set to N, this
prevents the Pay On
Receipt update
from occurring
(regardless of the
setting on the PO).
To allow payment
on receipt to occur,
set the control to Y.
APICTL WOOUT N N When Y, send work
order data to Oracle
Financials.
APICTL WOSTART N APPR When work order
status is equal to or
beyond the status in
the control value,
work order data is
sent from
MAXIMO to
Oracle Financials.
APICTL WOXIN N N When Y, receive
work order status
updates from
MAXIMO.
30

APICTL WOUNAPPACTUA N Y When N, a change

LS to the work order
status in MAXIMO
to Unapprove
(WAPPR) will not
be allowed when
work order actuals
exists.
APICTL RSVOUT Y N When Y, send
material
reservations for
externally owned
inventory to Oracle
Financials from
MAXIMO.
APICTL SRVIN N N When Y, receive
work order service
receipts from
MAXIMO.
APICTL LPYOUT N N When Y, send work
order labor pay data
to Oracle Financials
from MAXIMO.
APICTL ICFIN Y N When Y, receive
reservation
confirmation/updat
e from Oracle
Financials to
MAXIMO.
31
Chapter 2

APICTL RSVONLIN Y N When Y, accept

issues only when
they have an
associated
reservation. When
N, accept issues
regardless of an
association to a
reservation.
APICTL LOCATIONOUT N N When Y, send
locations from
MAXIMO to
Oracle Financials.
APICTL LOCATIONIN N N When Y, receive
locations from
MAXIMO.
APICTL EJESERVREC Y Y Send service receipt
journal data from
MAXIMO to
Oracle Financials
an Oracle-owned
PO.
APICTL POSTART Y APPR If PO status is equal
or greater than
control value, the
PO will be sent to
Oracle Financials.
APICTL PRSTART Y APPR If PR status is equal
or greater than
control value and
not previously sent,
the PR will be sent
to Oracle
Financials.
32

APICTL ERCVOUT Y Y When Y, send

receipts from
MAXIMO to
Oracle for a receipt
against an Oracle-
owned PO.
APICTL ISUOUT N Y Send Material
Issues from
MAXIMO to
Oracle Financials.
APICTL WOIN N N When Y, accept
work orders from
MAXIMO.
APICTL LPYIN N Y When Y, accept
Labor Pay
transactions from
Oracle Financials
into MAXIMO.
APICTL PRIN N N When Y, accept
Purchase
Requisitions from
Oracle Financials
into MAXIMO.
APICTL GLUPDATE N Y When Y, allow
online changes to
the WO GL account
after the WO has
been sent to the
external system
(WOOUT = Y).
APICTL SYSTEMOUT N N When Y, send
systems from
MAXIMO to
Oracle Financials.
33
Chapter 2

APICTL SYSTEMIN N N When Y, receive

systems from
MAXIMO.
APICTL APITRANS N N When Y, insert to
MAX_API_TRAN
S for outbound
interface
transactions defined
in the API.
APICTL RCVINGL Y Y Journal Receipt
APICTL RCVINGLINV Y Y Journal Inventory
Adjustment
APICTL RCVINGLDIRECT Y Y Journal Direct
Adjustment
APICTL APINGL Y N
APICTL APINVARGL Y N
APICTL APINGLINV Y Y
APICTL APINGLDIRECT Y N
APICTL JESPLITDBCR Y Y
API Control Applicable to Control Description

Control Oracle Value
Group Projects? Default
APICTL FCIN Y Y Financial
Control to
MAXIMO
APICTL PROJECTOUT Y Y Projects from
MAXIMO
APICTL TASKOUT Y Y Tasks from
MAXIMO
34
APICTL ACTUALSOUT Y Y Project Actuals

from MAXIMO
APICTL LCIN Y Y Labor to
MAXIMO
APICTL BUDGETOUT Y Y Budget from
MAXIMO
Use MAXIMO Application Setup to change the control code values.

Choose APICTL from the value list to access the control codes. For more
information about using the MAXIMO Application Setup application,
refer to the MAXIMO System Administrator’s Guide.
For more information about how the data is transferred, see Chapter 3,
“Using the Integration Module.”
Oracle Financials Control Codes

The Oracle Financials control codes modify the integration APIs
between MAXIMO and Oracle Financials. Many of the Oracle
Financials control codes either further control the behavior of the APIs or
provide defaults specific to Oracle Financials that are not available in
MAXIMO. Some Oracle Financials control codes may turn the APIs on
or off based upon qualifiers that are unique to Oracle Financials.
The MAXIMO Chart of Accounts application supports only one Chart of
Accounts ID from Oracle Financials. The APIs filter code combination
values coming from Oracle Financials to MAXIMO according to the
value set in the value list OFCTL.GLCOAID. However, MAXIMO
accepts code combinations for multiple sets of books, if each set of
books has the same Chart of Accounts ID.
In contrast, data passing from MAXIMO to Oracle Financials may need
a unique ID for each set of books, but MAXIMO only supports one set of
books. Thus, by default, for journal transactions to the GL_INTERFACE
table, and for invoices transferred to the tables
AP_EXPENSE_REPORT_HEADERS and
AP_EXPENSE_REPORT_LINES, the Set of Books ID is the value in
OFCTL.GLSOBID. However, you can write your own user exits in
OGLX.SP and OAPX.SP to support multiple sets of books. Replace the
35
Chapter 2
value automatically written to Set of Books ID with your derived Set of

Books ID.
The controls GLSOBID, GLCOAID and GLRCVECUMBID require
Oracle Financials internal identifiers (keys). These keys are not visible to
you on the application screens. Ask your database administrator or
Oracle consultant to obtain these keys by querying the tables directly.
GLSOBID and GLCOAID values can be obtained from the
ORG_ORGANIZATION_DEFINITIONS table. You must obtain your
organization code, then view this table for the SET_OF_BOOKS_ID and
CHART_OF_ACCOUNTS_ID column values.
The MAXIMO Purchasing applications support a second base currency
that can be used to track transactions in a second currency, allowing for
Euro currency reporting. Likewise, Oracle Financials uses Multiple
Reporting Currencies (MRC) functionality to provide similar support.
The main difference between the two is that MAXIMO has a limit of one
additional currency, whereas Oracle allows for multiple reporting
currencies for a single base (primary) currency.
The APIs support this multi-currency functionality in the following
manner. All transactions sent to Oracle Financials will have their
reporting currency calculated upon entry with the conversion rates stored
in Oracle Financials. Transactions sent to MAXIMO will retrieve the
Oracle Financials conversion rates which will then be used to calculate
the MAXIMO second currency amount. Therefore, all transactions sent
between the two systems will use the conversion rates that are held in
Oracle Financials.
The GLSOBID2 control needs to be set to the code for the reporting set
of books in Oracle. The currency for that reporting set of books should
match the MAXIMO second currency code.
The GLRCVECUMBID value can be obtained for the
GL_ENCUMBRANCE_TYPES table. You can only have one
encumbrance type in MAXIMO, i.e., on a receipt against a purchase
order. The likely encumbrance value will be the one used for purchasing
in Oracle Financials. You need to set up the encumbrance value only if
you plan to do receiving in MAXIMO and not update Oracle Financials
with the receipts. (Refer to Purchasing Configuration 2 in Chapter 4).
36
Note that currently there is no integration API for transferring receipts

from MAXIMO to Oracle Financials. Oracle is planning to provide this
functionality at a later date. However, if this functionality is implemented
through a consultant or a third party, then the encumbrance type ID is
required.
The GENUSR and GENSTORE flags provide mechanisms to substitute
the MAXIMO user and storeroom information. When GENUSR is
enabled, the API replaces the MAXIMO user with the user MAXIMO.
This provides a way to not add all MAXIMO users in Oracle Financials.
Since you can enforce security within MAXIMO, if you have only a
generic user defined in Oracle Financials with appropriate
responsibilities, it is easier to manage users across systems. If this is not
acceptable to you, and Oracle Financials must validate the user, then the
GENUSR flag should be set to N. GENSTORE is similar to GENUSR,
as it allows storerooms being transferred to be generalized. When
GENSTORE is set to Y; it acts as a filter for data coming into
MAXIMO. Only information for one organization, i.e., the master
organization defined in ITMORG, is allowed to pass through.
For data going out of MAXIMO, the storeroom code is replaced with the
value in ITMORG. As well, for PO receipt transactions, the subinventory
code is populated with the value in ITMSUB, instead of the Bin Number
from MAXIMO. Thus, when GENSTORE is set to Y, storeroom and
organizational/bin and subinventory information need not be in sync in
both systems. When GENSTORE is set to N, the MAXIMO storeroom
code is transferred to the Oracle Financials organization code for all item
data being transferred from MAXIMO.
For data coming from Oracle Financials, the organization code is
validated against the MAXIMO storeroom location. If the code exists,
the item is inserted/updated for that storeroom location. When Genstore
is N, the bin and subinventory codes are transferred to each other for PO
receipt transactions going in both directions.
NOTE: The Current APIs support full storeroom synchronization, i.e.,
synchronization of balances, issues and reservations for Oracle
owned inventory. This is not supported for MAXIMO-owned
inventory. Item synchronization for MAXIMO-owned inventory
primarily supports purchasing.
37
Chapter 2
Vendor APIs between MAXIMO and Oracle Financials implement

additional logic to compensate for differences between the two systems.
The Vendor code in MAXIMO is a concatenated value consisting of
VENDOR_SEGMENT1 and VENDOR_SITE_CODE. Similarly,
purchase order line numbers in MAXIMO are also made on concatenated
values. In Oracle Financials, any release PO has a different identifier
than the originating blanket PO. Thus, for release purchase orders sent
from Oracle Financials to MAXIMO, the identifier (PONUM in
MAXIMO) consists of the blanket PO number concatenated with the
release number. Refer to the mapping for further details.
Refer to the following table for a list of the integration API control
codes, their descriptions, and default settings.
Oracle Control Control Value Description

Financials
Control Group
OFCTL GLSOBID 0 Set of Books ID
OFCTL GLSOBID2 0 Reporting Set of
Books ID
OFCTL GLCOAID 0 Chart of
Accounts ID
OFCTL GLCURNCY USD Default currency
code
OFCTL GLCURNCYTYPE User Currency
conversion type
OFCTL GLRCVECUMBID 0 Receipt
encumbrance
type ID. This is
the internal ID for
the encumbrance
type code used
for purchase
order
encumbrance
38

Financials
Control Group
OFCTL PRSTOCK INVENTOR Oracle Financials
Y destination type
code for
inventory items
OFCTL PRDIRECT EXPENSE Oracle Financials
destination type
code for direct
issue items
OFCTL PRSERVLINETYPE SERVICE Requisition line
type for services.
All other
MAXIMO PR
lines use the
default
requisition line
type as defined in
Oracle Financials
OFCTL ITEMCATID X Purchasing
category for non-
service PR lines
without a valid
item ID (e.g.,
materials and SP
items)
OFCTL SERVCATID X Purchasing
category for
service PR line
type
OFCTL USEPRNUM N Use PRNUM for
requisition
number.
OFCTL ITMORG XXX Inventory master
organization
39
Chapter 2

Financials
Control Group
OFCTL ITMINV Y Inventory item
flag used when a
new item is added
in MAXIMO and
transferred to
Oracle Financials
OFCTL ITMINT Y Internal order
enable flag used
when a new item
is added in
MAXIMO and
transferred to
Oracle Financials
OFCTL GENSTORE N Mask MAXIMO
storeroom
OFCTL JEITMREC MAXIMO1 Journal category
for item receipts
(commitment/
encumbrance)
OFCTL JEITMRECINVC MAXIMO1 Journal category
for invoice
adjustment/auto
for receipts
OFCTL JEITMRECRET MAXIMO1 Journal category
for item receipt
returns
OFCTL JEITMRECTRANS MAXIMO1 Journal category
for receipts
(transfers)
OFCTL JEITMISS MAXIMO1 Journal category
for item usage
OFCTL JEITMISSINVC MAXIMO1 Journal category
for invoice
adjustment for
usage
40

Financials
Control Group
OFCTL JEITMISSRET MAXIMO1 Journal category
for item usage
returns
OFCTL JEITMISSTRANS MAXIMO1 Journal category
for item usage
(transfers)
OFCTL JEITMAVGADJ MAXIMO1 Journal category
for inventory
average cost
adjustments
OFCTL JEITMCAPADJ MAXIMO1 Journal category
for inventory
capital cost
adjustments
OFCTL JEITMBALADJ MAXIMO1 Journal category
for inventory
current balance
adjustments
OFCTL JEITMSTDADJ MAXIMO1 Journal category
for inventory
standard cost
adjustments
OFCTL JEITMRECADJ MAXIMO1 Journal category
for inventory
standard receipt
adjustments
OFCTL JELABWORK MAXIMO1 Journal category
for labor (work)
reporting
OFCTL JELABNWORK MAXIMO1 Journal category
for labor (non-
work) reporting
41
Chapter 2

Financials
Control Group
OFCTL JESERVREC MAXIMO1 Journal category
for service
receipts
(commitment/
encumbrance)
OFCTL JEINVCCVAR MAXIMO1 Journal category
for invoice
currency
variances
OFCTL JEINVCIVAR MAXIMO1 Journal category
for invoice
variances
OFCTL JEINVCTAX1 MAXIMO1 Journal category
for invoice TAX
1 type
transactions
for invoice TAX
2 type
transactions
for invoice TAX
3 type
transactions
for invoice TAX
4 type
transactions
for invoice TAX
5 type
transactions
OFCTL JEINVOICE MAXIMO1 Journal category
for invoice
payables
42

Financials
Control Group
OFCTL JETOOL MAXIMO1 Journal category
for tool usage
OFCTL POLINETYPE Goods PO line type for
non-service PO
lines
OFCTL OPERUNITID 0 Default Operating
Unit ID
OFCTL SUBLOCDEL - Delimiter to
separate the
Oracle
Subinventory
code and Locator
ID when
populating the
MAXIMO BIN
OFCTL PAYTERMSID 0 Default Payment
Terms used for
sending POs to
Oracle
OFCTL GLVALIDATE Y Validate the GL
accounts prior to
sending to Oracle
OFCTL DMDSRCTYPE MAXIMO1 Demand Source
Type used for
Reservations
being sent to
Oracle
OFCTL APLINETYPE MAXIMO1 Invoice line type
OFCTL GENUSR N Mask MAXIMO
user
OFCTL ITMSUB STORES MAXIMO Inv
default subinv
43
Chapter 2

Projects
Control Group
OFCTL EXPENDTOOL Tools Expenditure Type
for Tools
OFCTL EXPENDITEM Materials Expenditure Type
for Materials
OFCTL EXPENDLABOR MAX-Labor-L Expenditure Type
for Labor
OFCTL RESLEVELTOOL 1 Resource Level
for Tools
OFCTL RESLEVELITEM 1 Resource Level
for Materials
OFCTL RESLEVELLABOR 1 Resource Level
for Labor
OFCTL PAORG 204 Project
Organization
OFCTL PAUSER MAXIMO Project
Accounting User
OFCTL PAVERSIONID 1 Project Acct
Version
OFCTL PAPRODCODE MAXIMO Project Acct
Product Code
OFCTL CHARGEORG Consulting- Charging
West Organization
OFCTL NLRORG Consulting- NLR Owning
West Organization
OFCTL BUDGETTYPE Approved Cost Default Budget
Budget Type Code
OFCTL SRCUSE MAXIMO-U Trans Source for
Usages
OFCTL SRCEXP MAXIMO-E Trans Source for
Expenses
OFCTL LABORCOSTED N Labor Codes sent
as Costed
44

Projects
Control Group
OFCTL CRAFTCOSTED N Craft Codes sent
as Costed
OFCTL SRCTIM-NC MAXIMO-T Trans Src - Non-
Costed
OFCTL SRCTIM-C MAXIMO-T- Trans Src -
C Costed
OFCTL RESLIST MAXIMO 'Default Resource
List
OFCTL JETOOLAPI N Send Non-Project
Tool JE to Oracle
GL
OFCTL JETOOLAPIPR N Send Project Tool
JE to Oracle GL
OFCTL JELABORAPI N Send Non-Project
Labor JE to
Oracle GL
OFCTL JELABORAPIPR N Send Project
Labor JE to
Oracle GL
OFCTL JEMATUSEAPI N Send Non-Project
Matl Usage JE to
Oracle GL
OFCTL JEMATUSEAPIPR N Send Project Matl
Usage JE to
Oracle GL
OFCTL JEMATRECAPI N Send Non-Project
Receipt to Oracle
GL
OFCTL JEMATRECAPIPR N Send Project
Receipt to Oracle
GL
OFCTL PROJPAY No Use Projects Pay
Rate
45
Chapter 2

Projects
Control Group
OFCTL CONVHRS 2080 Annual Converted
to Hourly Rate
OFCTL PROJAPPR APPROVED Proj Status for
WO Appr
OFCTL PROJCOMP PENDING_C Proj Status for
LOSE WO COMP
OFCTL PROJCLOS CLOSED Proj Status for
WO CLOSE
OFCTL PROJPR No Send Projects
Data on PR
OFCTL PROJPO No Send Projects
Data on PO
OFCTL PROJAP No Send Projects
Data on AP
OFCTL WOHEIRVAL No Validate FC/WO
Heirarchies
Use the MAXIMO Application Setup application to change the control

code values. Choose OFCTL from the value list to access the control
codes. For more information about using the MAXIMO Application
Setup application, refer to the MAXIMO System Administrator’s Guide.
For more information about how the data is transferred, see Chapter 3,
“Using the Integration Module.”
46
Customizing Integration Procedures

The MAXIMO integration module transfers data between MAXIMO and
the MAXIMO interface tables. However, you must customize the
external integration procedures to transfer the data between the
MAXIMO interface tables and Oracle Financials.
MRO Software provides interface tables as integration points for all
outbound transfers. These interface tables insulate your data from the
internal processing in MAXIMO. They also assure you of a consistent
view of the data during MAXIMO upgrades. You should connect to
these integration points and provide the means to integrate to these
points.
After the MAXIMO integration API writes to the interface table, the API
calls an external integration procedure, which acts as a template for your
custom procedure. All of the MAXIMO external integration procedures
include sample code to guide you in the development of integration
procedures to Oracle Financials. Note that these integration procedures
are for real-time routines. In a batch environment, you need not use these
procedures.
WARNING: The Oracle Financials integration module includes
vendor-supported external integration procedures provided by
MRO Software and Oracle. While Oracle Financials users can
customize the user exit procedures, they should not customize the
external integration procedures.
There are many file types in the integration module. Files containing
triggers have the filename extension .TRG; files containing packages
have the filename extensions .PSP and .PKG; files containing stored
procedures have the filename extension .SP; and files containing user
exit procedures have the filename extension .USP. You should modify
only .USP (user exits) and e*.SP (external integration procedures) files.
47
Chapter 2
48
CHAPTER 3
USING THE INTEGRATION MODULE
Use the MAXIMO financial application integration module to transfer and

process data between MAXIMO and Oracle Financials. The integration module
does not change the basic functions of either application.
Most of the integration APIs in the module involve purchasing processes and the
general ledger.
The APIs provide the interface tables as integration points for inventory location
and balance updates. The interface tables accept storeroom locations from your
Oracle inventory system so that MAXIMO can create them in its applications,
and send storeroom information from MAXIMO to your Oracle system. The
inventory balance interface synchronizes item balance and cost information
between the two applications by overlaying the existing item balance and cost
data, in MAXIMO, with values sent from your Oracle Inventory system.
NOTE: The current integration for Oracle Financials does not support sending
balance and cost information from MAXIMO to Oracle Inventory. The
MAXIMO integration gateway can be set up to send balances from
MAXIMO to the MAX_ITM_INTERFACE table. However, there is no
method of moving that data from the interface table into the Oracle
Inventory tables. Any mention of sending balances and costs from
MAXIMO is there only to help describe functionality.
The inventory balance API uses the MAX_ITM_INTERFACE table to contain
data for transactions coming into MAXIMO from your Oracle Inventory system.
49
Chapter 3
NOTE: If a storeroom location in MAXIMO is created by an API (rather than

by MAXIMO), MAXIMO does not automatically grant user access to that
storeroom. The system administrator must set user-level security for anyone who
needs to process transactions for that storeroom in MAXIMO. This security is set
in the usual manner in theMAXIMO Signature Security application.
Inventory Ownership
The inventory ownership, which is defined by the combination of an item and
its location, determines the direction of the data flow for inventory balance and
cost transactions.
• MAXIMO owned inventory is inventory that is created in MAXIMO by a
MAXIMO application.
• Oracle owned inventory is created in MAXIMO by the Integration Gateway.
Determining Inventory Ownership

The APIs determine the inventory ownership by identifying how the inventory
was created in MAXIMO. As explained above, inventory created via the
integration module is owned by your Oracle Financials system and inventory
created by a MAXIMO table in MAXIMO contains the column INVOWNER.
The value in the INVOWNER column is set to E (external) for an inventory
record that the integration module creates. If the value is anything other than E,
the inventory is treated in all transactions as though it is MAXIMO owned.
WARNING: The integration module treats all inventory records that were
created in versions of MAXIMO before Release 4.0 as
MAXIMO owned.
50
Using the Integration Module
Viewing Inventory Ownership

To view the owners of your inventory data, perform the following query using
SQL*Plus or any other SQL language:
Select INVOWNER from INVENTORY where ITEMNUM = ‘your item
number’ and LOCATION = ‘your storeroom location’;
Query results:
• Items with INVOWNER = E are treated as Oracle owned inventory by the
APIs.
• Items with INVOWNER ≠ E are treated as MAXIMO owned inventory by the

APIs. When INVOWNER is set to any value other than E, including NULL
values and spaces, the APIs treat the associated item number as MAXIMO
owned.
Changing Inventory Ownership

To change the owner of the inventory, enter the following SQL statement:
Update INVENTORY
Set INVOWNER = ‘E’ (for Oracle owned; use any other value for MAXIMO
owned)
Where ITEMNUM = ‘your item number’
and LOCATION = ‘your storeroom location’;
Commit;
51
Chapter 3
Inventory Balance Transactions

The APIs do not allow an update of inventory balances in both directions for any
single combination of an item and its location. The integration currently supports
receiving balance transactions from the Oracle Inventory system to update
MAXIMO inventory tables.
Direction of Inventory Balance Updates:

Oracle Inventory
MAXIMO
System
MAXIMO No MAXIMO
owned owned
Inventory No
Inventory
Oracle No Oracle
owned owned
Inventory Yes Inventory
52
APICTLs for Inventory Balance Transactions

Usually, the application that is the owner of the inventory performs all
transactions (including receipts and issues) that affect the balances of that
inventory. However, the APIs provide capabilities for receipt and issue
transactions on the system that does not own the inventory. The table below
shows the default settings for the API controls associated with inventory
transactions.
Value Default Description
ITMSTOREIN Y Adds item to a location in MAXIMO. Also creates

the location in MAXIMO if it doesn’t exist.
ITMSTOREOUT Y Exports item and storeroom location updates to the

Oracle Financials system.
ITMBALXFRIN N Allows MAXIMO to import item balances for

Oracle owned inventory.
If set to Y, it imports item balances and cost updates

for Oracle owned inventory, when the inventory
balances are updated in Oracle.
53
Chapter 3
ITMBALXFROUT N NOTE: This transaction is not supported by the

current integration between MAXIMO and Oracle
Inventory. When the value is set to Y, data will
update the MAX_ITM_INTERFACE table, but it
will NOT update the Oracle Inventory tables.
Allows item balances of MAXIMO owned

inventory to be exported from MAXIMO.
If set to Y, it exports item balance and inventory

cost updates from MAXIMO for MAXIMO owned
inventory.
All cost adjustments (both standard and average),

balance adjustments, and physical count
adjustments performed by MAXIMO for Oracle
owned inventory cause an API error that you see on
the user screen in MAXIMO and cause a database
rollback.
All receipt and issue transactions performed by

MAXIMO for Oracle owned inventory cause a
database rollback and an API error that you see on
the user screen in MAXIMO. You can override this
condition by setting the EXTRCVOUT and
EXTISSOUT switches to Y. If you set these
switches to Y, MAXIMO completes the
transactions and sends them to your Oracle
Financials system. However, MAXIMO does not
send the inventory balance update that occurs as
part of the transaction to your Oracle Financials
system, since the inventory is not MAXIMO
owned.
EXTRCVOUT N If set to Y when RCVOUT = Y, allows item

receipts for Oracle owned inventory to be exported.
54
EXTISSOUT N Note: This transaction is not supported by the

current integration between MAXIMO and Oracle
Inventory. When the value is set to Y, data will
update the MOUT_ISU_INTERFACE table, but it
will NOT update the Oracle Inventory tables.
If set to Y when ISSOUT = Y, allows item issues

for Oracle owned inventory to be exported.
MAXRCVIN Y If set to Y when RCVIN = Y, allows item receipts

for MAXIMO owned inventory to be imported.
MAXISSIN Y If set to Y when ISUIN = Y, allows item issues for

MAXIMO owned inventory to be imported.
RCVIBUPD N When set to Y, performs the inventory balance

updates for Oracle owned inventory as part of the
receipt transaction when the receipt is imported into
MAXIMO.
ISSIBUPD N When set to Y, performs the inventory balance

updates for Oracle owned inventory as part of the
issue transaction when the issue transaction is
imported into MAXIMO.
55
Chapter 3
Importing and Exporting Inventory Balance Data

Importing MAXIMO can import balance data only for Oracle owned
inventory and only when the ITMBALXFRIN and
ITMSTOREIN controls are set to Y.
Exporting Note: Sending balance transactions from MAXIMO to Oracle
Inventory is not supported by the current integration.
MAXIMO can export balance data only for MAXIMO owned
inventory and only when the ITMBALXFROUT and
ITMSTOREOUT controls are set to Y.
Summary of Item Balance Transactions Using Default Settings of the APIs

The information below summarizes how the APIs transfer item balance data
when the default API settings are in place.
Using the Default API settings:

• Item storeroom information is exchanged between MAXIMO and your
financial system. MAXIMO creates locations in its applications if they don’t
already exist. You can modify this activity by using the ITMSTOREIN and
ITMSTOREOUT controls.
• You cannot transfer item balances. You can modify this activity by using the
ITMBALXFROUT(not currently supported) and ITMBALXFRIN controls.
• You cannot perform item balance and cost adjustments on Oracle owned
inventory in any MAXIMO application. The APIs prevent MAXIMO from
completing these transactions and display an error message on the relevant
MAXIMO screen. You also cannot import into MAXIMO any item balance
and cost adjustments performed on MAXIMO owned inventory. The APIs
hold these transactions in the MAX_ITM_INTERFACE table and display an
error in that table’s IMPORTSTATUS column.
56
You cannot modify this activity by using a control switch—these processes

are based strictly on inventory ownership. See “Inventory Ownership” on
page 50 for information on modifying inventory ownership.
• You cannot perform item receipt and issue transactions against Oracle
owned inventory in any MAXIMO application. The APIs prevent MAXIMO
from completing these transactions and display an error message on the
relevant MAXIMO screen. You can modify this activity by using the
EXTRCVOUT and EXTISSOUT controls.
• You cannot import item receipt and issue transactions on MAXIMO owned
inventory. The APIs hold these transactions in the MAX_RCV_INTERFACE
and MAX_ISU_INTERFACE tables and display an error in the
IMPORTSTATUS column. You can modify this activity by using the
MAXRCVIN and MAXISSIN controls.
• Inventory balance updates are performed as part of the item receipt and
issue transactions that you import into MAXIMO for MAXIMO owned
inventory.
These updates are not performed as part of the item receipt and issue
transactions you import into MAXIMO for Oracle owned inventory.
However, you can allow balance updates for Oracle owned inventory by using
the RCVIBUPD and ISSIBUPD settings. When you set these controls to Yes,
MAXIMO creates the receipt and updates the inventory balance to reflect the
receipt. When you set these controls to No, MAXIMO creates the receipt but
does not update the inventory balance.
There is an override switch for these controls that you can set on a per-
transaction basis. This override switch is a column called IBUPD, found in
the MAX_RCV_INTERFACE and MAX_ISU_INTERFACE tables. If you
set this override switch to N for a specific transaction, the APIs do not
perform inventory balance updates with that transaction, even if the control
switches RCVIBUPD and ISSIBUPD are set to Y.
NOTE: You cannot set this switch to Y to override the RCVIBUPD and
ISSIBUPD switches being set to N.
57
Chapter 3
We make this feature available because balance transfers to MAXIMO of

Oracle owned items usually follow receipt and issue transactions and
overwrite the inventory balances in MAXIMO.
Recommended API Settings for Exchanging Item Balances

We recommend the following settings for the APICTL control switches when
you want to exchange item balance information between MAXIMO and your
Oracle Financials system.
NOTE: You can choose to send information one way only, i.e., send only
Oracle owned inventory to MAXIMO or send only MAXIMO owned
inventory to your Oracle Financials system.
APICTL Applicable to: MAXIMO- MAXIMO- Oracle-

owned owned owned
(B) MAXIMO
Not in Oracle In Oracle View is in
(O) Oracle Financials Financials MAXIMO
Financials System System
(B/O) Both
ITMCATIN B/O Y (Optional – Y (For Y

for standardized
standardized or
or centralized centralized
part part
numbers.) numbers.)
ITMCATOUT B/O N Y (For Spot N/A

Buys)
ISUIN B/O N N Y
ISUOUT B N/A N/A N/A
JEINVENTORY B/O N Y N
JEMATUSE B/O Y Y N
58
APICTL Applicable to: MAXIMO- MAXIMO- Oracle-

owned owned owned
(B) MAXIMO
Not in Oracle In Oracle View is in
(O) Oracle Financials Financials MAXIMO
Financials System System
(B/O) Both
ITMBALXFROUT B N/A N/A N/A
ITMSTOREOUT B N Y (For N/A

centralized
inventory
visibility.)
ICFIN E N/A N/A Y
RSVOUT E N/A N/A Y
ITMBALXFRIN E N/A N/A Y
ITMSTOREIN E N/A N/A Y
With these settings, the APIs will work as follows:

• You can transfer item storeroom information between MAXIMO and your
Oracle Financials system. The integration module creates locations in
MAXIMO if the locations do not already exist. You can modify this activity
with the ITMSTOREIN and ITMSTOREOUT controls.
• The APIs will import the item balances of Oracle owned inventory into
MAXIMO after your Oracle Financials system inserts them into the
MAX_ITM_INTERFACE table. You can control this activity with the
ITMBALXFRIN control.
• You cannot use MAXIMO to perform item balance and cost adjustments on
Oracle owned inventory. The APIs prevent these transactions from being
completed and display an error message on the relevant MAXIMO screen.
MAXIMO does not import item balance and cost adjustments on MAXIMO
59
Chapter 3
owned inventory. This data is stopped in the MAX_ITM_INTERFACE table;

the table displays an error in the IMPORTSTATUS column. You cannot
control these processes with control switches; this activity is based on
inventory ownership. See “Inventory Ownership” on page 50 for information
on modifying inventory ownership.
• If needed, you can use MAXIMO to perform item receipt transactions on
Oracle owned inventory; the APIs send updates to your Oracle Financials
system. You can control this with the EXTRCVOUT control.
• If needed, you can import item receipt and issue transactions for MAXIMO
owned inventory. You can control this activity with the MAXRCVIN and
MAXISSIN controls.
If you are using the standard integration control settings, the integration module
does not do the usual inventory balance update as part of the item receipt and
issue transaction for Oracle owned inventory that is imported into MAXIMO. If
you want to modify this activity, see the information on the API settings
RCVIBUPD and ISSIBUPD, which control updates to inventory balances
(“APICTLs for Inventory Balance Transactions” on page 53).
NOTE: Externally owned inventory costs in MAXIMO may not match costs in
Oracle if processes in Oracle Financials affect the costs without
sending the transaction information to MAXIMO via the API.
60
Purchasing Transactions
The APIs provide the interface tables as integration points for purchasing
transactions. Using the APIs, you can exchange purchase requisition data,
purchase order data, and receipt data between the systems. Several interface
tables are used for these transactions. See “Purchasing Interface Tables” on page
130 for more information on these transactions.
Purchase Order Ownership

As of Release 4.0.3 of the integration module, purchase orders are considered to
be “owned” by the application that creates them:
• Oracle owned purchase orders were created in MAXIMO by the Integration
Gateway.
• MAXIMO owned purchase orders were created in MAXIMO by a MAXIMO
application.
Since the integration module can both send and receive purchase orders, there
can be both MAXIMO and Oracle owned POs in the MAXIMO system at one
time. We provide several APICTLs that allow you to control the POs for which
you send receipts, material receipt journal entries, and service receipt journal
entries.
61
Chapter 3
APICTLs for PO Ownership
RCVOUT Controls sending receipts for MAXIMO owned POs.

RECEIPTS
ERCVOUT Controls sending receipts for Oracle owned POs.
Controls sending material receipt journal entries for

MATERIAL JEMATREC
MAXIMO owned POs.
RECEIPT
JOURNAL
ENTRIES Controls sending material receipt journal entries for
EJMATREC
Oracle owned POs.
Controls sending service receipt journal entries for

SERVICE JESERVREC
MAXIMO owned POs.
RECEIPT
JOURNAL
ENTRIES Controls sending service receipt journal entries for
EJSERVREC
Oracle owned POs.
See Chapter 2, “Implementing the Software Integration,” for more information

on these controls.
WARNING: The integration module treats all PO records that were created
in versions of MAXIMO before Release 4.0.3 as MAXIMO
owned.
62
Viewing PO Ownership
To view the owners of your purchase order data, perform the following query
using SQL*Plus or any other SQL language:
Select OWNERSYSID from PO where PONUM = ‘your purchase order
number’;
Query results:
• POs with OWNERSYSID = Null are treated as MAXIMO owned POs by the
APIs.
• POs with OWNERSYSID = OA are treated as Oracle owned POs by the APIs.
Changing PO Ownership
To change the owner of the purchase order, enter the following SQL statement:
Update PO
Set OWNERSYSID = ‘OA’ (‘OA’ for Oracle owned; use Null for MAXIMO
owned)
Where PONUM = ‘your PO number’;
Commit;
63
Chapter 3
Purchasing Configurations
Purchasing data transactions are supported by five configurations in the
Integration Gateway. You should evaluate which configuration is the best model
of your purchasing management practices, then implement the APIs for it. You
can choose not to implement specific processes in the configuration you use, but
you cannot change any of the processes in a configuration.
The configuration processes are supported by a set of API controls. Each
discussion of the configurations lists the primary API control settings for that
configuration. To implement a specific configuration, you must match your
control settings to those listed.
NOTE: Chapter 2 includes a list of all APICTLs and their default settings. You
should review all the APICTLs and their settings, as they may affect
other processes you use.
Common purchasing transactions supported by configurations in the integration
module are summarized in the following table. Most of the transactions are
labeled to specify the configuration to which they apply. Several of the
transactions apply to more than one configuration. Each configuration is
explained in more detail in the sections following this table.
Purchasing Transaction Related Configuration(s)

Create purchase requisitions in MAXIMO. All
Send purchase requisitions from MAXIMO to your Configuration 1

financial system.
Send approved purchase orders from your financial Configuration 1

system to MAXIMO.
Send approved purchase orders from MAXIMO to your Configurations 2, 4, and 5

financial system.
Process receipts in MAXIMO and transfer the receipt Configurations 4 and 5

data to your financial system.
64
Purchasing Transaction Related Configuration(s)

Process receipts in your financial system and transfer Configurations 1 and 2
the receipt data to MAXIMO.
Exchange vendor information. All
Generate invoices in the Oracle Financials financial Configurations 1, 2, and 4

system and transfer the invoice data to MAXIMO.
Generate invoices in MAXIMO and transfer the invoice Configurations 3 and 5

data to your financial system.
Send invoice variances from the Oracle Financials All

system to MAXIMO.
Transfer chart of accounts data from your financial All

system to the MAXIMO Chart of Accounts application.
Transfer purchasing-related general ledger journal Configuration 3

entries from MAXIMO to your financial system.
Comparison of APICTLs for the Configurations

The table below compares some of the most important APICTL settings for each
configuration. Note that there are additional APICTL values that affect how the
two systems exchange information. See Chapter 2, “Implementing the Software
Integration,” for a list of all APICTLs and their default values.
Setting for Configuration:

API Control
1 2 3 4 5
APIN Y Y N Y N
APOUT N N Y N Y
PROUT Y N N N N
65
Chapter 3
Setting for Configuration:

API Control
1 2 3 4 5
POIN Y N N N N
POOUT N Y N Y Y
RCVIN Y Y N N N
RCVOUT N N N Y Y
JEMATREC N N Y N N
JESERVREC N N Y N N
JEINVOICE N N Y N N
APDETAILS N N Y/N N N
APINADJINV Y Y Y Y Y
APINADJDIRECT Y Y Y Y Y
66
Configuration 1
Configuration 1 supports distributed (decentralized) requisitioning, centralized
purchasing, receiving, and invoicing activities.
In the first configuration:
• Create purchase requisitions with MAXIMO at the decentralized location and
send them to your financial system.
• Generate purchase orders at a central location with your purchasing system
and send them to MAXIMO.
• Use your purchasing system if you receive items at a central location.
• Receive invoices and process them at a central location using your accounts
payable system.
• Send details, including variances, of approved/matched invoices from your
accounts payable system to MAXIMO for further processing. MAXIMO will
use this data to update inventory and direct costs at the decentralized location.
• Transfer chart of accounts data from your financial system to the MAXIMO
Chart of Accounts application.
• Exchange vendor information.
67
Chapter 3
APICTL Control Values for Configuration 1

If your processes are the same as those described for Configuration 1, you should
set your APICTL control code values as shown below. Use Application Setup in
MAXIMO to view or change these codes.
The controls listed below are the “primary” controls for this configuration.
However, you should review all the control codes listed in chapter 2 and set them
according to the configuration that you implement.
Control Control Value
APIN Y
APOUT N
PROUT Y
POIN Y
POOUT N
RCVIN Y
RCVOUT N
JEMATREC N
JESERVREC N
JEINVOICE N
APDETAILS N
APINADJINV Y
APINADJDIRECT Y
68
Configuration 2
Configuration 2 supports distributed requisitioning and purchasing in MAXIMO;
and centralized receiving, invoicing, and accounts payable activities.
In the second configuration:
• Create and process purchase requisitions in MAXIMO.
• Create purchase orders in MAXIMO send them to the Oracle Financials
system.
• Process receipts at a centralized location.
• Receive invoices and process them at the centralized location.
• Send the invoice summary or detail to MAXIMO after accounts payable
processing by the Oracle Financials system.
• Transfer purchasing-related general ledger journal entries from MAXIMO to
your financial system.
69
Chapter 3

APIN Y
APOUT N
PROUT N
POIN N
POOUT Y
RCVIN Y
RCVOUT N
JEMATREC N
JESERVREC N
JEINVOICE N
APDETAILS N
APINADJINV Y
APINADJDIRECT Y
70
Configuration 3
Configuration 3 supports distributed requisitioning, purchasing, receiving and
inventory management, all done within MAXIMO. In addition, this configuration
supports distributed invoice matching with invoice details sent to your accounts
payable system.
In the third configuration:
• Use MAXIMO to create and process purchase requisitions, purchase orders,
receipts, and invoices at a decentralized location.
• Send purchasing and inventory-related general ledger journal entries from
MAXIMO to your financial system.
• Send invoice information from MAXIMO to the centralized Accounts
Payables system for payment.
71
Chapter 3

APIN N
APOUT Y
PROUT N
POIN N
POOUT N
RCVIN N
RCVOUT N
JEMATREC Y
JESERVREC Y
JEINVOICE Y
APDETAILS Y/N
APINADJINV Y
APINADJDIRECT Y
72
Configuration 4
Configuration 4 supports distributed requisitioning, purchasing, and receiving in
MAXIMO, and centralized invoicing and accounts payable activities.
In the fourth configuration:
• Create purchase orders in MAXIMO and send them to the Oracle Financials
system; process receipts in MAXIMO.
• Receive invoices and process them at the centralized location.
73
Chapter 3

APIN Y
APOUT N
PROUT N
POIN N
POOUT Y
RCVIN N
RCVOUT Y
JEMATREC N
JESERVREC N
JEINVOICE N
APDETAILS N
APINADJINV Y
APINADJDIRECT Y
74
Configuration 5
Configuration 5 supports distributed requisitioning, purchasing, receiving, and
invoicing in MAXIMO, and centralized accounts payable activities.
In the fifth configuration:
• Create purchase orders in MAXIMO and send them to the Oracle Financials
system; process receipts in MAXIMO.
• Receive invoices and process them in MAXIMO.
75
Chapter 3

APIN N
APOUT Y
PROUT N
POIN N
POOUT Y
RCVIN N
RCVOUT Y
JEMATREC N
JESERVREC N
JEINVOICE N
APDETAILS N
APINADJINV Y
APINADJDIRECT Y
76
Other Configurations
Your business processes may require that you implement the integration module
to work differently than one of the configurations discussed here. For example,
you may decide that Configuration 2 most closely matches your business
processes, but you need to do some receiving in MAXIMO. If so, your RCVOUT
setting would differ from the standard Configuration 2 setting.
Whether you do or do not implement a specific configuration, you should
thoroughly test all transactions and verify that you get the desired results in both
systems for General Ledger, purchasing, inventory and accounts payables
transactions.
77
Chapter 3
User Exit Procedures

You can customize the integration APIs using the user exit procedures that are
available with each integration API. User exit procedures are templates for
custom procedures. You can add a procedure that manipulates data being sent to
MAXIMO or Oracle Financials. For more information on customizing user exit
procedures, see “Customizing the Integration APIS” on page 466.
WARNING: The Oracle Financials integration module includes vendor -
supported external integration procedures provided by MRO Software
and Oracle. While Oracle Financials users can customize user exit
procedures, they should not customize the external integration
procedures.
There are many file types in the integration module. Files containing triggers
have the filename extension .TRG. Files containing stop procedures have the
filename extension .SP, and files containing user stop procedures have the
filename extension .USP. Modify only .USP files. User exit procedures are .USP
files. Do not modify any of the e*.SP (external integration procedures) files.
These are vendor-supported integration procedures.
You can use the UTRANSTYPE user control column in the interface tables to
specify an integration API process. In some cases, this process will override the
default process for an API. Transactions from Oracle Financials to MAXIMO
have default processes. The default processes generally are update followed by
insert. The API first tries to update the record. If the record does not exist, the
API inserts it. The API does not delete the record unless the delete code is listed
in the UTRANSTYPE column.
For more information about the UTRANSTYPE column, see “MAXIMO
Interface Tables” on page 125. The UTRANSTYPE values for each API are
listed in the following API descriptions.
78
External Procedures
MRO Software provides the interface tables as integration points for the external
procedures you must use if you rely on your inbound and outbound APIs to
exchange data between the interface tables and Oracle Financials. We provide
sample external procedures you can customize for your own use. Inbound APIs
are your APIs that transfer data from Oracle Financials to the interface tables;
outbound APIs are your APIs that transfer data from the interface tables to
Oracle Financials.
For more information on customizing external procedures, see “Customizing the
Integration APIS” on page 466.
API Integration Points, Default Processes, and the UTRANSTYPE Control

You can specify the integration points you use by setting the value of the
UTRANSTYPE user control column of the interface tables. Each integration
point has a corresponding UTRANSTYPE setting which provides instructions to
MAXIMO or Oracle Financials on how to process a record.
In some cases, the UTRANSTYPE setting overrides the default process for an
API. All transactions moving from Oracle Financials to MAXIMO have default
processes. The default processes generally are insert followed by update. The
API’s first action is to insert a record as a new record. If the record already exists,
the API updates it instead. The API does not delete the record unless the delete
code is listed in the UTRANSTYPE column.
For more information about the UTRANSTYPE values, see “The User Control
Column” on page 126.
79
Chapter 3
API Processing of Shared Information

The following sections describe how the integration module APIs process the
information shared by MAXIMO and Oracle Financials. The UTRANSTYPE
values for each API are listed in each section. Associated purchasing
configurations are also indicated.
Purchasing Data Transfers

The two applications can exchange data from purchase requisitions, purchase
orders, and receipts. You can use the integration APIs to:
• Transfer purchase requisitions from MAXIMO to Oracle Financials’
purchasing system (Configuration 1).
• Transfer changes in purchase requisitions from Oracle Financials’ purchasing
system to MAXIMO (Configuration 1).
• Transfer purchase orders and changes in purchase orders from Oracle
Financials’ purchasing system to MAXIMO (Configuration 1).
• Transfer receipts from Oracle Financials’ purchasing system to MAXIMO
(Configuration 1).
Transferring Purchase Requisitions from MAXIMO to Oracle Financials

When the status of a purchase requisition changes to indicate transfer to Oracle
Financials, the integration API places the purchase requisition in the MAXIMO
purchase requisition interface table. The API then places the purchase requisition
in the Oracle Financials requisitions interface table.
Note that PR line items in MAXIMO that have no valid item ID in Oracle
Financials need a valid purchasing category in the RLIN1 column. This column
is hidden by default in MAXIMO. Special order items, materials without item
numbers, and services require a valid purchasing category.
80
User Action API Action User Exit
Approves PR in Copies a composite record consisting MXO_USR_PR_SP

MAXIMO. of PR header and PR line for each PR
line record. Copies relevant company,
item, and inventory data, and
appropriate API coding. All copied to
MOUT_PR_INTERFACE table.
This transaction is generated if

APICTL.PROUT is set to Y.
MOUT_PR_INTERFACE copies the MXE_USR_PR_SP

data to the
PO_REQUISITIONS_INTERFACE
table in Oracle Financials for further
processing.
The Oracle Requisition Import is used to import data into Oracle. Refer to Oracle
Applications documentation for further information.
The API does not use any UTRANSTYPE codes for this process.
The API copies relevant purchasing data from these tables:
• PR
• PRLINE
• ITEM
• INVENTORY
• COMPANIES
For more information on customizing user exit procedures, see “Customizing the
Integration APIS” on page 466. For more information on customizing external
integration procedures, see “Customizing Integration Procedures” on page 47.
81
Chapter 3
Import errors
When an error is detected in the import, the PR status in MAXIMO is reset to
WAPPR and the CHANGEBY field in the PR is set to ‘REQnnnnnn’, where
‘nnnnnn’ is the request_id in the Purchasing view request ID. Check the
Requisitions Import Exceptions report.
If some of the PR lines were successfully imported to Oracle Financials, then
there exists a PR in Oracle Financials with those lines. Thus, before reapproving
the PR in MAXIMO, you should either cancel the requisition in Oracle
Financials or create a duplicate PR in MAXIMO that does not contain the already
imported lines. Otherwise, after you import the PR again, Oracle Financials
contains two copies of each line that originally imported successfully.
No UTRANSTYPE codes are defined.
MAXIMO-related data is available from the following MAXIMO tables:
• PR
• PRLINE
• ITEM
• INVENTORY
• COMPANIES
82
Transferring Purchase Requisition Change of Status from Oracle Financials

to MAXIMO
When the status of a purchase requisition changes in Oracle Financials (for
example, it is closed or canceled), it sends the purchase requisition data to the
MAXIMO purchase requisition update interface table. Also, when an error is
detected in the requisition import process in Oracle Financials, the error is sent
here to update the PR. The integration API copies the data and updates the
purchase requisition’s status in MAXIMO.
Updates PR status or Oracle’s API calls the MAXIMO MXI_USR_PRX_SP

deletes PR in partner API stub that writes the
MAX_PRX_INTERFACE received data into
table. MAX_PRX_INTERFACE table.

APICTL.PRIN is set to Y.
MAX_PRX_INTERFACE calls
MAXIMO internal procedures to
update the PR status or delete the PR
in MAXIMO.
The UTRANSTYPE column in the interface table indicates the API process for
the purchase requisition change using the following values:
• D – Delete the purchase requisition.
• S – Update the purchase requisition status. Status can be either canceled
(CAN) or closed (CLOSE).
• X – Follow a user-defined special process.

Interface Tables” on page 125.
83
Chapter 3
Transferring Purchase Orders from Oracle Financials to MAXIMO

To transfer data for a purchase order to MAXIMO, Oracle Financials should
place a copy of the data in the MAXIMO purchase order interface table,
MAX_PO_INTERFACE. The integration API then creates all the necessary
records for the purchase order in MAXIMO. This is part of purchasing
Configuration 1.
User Action API Action User Exit / External API
Approves PO in Oracle Oracle’s API calls the MAXIMO MXI_USR_PO_SP

Financials. partner API stub that writes the
received data into
MAX_PO_INTERFACE table.
MAX_PO_INTERFACE calls MOF_USR_PO_SP

record the PO in MAXIMO.
Optionally, the internal procedures
can also record a new vendor.

APICTL.POIN is set to Y.
Note: This API only provides

informational PO data. No
further PO processing occurs in
MAXIMO.
84
Transferring Purchase Order Change of Status from Oracle Financials to

MAXIMO
When the status of a purchase order changes in Oracle Financials (for example, it
is closed or canceled), it sends the purchase order data to the MAXIMO purchase
order update interface table. The integration API copies the data and updates the
purchase order’s status in MAXIMO. This is part of purchasing Configuration 1.
Updates PO status or Oracle’s API calls the MAXIMO MXI_USR_POX_SP

deletes PO in partner API stub that writes the
MAX_POX_INTERFACE received data into
table. MAX_POX_INTERFACE table.

APICTL.POIN is set to Y.
MAX_POX_INTERFACE calls
update the PO status or delete the PO
in MAXIMO.
For more information on customizing user exit procedures, “Customizing the

the purchase order change using the following values:
• D – Delete the purchase order.
• DI – Delete the purchase order for reinsert.
• S – Update the purchase order status. Status can be either canceled (CAN) or
closed (CLOSE).
• X – Follow a user-defined special process.

85
Chapter 3
Transferring Receipts from Oracle Financials to MAXIMO

To transfer receipt data to MAXIMO, Oracle Financials must write the data to
the MAXIMO receipt interface table, MAX_RCV_INTERFACE. The integration
API then creates all necessary records for the receipt in MAXIMO. This is part of
purchasing Configuration 1.
Records receipts in Oracle Oracle’s API calls the MAXIMO

Financials. partner API stub that writes the
received data into
MAX_RCV_INTERFACE table.

APICTL.RCVIN is set to Y.
MAX_RCV_INTERFACE calls MXI_USR_RCV_SP

record the receipt in MAXIMO.
The MAXIMO APIs have a feature that automatically generates an invoice for a
receipt. To use this feature, set both the Pay On Receipt flag on the purchase
order and the APICTL.PAYONRCPT control to Y. If the
APICTL.PAYONRCPT control is not set to Y, MAXIMO does not generate an
invoice, regardless of the flag on the purchase order.
NOTE: Invoices that you automatically generate from receipts are always in the
form of a single invoice containing a single invoice line per receipt line.
86
Transferring Purchase Orders from MAXIMO to Oracle Financials

To transfer data for a purchase order from MAXIMO to Oracle Financials, the
integration API places a copy of the data in the MAXIMO purchase order
interface table, MOUT_PO_INTERFACE.
If you are sending the PO to Oracle, you should not send the corresponding PR
from MAXIMO to Oracle. A PO loaded into Oracle via the API will not
reference a PR that exists in Oracle.
Approves PO in Copies a composite record consisting MOF_USR_PO_APP_SP

MAXIMO (User of PO header and PO line for each PO
definable – see line record and copies relevant
chapter 2.) company, item, and inventory data, and
appropriate batch and API coding to
Updates the PO MOUT_PO_INTERFACE table.
header once it has
been sent to the The API generates this transaction if
external system. APICTL.POOUT is set to Y.
MOUT_PO_INTERFACE calls MXE_PO_SP

external procedure for further
processing.
The custom PO Validate and Import process is used to import data into Oracle.
Refer to the Integration Setup documentation for further information.
The API copies relevant purchasing data from the following MAXIMO tables:
• PO
• POLINE
• ITEM
• COMPANIES
87
Chapter 3
The API uses the following values in the UTRANSTYPE column to determine
how to process the PO record:
• MPOI – MAXIMO inserted a new PO record.
• MPOU – MAXIMO updated the PO record.
• MPOS – PO record status change.
Column” on page 126. For more information on customizing user exit
procedures, see Chapter 2, “Implementing the Software Integration.”
You have the option to implement either the CAI PO Interface or the Oracle
Standard PO Interface. The Oracle Standard PO Interface is available with Oracle
version 11.5.3 and greater.
The CAI PO interface is provided by Oracle CAI group, whereas the Standard
PO Interface is the Oracle Standard Purchasing Documents Open Interface. The
CAI interface is installed by setting the parameters OFPOApi= 'y' in the script
SETOFVAR.SQL (as described in the Installation guide. If the parameter
OFPOApi= 'n', then the Oracle Standard PO interface is installed.
88
The table below shows the differences between the CAI PO Interface and the
Oracle Standard PO Interface:
CAI Interface Standard PO Interface
The concurrent process for importing POs from The standard concurrent process is
MAXIMO to Oracle should be created as available. It is called “Purchasing
described in Appendix C of the Installation guide. Documents Open Interface”.
The POs created in MAXIMO are imported into The PO’s created in MAXIMO are
Oracle as Approved status. imported into Oracle as Incomplete
status and then approved in Oracle
system.
Once the PO is approved in MAXIMO, the API Once the PO is approved in

inserts the records into these tables: MAXIMO, the new API inserts the
records into the Oracle standard
PO_HEADERS_INTERFACE_CAI_ALL interface tables:
PO_LINES_INTERFACE_CAI_ALL PO_HEADERS_INTERFACE
PO_DISTRIBUTIONS_INTERFACE_CAI_ALL PO_LINES_INTERFACE
PO_RELEASES_INTERFACE_CAI_ALL PO_DISTRIBUTIONS_INTERFA
CE
The PO updates can be done in MAXIMO and the The PO updates cannot be done in
updates can be imported back to Oracle. MAXIMO; so the updates can be
only done in Oracle.
The PO can be cancelled in MAXIMO and Cancellations must be done in

imported to Oracle. Oracle.
Blanket POs are created in MAXIMO and Blanket POs are created in
imported to Oracle as Approved. You also can MAXIMO and imported to Oracle
create releases for Blanket POs in MAXIMO and as Approved, but the Releases for
import them to Oracle. Blanket PO’s must be created in
Oracle.
89
Chapter 3
Transferring Receipts from MAXIMO to Oracle Financials

When you enter receipt records in MAXIMO, the integration API places a copy
of the receipt data in the MAXIMO receipt interface table,
MOUT_RCV_INTERFACE. This is part of purchasing Configuration 1.
NOTE: Due to limitations in the Oracle Receiving interface, negative receipts

(returns/corrections) cannot be sent from MAXIMO to Oracle. These
must be done in Oracle.
Inserts materials Copies material receipt data and MXO_USR_MATRECTRAN

receipt record in appropriate batch and API coding to S_RCV_SP
MAXIMO. MOUT_RCV_INTERFACE.
Inserts service Copies service receipt data and MXO_USR_SERVRECTRA

receipt record in appropriate batch and API coding to NS_RCV_SP
MAXIMO. MOUT_RCV_INTERFACE.
The API generates these transactions

for MAXIMO-owned POs if
APICTL.RCVOUT is set to Y.
The API generates these transaction

for externally owned POs if
APICTL.ERCVOUT is set to Y.
MOUT_RCV_INTERFACE calls MXE_RCV_SP

external procedure for further
processing.
The Oracle Receiving Transaction Processor is used to import data into Oracle.
Refer to Oracle Applications documentation for further information.
90
The API uses the following values in the UTRANSTYPE column of the interface
table to determine how to process the receipts:
• SERVREC – Specifies a service receipt record.
• MATREC – Specifies a material receipt record.
• MATRECTRANS
NOTE: When sending receipt transactions to Oracle, be sure the
corresponding Journal transactions, controlled by JEMATREC and
EJEMATREC, are set appropriately so that you do not get duplicate
journal entries in Oracle for your receipt transactions.
procedures, see chapter 2.
Inventory Ownership for Material Receipts Sent to Oracle Financials

MAXIMO processes receipt transactions for inventory records that originate in
MAXIMO. However, there are no application rules in MAXIMO to prevent it
from processing a receipt transaction for inventory that is “owned” by your
external system. Because of this, the APIs do not send receipt transactions for
externally owned inventory to an external system unless the API control value
setting APICTL.EXTRCVOUT is Y. The default value for this switch is N. See
“Item Data Exchanges ” on page 94 for more information on the inventory
balance interface and inventory ownership.
91
Chapter 3
Impact of Inventory Ownership on Material Receipts Imported into

MAXIMO
Usually, only transactions for externally owned inventory are imported to
MAXIMO from Oracle Financials. However, there are no application rules in
your external system to prevent a receipt transaction for MAXIMO-owned
inventory from being processed there. To account for this situation, the
MAXIMO APIs do not accept receipt transactions for MAXIMO-owned
inventory being sent to MAXIMO unless you set APICTL/MAXRVCIN to Yes.
If the setting is No, an error is recorded in the in the MAX_RCV_INTERFACE
table. The default setting for the MAXRCVIN switch is Yes.
See “Item Data Exchanges” on page 94 for more details on the inventory balance
interface and inventory ownership.
Loaded Costs for Material Receipts that are Imported into MAXIMO
In MAXIMO Release 4.1.1, functionality allows you to add a loaded cost to a PO
line, PO receipt line, or invoice line. You can add a loaded cost to an item’s cost
to account for things like taxes or services. MAXIMO then uses the loaded cost
in the calculation of the item’s average cost or the actual cost on a work order
associated with the item. Loaded costs do not affect invoice costs. If you add a
loaded cost to an invoice line you modify the item’s average cost or work order
cost only if the invoice line’s loaded cost is different from the cost on the PO
receipt.
Loaded Costs in MAXIMO

See the following example of adding a loaded cost to a PO in MAXIMO:
In MAXIMO you may enter a PO line for a stocked item and a PO line for a
standard service. You pro-rate the cost of the service to the cost of the item; this
action sets the item’s loaded cost equal to the item’s line cost plus the service’s
line cost (assuming you pro-rate the service cost at 100%). The loaded cost of the
service line is zero (0). When you receive the item in MAXIMO, it calculates the
item’s average based on the loaded cost, not on the line cost. If the item is a
direct issue item to a work order, the cost that MAXIMO adds to the work order
92
is the loaded cost. Refer to the on-line MAXIMO documentation for more
information on loaded costs.
Loaded Cost in the APIs

The APIs accept a loaded cost for a transaction if Oracle Financials provides it in
the interface table. If the loaded cost is provided, the APIs use it to recalculate
average costs and to update work order costs. The APIs do not calculate a loaded
cost value. Your external system also must provide the rules for adding a loaded
cost to the cost of an item in a transaction. If you do not wish to add loaded costs
to an item or if you do not wish the APIs to accept a loaded cost on a transaction,
set the value of the loaded cost to Null in the appropriate interface table.
93
Chapter 3
Item Data Exchanges

You can use the integration APIs to exchange item data between MAXIMO and
Oracle Financials, and thus maintain a consistent view of the data in both
systems.
Transferring Item Data from MAXIMO to Oracle Financials

When you insert, update, or delete item data in the MAXIMO Inventory module,
the integration API places a copy of the data in the MAXIMO item interface
table, MAX_ITM_INTERFACE.
Inserts, updates, or Copies item data with appropriate batch MXO_USR_ITM_SP

deletes item(s) in and API coding to
MAXIMO. MAX_ITM_INTERFACE table.

APICTL.ITMCAOUT is set to Y.
OR
Inserts, updates, or Copies item’s vendor/manufacturer MXO_USR_ITM_SP

deletes item’s data, all item and company data, and
vendor(s) and/or appropriate batch and API coding to
manufacturer(s) in MAX_ITM_INTERFACE table.
MAXIMO.
The vendor transaction is generated if
APICTL.ITMVNDOUT is set to Y.
MAX_ITM_INTERFACE copies the

data to
MTL_SYSTEM_ITEMS_INTERFACE
table in Oracle Financials for further
processing.
94

• ITEM
• INVVENDOR
• COMPANIES
tables to determine how to process the change to the item data:
• MII – MAXIMO inserts the item record.
• MIU – MAXIMO updates the item record.
• MID – MAXIMO deletes the item record.
tables to determine how to process the change to the vendor data:
• MVI – MAXIMO inserts the item’s vendor record.
• MVU – MAXIMO updates the item’s vendor record.
• MVD – MAXIMO deletes the item’s vendor record.
tables to determine how to process the change to the manufacturer data:
• MMI – MAXIMO inserts the item’s manufacturer record.
• MMU – MAXIMO updates the item’s manufacturer record.
• MMD – MAXIMO deletes the item’s manufacturer record.
exit procedures, see “Customizing Integration Procedures” on page 47.
95
Chapter 3
The Oracle Item Interface is used to import data into Oracle. Refer to Oracle
Transferring Item Data from Oracle Financials to MAXIMO

To transfer data for an item record to MAXIMO, Oracle Financials must write to
the MAXIMO item interface table, MAX_ITM_INTERFACE. The integration
API then creates all the necessary records for the item in MAXIMO.
Inserts or updates item(s) Oracle’s CAI API calls the

in Oracle Financials. MAXIMO partner API stub that
writes the received data into
MAX_ITM_INTERFACE table.
The item transaction is generated if

APICTL.ITMCATIN is set to Y.
The vendor transaction is generated
if APICTL.ITMVNDIN is set to Y.
MAX_ITM_INTERFACE calls MXI_USR_ITM_SP

record the item and/or item’s
vendor/manufacturer in MAXIMO.
Optionally, the internal procedures
can also record a new vendor and/or
manufacturer.
96
The API can update the following tables from this transaction:
• ITEM
• INVVENDOR
• COMPANIES
table to determine how to process the item record:
• XII – Insert the item record. Default process.
• XIU – Update the item record. Default process.
• XID – Delete the item record.
table to determine how to process the vendor information:
• XVI – Insert the vendor record. Default process.
• XVU – Update the vendor record. Default process.
• XVD – Delete the vendor record.
table to determine how to process the manufacturer information:
• XMI – Insert the manufacturer record.
• XMU – Update the manufacturer record.
• XMD – Delete the manufacturer record.
For more information about the UTRANSTYPE values see “The User Control
97
Chapter 3
Transferring Material Reservations/ Demands to Oracle Financials

The API transfers material reservations to Oracle Financials with work orders
that contain them or after users enter them on work orders that the API has
already transferred to Oracle Financials. The API places a copy of the material
reservation in the MAXIMO reservations interface table,
MOUT_RSV_INTERFACE.
Approves a work Copies the material reservations MO_USR_INVRESERVE_SP

order in data into the
MAXIMO. MOUT_RSV_INTERFACE.
The API generates this transaction

if APICTL.RSVOUT is set to Y.
MOUT_RSV_INTERFACE calls MXE_INVRESERVE_SP

the external procedure for further
processing.
The API copies relevant material reservation data from these tables:
• INVRESERVE
• WORKORDER
• ITEM
• INVENTORY
The API uses the following values in the UTRANSTYPE column to determine
how to process the material reservations:
• MRSVI – MAXIMO inserted a new material reservations record.
• MRSVU – MAXIMO updated the material reservations record.
The Oracle Reservations Interface is used to import data into Oracle. Refer to
Oracle Applications documentation for further information.
98
Inventory Ownership for Material Reservations Sent to Your System

Only transactions for externally owned inventory are exported from MAXIMO to
your external system. See “Item Data Exchanges” on page 94 for more details on
the inventory balance interface and inventory ownership.
99
Chapter 3
Transferring Material Issues from Oracle Financials to MAXIMO

To transfer data for a material issue record to MAXIMO, your external
application must write to the MAXIMO issue interface table,
MAX_ISU_INTERFACE. The integration API then creates all the necessary
records for the item in MAXIMO.
Inserts or updates a record MAX_ISU_INTERFACE makes a MXI_USR_ISU_SP

in the programming call to MAXIMO
MAX_ISU_INTERFACE internal procedures to record the
table. issue and update inventory and work
order data.
The API generates the item

transaction if APICTL.ISUIN is set
to Y.
If APICTL.RSVONLIN is set to Y,
the procedures will only accept
issues that are associated with item
reservations.
The API does not use any UTRANSTYPE codes for this process. For more
information on customizing user exit procedures, see Chapter 2, “Implementing
the Software Integration.”
The column DIRECTWO in the MAX_ISU_INTERFACE table acts as Yes or
No flag; when it is set to Yes, MAXIMO updates inventory reservations for the
item on the work order. When the flag is set to No, MAXIMO does not update
the inventory reservation update table, INVRESERVE, but does perform other
updates for this transaction.
Inventory Ownership for Material Issues Sent to MAXIMO

Only transactions for externally owned inventory are imported into MAXIMO
from Oracle Financials. However, there may be cases where a non-MAXIMO
application could be used to issue items on behalf of MAXIMO. To account for
100
this situation, the APIs can accept issue transactions for MAXIMO-owned
inventory into MAXIMO if you set APICTL/MAXISSIN to Yes. If you try to
send these transactions to MAXIMO when the control is set to No, you will see
the error recorded in the MAX_ISU_INTERFACE table. The default setting for
the MAXISSIN switch is No. See “Item Data Exchanges ” on page 94 for more
details on the inventory balance interface and inventory ownership.
Transferring Item Balance Data from Oracle Financials to MAXIMO

To transfer data for an item balance record to MAXIMO, Oracle Financials must
write to the MAXIMO item interface table, MAX_ITM_INTERFACE. The
integration API then creates all the necessary records for the item balance update
in MAXIMO.
Inserts or updates a record MAX_ITM_INTERFACE makes a MXI_USR_ITM_SP

in the programming call to MAXIMO
MAX_ITM_INTERFACE internal procedures to update the
table. item balance and item cost in
MAXIMO.
The API generates the item balance

transaction if
APICTL.ITMSTOREIN is set to Y
and APICTL.ITMBALXFRIN is set
to Y.
This API can update the MAXIMO ITEM, INVENTORY, INVVENDOR, and
COMPANIES table as well as update the inventory balances and costs in the
INVENTORY table. The API uses the following values in the UTRANSTYPE
column in the interface table to determine how to process the item record:
• XSB – Insert or update the item balance record. Default process.
• XSU – Update the item storeroom data. The storeroom update also updates
item balance and cost information as long as the balance and cost are
supplied in the interface table and the APICTL.ITMBALXFRIN is set to
Y.
101
Chapter 3
This API only updates inventory balances for inventory that is owned by the
external system. Inventory balance transactions for MAXIMO-owned inventory
are rejected by the interface process and display errors in the interface table. See
“Inventory Ownership” on page 50 for more information on determining and
changing inventory ownership.
102
Transferring Item Confirmations to MAXIMO

To transfer data from an item confirmation record to MAXIMO, Oracle
Financials must write to the MAXIMO item confirmation interface table,
MAX_ICF_INTERFACE. The integration API then creates all the necessary
records for the item in MAXIMO.
Inserts or updates an MAX_ICF_INTERFACE makes a MXI_USR_ICF_SP

inventory balance in programming call to the MAXIMO
MAXIMO. internal procedure to record the item
confirmation.
The API generates the item

transaction if APICTL.ICFIN is set
to Y.
For more information on customizing user exit procedures, see Chapter 2,
“Implementing the Software Integration.”
Inventory Ownership with Item Confirmations Sent to MAXIMO

Only transactions for externally owned inventory are imported into MAXIMO
from your external system. See “Item Data Exchanges” on page 94 for more
information on the inventory balance interface and inventory ownership.
103
Chapter 3
Vendors
You can synchronize vendor data between MAXIMO and Oracle Financials.
However, the integration API only supports the transmission of vendor
information from Oracle Financials to MAXIMO. Oracle Financials provides no
standard interface for receiving vendor data into Oracle Financials. Thus, neither
changes nor additions in the Companies application of MAXIMO are reflected in
Oracle Financials. Thus, when using the integrated system, you should make any
vendor modifications in Oracle Financials, instead of in the Companies
application of MAXIMO.
Furthermore, only changes either to the vendor header or the vendor site are sent
from Oracle Financials to MAXIMO. Since MAXIMO has no hierarchical
structure in companies, the Oracle Financials vendor header and vendor site data
are concatenated to form the Companies ID in MAXIMO. The Companies
application of MAXIMO contains all the purchasing-enabled Oracle Financials
vendor sites.
MAXIMO receives the AP control account, but neither the AP suspense nor the
RBNI account, for each Oracle Financials vendor site. Thus, if you are planning
to use purchasing Configuration 2, you need to use MAXIMO to specify both the
AP suspense account and the RBNI account for each Oracle Financials vendor
site. Both the AP suspense account and the RBNI account are required for
invoice processing in MAXIMO.
MAXIMO and Oracle Financials also differ in their respective approaches to
encumbrance and liability management. Oracle Financials supports multiple
organizations, departments, subsidiaries, companies, etc. Thus, in Oracle
Financials you manage encumbrance and liability at the organization level. In
contrast, MAXIMO addresses primarily the maintenance organization within
these higher-level organizations, subsidiaries or companies. Thus, in MAXIMO,
you manage encumbrance and liability in more detail by assigning AP Suspense
and RBNI accounts by vendor.
104
Transferring Vendor Data from Oracle Financials to MAXIMO

When a company is inserted, updated, or deleted in Oracle Financials, the
company data is placed in the MAXIMO company interface table. The
integration API copies the data and updates company records in MAXIMO.
Inserts or updates Oracle’s CAI API calls the

vendor(s) and/or vendor MAXIMO partner API stub that
site(s) in Oracle writes the received data into
Financials. MAX_COM_INTERFACE table.

APICTL.COMIN is set to Y.
MAX_COM_INTERFACE calls MXI_USR_COM_SP

record the vendor in MAXIMO.
vendor using the following values:
• XCI – Insert the vendor record. Default process.
• XCU – Update the vendor record. Default process.
• XCD – Delete the vendor record.
MAXIMO-related data is available from the following MAXIMO table:
• COMPANIES
105
Chapter 3
Accounts Payable Data Transfers

You can exchange invoice data between MAXIMO and Oracle Financials
accounts payable system.
Transferring Invoices from MAXIMO to Oracle Financials

When you approve an invoice in MAXIMO, the integration API places a copy of
it in the MAXIMO accounts payable interface table, MOUT_AP_INTERFACE.
In purchasing Configuration 2, you enter, match, and approve invoices in
MAXIMO. When you approve the invoice, the integration API places it in the
MAXIMO accounts payable interface table. Furthermore, summary data is
passed to Oracle Financials Accounts Payable for payment processing. Resulting
journal entries are passed to Oracle Financials General Ledger.
Approves invoice in Copies invoice payment summary MXO_USR_APTRANS_GL_

MAXIMO. data from APTRANS, required SP
data from invoice header and
companies, and appropriate batch
and API coding to
MOUT_AP_INTERFACE table.

APICTL.APOUT is set to Y.
MOUT_AP_INTERFACE calls MXE_AP__SP

Oracle Financials’ procedure for
further processing.
The Oracle Invoice Import is used to import data into Oracle. Refer to Oracle
The API uses one value in the UTRANSTYPE column to process the change:
• INVOICEAPPR – Insert an invoice record.
106

• INVOICE
• INVOICELINE
• INVOICECOST
• COMPANIES
exit procedures, see “Customizing Integration Procedures” on page 47.
Transferring Invoices from Oracle Financials to MAXIMO

To transfer invoice data to MAXIMO, Oracle Financials must write to the
MAXIMO accounts payable interface table, MAX_AP_INTERFACE.
NOTE: You should consider carefully how to determine when an invoice is

ready to be sent to MAXIMO as there is no reverse or corrective
process available after MAXIMO has processed the invoice.
After Oracle Financials puts the invoice data in the interface table, the integration
API creates all the necessary records for the invoice in MAXIMO. This is part of
purchasing Configuration 1. It adds all invoice data to MAXIMO to maintain
consistency between the two applications.
The primary function of this API is to apply all invoice variances to inventory,
work order, and equipment records so that MAXIMO can calculate all costs
accurately. Thus it is important that you provide the value of the invoice variance
in the PRICVAR column of the MAX_AP_INTERFACE table. Since your
accounts payable system has already calculated the variance during invoice
approval, we recommend that you use only that variance rather than have
MAXIMO recalculate the variance. MAXIMO does attempt to calculate a
107
Chapter 3
variance if none is provided, but it may not be the same amount that your
accounts payable system has calculated.
Approves invoice in Oracle’s CAI API calls the

Oracle Financials. MAXIMO partner API stub that
MAX_INVC_INTERFACE table.

APICTL.APIN is set to Y.
MAX_INVC_INTERFACE calls MXI_USR_INVC_SP

record the invoice in MAXIMO.
Optionally, internal procedures
could also record a new vendor.
Note: This API only processes

invoice data necessary for
variance processing. No further
processing occurs in MAXIMO.
108
General Ledger Data Exchanges

MAXIMO and Oracle Financials can exchange general ledger information as
described below:
• Transfer journal entries from MAXIMO to Oracle Financials.
• Transfer chart of accounts data from Oracle Financials to MAXIMO to
synchronize this data between the two applications.
The integration API passes all GL code combinations created in Oracle
Financials into MAXIMO. However, please observe the following:
1. You must configure MAXIMO to support the Oracle account structure.
Within MAXIMO, to specify the basic format of the GL account codes, use
the GL Account Configuration option in the Database Configuration
application.
2. MAXIMO can support only one GL account structure. Thus, MAXIMO, as
distributed, supports none of the following.
• Multiple account templates
• Multiple sets of books
• Multiple organizations
However, you can use extra fields in MAXIMO both to store and to track
different sets of books or organizations. Furthermore, you may want to use the
MAXIMO Developer’s Kit to validate sets of books or organizations, i.e.,
cross-validation between sets of books, organizations, general ledger
accounts, employees, projects, work orders, etc.
109
Chapter 3
Transferring Journal Entries from MAXIMO to Oracle Financials

When a user inserts a record in any of the MAXIMO journal transaction tables,
one of the following integration APIs places a copy of it in the MAXIMO journal
interface table.
The only API process that occurs in this transaction is INSERT. The API uses the
following UTRANSTYPE values to specify the general ledger transaction table:
UTRANSTYPE Value Table Table Description
INV INVTRANS Inventory transactions
MATREC MATRECTRANS Material receipt

transactions
MATUSE MATUSETRANS Material usage (issue)

transactions
SERVREC SERVRECTRANS Service receipt

transactions
LABOR LABTRANS Labor transactions
TOOL TOOLTRANS Tools transactions
INVOICE INVOICETRANS Invoice transactions
You may not need all of the journal entries APIs, depending on the purchasing
Configuration that you use. If you use purchasing Configuration 1, your
purchasing system may process the material receipt, service receipts, and invoice
transactions. If you do not use the associated APIs you should turn them off with
the API controls. You can also use the user exit procedures to filter out
transactions for specific GL accounts from reaching the
MOUT_GL_INTERFACE table.
110
procedures, see “Customizing the Integration APIS” on page 466. For more
information on customizing external exit procedures, see “Customizing
Integration Procedures” on page 47.
111
Chapter 3
Transferring Entries from INVTRANS to Oracle Financials

When a user enters a record in the INVTRANS table, the integration API places
a copy of it in the MAXIMO general ledger interface table,
MOUT_GL_INTERFACE.
Enters inventory Copies data from INVTRANS MXO_USR_INVTRANS_

transaction where Debit GL Account is not GL_SP
the same as Credit GL Account,
LINECOST is not 0, and the
account is not of the following
transaction types:
INSERTITEM
PCOUNTADJ
Adds appropriate batch and API

coding to the

APICTL.JEINVENTORY is set
to Y.
MOUT_GL_INTERFACE copies MXO_USR_MOUT_GL_

the data to the GL_INTERFACE INTERFACE_SP
table in Oracle Financials for
further processing.
The API copies relevant data from the following table:

• INVTRANS
Transferring Journal Entries from MATRECTRANS to Oracle Financials

When a user inserts a record in the MATRECTRANS table, the integration API
places a copy of it in the MAXIMO general ledger interface table,
MOUT_GL_INTERFACE.
112
Enters Copies data from MATUSETRANS MXO_USR_MATUSETRA

material where Debit GL Account is not the same NS_GL_SP
usage as Credit GL Account and LINECOST is
not 0.
Adds appropriate batch and API coding

to the MOUT_GL_INTERFACE table.

APICTL.JESERVREC is set to Y and the
PO is MAXIMO-owned.

APICTL.EJESERVREC is set to Y and
the PO is Oracle-owned.
MOUT_GL_INTERFACE copies the MXO_USR_MOUT_GL_

data to the GL_INTERFACE table in INTERFACE_SP
Oracle Financials for further processing.
The API copies relevant data from this table:

• MATRECTRANS
113
Chapter 3
Transferring Journal Entries from MATUSETRANS to Oracle Financials

When a user inserts a record in the MATUSETRANS table, the integration API
MOUT_GL_INTERFACE.
Enters material usage Copies data from MXO_USR_MATUSETRA

MATUSETRANS where Debit NS_GL_SP
GL Account is not the same as
Credit GL Account and
LINECOST is not 0.
Adds appropriate batch and

API coding to the
MOUT_GL_INTERFACE
table.

APICTL.JEMATUSE is set to
Y.
MOUT_GL_INTERFACE MXO_USR_MOUT_GL_
copies the data to the INTERFACE_SP
GL_INTERFACE table in
Oracle Financials for further
processing.

• MATUSETRANS
114
Transferring Entries from SERVRECTRANS to Oracle Financials

When a user inserts a record in the SERVRECTRANS table, the integration API
places a copy of it in the MAXIMO general ledger interface table.
Enters service Copies data from MXO_USR_SERVRECTRANS_

receipt. SERVRECTRANS where GL_SP
Debit GL Account is not the
same as Credit GL Account
and LINECOST is not 0.

API coding to the
MOUT_GL_INTERFACE
table.
This transaction is generated

if APICTL.JESERVREC is
set to Y.
MOUT_GL_INTERFACE MXO_USR_MOUT_GL_
copies the data to the INTERFACE_SP
GL_INTERFACE table in
Oracle Financials for further
processing.

• SERVRECTRANS
115
Chapter 3
Transferring Entries from LABTRANS to Oracle Financials

When a user inserts a record in the LABTRANS table, the integration API places
a copy of it in the MAXIMO general ledger interface table,
MOUT_GL_INTERFACE.
Enters labor usage. Copies data from LABTRANS MXO_USR_LABTRANS_

where Debit GL Account is not the GL_SP
same as Credit GL Account,
LINECOST is not 0, and the
account is of the following
transaction type:
WORK
NON-WORK

coding to the

APICTL.JELABOR is set to Y.

further processing.

• LABTRANS
116
Transferring Entries from TOOLTRANS to Oracle Financials

When a user inserts a record in the TOOLTRANS table, the integration API
MOUT_GL_INTERFACE.
Enters tool usage. Copies data from TOOLTRANS MXO_USR_TOOLTRANS

where Debit GL Account is not _GL_SP
the same as Credit GL Account

coding to the

APICTL.JETOOL is set to Y.

further processing.
The API copies relevant data from the following table:

• TOOLTRANS
117
Chapter 3
Transferring Entries from INVOICETRANS to Oracle Financials

When a user inserts a record in the INVOICETRANS table, the integration API
MOUT_GL_INTERFACE.
Approves invoice in Copies data from MXO_USR_INVOICETRANS_

MAXIMO. INVOICETRANS where the GL_SP
debit GL account is not the
same as the credit GL account

API coding to the
MOUT_GL_INTERFACE
table.
The API generates this

transaction if
APICTL.JEINVOICE is set to
Y.
MOUT_GL_INTERFACE MXE_GL_SP
calls external procedure for
further processing.
The API copies relevant data from these tables:

• INVOICETRANS
• INVOICELINE
• INVOICECOST: The Oracle GL Interface is used to import data into
Oracle. Refer to Oracle Applications documentation for further
information.
118
Transferring Chart of Accounts Data from Oracle Financials to MAXIMO

When a chart of accounts record or a general ledger component for the chart of
accounts record is inserted, updated, or deleted in Oracle Financials, the chart of
accounts data is placed in the MAXIMO chart of accounts interface table. The
integration API copies the data and updates chart of accounts records in
MAXIMO.
Inserts or updates GL(s) in Oracle’s CAI API calls the

Oracle Financials. MAXIMO partner API stub that
MAX_COA_INTERFACE table.

APICTL.COA is set to Y.
MAX_COA_INTERFACE calls MXI_USR_COA_SP

populate the MAXIMO
CHARTOFACCOUNTS table
and/or GLCOMPONENTS table.
modifying either the chart of accounts or general ledger components of the chart
of accounts. The following values modify the chart of accounts:
• XGI – Insert the chart of accounts record. Default process.
• XGU – Update the chart of accounts record. Default process.
• XGD – Delete the chart of accounts record.
119
Chapter 3
The following values modify general ledger components of the chart of accounts:
• XCI – Insert the general ledger account component record. Default
process.
• XCU – Update the general ledger account component record. Default
process.
• XCD – Delete the general ledger account component record.
Interface Tables”on page 125.
MAXIMO-related data is available from the following MAXIMO tables:
• CHARTOFACCOUNTS
• GLCOMPONENTS
GL Synchronization Transformations
There are some cases in which the GL structure in MAXIMO is not exactly the
same as in Oracle Financials. Therefore, when transferring accounts from one
system to the other, you must transform those accounts. This section both
outlines the cases in which you need to perform the account transformation and
explains how to make the transformation.
In the APIUSER directory, there are two user exit procedures for transforming
GL accounts from one system to the other.
Transferring Accounts from MAXIMO to Oracle Financials

If you are transferring accounts from MAXIMO to Oracle Financials, use user
exit procedure MXE_USR_GLOUTX_SP. This procedure is in the
OFGLOUTX.USP file.
120
Transferring Accounts from Oracle Financials to MAXIMO

If you are transferring accounts from Oracle Financials to MAXIMO, use user
exit procedure MXI_USR_GLINX_SP. This procedure is in file OFGLINX.USP.
MAXIMO Support for the Transformation of the GL Accounts

MAXIMO supports Independent GL Segments, but does not support Dependent
or Table Validated segments. Because of this, we cannot guarantee the accuracy
of the description for these segments coming to MAXIMO.
Cases Requiring Transformation of GL Accounts

As shown in the following table, there are two relevant differences between the
account structure in Oracle Financials and the account structure in MAXIMO:
Oracle Financials MAXIMO
Segment length May be variable Always fixed
Null segments allowed In any part of the account Only after all non-nulls
The remainder of the section contains examples of these two relevant differences,
including the specific changes to the user exits.
1. In Oracle Financials some segments are of variable length, not fixed length; in
MAXIMO all segments are of fixed length. If necessary, you can use zeros to
pad the account segments in MAXIMO.
Example Your accounts have two segments. The first segment is fixed at two
characters long. One particular account is 22-333.
In Oracle Financials, the second segment can be variable in length. Thus,

using Oracle Financials, you can enter an account number of 22-4444.
However, in MAXIMO, the second segment must always be three
characters long. Thus, 22-4444 is not a valid account in MAXIMO.
121
Chapter 3
Similarly, 22-22 is a valid account in Oracle Financials, but not in MAXIMO.

In MAXIMO, you need to pad the second segment with zeros. Thus, the
MAXIMO account needs to be 22-022.
Thus, if transferring this account from one system to another, you must
make the following changes to the user exit procedures.
Transferring from MAXIMO to Oracle Financials
Before transferring the account to Oracle Financials, you must trim the
zeros from the fixed-length segment. In Oracle Financials, the segment
becomes a variable-length segment. Thus, the account 22-022 in MAXIMO
becomes 22-22 in Oracle Financials.
Add the following statement to the procedure MXE_USR_GLOUTX_SP in

file OFGLOUTX.USP:
OFGLSegs(2) := LTRIM(OFGLSegs(2),’0’);
Transferring from Oracle Financials to MAXIMO
Before transferring the account to MAXIMO, you must pad the variable-
length segment in Oracle Financials. The segment becomes a fixed-length
segment in MAXIMO. Thus, the Oracle Financials account 22-22 becomes
MAXIMO account 22-022.
Add the following statement to the procedure MXE_USR_GLINX_SP in file

OFGLINX.USP:
OFGLSegs(2) := LPAD(OFGLSegs(2),3,’0’);
122
2. In Oracle Financials, null segments are permitted in any part of the account.
However, MAXIMO does not allow a null segment to precede a non-null
segment.
Example Your accounts in Oracle Financials have three segments:
Segment1 = null
Segment2 = size(2)
Segment3 = size(3)
In MAXIMO, a null segment cannot precede a non-null segment. Thus,

these accounts must consist of only two segments:
Segment1 = size(2)
Segment2 = size(3)
Thus, if transferring this account from one system to another, you must
make the following changes to the user exit procedures.
123
Chapter 3
Transferring from MAXIMO to Oracle Financials
Before transferring the account, you must convert the two-segment account
in MAXIMO to a three-segment account for Oracle Financials. The existing
two segments are shifted down, and the first segment of the account in
Oracle Financials is created as a null.
Taking note of the order of movements, add the following statements to the
procedure MXE_USR_GLOUTX_SP in file OFGLOUTX.USP:
OFGLSegs(3) := OFGLSegs(2);
OFGLSegs(1) := Null;
nSegs := 3; (change the number of segments from two to three)
Transferring from Oracle Financials to MAXIMO
Before transferring the account, you must convert the three-segment

account in Oracle Financials to a two-segment account for MAXIMO. The
two non-null segments are shifted up, and the third segment of the account
in MAXIMO becomes a null.
Taking note of the order of movements, add the following statements to the
procedure MXE_USR_GLINX_SP in file OFGLINX.USP:
OFGLSegs(3) := Null;
nSegs := 2; (change the number of segments from three to two)
124
MAXIMO Interface Tables

Interface tables are the intermediate locations where data resides while it is being
transferred between MAXIMO and Oracle Financials. Data is sent to an interface
table, where it remains while it is validated. Once it is validated, an integration
API processes the data and places it in its destination.
For audit trail purposes, a copy of the data remains in the interface table.
In addition to the interface tables, the integration module keeps a log table called
MAX_INTERFACE_LOG. The log table tracks transactions between the two
applications and keeps records of transaction errors. For more information about
the interface log, see “Troubleshooting ” on page 476.
For details about the mapping between MAXIMO and Oracle Financials
interface tables, refer to the APIDOC subdirectory.
Interface tables contain several types of columns, which store different kinds of
information.
Data Columns
Data columns store the specific attributes that the source application is sending to
the destination application. For example, one attribute of a purchase order is the
order quantity.
Data columns contain information that is either required or optional. The required
or optional status is indicated under the Nulls heading in the interface tables. N
indicates that the data is required; Y indicates that the data is not required.
Required columns store the minimum information needed by the destination
application to process the interface row. For example, price is required for all
purchase orders. Some columns are conditionally required, based on the specifics
of the system integration.
Information stored in optional columns is not necessarily required by the
destination application, but the destination application can use it for additional
value-added functionality beyond the basics. For example, on a vendor
125
Chapter 3
transaction, the CO1 column is not required, but you can optionally use it to
collect additional information about a vendor.
User Columns
There are 10 user data columns, USERDATA1 – USERDATA10, available for
general use. By default the columns are alphanumeric with a column length of
one (ALN1). Use the MAXIMO Database Configuration application to
reconfigure the MAXIMO columns for your use.
To configure the columns, you must access their tables using the Database
Configuration application. Run MAXIMO and choose Setup Database
Configuration. In the application list box, select the INTERFACE application.
All of the API tables appear in the table list box. Choose each table and configure
the user data columns in it.
For instructions on how to configure columns using the Database Configuration
application, refer to the MAXIMO System Administrator’s Guide.
Batch Control Columns

Batch columns store information about the batch routine transferring of data to
the destination application. Batch columns identify the batch number and the
transaction line number within the batch routine.
For information about batch routines, see “Using Batch Routines” on page 468.
The User Control Column

The user control column, called UTRANSTYPE, stores user-defined program
directives. Users can specify an integration API process by inserting a value in
this column.
In some cases, the integration API process overrides a default API process. Only
transactions from Oracle Financials to MAXIMO have default processes. The
default processes generally are insert and update. The API first tries to insert the
126
record. If the record already exists, the API updates it. The API does not delete
the record unless the delete value is listed in the UTRANSTYPE column.
For example, the default processes for the vendor API are insert or update. If a
vendor record is deleted in Oracle Financials, the value XCD (external vendor
delete) may be inserted in the control column. When the API processes the
transaction, it deletes the record in MAXIMO if the XCD value is in the control
column.
UTRANSTYPE values for transactions sent from Oracle Financials to MAXIMO
are automatically processed. UTRANSTYPE values for transactions sent from
MAXIMO to Oracle Financials must be processed by Oracle Financials.
Interface Control Columns

Interface control columns identify the integration API used in the transaction, and
the source and destination applications. These columns also provide details about
the data being transferred. For example, the interface control columns for a
purchase order transaction would specify whether the purchase order was just
created, updated, or deleted in the source application.
Three interface control columns are APISEQ, APISYNC, and SOURCEID.
• The APISEQ column contains an internally generated value from the Oracle
sequence APISEQ. This APISEQ value links each MAXIMO record with its
associated record in the interface table.
Example When a PR is approved, APISEQ is inserted into tables PRLINE and

MOUT_PR_INTERFACE
• The APISYNC value links records across different applications and systems,
providing an audit trail. APISYNC links records associated with purchase
requisitions, with purchase orders, with receipts and with invoices.
Example When you generate a purchase requisition in MAXIMO, each line is

assigned an APISYNC value. When you transfer the purchase requisition
to Oracle Financials, the APISYNC value is transferred with it. When you
create a purchase order in Oracle Financials and transfer the PO to
127
Chapter 3
MAXIMO, the APISYNC value is stored in the APISYNC column in the

MAXIMO table POLINE. Therefore, the purchase order can be traced back
to the PRLINE record.
• The SOURCEID column identifies the source of the data. Either a null
SOURCEID or a SOURCEID of ‘M’ indicates data from MAXIMO. A
SOURCEID of ‘I’ indicates data imported from Oracle Financials.
Status Columns
Status columns provide information about the status of a transaction. They
indicate whether or not a transaction was completed successfully. The status
columns also provide the date and time of transaction completion or failure, and
general messages, such as error messages.
For information about other error messages, see “Troubleshooting ” on page 476.
128
Error Messages
This section describes some of the error messages that you might see when using
the APIs. These error messages are specific to Oracle Financials. For information
about other messages, see “Troubleshooting” on page 476.
You might see one of the following error messages when transferring data from
MAXIMO to Oracle Financials.
Invalid Debit/Credit GL Code Combinations
The GL account value failed Oracle Financials validation. Enter a valid GL account.
Invalid BillTo
BillTo must have a valid organization in Oracle Financials. Specify a valid
organization defined in Oracle Financials.
Invalid enter by user
The user ID value failed Oracle Financials validation. If GENUSR is set to N, the
user ID being passed may be invalid or not authorized for the function being
performed in Oracle Financials. Enter a valid user ID. If GENUSR is Y, set up
the MAXIMO ID in Oracle Financials to have access to the function being
performed.
Invalid vendor or Invalid vendor header
The component in the MAXIMO vendor key that makes up the vendor ID failed
Oracle Financials validation. Enter a valid vendor.
Invalid vendor site
The component in the MAXIMO vendor key that makes up the vendor site ID
failed Oracle Financials validation. Enter a valid vendor.
129
Chapter 3
Purchasing Interface Tables

This section provides the mapping for the interface tables the APIs use when
transferring purchasing data between MAXIMO and Oracle Financials. The
values displayed in the following tables are examples, and do not necessarily
reflect your values. Your MAXIMO system catalogue determines your values.
MOUT_PR_INTERFACE Table
The MOUT_PR_INTERFACE table receives purchase requisition data from the
following MAXIMO tables when a purchase requisition is approved. Data is
transferred to Oracle Financials.
Empty rows in the table are not physical rows in the database. They are there to
group sets of data or to separate information that comes from different tables.
MOUT_PR_INTERFACE Table MAXIMO Tables
Column Name Type Length Nulls Table Column Name
PRNUM UPPER 8 S PR PRNUM
ISSUEDATE DATETIME 10 Y PR ISSUEDATE
REQUIREDDATE DATETIME 10 Y PR REQUIREDDATE
REQUESTEDBY UPPER 18 Y PR REQUESTEDBY
VENDOR UPPER 8 Y PR VENDOR
CONTACT ALN 50 Y PR CONTACT
CUSTOMERNUM ALN 16 Y PR CUSTOMERNUM
FOB ALN 20 Y PR FOB
FREIGHTTERMS ALN 50 Y PR FREIGHTTERMS
SHIPVIA ALN 20 Y PR SHIPVIA
PAYMENTTERMS ALN 20 Y PR PAYMENTTERMS
130
SHIPTO UPPER 8 Y PR SHIPTO
SHIPTOATTN ALN 50 Y PR SHIPTOATTN
BILLTO UPPER 8 Y PR BILLTO
BILLTOATTN ALN 50 Y PR BILLTOATTN
DESCRIPTION ALN 50 Y PR DESCRIPTION
STATUS UPPER 6 Y PR STATUS
STATUSDATE DATETIME 10 Y PR STATUSDATE
CHANGEDATE DATETIME 10 Y PR CHANGEDATE
CHANGEBY UPPER 18 Y PR CHANGEBY
TOTALCOST DECIMAL 10.2 Y PR TOTALCOST
PRIORITY INTEGER 4 Y PR PRIORITY
HISTORYFLAG YORN 1 Y PR HISTORYFLAG
PR1 ALN 10 Y PR PR1
PR2 ALN 10 Y PR PR2
PR3 ALN 10 Y PR PR3
PR4 ALN 10 Y PR PR4
PR5 ALN 10 Y PR PR5
PR6 AMOUNT 10.2 Y PR PR6
PR7 DATETIME 10 Y PR PR7
PR8 DECIMAL 15.2 Y PR PR8
PR9 INTEGER 4 Y PR PR9
PR10 YORN 1 Y PR PR10
131
Chapter 3
PRLONGDESC ALN 2000 Y
PRLINELONGDESC ALN 2000 Y
SUPERVISOR UPPER 8 Y PR SUPERVISOR
CURRENCYCODE UPPER 8 Y PR CURRENCYCODE
EXCHANGERATE DECIMAL 14.7 Y PR EXCHANGERATE
EXCHANGEDATE DATE 4 Y PR EXCHANGEDATE
BUYAHEAD YORN 1 Y PR BUYAHEAD
TOTALTAX1 DECIMAL 10.2 Y PR TOTALTAX1
INCLUSIVE1 YORN 1 Y PR INCLUSIVE1
INTERNAL YORN 1 Y PR INTERNAL
PAYONRECEIPT ALN 1 Y PR PAYONRECEIPT
132
WFID INTEGER 4 Y PR WFID
WFACTIVE ALN 1 Y PR WFACTIVE
EXCHANGERATE2 DECIMAL 14.7 Y PR EXCHANGERATE2
SOURCESYSID ALN 10 Y PR SOURCESYSID
OWNERSYSID ALN 10 Y PR OWNERSYSID
EXTERNALREFID ALN 10 Y PR EXTERNALREFID
PRLA1 ALN 10 Y PR PRLA1
PCARDNUM ALN 30 Y PR PCARDNUM
PCARDTYPE ALN 20 Y PR PCARDTYPE
PCARDEXPDATE ALN 7 Y PR PCARDEXPDATE
PCARDVERIFICATION ALN 4 Y PRLINE PCARDVERIFICATION
APISEQ INTEGER 4 Y PRLINE APISEQ
SENDERSYSID ALN 50 Y PR SENDERSYSID
ITEMNUM UPPER 30 Y PRLINE ITEMNUM
STORELOC UPPER 8 Y PRLINE STORELOC
ORDERQTY DECIMAL 15.2 Y PRLINE ORDERQTY
ORDERUNIT ALN 8 Y PRLINE ORDERUNIT
UNITCOST DECIMAL 10.2 Y PRLINE UNITCOST
133
Chapter 3
CONVERSION DECIMAL 15.2 Y PRLINE CONVERSION
PONUM ALN 8 Y PRLINE PONUM
REQDELIVERYDATE DATE 4 Y PRLINE REQDELIVERYDATE
VENDELIVERYDATE DATE 4 Y PRLINE VENDELIVERYDATE
ENTERDATE DATETIME 10 Y PRLINE ENTERDATE
ENTERBY UPPER 18 Y PRLINE ENTERBY
PRLDESCRIPTION ALN 80 Y PRLINE DESCRIPTION
RL1 ALN 10 Y PRLINE RL1
RL4 DECIMAL 15.2 Y PRLINE RL4
WONUM UPPER 10 Y PRLINE WONUM
PRLREQUESTEDBY UPPER 18 Y PRLINE REQUESTEDBY
ISSUE YORN 1 Y PRLINE ISSUE
WPOPERATION INTEGER 4 Y PRLINE WPOPERATION
RLIN1 ALN 10 Y PRLINE RLIN1
RLIN4 DATETIME 10 Y PRLINE RLIN4
RLIN5 DECIMAL 15.2 Y PRLINE RLIN5
EQNUM UPPER 8 Y PRLINE EQNUM
134
CHARGESTORE YORN 1 Y PRLINE CHARGESTORE
GLDEBITACCT ALN 20 Y PRLINE GLDEBITACCT
GLCREDITACCT ALN 20 Y PRLINE GLCREDITACCT
LINECOST DECIMAL 10.2 Y PRLINE LINECOST
TAX1CODE UPPER 8 Y PRLINE TAX1CODE
TAX1 DECIMAL 10.2 Y PRLINE TAX1
SCHARGECODE UPPER 8 Y PRLINE SCHARGECODE
RECEIPTREQD YORN 1 Y PRLINE RECEIPTREQD
MANUFACTURER UPPER 8 Y PRLINE MANUFACTURER
MODELNUM ALN 8 Y PRLINE MODELNUM
CATALOGCODE ALN 30 Y PRLINE CATALOGCODE
PRLINENUM INTEGER 4 Y PRLINE PRLINENUM
POLINENUM INTEGER 4 Y PRLINE POLINENUM
135
Chapter 3
CATEGORY UPPER 4 Y PRLINE CATEGORY
REMARK ALN 50 Y PRLINE REMARK
SERVICE YORN 1 Y PRLINE SERVICE
LOCATION UPPER 8 Y PRLINE LOCATION
LOADEDCOST AMOUNT 10.2 Y PRLINE LOADEDCOST
PRORATESERVICE ALN 1 Y PRLINE PRORATESERVICE
AGREEMENTPONUM ALN 8 Y PRLINE AGREEMENTPONUM
AGREEMENTPOTYPE ALN 6 Y PRLINE AGREEMENTPOTYPE
CONVERTTORFQ ALN 1 Y PRLINE CONVERTTORFQ
RFQNUM ALN 8 Y PRLINE RFQNUM
RFQLINENUM INTEGER 4 Y PRLINE RFQLINENUM
INSPECTIONREQUIRED ALN 1 Y PRLINE INSPECTIONREQUIRED
RFQLINEID INTEGER 4 Y PRLINE RFQLINEID
POLINEID INTEGER 4 Y PRLINE POLINEID
LINECOST2 DECIMAL 10.2 Y PRLINE LINECOST
VARVALUE(BASCURREN
CURRENCYCODE2 UPPER 8 Y MAXVAR CY2)
MRNUM ALN 8 Y PRLINE MRNUM
MRLINENUM INTEGER 4 Y PRLINE MRLINENUM
MKTPLCITEM YORN 1 Y PRLINE MKTPLCITEM
VENDORPACKCODE ALN 12 Y PRLINE VENDORPACKCODE
VENDORPACKQUANTIT VENDORPACKQUANTIT
Y ALN 12 Y PRLINE Y
136
VENDORWAREHOUSE ALN 12 Y PRLINE VENDORWAREHOUSE
PRLALN1 ALN 10 Y PRLINE PRLALN1
PRLPRPCARDNUM ALN 30 Y PRLINE PCARDNUM
PRLPRPCARDTYPE ALN 20 Y PRLINE PCARDTYPE
PRLPRPCARDEXPDATE ALN 7 Y PRLINE PCARDEXPDATE
RPCARDVERIFICATION ALN 4 Y PRLINE PCARDVERIFICATION
FINCNTRLID ALN 8 Y
COMPANYTYPE ALN 1 Y COMPANIES TYPE
MFGNAME ALN 50 Y COMPANIES NAME
137
Chapter 3
NAME ALN 50 Y COMPANIES NAME
ADDRESS1 ALN 36 Y COMPANIES ADDRESS1
PHONE ALN 20 Y COMPANIES PHONE
FAX ALN 20 Y COMPANIES FAX
CO1 ALN 10 Y COMPANIES CO1
CO4 DECIMAL 10.2 Y COMPANIES CO4
CO5 DATETIME 10 Y COMPANIES CO5
CO7 AMOUNT 10.2 Y COMPANIES CO7
CO9 INTEGER 4 Y COMPANIES CO9
CO10 YORN 1 Y COMPANIES CO10
COMPANYLOC UPPER 8 Y COMPANIES LOCATION
REGISTRATION1 ALN 20 Y COMPANIES REGISTRATION1
138
APCONTROLACC ALN 20 Y COMPANIES APCONTROLACC
APSUSPENSEACC ALN 20 Y COMPANIES APSUSPENSEACC
RBNIACC ALN 20 Y COMPANIES RBNIACC
PAYVENDOR UPPER 8 Y COMPANIES PAYVENDOR
BANKACCOUNT UPPER 20 Y COMPANIES BANKACCOUNT
REMITADDRESS1 ALN 36 Y COMPANIES REMITADDRESS1
REMITCONTACT ALN 50 Y COMPANIES REMITCONTACT
HOMEPAGE ALN 124 Y COMPANIES HOMEPAGE
BANKNUM ALN 16 Y COMPANIES BANKNUM
DUNSNUM ALN 16 Y COMPANIES DUNSNUM
TAXEXEMPTCODE ALN 1 Y COMPANIES TAXEXEMPTCODE
TAXEXEMPTNUM ALN 20 Y COMPANIES TAXEXEMPTNUM
ECOMMERCEENABLED ALN 1 Y COMPANIES ECOMMERCEENABLED
DISABLED ALN 1 Y COMPANIES DISABLED
139
Chapter 3
POSITION ALN 24 Y COMPCONTACT POSITION
ITMDESCRIPTION ALN 80 Y ITEM DESCRIPTION
ITEMLONGDESC ALN 2000 Y
STOCKTYPE ALN 8 Y ITEM STOCKTYPE
LOTTYPE UPPER 5 Y ITEM LOTTYPE
CAPITALIZED YORN 1 Y ITEM CAPITALIZED
ROTATING ALN 1 Y ITEM ROTATING
ISSUEUNIT ALN 8 Y INVENTORY ISSUEUNIT
ROWSTAMP ALN 40 Y
MEMO ALN 40 Y POSTATUS MEMO
USERDATA1 ALN 1 Y
USERDATA2 ALN 1 Y
USERDATA3 ALN 1 Y
USERDATA4 ALN 1 Y
USERDATA5 ALN 1 Y
USERDATA6 ALN 1 Y
USERDATA7 ALN 1 Y
140
USERDATA8 ALN 1 Y
USERDATA9 ALN 1 Y
USERDATA10 ALN 1 Y
TOTALLINES INTEGER 4 Y
MEMO ALN 25 Y
BATCHID ALN 25 Y
BATCHLINEID INTEGER 4 Y
UTRANSTYPE ALN 25 Y
SOURCEID ALN 25 Y PR SOURCEID
APISITE ALN 256 Y
IMPORTSTATUS ALN 25 Y
IMPORTTIMESTAMP DATETIME 10 Y
IMPORTMESSAGE ALN 2000 Y
141
Chapter 3
MAX_PRX_INTERFACE Table
The MAX_PRX_INTERFACE table receives purchase requisition update data
from Oracle Financials. Data is sent to the following MAXIMO tables.
separate information coming from different tables or to group sets of data.
MAX_PR_INTERFACE Table MAXIMO Tables
PRNUM UPPER 8 N PR PRNUM
ISSUEDATE DATETIME 10 Y PR ISSUEDATE
REQUIREDDATE DATETIME 10 Y PR REQUIREDDATE
REQUESTEDBY UPPER 18 Y PR REQUESTEDBY
VENDOR UPPER 8 Y PR VENDOR
CONTACT ALN 50 Y PR CONTACT
CUSTOMERNUM ALN 16 Y PR CUSTOMERNUM
FOB ALN 20 Y PR FOB
FREIGHTTERMS ALN 50 Y PR FREIGHTTERMS
SHIPVIA ALN 20 Y PR SHIPVIA
PAYMENTTERMS ALN 20 Y PR PAYMENTTERMS
SHIPTO UPPER 8 Y PR SHIPTO
SHIPTOATTN ALN 50 Y PR SHIPTOATTN
BILLTO UPPER 8 Y PR BILLTO
BILLTOATTN ALN 50 Y PR BILLTOATTN
DESCRIPTION ALN 50 Y PR DESCRIPTION
STATUS UPPER 6 Y PR STATUS
142
STATUSDATE DATETIME 10 Y PR STATUSDATE
CHANGEDATE DATETIME 10 Y PR CHANGEDATE
CHANGEBY UPPER 18 Y PR CHANGEBY
TOTALCOST DECIMAL 10.2 Y PR TOTALCOST
PRIORITY INTEGER 4 Y PR PRIORITY
HISTORYFLAG YORN 1 Y PR HISTORYFLAG
PR1 ALN 10 Y PR PR1
PR2 ALN 10 Y PR PR2
PR3 ALN 10 Y PR PR3
PR4 ALN 10 Y PR PR4
PR5 ALN 10 Y PR PR5
PR6 AMOUNT 10.2 Y PR PR6
PR7 DATETIME 10 Y PR PR7
PR8 DECIMAL 15.2 Y PR PR8
PR9 INTEGER 4 Y PR PR9
PR10 YORN 1 Y PR PR10
PRLONGDESC ALN 2000 Y
PRLINELONGDESC ALN 2000 Y
SUPERVISOR UPPER 8 Y PR SUPERVISOR
CURRENCYCODE UPPER 8 Y PR CURRENCYCODE
EXCHANGERATE DECIMAL 14.7 Y PR EXCHANGERATE
EXCHANGEDATE DATE 10 Y PR EXCHANGEDATE
143
Chapter 3
BUYAHEAD YORN 1 Y PR BUYAHEAD
INTERNAL YORN 1 Y PR INTERNAL
PAYONRECEIPT ALN 1 Y PR PAYONRECEIPT
WFID INTEGER 4 Y PR WFID
WFACTIVE ALN 1 Y PR WFACTIVE
EXCHANGERATE2 DECIMAL 14.7 Y PR EXCHANGERATE2
APISEQ INTEGER 4 Y PRLINE APISEQ
SENDERSYSID ALN 50 Y PR SENDERSYSID
ITEMNUM UPPER 30 Y PRLINE ITEMNUM
STORELOC UPPER 8 Y PRLINE STORELOC
ORDERQTY DECIMAL 15.2 Y PRLINE ORDERQTY
144
ORDERUNIT ALN 8 Y PRLINE ORDERUNIT
UNITCOST DECIMAL 10.2 Y PRLINE UNITCOST
CONVERSION DECIMAL 15.2 Y PRLINE CONVERSION
PONUM ALN 8 Y PRLINE PONUM
REQDELIVERYDATE DATE 4 Y PRLINE REQDELIVERYDATE
VENDELIVERYDATE DATE 4 Y PRLINE VENDELIVERYDATE
ENTERDATE DATETIME 10 Y PRLINE ENTERDATE
ENTERBY UPPER 18 Y PRLINE ENTERBY
PRLDESCRIPTION ALN 80 Y PRLINE DESCRIPTION
RL4 DECIMAL 15.2 Y PRLINE RL4
WONUM UPPER 10 Y PRLINE WONUM
PRLREQUESTEDBY UPPER 18 Y PRLINE REQUESTEDBY
ISSUE YORN 1 Y PRLINE ISSUE
WPOPERATION INTEGER 4 Y PRLINE WPOPERATION
RLIN4 DATETIME 10 Y PRLINE RLIN4
145
Chapter 3
RLIN5 DECIMAL 15.2 Y PRLINE RLIN5
EQNUM UPPER 8 Y PRLINE EQNUM
CHARGESTORE YORN 1 Y PRLINE CHARGESTORE
GLDEBITACCT ALN 20 Y PRLINE GLDEBITACCT
GLCREDITACCT ALN 20 Y PRLINE GLCREDITACCT
LINECOST DECIMAL 10.2 Y PRLINE LINECOST
SCHARGECODE UPPER 8 Y PRLINE SCHARGECODE
RECEIPTREQD YORN 1 Y PRLINE RECEIPTREQD
MANUFACTURER UPPER 8 Y PRLINE MANUFACTURER
MODELNUM ALN 8 Y PRLINE MODELNUM
CATALOGCODE ALN 30 Y PRLINE CATALOGCODE
146
POLINENUM INTEGER 4 Y PRLINE POLINENUM
CATEGORY UPPER 4 Y PRLINE CATEGORY
REMARK ALN 50 Y PRLINE REMARK
SERVICE YORN 1 Y PRLINE SERVICE
LOCATION UPPER 8 Y PRLINE LOCATION
LOADEDCOST AMOUNT 10.2 Y PRLINE LOADEDCOST
PRORATESERVICE ALN 1 Y PRLINE PRORATESERVICE
AGREEMENTPONUM ALN 8 Y PRLINE AGREEMENTPONUM
AGREEMENTPOTYPE ALN 6 Y PRLINE AGREEMENTPOTYPE
CONVERTTORFQ ALN 1 Y PRLINE CONVERTTORFQ
RFQNUM ALN 8 Y PRLINE RFQNUM
RFQLINENUM INTEGER 4 Y PRLINE RFQLINENUM
INSPECTIONREQUIRED ALN 1 Y PRLINE INSPECTIONREQUIRED
RFQLINEID INTEGER 4 Y PRLINE RFQLINEID
POLINEID INTEGER 4 Y PRLINE POLINEID
LINECOST2 DECIMAL 10.2 Y PRLINE LINECOST
CURRENCYCODE2 UPPER 8 Y
MKTPLCITEM YORN 1 Y PRLINE MKTPLCITEM
VENDORPACKCODE ALN 12 Y PRLINE VENDORPACKCODE
VENDORPACKQUANTI VENDORPACKQUANTIT
TY ALN 12 Y PRLINE Y
147
Chapter 3
VENDORWAREHOUSE ALN 12 Y PRLINE VENDORWAREHOUSE
148
149
Chapter 3
DISABLED ALN 1 Y COMPANIES DISABLED
ITMDESCRIPTION ALN 80 Y ITEM DESCRIPTION
ROTATING YORN 1 Y ITEM ROTATING
ROWSTAMP ALN 40
MEMO ALN 50 Y PRSTATUS MEMO
USERDATA1 ALN 1 Y
USERDATA2 ALN 1 Y
USERDATA3 ALN 1 Y
USERDATA4 ALN 1 Y
USERDATA5 ALN 1 Y
USERDATA6 ALN 1 Y
USERDATA7 ALN 1 Y
USERDATA8 ALN 1 Y
150
USERDATA9 ALN 1 Y
USERDATA10 ALN 1 Y
BATCHID ALN 25 Y
UTRANSTYPE ALN 25 Y
SOURCEID ALN 25 Y PR SOURCEID
SOURCESYSID ALN 10 Y PR SOURCESYSID
OWNERSYSID ALN 10 Y PR OWNERSYSID
EXTERNALREFID ALN 10 Y PR EXTERNALREFID
APISITE ALN 256 Y
151
Chapter 3
MAX_PO_INTERFACE Table
The MAX_PO_INTERFACE table receives purchase order data from Oracle
Financials. Data is sent to the following MAXIMO tables.
MAX_PO_INTERFACE Table MAXIMO Tables
PONUM UPPER 8 N PO PONUM
PODESCRIPTION ALN 80 Y PO DESCRIPTION
PURCHASEAGENT ALN 50 Y PO PURCHASEAGENT
ORDERDATE DATETIME 10 Y PO ORDERDATE
REQUIREDDATE DATETIME 10 Y PO REQUIREDDATE
FOLLOWUPDATE DATE 4 Y PO FOLLOWUPDATE
POTYPE UPPER 6 Y PO POTYPE
ORIGINALPONUM UPPER 8 Y PO ORIGINALPONUM
STATUS UPPER 6 Y PO STATUS
STATUSDATE DATETIME 10 Y PO STATUSDATE
VENDOR UPPER 8 Y PO VENDOR
CONTACT ALN 50 Y PO CONTACT
FREIGHTTERMS ALN 50 Y PO FREIGHTTERMS
PAYMENTTERMS ALN 20 Y PO PAYMENTTERMS
SHIPVIA ALN 20 Y PO SHIPVIA
CUSTOMERNUM ALN 16 Y PO CUSTOMERNUM
FOB UPPER 20 Y PO FOB
152
SHIPTO UPPER 8 Y PO SHIPTO
SHIPTOATTN ALN 50 Y PO SHIPTOATTN
BILLTO UPPER 8 Y PO BILLTO
BILLTOATTN ALN 50 Y PO BILLTOATTN
TOTALCOST DECIMAL 10 Y PO TOTALCOST
CHANGEBY UPPER 18 Y PO CHANGEBY
CHANGEDATE DATETIME 10 Y PO CHANGEDATE
PRIORITY INTEGER 4 Y PO PRIORITY
HISTORYFLAG YORN 1 Y PO HISTORYFLAG
PO1 ALN 1 Y PO PO1
PO2 ALN 1 Y PO PO2
PO3 ALN 1 Y PO PO3
PO4 ALN 1 Y PO PO4
PO5 ALN 1 Y PO PO5
PO6 ALN 1 Y PO PO6
PO7 ALN 1 Y PO PO7
PO8 ALN 1 Y PO PO8
PO9 ALN 1 Y PO PO9
PO10 ALN 1 Y PO PO10
CURRENCYCODE UPPER 8 Y PO CURRENCYCODE
EXCHANGERATE DECIMAL 12 Y PO EXCHANGERATE
EXCHANGEDATE DATE 4 Y PO EXCHANGEDATE
153
Chapter 3
BUYAHEAD YORN 1 Y PO BUYAHEAD
TOTALTAX1 DECIMAL 10 Y PO TOTALTAX1
INCLUSIVE1 YORN 1 Y PO INCLUSIVE1
INTERNAL YORN 1 Y PO INTERNAL
STARTDATE DATE 4 Y PO STARTDATE
ENDDATE DATE 4 Y PO ENDDATE
PAYONRECEIPT ALN 1 Y PO PAYONRECEIPT
WFID FLOAT 126 Y PO WFID
WFACTIVE ALN 1 Y PO WFACTIVE
BUYERCOMPANY ALN 8 Y PO BUYERCOMPANY
ITEMNUM UPPER 8 Y POLINE ITEMNUM
STORELOC UPPER 8 Y POLINE STORELOC
MODELNUM ALN 8 Y POLINE MODELNUM
CATALOGCODE ALN 12 Y POLINE CATALOGCODE
154
ORDERQTY DECIMAL 15 Y POLINE ORDERQTY
ORDERUNIT ALN 8 Y POLINE ORDERUNIT
UNITCOST DECIMAL 10 Y POLINE UNITCOST
CONVERSION DECIMAL 15 Y POLINE CONVERSION
RECEIVEDQTY DECIMAL 15 Y POLINE RECEIVEDQTY
RECEIVEDUNITCOST DECIMAL 10 Y POLINE RECEIVEDUNITCOST
RECEIVEDTOTALCOST DECIMAL 10 Y POLINE RECEIVEDTOTALCOST
REJECTEDQTY DECIMAL 15 Y POLINE REJECTEDQTY
VENDELIVERYDATE DATE 4 Y POLINE VENDELIVERYDATE
SUPERVISOR UPPER 8 Y POLINE SUPERVISOR
TAXED YORN 1 Y POLINE TAXED
ENTERDATE DATETIME 10 Y POLINE ENTERDATE
ENTERBY UPPER 18 Y POLINE ENTERBY
DESCRIPTION ALN 50 Y POLINE DESCRIPTION
PL1 ALN 1 Y POLINE PL1
WONUM UPPER 10 Y POLINE WONUM
REQUESTEDBY UPPER 18 Y POLINE REQUESTEDBY
REQDELIVERYDATE DATE 4 Y POLINE REQDELIVERYDATE
155
Chapter 3
ISSUE YORN 1 Y POLINE ISSUE
POLINENUM INTEGER 4 Y POLINE POLINENUM
WPOPERATION INTEGER 4 Y POLINE WPOPERATION
PLIN1 ALN 1 Y POLINE PLIN1
EQNUM UPPER 8 Y POLINE EQNUM
CHARGESTORE YORN 1 Y POLINE CHARGESTORE
GLDEBITACCT ALN 20 Y POLINE GLDEBITACCT
GLCREDITACCT ALN 20 Y POLINE GLCREDITACCT
LINECOST DECIMAL 10 Y POLINE LINECOST
TAX1CODE UPPER 8 Y POLINE TAX1CODE
TAX1 DECIMAL 10 Y POLINE TAX1
SCHARGECODE UPPER 8 Y POLINE SCHARGECODE
RECEIPTREQD YORN 1 Y POLINE RECEIPTREQD
MANUFACTURER UPPER 8 Y POLINE MANUFACTURER
156
SERVICE ALN 1 Y POLINE SERVICE
CATEGORY UPPER 4 Y POLINE CATEGORY
REMARK ALN 50 Y POLINE REMARK
LOCATION UPPER 8 Y POLINE LOCATION
LOADEDCOST DECIMAL 10 Y POLINE LOADEDCOST
PRORATESERVICE ALN 1 Y POLINE PRORATESERVICE
AGREEMENTPONUM ALN 8 Y POLINE AGREEMENTPONUM
AGREEMENTPOTYPE ALN 6 Y POLINE AGREEMENTPOTYPE
RECEIPTSCOMPLETE ALN 1 Y POLINE RECEIPTSCOMPLETE
INSPECTIONREQUIRED ALN 1 Y POLINE INSPECTIONREQUIRED
PRORATECOST DECIMAL 10.2 Y POLINE PRORATECOST
POLINEID DECIMAL 10 Y POLINE POLINEID
PRNUM ALN 8 Y PR PRNUM
157
Chapter 3
158
POLONGDESC ALN 2000 Y
POLINELONGDESC ALN 2000 Y
USERDATA1 ALN 1 Y
USERDATA2 ALN 1 Y
USERDATA3 ALN 1 Y
USERDATA4 ALN 1 Y
USERDATA5 ALN 1 Y
USERDATA6 ALN 1 Y
USERDATA7 ALN 1 Y
USERDATA8 ALN 1 Y
USERDATA9 ALN 1 Y
USERDATA10 ALN 1 Y
BATCHID ALN 25 Y
159
Chapter 3
UTRANSTYPE ALN 25 Y
SOURCEID ALN 25 Y PO SOURCEID
APISEQ INTEGER 4 Y POLINE APISEQ
APISITE ALN 256 Y
APISYNC INTEGER 4 Y POLINE APISYNC
160
MAX_POX_INTERFACE Table
The MAX_POX_INTERFACE table receives purchase order update data from
Oracle Financials. Data is sent to the following MAXIMO tables.
MAX_POX_INTERFACE Table MAXIMO Tables
CHANGEBY UPPER 18 N PO CHANGEBY
PO1 ALN 10 Y PO PO1
PO2 ALN 10 Y PO PO2
PO3 ALN 10 Y PO PO3
PO4 ALN 10 Y PO PO4
PO5 ALN 10 Y PO PO5
PO6 AMOUNT 10 Y PO PO6
PO7 DATETIME 10 Y PO PO7
PO8 DECIMAL 15 Y PO PO8
PO9 INTEGER 4 Y PO PO9
PO10 YORN 1 Y PO PO10
POTYPE ALN 6 Y PO POTYPE
161
Chapter 3
MAX_POX_INTERFACE Table MAXIMO Tables
ORIGINALPONUM ALN 8 Y PO ORIGINALPONUM
USERDATA1 ALN 1 Y
USERDATA2 ALN 1 Y
USERDATA3 ALN 1 Y
USERDATA4 ALN 1 Y
USERDATA5 ALN 1 Y
USERDATA6 ALN 1 Y
USERDATA7 ALN 1 Y
USERDATA8 ALN 1 Y
USERDATA9 ALN 1 Y
USERDATA10 ALN 1 Y
ROWSTAMP ALN 40 Y
BATCHID ALN 25 Y
UTRANSTYPE ALN 25 Y
APISITE ALN 256 Y
162
MAX_RCV_INTERFACE Table
The MAX_RCV_INTERFACE table receives receipt data from Oracle
Financials. This interface tables sends data to two MAXIMO tables:
MATRECTRANS and SERVRECTRANS.
The following table shows the mapping for the MAX_RCV_INTERFACE and
MATRECTRANS tables.
MAX_RCV_INTERFACE Table MATRECTRANS Table
Column Name Type Length Nulls Column Name
ITEMNUM UPPER 30 Y ITEMNUM
TOSTORELOC UPPER 8 Y TOSTORELOC
TRANSDATE DATETIME 10 Y TRANSDATE
ACTUALDATE DATETIME 10 Y ACTUALDATE
QUANTITY DECIMAL 15 Y QUANTITY
RECEIVEDUNIT ALN 8 Y RECEIVEDUNIT
ISSUETYPE UPPER 8 Y ISSUETYPE
UNITCOST AMOUNT 10 Y UNITCOST
ACTUALCOST AMOUNT 10 Y ACTUALCOST
PONUM UPPER 8 Y PONUM
INVOICENUM UPPER 8 Y INVOICENUM
REJECTCODE UPPER 6 Y REJECTCODE
REJECTQTY DECIMAL 15 Y REJECTQTY
REJECTCOST DECIMAL 15 Y
CONVERSION DECIMAL 15 Y CONVERSION
163
Chapter 3
WONUM UPPER 10 Y WONUM
EQNUM UPPER 8 Y EQNUM
SERIALNUM UPPER 15 Y
ENTERBY UPPER 18 Y ENTERBY
IT1 ALN 10 Y IT1
IT2 ALN 10 Y IT2
IT3 ALN 10 Y IT3
IT4 AMOUNT 15 Y IT4
IT5 ALN 10 Y IT5
OUTSIDE YORN 1 Y WPOPERATION
WPOPERATION INTEGER 4 Y WPOPERATION
ISSUETO UPPER 8 Y ISSUETO
PACKINGSLIPNUM ALN 20 Y PACKINGSLIPNUM
POLINENUM INTEGER 4 Y POLINENUM
ISSUE YORN 1 Y ISSUE
REQUESTEDBY ALN 20 Y REQUESTEDBY
TOTALCURBAL AMOUNT 15 Y
OLDAVGCOST AMOUNT 10 Y
ITIN1 ALN 10 Y ITIN1
TOBIN ALN 8 Y TOBIN
164
GLDEBITACCT ALN 20 Y GLDEBITACCT
GLCREDITACCT ALN 20 Y GLCREDITACCT
LINECOST AMOUNT 10 Y LINECOST
LINECOST2 AMOUNT 10 Y LINECOST2
FINANCIALPERIOD ALN 6 Y FINANCIALPERIOD
CURRENCYCODE UPPER 8 Y CURRENCYCODE
EXCHANGERATE DECIMAL 14 Y EXCHANGERATE
EXCHANGERATE2 DECIMAL 14 Y EXCHANGERATE2
CURRENCYUNITCOST DECIMAL 10 Y CURRENCYUNITCOST
MANUFACTURER UPPER 8 Y MANUFACTURER
MODELNUM ALN 8 Y MODELNUM
CURRENCYLINECOST DECIMAL 10 Y CURRENCYLINECOST
LOCATION UPPER 8 Y LOCATION
DESCRIPTION ALN 80 Y DESCRIPTION
REMARK ALN 50 Y REMARK
FROMSTORELOC UPPER 8 Y FROMSTORELOC
FROMBIN ALN 8 Y FROMBIN
QTYHELD DECIMAL 15 Y QTYHELD
FROMLOT ALN 8 Y FROMLOT
TOLOT ALN 8 Y TOLOT
LOADEDCOST DECIMAL 10 Y LOADEDCOST
165
Chapter 3
TAX1CODE ALN 8 Y TAX1CODE
TAX1 DECIMAL 10 Y TAX1
PRORATED ALN 1 Y PRORATED
PRORATECOST DECIMAL 10 Y PRORATECOST
STATUS ALN 8 Y STATUS
STATUSDATE DATETIME 10 Y STATUSDATE
STATUSCHANGEBY ALN 18 Y STATUSCHANGEBY
CURBAL DECIMAL 15 Y CURBAL
INVOICEDQTY DECIMAL 15 Y
CLAIMNUM UPPER 8 Y
APPROVED YORN 1 Y
APPROVEDATE DATETIME 10 Y
APPROVEBY UPPER 18 Y
MRNUM ALN 8 Y MRNUM
166
MRLINENUM INTEGER 4 Y MRLINENUM
MATRECTRANSID NUMBER 10 Y MATRECTRANSID
SERVRECTRANSID INTEGER 4 Y
SOURCESYSID ALN 10 Y SOURCESYSID
QTYREQUESTED DECIMAL 15 Y QTYREQUESTED
OWNERSYSID ALN 10 Y OWNERSYSID
EXTERNALREFID ALN 10 Y EXTERNALREFID
IT6 ALN 10 Y IT6
IT7 ALN 10 Y IT7
IT8 ALN 10 Y IT8
IT9 ALN 10 Y IT9
IT10 ALN 10 Y IT10
APISEQ INTEGER 4 Y APISEQ
SENDERSYSID ALN 50 Y SENDERSYSID
RECID ALN 1 Y
ROLLUP ALN 1 Y
IBUPD YORN 1 Y
LONGDESC ALN 2000 Y
167
Chapter 3
ROWSTAMP ALN 40 N
USERDATA1 ALN 1 Y
USERDATA2 ALN 1 Y
USERDATA3 ALN 1 Y
USERDATA4 ALN 1 Y
USERDATA5 ALN 1 Y
USERDATA6 ALN 1 Y
USERDATA7 ALN 1 Y
USERDATA8 ALN 1 Y
USERDATA9 ALN 1 Y
USERDATA10 ALN 1 Y
BATCHID ALN 25 Y
UTRANSTYPE ALN 25 Y
SOURCEID ALN 25 Y SOURCEID
APISITE ALN 256 Y
168
The following table shows the mapping for the MAX_RCV_INTERFACE and
SERVRECTRANS tables.
MAX_RCV_INTERFACE Table SERVRECTRANS Table
ITEMNUM UPPER 30 Y
TOSTORELOC UPPER 8 Y
ACTUALDATE DATETIME 10 Y ENTERDATE
RECEIVEDUNIT ALN 8 Y
ISSUETYPE UPPER 8 Y
ACTUALCOST AMOUNT 10 Y
REJECTCODE UPPER 6 Y
REJECTCOST DECIMAL 15 Y REJECTCOST
CONVERSION DECIMAL 15 Y
SERIALNUM UPPER 15 Y
169
Chapter 3
IT1 ALN 10 Y SS1
IT2 ALN 10 Y
IT3 ALN 10 Y
IT4 AMOUNT 15 Y
IT5 ALN 10 Y
OUTSIDE YORN 1 Y OUTSIDE
ISSUETO UPPER 8 Y
PACKINGSLIPNUM ALN 20 Y
ISSUE YORN 1 Y
REQUESTEDBY ALN 20 Y
ITIN1 ALN 10 Y SSPL1
TOBIN ALN 8 Y
LINECOST AMOUNT 10 Y LINECOST
170
LINECOST2 AMOUNT 10 Y LINECOST2
MANUFACTURER UPPER 8 Y
MODELNUM ALN 8 Y
FROMSTORELOC UPPER 8 Y
FROMBIN ALN 8 Y
QTYHELD DECIMAL 15 Y
FROMLOT ALN 8 Y
TOLOT ALN 8 Y
LOADEDCOST DECIMAL 10 Y
TAX1CODE ALN 8 Y
TAX1 DECIMAL 10 Y
TAX2CODE ALN 8 Y
171
Chapter 3
TAX2 DECIMAL 10 Y
TAX3CODE ALN 8 Y
TAX3 DECIMAL 10 Y
TAX4CODE ALN 8 Y
TAX4 DECIMAL 10 Y
TAX5CODE ALN 8 Y
TAX5 DECIMAL 10 Y
PRORATED ALN 1 Y
PRORATECOST DECIMAL 10 Y
STATUS ALN 8 Y
STATUSDATE DATETIME 10 Y
STATUSCHANGEBY ALN 18 Y
CURBAL DECIMAL 15 Y
INVOICEDQTY DECIMAL 15 Y
CLAIMNUM UPPER 8 Y CLAIMNUM
APPROVED YORN 1 Y APPROVED
APPROVEDATE DATETIME 10 Y APPROVEDATE
APPROVEBY UPPER 18 Y APPROVEBY
MRNUM ALN 8 Y MRNUM
MATRECTRANSID NUMBER 10 Y
SERVRECTRANSID INTEGER 4 Y SERVRECTRANSID
172
QTYREQUESTED DECIMAL 15 Y
IT6 ALN 10 Y
IT7 ALN 10 Y
IT8 ALN 10 Y
IT9 ALN 10 Y
IT10 ALN 10 Y
ITIN4 ALN 10 Y
ITIN5 ALN 10 Y
ITIN6 ALN 10 Y
ITIN7 ALN 10 Y
RECID ALN 1 Y
ROLLUP ALN 1 Y ROLLUP
IBUPD YORN 1 Y
LONGDESC ALN 2000 Y
ROWSTAMP ALN 40 N
USERDATA1 ALN 1 Y
USERDATA2 ALN 1 Y
173
Chapter 3
USERDATA3 ALN 1 Y
USERDATA4 ALN 1 Y
USERDATA5 ALN 1 Y
USERDATA6 ALN 1 Y
USERDATA7 ALN 1 Y
USERDATA8 ALN 1 Y
USERDATA9 ALN 1 Y
USERDATA10 ALN 1 Y
BATCHID ALN 25 Y
UTRANSTYPE ALN 25 Y
APISITE ALN 256 Y
174
MOUT_PO_INTERFACE Table
The MOUT_PO_INTERFACE table sends purchase order data from MAXIMO
to Oracle Financials. Data is sent from the following MAXIMO tables. The
mappings displayed are the defaults, and do not necessarily reflect your values.
Your MAXIMO system catalogue determines your values.
NOTE: Empty rows in the table are not physical rows in the database; they
either separate information that comes from different tables or they
group different sets of data.
MOUT_PO_INTERFACE Table MAXIMO Tables
PODESCRIPTION ALN 50 Y PO DESCRIPTION
PURCHASEAGENT ALN 50 Y PO PURCHASEAGENT
ORDERDATE DATETIME 10 Y PO ORDERDATE
REQUIREDDATE DATETIME 10 Y PO REQUIREDDATE
FOLLOWUPDATE DATE 4 Y PO FOLLOWUPDATE
POTYPE UPPER 6 Y PO POTYPE
ORIGINALPONUM UPPER 8 Y PO ORIGINALPONUM
VENDOR UPPER 8 Y PO VENDOR
CONTACT ALN 50 Y PO CONTACT
FREIGHTTERMS ALN 50 Y PO FREIGHTTERMS
PAYMENTTERMS ALN 20 Y PO PAYMENTTERMS
SHIPVIA ALN 20 Y PO SHIPVIA
175
Chapter 3
CUSTOMERNUM ALN 16 Y PO CUSTOMERNUM
FOB UPPER 20 Y PO FOB
SHIPTO UPPER 8 Y PO SHIPTO
SHIPTOATTN ALN 50 Y PO SHIPTOATTN
BILLTO UPPER 8 Y PO BILLTO
BILLTOATTN ALN 50 Y PO BILLTOATTN
TOTALCOST DECIMAL 10 Y PO TOTALCOST
CHANGEBY UPPER 18 Y PO CHANGEBY
PRIORITY INTEGER 4 Y PO PRIORITY
HISTORYFLAG YORN 1 Y PO HISTORYFLAG
PO1 ALN 10 Y PO PO1
PO2 ALN 10 Y PO PO2
PO3 ALN 10 Y PO PO3
PO4 ALN 10 Y PO PO4
PO5 ALN 10 Y PO PO5
PO6 AMOUNT 10 Y PO PO6
PO7 DATETIME 10 Y PO PO7
PO8 DECIMAL 15 Y PO PO8
PO9 INTEGER 4 Y PO PO9
PO10 YORN 1 Y PO PO10
RECEIPTS ALN 20 Y PO RECEIPTS
176
CURRENCYCODE UPPER 8 Y PO CURRENCYCODE
VARVALUE(BASCURREN
EXCHANGERATE DECIMAL 14 Y PO EXCHANGERATE
EXCHANGERATE2 DECIMAL 14 Y PO EXCHANGERATE2
EXCHANGEDATE DATE 4 Y PO EXCHANGEDATE
BUYAHEAD YORN 1 Y PO BUYAHEAD
INTERNAL YORN 1 Y PO INTERNAL
STARTDATE DATE 4 Y PO STARTDATE
ENDDATE DATE 4 Y PO ENDDATE
PAYONRECEIPT ALN 1 Y PO PAYONRECEIPT
WFID FLOAT 126 Y PO WFID
177
Chapter 3
WFACTIVE ALN 1 Y PO WFACTIVE
BUYERCOMPANY ALN 8 Y PO BUYERCOMPANY
MNETSENT ALN 12 Y PO MNETSENT
ECOMERROR ALN 254 Y PO ECOMERROR
ECOMSTATUSDATE DATETIME 10 Y PO ECOMSTATUSDATE
SOURCESYSID ALN 10 Y PO SOURCESYSID
OWNERSYSID ALN 10 Y PO OWNERSYSID
EXTERNALREFID ALN 10 Y PO EXTERNALREFID
SENDERSYSID ALN 50 Y PO SENDERSYSID
ITEMNUM UPPER 30 Y POLINE ITEMNUM
STORELOC UPPER 8 Y POLINE STORELOC
CATALOGCODE ALN 30 Y POLINE CATALOGCODE
ORDERQTY DECIMAL 15 Y POLINE ORDERQTY
ORDERUNIT ALN 8 Y POLINE ORDERUNIT
UNITCOST DECIMAL 10 Y POLINE UNITCOST
CONVERSION DECIMAL 15 Y POLINE CONVERSION
RECEIVEDQTY DECIMAL 15 Y POLINE RECEIVEDQTY
RECEIVEDUNITCOST DECIMAL 10 Y POLINE RECEIVEDUNITCOST
RECEIVEDTOTALCOST DECIMAL 10 Y POLINE RECEIVEDTOTALCOST
178
REJECTEDQTY DECIMAL 15 Y POLINE REJECTEDQTY
VENDELIVERYDATE DATE 4 Y POLINE VENDELIVERYDATE
TAXED ALN 1 Y POLINE TAXED
ENTERDATE DATE 4 Y POLINE ENTERDATE
ENTERBY ALN 18 Y POLINE ENTERBY
DESCRIPTION ALN 80 Y POLINE DESCRIPTION
PL4 DECIMAL 15 Y POLINE PL4
WONUM ALN 10 Y POLINE WONUM
REQUESTEDBY UPPER 18 Y POLINE REQUESTEDBY
REQDELIVERYDATE DATE 4 Y POLINE REQDELIVERYDATE
POLINENUM INTEGER 4 Y POLINE POLINENUM
WPOPERATION INTEGER 4 Y POLINE WPOPERATION
PLIN4 DATE 4 Y POLINE PLIN4
PLIN5 DECIMAL 15 Y POLINE PLIN5
179
Chapter 3
PCARDNUM ALN 30 Y POLINE PCARDNUM
PCARDTYPE ALN 20 Y POLINE PCARDTYPE
PCARDEXPDATE ALN 7 Y POLINE PCARDEXPDATE
PCARDVERIFICATION ALN 4 Y POLINE PCARDVERIFICATION
EQNUM ALN 8 Y POLINE EQNUM
CHARGESTORE UPPER 1 Y POLINE CHARGESTORE
GLDEBITACCT ALN 20 Y POLINE GLDEBITACCT
GLCREDITACCT ALN 20 Y POLINE GLCREDITACCT
LINECOST DECIMAL 10 Y POLINE LINECOST
LINECOST2 DECIMAL 10 Y POLINE LINECOST
180
SCHARGECODE UPPER 8 Y POLINE SCHARGECODE
RECEIPTREQD YORN 1 Y POLINE RECEIPTREQD
MANUFACTURER ALN 8 Y POLINE MANUFACTURER
SERVICE UPPER 1 Y POLINE SERVICE
SUPERVISOR ALN 8 Y POLINE SUPERVISOR
CATEGORY UPPER 4 Y POLINE CATEGORY
REMARK ALN 50 Y POLINE REMARK
LOCATION UPPER 8 Y POLINE LOCATION
LOADEDCOST DECIMAL 10 Y POLINE LOADEDCOST
PRORATESERVICE ALN 1 Y POLINE PRORATESERVICE
AGREEMENTPONUM ALN 8 Y POLINE AGREEMENTPONUM
AGREEMENTPOTYPE ALN 6 Y POLINE AGREEMENTPOTYPE
RECEIPTSCOMPLETE ALN 1 Y POLINE RECEIPTSCOMPLETE
INSPECTIONREQUIRED ALN 1 Y POLINE INSPECTIONREQUIRED
PRORATECOST DECIMAL 10 Y POLINE PRORATECOST
181
Chapter 3
POLINEID DECIMAL 10 Y POLINE POLINEID
PRNUM ALN 8 Y PR PRNUM
MRNUM ALN 8 Y POLINE MRNUM
MRLINENUM INTEGER 4 Y POLINE MRLINENUM
CO4 DECIMAL 10 Y COMPANIES CO4
CO5 DATE 10 Y COMPANIES CO5
182
CO13 DECIMAL 15 Y COMPANIES CO13
COMPANYLOC ALN 8 Y COMPANIES LOCATION
REGISTRATION2 UPPER 20 Y COMPANIES REGISTRATION2
PAYVENDOR ALN 8 Y COMPANIES PAYVENDOR
BANKACCOUNT ALN 20 Y COMPANIES BANKACCOUNT
ROWSTAMP ALN 40 Y
ITEMDESCRIPTION ALN 80 Y ITEM DESCRIPTION
LOTTYPE ALN 5 Y ITEM LOTTYPE
183
Chapter 3
CAPITALIZED ALN 1 Y ITEM CAPITALIZED
POLONGDESC ALN 2000 Y
POLINELONGDESC ALN 2000 Y
USERDATA1 ALN 1 Y
USERDATA2 ALN 1 Y
USERDATA3 ALN 1 Y
USERDATA4 ALN 1 Y
USERDATA5 ALN 1 Y
USERDATA6 ALN 1 Y
USERDATA7 ALN 1 Y
USERDATA8 ALN 1 Y
USERDATA9 ALN 1 Y
USERDATA10 ALN 1 Y
MKTPLCITEM YORN 1 Y POLINE MKTPLCITEM
VENDORPACKCODE ALN 12 Y POLINE VENDORPACKCODE
VENDORPACKQUANTI VENDORPACKQUANTIT
TY ALN 12 Y POLINE Y
VENDORWAREHOUSE ALN 12 Y POLINE VENDORWAREHOUSE
BATCHID ALN 25 Y
184
UTRANSTYPE ALN 25 Y
APISITE ALN 256 Y
IMPORTTIMESTAMP DATE 4 Y
185
Chapter 3
MOUT_RCV_INTERFACE Table
MAXIMO sends data to the MOUT_RCV_INTERFACE table from two tables:
MATRECTRANS and SERVRECTRANS. Data is transferred to the external
financial application.
The following table shows the mapping for the MOUT_RCV_INTERFACE and
MATRECTRANS tables. The mappings displayed are the defaults, and do not
necessarily reflect your values. Your MAXIMO system catalogue determines
your values.
MOUT_RCV_INTERFACE Table MATRECTRANS Table
TOSTORELOC UPPER 8 Y TOSTORELOC
ACTUALDATE DATETIME 10 Y ACTUALDATE
RECEIVEDUNIT ALN 8 Y RECEIVEDUNIT
ISSUETYPE UPPER 8 Y ISSUETYPE
ACTUALCOST AMOUNT 10 Y ACTUALCOST
REJECTCODE UPPER 6 Y REJECTCODE
186
REJECTCOST DECIMAL 15 Y
CONVERSION DECIMAL 15 Y CONVERSION
IT1 ALN 10 Y IT1
IT2 ALN 10 Y IT2
IT3 ALN 10 Y IT3
IT4 DECIMAL 15 Y IT4
IT5 ALN 10 Y IT5
OUTSIDE YORN 1 Y OUTSIDE
ISSUETO UPPER 8 Y ISSUETO
PACKINGSLIPNUM ALN 20 Y PACKINGSLIPNUM
ISSUE YORN 1 Y ISSUE
REQUESTEDBY ALN 20 Y REQUESTEDBY
TOTALCURBAL AMOUNT 15 Y TOTALCURBAL
OLDAVGCOST AMOUNT 10 Y OLDAVGCOST
ITIN3 ALN 1 Y ITIN3
187
Chapter 3
TOBIN ALN 8 Y TOBIN
LOTNUM UPPER 8 Y LOTNUM
LINECOST AMOUNT 10 N LINECOST
LINECOST2 AMOUNT 10 N LINECOST2
CURRENCYCODE2 UPPER 8 Y MAXVAR
MANUFACTURER UPPER 8 Y MANUFACTURER
MODELNUM ALN 8 Y MODELNUM
FROMBIN ALN 8 Y FROMBIN
QTYHELD DECIMAL 15 Y QTYHELD
CLAIMNUM UPPER 8 Y
188
APPROVED YORN 1 Y
APPROVEDATE DATETIME 10 Y
APPROVEBY UPPER 18 Y
LONGDESC ALN 2000 Y
ROWSTAMP ALN 40 N
FROMLOT ALN 8 Y FROMLOT
TOLOT ALN 8 Y TOLOT
LOADEDCOST AMOUNT 10 N LOADEDCOST
TAX1 AMOUNT 10 Y TAX1
PRORATED ALN 1 N PRORATED
PRORATECOST AMOUNT 10 Y PRORATECOST
STATUS ALN 8 Y STATUS
STATUSDATE DATETIME 10 Y STATUSDATE
189
Chapter 3
STATUSCHANGEBY ALN 18 Y STATUSCHANGEBY
CURBAL AMOUNT 15 N CURBAL
INVOICEDQTY AMOUNT 15 Y FUTURE
MRNUM ALN 8 Y MRNUM
MATRECTRANSID NUMBER 10 Y MATRECTRANSID
SERVRECTRANSID INTEGER 4 Y
QTYREQUESTED DECIMAL 15 Y QTYREQUESTED
IT6 ALN 10 Y IT6
IT7 ALN 10 Y IT7
IT8 ALN 10 Y IT8
IT9 ALN 10 Y IT9
IT10 ALN 10 Y IT10
190
RECID ALN 1 Y
ROLLUP ALN 1 Y
USERDATA1 ALN 1 Y
USERDATA2 ALN 1 Y
USERDATA3 ALN 1 Y
USERDATA4 ALN 1 Y
USERDATA5 ALN 1 Y
USERDATA6 ALN 1 Y
USERDATA7 ALN 1 Y
USERDATA8 ALN 1 Y
USERDATA9 ALN 1 Y
USERDATA10 ALN 1 Y
BATCHID ALN 25 Y
UTRANSTYPE ALN 25 Y
APISITE ALN 256 Y
191
Chapter 3
The following table shows the mapping for MOUT_RCV_INTERFACE and

SERVRECTRANS. The mappings displayed are the defaults, and do not
necessarily reflect your values. Your MAXIMO system catalogue determines
your values.
MOUT_RCV_INTERFACE Table SERVRECTRANS Table
ITEMNUM UPPER 30 Y
TOSTORELOC UPPER 8 Y
ACTUALDATE DATETIME 10 Y ENTERDATE
RECEIVEDUNIT ALN 8 Y
ISSUETYPE UPPER 8 Y
ACTUALCOST AMOUNT 10 Y
REJECTCODE UPPER 6 Y
REJECTCOST DECIMAL 15 Y REJECTCOST
CONVERSION DECIMAL 15 Y
192
IT1 ALN 10 Y SS1
IT2 ALN 10 Y
IT3 ALN 10 Y
IT4 DECIMAL 15 Y
IT5 ALN 10 Y
OUTSIDE YORN 1 Y WPOPERATION
ISSUETO UPPER 8 Y
PACKINGSLIPNUM ALN 20 Y
ISSUE YORN 1 Y
REQUESTEDBY ALN 20 Y
ITIN3 ALN 1 Y SSPL3
TOBIN ALN 8 Y
LOTNUM UPPER 8 Y
193
Chapter 3
LINECOST AMOUNT 10 N LINECOST
LINECOST2 AMOUNT 10 N LINECOST2
CURRENCYCODE2 UPPER 8 Y MAXVAR
MANUFACTURER UPPER 8 Y
MODELNUM ALN 8 Y
FROMBIN ALN 8 Y
QTYHELD DECIMAL 15 Y
APPROVED YORN 1 Y APPROVED
APPROVEDATE DATETIME 10 Y APPROVEDATE
APPROVEBY UPPER 18 Y APPROVEBY
194
LONGDESC ALN 2000 Y
ROWSTAMP ALN 40 N
FROMLOT ALN 8 Y
TOLOT ALN 8 Y
LOADEDCOST AMOUNT 10 N
TAX1CODE ALN 8 Y
TAX1 AMOUNT 10 Y
TAX2CODE ALN 8 Y
TAX2 AMOUNT 10 Y
TAX3CODE ALN 8 Y
TAX3 AMOUNT 10 Y
TAX4CODE ALN 8 Y
TAX4 AMOUNT 10 Y
TAX5CODE ALN 8 Y
TAX5 AMOUNT 10 Y
PRORATED ALN 1 N
PRORATECOST AMOUNT 10 Y
STATUS ALN 8 Y
STATUSDATE DATETIME 10 Y
STATUSCHANGEBY ALN 18 Y
CURBAL AMOUNT 15 N
INVOICEDQTY AMOUNT 15 Y
195
Chapter 3
MRNUM ALN 8 Y MRNUM
MATRECTRANSID NUMBER 10 Y
SERVRECTRANSID INTEGER 4 Y SERVRECTRANSID
QTYREQUESTED DECIMAL 15 Y
IT6 ALN 10 Y
IT7 ALN 10 Y
IT8 ALN 10 Y
IT9 ALN 10 Y
IT10 ALN 10 Y
ITIN4 ALN 10 Y
ITIN5 ALN 10 Y
ITIN6 ALN 10 Y
ITIN7 ALN 10 Y
RECID ALN 1 Y
ROLLUP ALN 1 Y ROLLUP
USERDATA1 ALN 1 Y
196
USERDATA2 ALN 1 Y
USERDATA3 ALN 1 Y
USERDATA4 ALN 1 Y
USERDATA5 ALN 1 Y
USERDATA6 ALN 1 Y
USERDATA7 ALN 1 Y
USERDATA8 ALN 1 Y
USERDATA9 ALN 1 Y
USERDATA10 ALN 1 Y
BATCHID ALN 25 Y
UTRANSTYPE ALN 25 Y
APISITE ALN 256 Y
197
Chapter 3
Item Interface Tables

This section provides the mapping for the interface tables that the APIs use to
transfer item data between MAXIMO and Oracle Financials.
The values displayed in the following tables are examples, and do not necessarily
reflect your actual values. Your MAXIMO system catalogue determines your
values.
MAX_ITM_INTERFACE
The MAX_ITM_INTERFACE table receives item data from Oracle Financials
and sends it to the following MAXIMO tables. It also receives item data from the
following MAXIMO tables and transfers it to Oracle Financials.
Note that the CHANGEBY column in the MAX_ITM_INTERFACE table maps
to both the CHANGEBY column in the COMPANIES table and the ENTERBY
column in the INVTRANS table.
MAX_ITM_INTERFACE Table MAXIMO Tables
ITEMNUM UPPER 8 N ITEM ITEMNUM
DESCRIPTION ALN 50 Y ITEM DESCRIPTION
ROTATING YORN 1 Y ITEM ROTATING
MSDSNUM ALN 10 Y ITEM MSDSNUM
OUTSIDE YORN 1 Y ITEM OUTSIDE
198
IN1 ALN 10 Y ITEM IN1
IN9 AMOUNT 10 Y ITEM IN9
IN10 DATETIME 10 Y ITEM IN10
IN11 DECIMAL 15.2 Y ITEM IN11
IN14 INTEGER 4 Y ITEM IN14
IN15 YORN 1 Y ITEM IN15
IN17 AMOUNT 10.2 Y ITEM IN17
199
Chapter 3
TAX1CODE UPPER 8 Y ITEM TAX1CODE
SPAREPARTAUTOADD ALN 1 Y ITEM SPAREPARTAUTOADD
HAZARDID ALN 8 Y ITEM HAZARDID
CLASSSTRUCTUREID ALN 8 Y ITEM CLASSSTRUCTUREID
INSPECTIONREQUIRED ALN 1 Y ITEM INSPECTIONREQUIRED
LDKEY INTEGER 4 Y ITEM LDKEY
LOCATION UPPER 8 Y INVENTORY LOCATION
BINNUM ALN 8 Y INVENTORY BINNUM
MINLEVEL DECIMAL 15 Y INVENTORY MINLEVEL
MAXLEVEL DECIMAL 15 Y INVENTORY MAXLEVEL
CATEGORY UPPER 4 Y INVENTORY CATEGORY
ORDERUNIT ALN 8 Y INVENTORY ORDERUNIT
200
CONVERSION DECIMAL 15 Y INVENTORY CONVERSION
QUANTITY DECIMAL 15 Y INVTRANS QUANTITY
LOTNUM UPPER 8 Y INVBALANCES LOTNUM
CURBAL DECIMAL 15 Y INVTRANS CURBAL
PHYSCNT DECIMAL 15 Y INVBALANCES PHYSCNT
PHYSCNTDATE DATETIME 10 Y INVBALANCES PHYSCNTDATE
IB1 ALN 1 Y INVBALANCES IB1
RECONCILED YORN 1 Y INVBALANCES RECONCILED
ORDERQTY DECIMAL 15 Y INVENTORY ORDERQTY
STDCOST AMOUNT 10 Y INVENTORY STDCOST
AVGCOST AMOUNT 10 Y INVENTORY AVGCOST
LASTCOST AMOUNT 10 Y INVENTORY LASTCOST
COSTCURRENCYCODE ALN 8 EXCHANGE CURRENCYCODE
COSTCURRENCYCODE2 ALN 8 EXCHANGE CURRENCYCODE
EXCHANGERATE2 DECIMAL 12.5 EXCHANGE EXCHANGERATE
LASTISSUEDATE DATETIME 10 Y INVENTORY LASTISSUEDATE
ISSUEYTD DECIMAL 15 Y INVENTORY ISSUEYTD
ISSUE1YRAGO DECIMAL 15 Y INVENTORY ISSUE1YRAGO
201
Chapter 3
ABCTYPE UPPER 1 Y INVENTORY ABCTYPE
CCF INTEGER 4 Y INVENTORY CCF
SSTOCK DECIMAL 15 Y INVENTORY SSTOCK
DELIVERYTIME INTEGER 4 Y INVENTORY DELIVERYTIME
IL1 ALN 10 Y INVENTORY IL1
IL4 DATETIME 10 Y INVENTORY IL4
IL5 DECIMAL 15.2 Y INVENTORY IL5
GLACCOUNT ALN 20 Y INVENTORY GLACCOUNT
CONTROLACC ALN 20 Y INVENTORY CONTROLACC
SHRINKAGEACC ALN 20 Y INVENTORY SHRINKAGEACC
INVCOSTADJACC ALN 20 Y INVENTORY INVCOSTADJACC
VENDOR UPPER 8 Y INVVENDOR VENDOR
202
MANUFACTURER UPPER 8 Y INVVENDOR MANUFACTURER
MODELNUM ALN 8 Y INVVENDOR MODELNUM
CATALOGCODE ALN 12 Y INVVENDOR CATALOGCODE
IV1 ALN 10 Y INVVENDOR IV1
IVCO1 ALN 10 Y INVVENDOR IVCO1
IVCO2 DATETIME 10 Y INVVENDOR IVCO2
IVCO3 DECIMAL 15.2 Y INVVENDOR IVCO3
BIDPRICE DECIMAL 10 Y INVVENDOR BIDPRICE
BIDDATE DATETIME 10 Y INVVENDOR BIDDATE
PROMDELIVERYTIME INTEGER 4 Y INVVENDOR PROMDELIVERYTIME
VENDORLASTCOST DECIMAL 10 Y INVVENDOR LASTCOST
LASTDATE DATETIME 10 Y INVVENDOR LASTDATE
CATALOGWEBPAGE ALN 124 Y INVVENDOR CATALOGWEBPAGE
203
Chapter 3
CONTACT ALN 50 Y COMPANIES CONTACT
FOB ALN 20 Y COMPANIES FOB
FREIGHTTERMS ALN 50 Y COMPANIES FREIGHTTERMS
SHIPVIA ALN 20 Y COMPANIES SHIPVIA
PAYMENTTERMS ALN 20 Y COMPANIES PAYMENTTERMS
CUSTOMERNUM ALN 16 Y COMPANIES CUSTOMERNUM
CO9 INTERGER 4 Y COMPANIES CO9
204
LO2 ALN 10 Y LOCATIONS LO2
LO9 DECIMAL 10.2 Y LOCATIONS LO9
LO10 DATETIME 10 Y LOCATIONS LO10
LO14 DECIMAL 38 Y LOCATIONS LO14
CHANGEBY UPPER 18 Y COMPANIES CHANGEBY
CHANGEDATE DATETIME 10 Y COMPANIES CHANGEDATE
205
Chapter 3
INCLUSIVE1 YORN 1 Y COMPANIES INCLUSIVE1
CURRENCYCODE UPPER 8 Y COMPANIES CURRENCYCODE
DISABLED YORN 1 Y COMPANIES DISABLED
206
PAYONRECEIPT ALN 1 Y COMPANIES PAYONRECEIPT
OLDCONTROLACC ALN 20 Y LOCATIONS OLDCONTROLACC
OLDSHRINKAGEACC ALN 20 Y LOCATIONS OLDSHRINKAGEACC
OLDINVCOSTAJDACC ALN 20 Y LOCATIONS OLDINVCOSTAJDACC
GISPARAM1 ALN 1 Y LOCATIONS GISPARAM1
LOC_DISABLED ALN 1 Y LOCATIONS DISABLED
ISDEFAULT ALN 1 Y INVVENDOR ISDEFAULT
LODESC ALN 50 Y LOCATIONS DESCRIPTION
PURCHVARACC ALN 20 Y LOCATIONS PURCHVARACC
INVOICEVARACC ALN 20 Y LOCATIONS INVOICEVARACC
CURVARACC ALN 20 Y LOCATIONS CURVARACC
207
Chapter 3
RECEIPTVARACC ALN 20 Y LOCATIONS RECEIPTVARACC
LONGDESC ALN 2000 Y
USERDATA1 ALN 1 Y
USERDATA2 ALN 1 Y
USERDATA3 ALN 1 Y
USERDATA4 ALN 1 Y
USERDATA5 ALN 1 Y
USERDATA6 ALN 1 Y
USERDATA7 ALN 1 Y
USERDATA8 ALN 1 Y
USERDATA9 ALN 1 Y
USERDATA10 ALN 1 Y
BATCHID ALN 25 Y
UTRANSTYPE ALN 25 Y
ITEM_SOURCESYSID ALN 10 Y ITEM SOURCESYSID
ITEM_OWNERSYSID ALN 10 Y ITEM OWNERSYSID
ITEM_EXTERNALREFID ALN 10 Y ITEM EXTERNALREFID
INV_SOURCESYSID ALN 10 Y INVENTORY SOURCESYSID
INV_OWNERSYSID ALN 10 Y INVENTORY OWNERSYSID
208
INV_EXTERNALREFID ALN 10 Y INVENTORY EXTERNALREFID
BAL_SOURCESYSID ALN 10 Y INVBALANCES SOURCESYSID
BAL_OWNERSYSID ALN 10 Y INVBALANCES OWNERSYSID
BAL_EXTERNALREFID ALN 10 Y INVBALANCES EXTERNALREFID
VND_SOURCESYSID ALN 10 Y INVVENDOR SOURCESYSID
VND_OWNERSYSID ALN 10 Y INVVENDOR OWNERSYSID
VND_EXTERNALREFID ALN 10 Y INVVENDOR EXTERNALREFID
COMP_SOURCESYSID ALN 10 Y COMPANIES SOURCESYSID
COMP_OWNERSYSID ALN 10 Y COMPANIES OWNERSYSID
COMP_EXTERNALREFID ALN 10 Y COMPANIES EXTERNALREFID
LOC_SOURCESYSID ALN 10 Y LOCATIONS SOURCESYSID
LOC_OWNERSYSID ALN 10 Y LOCATIONS OWNERSYSID
LOC_EXTERNALREFID ALN 10 Y LOCATIONS EXTERNALREFID
SOURCEID ALN 25 Y SOURCE SOURCEID
APISEQ INTEGER 4 Y SOURCE APISEQ
SENDERSYSID ALN 50 Y ITEM SENDERSYSID
APISITE ALN 256 Y SOURCE APISITE
209
Chapter 3
210
MOUT_RSV_INTERFACE Table
The MOUT_RSV_INTERFACE table receives material reservation data from the
following MAXIMO tables when they are created for a work order that is sent to
the external application.
MOUT_RSV_INTERFACE Table MAXIMO Tables
REQUESTNUM UPPER 8 N INVRESERVE REQUESTNUM
ITEMNUM UPPER 8 N INVRESERVE ITEMNUM
LOCATION UPPER 8 N INVRESERVE LOCATION
WONUM UPPER 10 Y INVRESERVE WONUM
WPOPERATION INTEGER 4 Y INVRESERVE WPOPERATION
ACTUALQTY DECIMAL 15.2 N INVRESERVE ACTUALQTY
RESERVEDQTY DECIMAL 15.2 N INVRESERVE RESERVEDQTY
INITFLAG YORN 1 N INVRESERVE INITFLAG
DIRECTREQ YORN 1 N INVRESERVE DIRECTREQ
GLACCOUNT ALN 20 Y INVRESERVE GLACCOUNT
REQUESTEDBY ALN 20 Y INVRESERVE REQUESTEDBY
REQUESTEDDATE DATETIME 10 Y INVRESERVE REQUESTEDDATE
REQUIREDDATE DATETIME 10 Y INVRESERVE REQUIREDDATE
PONUM UPPER 8 Y INVRESERVE PONUM
POLINENUM INTEGER 4 Y INVRESERVE POLINENUM
DELLOCATION UPPER 8 Y INVRESERVE DELLOCATION
211
Chapter 3
DESCRIPTION ALN 50 Y INVRESERVE DESCRIPTION
IR1 ALN 10 Y INVRESERVE IR1
IR4 DATETIME 10 Y INVRESERVE IR4
IR5 AMOUNT 15.2 Y INVRESERVE IR5
POLINEID INTEGER 4 Y INVRESERVE POLINEID
MRNUM ALN 8 Y INVRESERVE MRNUM
MRLINENUM INTEGER 4 Y INVRESERVE MRLINENUM
SOURCESYSID ALN 10 Y INVRESERVE SOURCESYSID
OWNERSYSID ALN 10 Y INVRESERVE OWNERSYSID
EXTERNALREFID ALN 10 Y INVRESERVE EXTERNALREFID
ISSUETO ALN 8 Y
APISEQ INTEGER 4 Y INVRESERVE APISEQ
SENDERSYSID ALN 50 Y INVRESERVE SENDERSYSID
212
VENDOR UPPER 8 Y INVENTORY VENDOR
MANUFACTURER UPPER 8 Y INVENTORY MANUFACTURER
MODELNUM ALN 8 Y INVENTORY MODELNUM
CATALOGCODE ALN 12 Y INVENTORY CATALOGCODE
CATEGORY UPPER 4 N INVENTORY CATEGORY
213
Chapter 3
CONVERSION DECIMAL 15.2 N INVENTORY CONVERSION
STDCOST AMOUNT 10.2 N INVENTORY STDCOST
AVGCOST AMOUNT 10.2 N INVENTORY AVGCOST
PARENT UPPER 10 Y WORKORDER MASTERWONUM
STATUS UPPER 8 N WORKORDER STATUS
STATUSDATE DATETIME 10 N WORKORDER STATUSDATE
WORKTYPE UPPER 5 Y WORKORDER WORKTYPE
LEADCRAFT UPPER 8 Y WORKORDER LEADCRAFT
WODESC ALN 50 Y WORKORDER DESCRIPTION
EQNUM UPPER 8 Y WORKORDER EQNUM
WOLOCATION UPPER 8 Y WORKORDER LOCATION
JPNUM UPPER 10 Y WORKORDER JPNUM
FAILDATE DATETIME 10 Y WORKORDER FAILDATE
CHANGEBY UPPER 18 Y WORKORDER CHANGEBY
CHANGEDATE DATETIME 10 Y WORKORDER CHANGEDATE
PMNUM UPPER 8 Y WORKORDER PMNUM
HISTORYFLAG YORN 1 N WORKORDER HISTORYFLAG
CONTRACT UPPER 8 Y WORKORDER CONTRACT
WOPRIORITY INTEGER 4 Y WORKORDER WOPRIORITY
214
WOPM6 ALN 10 Y WORKORDER WOPM6
WOPM7 AMOUNT 15.2 Y WORKORDER WOPM7
TARGCOMPDATE DATETIME 10 Y WORKORDER TARGCOMPDATE
TARGSTARTDATE DATETIME 10 Y WORKORDER TARGSTARTDATE
WOEQ1 ALN 10 Y WORKORDER WOEQ1
WOEQ5 AMOUNT 10.2 Y WORKORDER WOEQ5
WOEQ6 DATETIME 10 Y WORKORDER WOEQ6
WO1 ALN 10 Y WORKORDER WO1
215
Chapter 3
REPORTEDBY ALN 18 Y WORKORDER REPORTEDBY
REPORTDATE DATETIME 10 Y WORKORDER REPORTDATE
PHONE ALN 15 Y WORKORDER PHONE
PROBLEMCODE UPPER 8 Y WORKORDER PROBLEMCODE
CALENDAR UPPER 8 Y WORKORDER CALENDAR
INTERRUPTABLE YORN 1 Y WORKORDER INTERRUPTABLE
ACTSTART DATETIME 10 Y WORKORDER ACTSTART
ACTFINISH DATETIME 10 Y WORKORDER ACTFINISH
SCHEDSTART DATETIME 10 Y WORKORDER SCHEDSTART
SCHEDFINISH DATETIME 10 Y WORKORDER SCHEDFINISH
CREWID ALN 8 Y WORKORDER CREWID
SUPERVISOR UPPER 8 Y WORKORDER SUPERVISOR
216
WOJP1 ALN 10 Y WORKORDER WOJP1
WOJP4 AMOUNT 10.2 Y WORKORDER WOJP4
WOJP5 DATETIME 10 Y WORKORDER WOJP5
WOL1 ALN 10 Y WORKORDER WOL1
WOL3 AMOUNT 10.2 Y WORKORDER WOL3
WOL4 DATETIME 10 Y WORKORDER WOL4
RESPONDBY DATETIME 10 Y WORKORDER RESPONDBY
EQLOCPRIORITY INTEGER 4 Y WORKORDER EQLOCPRIORITY
CALCPRIORITY INTEGER 4 Y WORKORDER CALCPRIORITY
CHARGESTORE YORN 1 N WORKORDER CHARGESTORE
FAILURECODE UPPER 8 Y WORKORDER FAILURECODE
WOLO1 ALN 10 Y WORKORDER WOLO1
WOLO6 AMOUNT 10.2 Y WORKORDER WOLO6
WOLO7 DATETIME 10 Y WORKORDER WOLO7
217
Chapter 3
WOLO10 INTEGER 4 Y WORKORDER WOLO10
DISABLED YORN 1 Y WORKORDER DISABLED
CURRENCYCODE UPPER 8 Y CURRENCY CURRENCYCODE
CURRENCYCODE2 UPPER 8 Y CURRENCY CURRENCYCODE
ROWSTAMP ALN 40 Y
USERDATA1 ALN 1 Y
USERDATA2 ALN 1 Y
USERDATA3 ALN 1 Y
USERDATA4 ALN 1 Y
USERDATA5 ALN 1 Y
USERDATA6 ALN 1 Y
USERDATA7 ALN 1 Y
USERDATA8 ALN 1 Y
USERDATA9 ALN 1 Y
USERDATA10 ALN 1 Y
BATCHID ALN 25 Y
218
UTRANSTYPE ALN 25 Y
SOURCEID ALN 25 Y INVRESERVE SOURCEID
APISITE ALN 256 Y
219
Chapter 3
Inventory Confirmation Tables

MAX_ICF_INTERFACE Table
The MAX_ICF_INTERFACE table receives inventory confirmation data from
Oracle Financials and sends it to the following MAXIMO tables.
REQUESTNUM UPPER 8 N INVRESERVE REQUESTNUM
ITEMNUM UPPER 8 N INVRESERVE ITEMNUM
LOCATION UPPER 8 N INVRESERVE LOCATION
WONUM UPPER 10 Y INVRESERVE WONUM
WPOPERATION INTEGER 4 Y INVRESERVE WPOPERATION
ACTUALQTY DECIMAL 15.2 N INVRESERVE ACTUALQTY
RESERVEDQTY DECIMAL 15.2 N INVRESERVE RESERVEDQTY
INITFLAG YORN 1 N INVRESERVE INITFLAG
DIRECTREQ YORN 1 N INVRESERVE DIRECTREQ
GLACCOUNT ALN 20 Y INVRESERVE GLACCOUNT
REQUESTEDBY ALN 20 Y INVRESERVE REQUESTEDBY
REQUESTEDDATE DATETIME 10 Y INVRESERVE REQUESTEDDATE
REQUIREDDATE DATETIME 10 Y INVRESERVE REQUIREDDATE
PONUM UPPER 8 Y INVRESERVE PONUM
POLINENUM INTEGER 4 Y INVRESERVE POLINENUM
220
DESCRIPTION ALN 50 Y INVRESERVE DESCRIPTION
IR4 DATETIME 10 Y INVRESERVE IR4
IR5 AMOUNT 15.2 Y INVRESERVE IR5
POLINEID INTEGER 4 Y INVRESERVE POLINEID
MRNUM ALN 8 Y INVRESERVE MRNUM
MRLINENUM INTEGER 4 Y INVRESERVE MRLINENUM
SOURCESYSID ALN 10 Y INVRESERVE SOURCESYSID
OWNERSYSID ALN 10 Y INVRESERVE OWNERSYSID
EXTERNALREFID ALN 10 Y INVRESERVE EXTERNALREFID
ISSUETO ALN 8 Y
APISEQ INTEGER 4 Y INVRESERVE APISEQ
SENDERSYSID ALN 50 Y INVRESERVE SENDERSYSID
221
Chapter 3
VENDOR UPPER 8 Y INVENTORY VENDOR
MANUFACTURER UPPER 8 Y INVENTORY MANUFACTURER
MODELNUM ALN 8 Y INVENTORY MODELNUM
CATALOGCODE ALN 12 Y INVENTORY CATALOGCODE
CATEGORY UPPER 4 N INVENTORY CATEGORY
222
CONVERSION DECIMAL 15.2 N INVENTORY CONVERSION
STDCOST AMOUNT 10.2 N INVENTORY STDCOST
AVGCOST AMOUNT 10.2 N INVENTORY AVGCOST
PARENT UPPER 10 Y WORKORDER MASTERWONUM
STATUS UPPER 8 N WORKORDER STATUS
STATUSDATE DATETIME 10 N WORKORDER STATUSDATE
WORKTYPE UPPER 5 Y WORKORDER WORKTYPE
LEADCRAFT UPPER 8 Y WORKORDER LEADCRAFT
WODESC ALN 50 Y WORKORDER DESCRIPTION
EQNUM UPPER 8 Y WORKORDER EQNUM
WOLOCATION UPPER 8 Y WORKORDER LOCATION
JPNUM UPPER 10 Y WORKORDER JPNUM
FAILDATE DATETIME 10 Y WORKORDER FAILDATE
CHANGEBY UPPER 18 Y WORKORDER CHANGEBY
CHANGEDATE DATETIME 10 Y WORKORDER CHANGEDATE
PMNUM UPPER 8 Y WORKORDER PMNUM
HISTORYFLAG YORN 1 N WORKORDER HISTORYFLAG
CONTRACT UPPER 8 Y WORKORDER CONTRACT
223
Chapter 3
WOPRIORITY INTEGER 4 Y WORKORDER WOPRIORITY
TARGCOMPDATE DATETIME 10 Y WORKORDER TARGCOMPDATE
TARGSTARTDATE DATETIME 10 Y WORKORDER TARGSTARTDATE
224
REPORTEDBY ALN 18 Y WORKORDER REPORTEDBY
REPORTDATE DATETIME 10 Y WORKORDER REPORTDATE
PHONE ALN 15 Y WORKORDER PHONE
PROBLEMCODE UPPER 8 Y WORKORDER PROBLEMCODE
CALENDAR UPPER 8 Y WORKORDER CALENDAR
INTERRUPTABLE YORN 1 Y WORKORDER INTERRUPTABLE
ACTSTART DATETIME 10 Y WORKORDER ACTSTART
ACTFINISH DATETIME 10 Y WORKORDER ACTFINISH
SCHEDSTART DATETIME 10 Y WORKORDER SCHEDSTART
SCHEDFINISH DATETIME 10 Y WORKORDER SCHEDFINISH
CREWID ALN 8 Y WORKORDER CREWID
SUPERVISOR UPPER 8 Y WORKORDER SUPERVISOR
225
Chapter 3
WOJP4 AMOUNT 10.2 Y WORKORDER WOJP4
WOJP5 DATETIME 10 Y WORKORDER WOJP5
WOL3 AMOUNT 10.2 Y WORKORDER WOL3
WOL4 DATETIME 10 Y WORKORDER WOL4
RESPONDBY DATETIME 10 Y WORKORDER RESPONDBY
EQLOCPRIORITY INTEGER 4 Y WORKORDER EQLOCPRIORITY
CALCPRIORITY INTEGER 4 Y WORKORDER CALCPRIORITY
CHARGESTORE YORN 1 N WORKORDER CHARGESTORE
FAILURECODE UPPER 8 Y WORKORDER FAILURECODE
226
WOLO7 DATETIME 10 Y WORKORDER WOLO7
WOLO10 INTEGER 4 Y WORKORDER WOLO10
DISABLED YORN 1 Y WORKORDER DISABLED
CURRENCYCODE UPPER 8 Y CURRENCY CURRENCYCODE
CURRENCYCODE2 UPPER 8 Y CURRENCY CURRENCYCODE
ROWSTAMP ALN 40 Y
USERDATA1 ALN 1 Y
USERDATA2 ALN 1 Y
USERDATA3 ALN 1 Y
USERDATA4 ALN 1 Y
USERDATA5 ALN 1 Y
USERDATA6 ALN 1 Y
USERDATA7 ALN 1 Y
USERDATA8 ALN 1 Y
USERDATA9 ALN 1 Y
USERDATA10 ALN 1 Y
BATCHID ALN 25 Y
227
Chapter 3
UTRANSTYPE ALN 25 Y
SOURCEID ALN 25 Y INVRESERVE SOURCEID
APISITE ALN 256 Y
228
Issues Data Tables

MAX_ISU_INTERFACE Table
The MAX_ISU_INTERFACE table receives item issues data from Oracle
Financials and sends it to the following MAXIMO tables.
MAX_ISU_INTERFACE Table MAXIMO Tables
ITEMNUM UPPER 30 Y MATUSETRANS ITEMNUM
STORELOC UPPER 8 Y MATUSETRANS STORELOC
TRANSDATE DATETIME 10 N MATUSETRANS TRANSDATE
ACTUALDATE DATETIME 10 N MATUSETRANS ACTUALDATE
QUANTITY DECIMAL 15.2 N MATUSETRANS QUANTITY
CURBAL DECIMAL 15.2 N MATUSETRANS CURBAL
PHYSCNT DECIMAL 15.2 N MATUSETRANS PHYSCNT
UNITCOST AMOUNT 10.2 N MATUSETRANS UNITCOST
ACTUALCOST AMOUNT 10.2 N MATUSETRANS ACTUALCOST
PONUM UPPER 8 Y MATUSETRANS PONUM
CONVERSION DECIMAL 15.2 N MATUSETRANS CONVERSION
WONUM UPPER 10 Y MATUSETRANS WONUM
EQNUM UPPER 8 Y MATUSETRANS EQNUM
ENTERBY UPPER 18 N MATUSETRANS ENTERBY
IT1 ALN 10 Y MATUSETRANS IT1
229
Chapter 3
IT4 DECIMAL 15.2 Y MATUSETRANS IT4
METERREADING DECIMAL 15.2 Y MATUSETRANS METERREADING
METERREADING2 DECIMAL 15.2 Y MATUSETRANS METERREADING2
MEMO ALN 254 Y MATUSETRANS MEMO
OUTSIDE YORN 1 Y MATUSETRANS OUTSIDE
WPOPERATION INTEGER 4 Y MATUSETRANS WPOPERATION
ISSUETO UPPER 8 Y MATUSETRANS ISSUETO
PACKINGSLIPNUM ALN 20 Y MATUSETRANS PACKINGSLIPNUM
POLINENUM INTEGER 4 Y MATUSETRANS POLINENUM
ROLLUP YORN 1 Y MATUSETRANS ROLLUP
ITIN1 ALN 10 Y MATUSETRANS ITIN1
BINNUM ALN 8 Y MATUSETRANS BINNUM
LOTNUM UPPER 8 Y MATUSETRANS LOTNUM
ISSUETYPE UPPER 8 N MATUSETRANS ISSUETYPE
GLDEBITACCT ALN 20 Y MATUSETRANS GLDEBITACCT
GLCREDITACCT ALN 20 Y MATUSETRANS GLCREDITACCT
LINECOST AMOUNT 10.2 N MATUSETRANS LINECOST
230
LINECOST2 AMOUNT 10.2 MATUSETRANS LINECOST2
FINANCIALPERIOD ALN 6 Y MATUSETRANS FINANCIALPERIOD
CURRENCYCODE UPPER 8 Y MATUSETRANS CURRENCYCODE
CURRENCYCODE2 UPPER 8 Y MATUSETRANS CURRENCYCODE2
CURRENCYUNITCOST DECIMAL 10.2 Y MATUSETRANS CURRENCYUNITCOST
ROTEQNUM UPPER 8 Y MATUSETRANS ROTEQNUM
CURRENCYLINECOST DECIMAL 10.2 Y MATUSETRANS CURRENCYLINECOST
LOCATION UPPER 8 Y MATUSETRANS LOCATION
DESCRIPTION ALN 80 Y MATUSETRANS DESCRIPTION
EXCHANGERATE DECIMAL 14.7 Y MATUSETRANS EXCHANGERATE
EXCHANGERATE2 DECIMAL 14.7 Y MATUSETRANS EXCHANGERATE2
SPAREPARTADDED ALN 1 Y MATUSETRANS SPAREPARTADDED
REQUESTNUM UPPER 8 Y INVRESERVE UPPER
DIRECTREQ YORN 1 Y INVRESERVE DIRECTREQ
IBUPD YORN 1 Y
MRNUM ALN 8 Y MRNUM
MATUSETRANSID INTEGER 4 Y MATUSETRANSID
MATRECTRANSID INTEGER 4 Y MATRECTRANSID
IT6 ALN 10 Y IT6
231
Chapter 3
IT7 ALN 10 Y IT7
IT8 ALN 10 Y IT8
IT9 ALN 10 Y IT9
IT10 ALN 10 Y IT10
IT11 ALN 10 Y IT11
IT12 ALN 10 Y IT12
APISEQ INTEGER 4 Y LABTRANS APISEQ
SENDERSYSID ALN 50 Y INVRESERVE ALN
ISSUEID INTEGER 4 Y
QTYREQUESTED DECIMAL 15.2 Y
QTYRETURNED DECIMAL 15.2 Y QTYREQUESTED
ROWSTAMP ALN 40 Y
USERDATA1 ALN 1 Y
232
USERDATA2 ALN 1 Y
USERDATA3 ALN 1 Y
USERDATA4 ALN 1 Y
USERDATA5 ALN 1 Y
USERDATA6 ALN 1 Y
USERDATA7 ALN 1 Y
USERDATA8 ALN 1 Y
USERDATA9 ALN 1 Y
USERDATA10 ALN 1 Y
BATCHID ALN 25 Y
UTRANSTYPE ALN 25 Y
SOURCEID ALN 25 Y LABTRANS SOURCEID
APISITE ALN 256 Y
233
Chapter 3
234
Vendor Interface Tables

transfer vendor data between MAXIMO and Oracle Financials.
reflect your actual values. Your MAXIMO system catalogue determines your
values.
MAX_COM_INTERFACE
The MAX_COM_INTERFACE table receives vendor data from Oracle
Financials and sends it to the following MAXIMO tables.
MAX_COM_INTERFACE Table MAXIMO Tables
COMPANY UPPER 8 N COMPANIES COMPANY
TYPE ALN 1 Y COMPANIES TYPE
CONTACT ALN 50 Y COMPANIES CONTACT
235
Chapter 3
PAYMENTTERMS ALN 20 Y COMPANIES PAYMENTTERMS
CHANGEBY UPPER 18 Y COMPANIES CHANGEBY
CHANGEDATE DATETIME 10 Y COMPANIES CHANGEDATE
236
TAX1CODE UPPER 8 Y COMPANIES TAX1CODE
CURRENCYCODE UPPER 8 Y COMPANIES CURRENCYCODE
LOCATION UPPER 8 Y COMPANIES LOCATION
LDKEY INTEGER Y COMPANIES LDKEY
237
Chapter 3
MNETUSERID ALN 50 Y COMPCONTACT MNETUSERID
MNETCOMPANYID ALN 8 Y COMPANIES MNETCOMPANYID
SOURCESYSID ALN 10 Y COMPANIES SOURCESYSID
OWNERSYSID ALN 10 Y COMPANIES OWNERSYSID
EXTERNALREFID ALN 10 Y COMPANIES EXTERNALREFID
238
VOICEPHONE ALN 20 Y COMPCONTACT VOICEPHONE
FAXPHONE ALN 20 Y COMPCONTACT FAXPHONE
EMAIL ALN 60 Y COMPCONTACT EMAIL
HOMEPHONE ALN 20 Y COMPCONTACT HOMEPHONE
PAGEPHONE ALN 30 Y COMPCONTACT PAGEPHONE
CNT1 ALN 1 Y COMPCONTACT CNT1
CNT4 DECIMAL 15.2 Y COMPCONTACT CNT4
CNT5 INTEGER 4 Y COMPCONTACT CNT5
PROCUREMENTCARDN PROCUREMENTCARDNU
UM ALN 30 Y COMPCONTACT M
PROCCARDEXPAIREDA PROCCARDEXPAIREDAT
TE DATETIME 4 Y COMPCONTACT E
LONGDESC ALN 2000 Y
PRIMARYCONTACT ALN 1 Y
PRIMARYREMIT ALN 1 Y
USERDATA1 ALN 1 Y
USERDATA2 ALN 1 Y
239
Chapter 3
USERDATA3 ALN 1 Y
USERDATA4 ALN 1 Y
USERDATA5 ALN 1 Y
USERDATA6 ALN 1 Y
USERDATA7 ALN 1 Y
USERDATA8 ALN 1 Y
USERDATA9 ALN 1 Y
USERDATA10 ALN 1 Y
BATCHID ALN 25 Y
UTRANSTYPE ALN 25 Y
SOURCEID ALN 25 Y SOURCE SOURCEID
APISEQ INTEGER 4 Y SOURCE APISEQ
APISITE ALN 256 Y SOURCE APISITE
SENDERSYSID ALN 50 Y COMPANIES SENDERSYSID
VENDORSENDSASN ALN 1 Y COMPANIES VENDORSENDSASN
VENDORSENDSINV ALN 1 Y COMPANIES VENDORSENDSINV
ECOMINTERFACE ALN 30 Y COMPANIES ECOMINTERFACE
MNETECOMNUM1 ALN 30 Y COMPANIES MNETECOMNUM1
240
VENDORSENDSSTATUS ALN 1 Y COMPANIES VENDORSENDSSTATUS
AUTOAPPROVEINV ALN 1 Y COMPANIES AUTOAPPROVEINV
AUTOSENDPOCANCEL ALN 1 Y COMPANIES AUTOSENDPOCANCEL
DEFAULTWAREHOUSE ALN 12 Y COMPANIES AUTOSENDPOCANCEL
AUTORECEIVEONASN ALN 1 Y COMPANIES AUTORECEIVEONASN
241
Chapter 3
Accounts Payable Interface Tables

transfer accounts payable data between MAXIMO and Oracle Financials.
reflect your values. Your MAXIMO system catalogue determines your values.
MOUT_AP_INTERFACE
MOUT_AP_INTERFACE receives invoice data from the following MAXIMO
tables. Data is transferred to Oracle Financials.
MOUT_AP_INTERFACE Table MAXIMO Tables
INVOICENUM UPPER 8 N INVOICE INVOICENUM
INVOICEDESC ALN 50 Y INVOICE DESCRIPTION
PONUM UPPER 8 Y INVOICE PONUM
VENDOR UPPER 8 N INVOICE VENDOR
CONTACT ALN 50 Y INVOICE CONTACT
PAYMENTTERMS ALN 20 Y INVOICE PAYMENTTERMS
CHECKCODE UPPER 8 Y INVOICE CHECKCODE
CHECKNUM UPPER 8 Y INVOICE CHECKNUM
CURRENCYCODE UPPER 8 Y INVOICE CURRENCYCODE
EXCHANGERATE DECIMAL 12 N INVOICE EXCHANGERATE
EXCHANGEDATE DATE 10 N INVOICE EXCHANGEDATE
DOCUMENTTYPE UPPER 8 N INVOICE DOCUMENTTYPE
242
ORIGINVOICENUM UPPER 8 Y INVOICE ORIGINVOICENUM
STATUS UPPER 7 N INVOICE STATUS
STATUSDATE DATETIME 10 N INVOICE STATUSDATE
APPROVALNUM ALN 8 Y INVOICE APPROVALNUM
INVOICEDATE DATETIME 10 N INVOICE INVOICEDATE
DISCOUNTDATE DATETIME 10 Y INVOICE DISCOUNTDATE
DUEDATE DATETIME 10 Y INVOICE DUEDATE
PAID DECIMAL 10 Y INVOICE PAID
PAIDDATE DATETIME 10 Y INVOICE PAIDDATE
ENTERDATE DATETIME 10 Y INVOICE ENTERDATE
ENTERBY UPPER 18 N INVOICE ENTERBY
CHANGEDATE DATETIME 10 Y INVOICE CHANGEDATE
CHANGEBY ALN 18 Y INVOICE CHANGEBY
HISTORYFLAG ALN 1 Y INVOICE HISTORYFLAG
TOTALTAX1 DECIMAL 12 N INVOICE TOTALTAX1
TAX1GL ALN 20 Y INVOICE TAX1GL
243
Chapter 3
INCLUSIVE1 YORN 1 N INVOICE INCLUSIVE1
DISCOUNT DECIMAL 10 Y INVOICE DISCOUNT
TOTALCOST DECIMAL 10 Y INVOICE TOTALCOST
INVOICE1 ALN 1 Y INVOICE INVOICE1
VENDORINVOICENUM ALN 12 Y INVOICE VENDORINVOICENUM
BASETOTALCOST NUMBER 10 Y INVOICE BASETOTALCOST
APSUSPENSEACCT ALN 20 Y INVOICE APSUSPENSEACCT
APCONTROLACCT ALN 20 Y INVOICE APCONTROLACCT
FINANCIALPERIOD ALN 4 Y INVOICE FINANCIALPERIOD
EXCHANGERATE2 DECIMAL 12 N INVOICE EXCHANGERATE2
BANKACCOUNT ALN 20 Y COMPANIES BANKACCOUNT
244
SOURCESYSID ALN 10 Y INVOICE SOURCESYSID
OWNERSYSID ALN 10 Y INVOICE OWNERSYSID
EXTERNALREFID ALN 10 Y INVOICE EXTERNALREFID
WFID INTEGER 4 Y INVOICE WFID
WFACTIVE YORN 1 Y INVOICE WFACTIVE
SYSCODE INTEGER 4 Y
APISEQ INTEGER 4 Y
SENDERSYSID ALN 50 Y INVOICE SENDERSYSID
INVOICELINENUM INTEGER 4 Y INVOICELINE INVOICELINENUM
POLINENUM INTEGER 4 Y INVOICELINE POLINENUM
ITEMNUM UPPER 8 Y INVOICELINE ITEMNUM
DESCRIPTION ALN 50 Y INVOICELINE DESCRIPTION
SCHARGECODE UPPER 8 Y INVOICELINE SCHARGECODE
INVOICEQTY DECIMAL 10 Y INVOICELINE INVOICEQTY
INVOICEUNIT ALN 8 Y INVOICELINE INVOICEUNIT
245
Chapter 3
INOVOICEUNITCOST DECIMAL 15 Y INVOICELINE UNITCOST
INVOICELINECOST DECIMAL 15 Y INVOICELINE LINECOST
CONVERSION DECIMAL 15 Y INVOICELINE CONVERSION
RECEIPTREQD YORN 1 Y INVOICELINE RECEIPTREQD
TAX1CODE UPPER 8 Y INVOICELINE TAX1CODE
TAX1 DECIMAL 10 Y INVOICELINE TAX1
INVOICELIN1 ALN 1 Y INVOICELINE INVOICELIN1
SERVICE YORN 1 Y INVOICELINE SERVICE
LOADEDCOST DECIMAL 10 Y INVOICELINE LOADEDCOST
PRORATED ALN 1 Y INVOICELINE PRORATED
246
PRORATECOST DECIMAL 12 Y INVOICELINE PRORATECOST
PRORATESERVICE ALN 1 Y INVOICELINE PRORATESERVICE
AGREEMENTPONUM ALN 8 Y INVOICELINE AGREEMENTPONUM
AGREEMENTPOTYPE ALN 6 Y INVOICELINE AGREEMENTPOTYPE
LINECOST2 DECIMAL 12 Y INVOICELINE LINECOST2

VARVALUE(BASCURRE
CURRENCYCODE2 UPPER 8 Y MAXVAR NCY2)
GLDEBITACCT ALN 20 N INVOICECOST GLDEBITACCT
GLCREDITACCT ALN 20 Y INVOICECOST GLCREDITACCT
WONUM UPPER 10 Y INVOICECOST WONUM
WPOPERATION INTEGER 4 Y INVOICECOST WPOPERATION
EQNUM UPPER 8 Y INVOICECOST EQNUM
PERCENTAGE DECIMAL 5 Y INVOICECOST PERCENTAGE
MEMO ALN 25 Y INVOICECOST MEMO
COSTLINENUM INTEGER 4 Y INVOICECOST COSTLINENUM
LINECOST DECIMAL 15 Y INVOICECOST LINECOST
CHARGESTORE YORN 1 Y INVOICECOST CHARGESTORE
ICT1 ALN 1 Y INVOICECOST ICT1
247
Chapter 3
QUANTITY DECIMAL 10 Y INVOICECOST QUANTITY
LOCATION UPPER 8 Y INVOICECOST LOCATION
ADDRESS4 ALN 36 Y COMPCONTACT ADDRESS4
POSITION ALN 24 Y COMPANIES POSITION
248
CO8 DATTIME 10 Y COMPANIES CO8
CO12 DATTIME 10 Y COMPANIES CO12
DISABLED ALN 1 N COMPANIES DISABLED
249
Chapter 3
ISSUE ALN 1 Y POLINE ISSUE
MFGNAME ALN 46 Y POLINE MFGNAME
STORELOC ALN 8 Y POLINE STORELOC
PRICEVAR DECIMAL 12 Y INVOICETRANS LINECOST
APLONGDESC ALN 2000 Y
APLINELONGDESC ALN 2000 Y
USERDATA1 ALN 1 Y
USERDATA2 ALN 1 Y
USERDATA3 ALN 1 Y
USERDATA4 ALN 1 Y
USERDATA5 ALN 1 Y
USERDATA6 ALN 1 Y
USERDATA7 ALN 1 Y
USERDATA8 ALN 1 Y
250
USERDATA9 ALN 1 Y
USERDATA10 ALN 1 Y
BATCHID ALN 25 Y
UTRANSTYPE ALN 25 Y
SOURCEID ALN 25 Y INVOICE SOURCEID
APISITE ALN 256 Y
EINVOICE ALN 1 Y INVOICE EINVOICE
251
Chapter 3
MAX_AP_INTERFACE
MAX_AP_INTERFACE receives invoice data from Oracle Financials. Data is
sent to the following MAXIMO tables.
MAX_AP_INTERFACE Table MAXIMO Tables
INVOICENUM UPPER 8 N INVOICE APCONTROLACCT
INVOICEDESC ALN 50 Y INVOICE APPROVALNUM
PONUM UPPER 8 Y INVOICE APSUSPENSEACCT
VENDOR UPPER 8 Y INVOICE BASETOTALCOST
CONTACT ALN 50 Y INVOICE CHANGEBY
PAYMENTTERMS ALN 20 Y INVOICE CHANGEDATE
CHECKCODE UPPER 8 Y INVOICE CHECKCODE
CHECKNUM UPPER 8 Y INVOICE CHECKNUM
CURRENCYCODE UPPER 8 Y INVOICE CONTACT
EXCHANGEDATE DATE 4 Y INVOICE EXCHANGEDATE
EXCHANGERATE DECIMAL 12 Y INVOICE EXCHANGERATE
DOCUMENTTYPE UPPER 8 Y INVOICE DOCUMENTTYPE
ORIGINVOICENUM UPPER 8 Y INVOICE DISCOUNTDATE
STATUS UPPER 7 Y INVOICE DOCUMENTTYPE
STATUSDATE DATETIME 10 Y INVOICE DUEDATE
APPROVALNUM ALN 8 Y INVOICE ENTERBY
INVOICEDATE DATETIME 10 Y INVOICE ENTERDATE
252
DISCOUNTDATE DATETIME 10 Y INVOICE DISCOUNTDATE
DUEDATE DATETIME 10 Y INVOICE DUEDATE
PAID DECIMAL 10 Y INVOICE FINANCIALPERIOD
PAIDDATE DATETIME 10 Y INVOICE EXCHANGERATE2
ENTERBY ALN 18 Y INVOICE ENTERBY
ENTERDATE DATETIME 10 Y INVOICE ENTERDATE
CHANGEBY ALN 18 Y INVOICE CHANGEBY
CHANGEDATE DATETIME 10 Y INVOICE CHANGEDATE
HISTORYFLAG ALN 1 Y INVOICE INCLUSIVE4
TOTALTAX1 DECIMAL 10 Y INVOICE INCLUSIVE5
TOTALTAX2 DECIMAL 10 Y INVOICE INVOICE2
TOTALTAX3 DECIMAL 10 Y INVOICE INVOICE4
TOTALTAX4 DECIMAL 10 Y INVOICE INVOICEDATE
TOTALTAX5 DECIMAL 10 Y INVOICE TAX4GL
TAX1GL ALN 20 Y INVOICE INVOICE1
253
Chapter 3
TAX4GL ALN 20 Y INVOICE INVOICENUM
INCLUSIVE1 YORN 1 Y INVOICE ORIGINVOICENUM
INCLUSIVE2 YORN 1 Y INVOICE PAID
INCLUSIVE3 YORN 1 Y INVOICE PAIDDATE
DISCOUNT DECIMAL 10 Y INVOICE DISCOUNT
TOTALCOST DECIMAL 10 Y INVOICE PONUM
INVOICE1 ALN 1 Y INVOICE STATUS
INVOICE2 ALN 1 Y INVOICE STATUSDATE
INVOICE3 ALN 1 Y INVOICE TAX1GL
INCLUSIVE4 YORN 1 Y INVOICE TOTALCOST
INCLUSIVE5 YORN 1 Y INVOICE TOTALTAX1
VENDORINVOICENUM ALN 12 Y INVOICE TOTALTAX2
BASETOTALCOST DECIMAL 10 Y INVOICE TOTALTAX3
APSUSPENSEACCT ALN 20 Y INVOICE TOTALTAX4
254
APCONTROLACCT ALN 20 Y INVOICE APCONTROLACCT
FINANCIALPERIOD ALN 4 Y INVOICE VENDOR
EXCHANGERATE2 DECIMAL 12 N INVOICE EXCHANGERATE2
BANKACCOUNT ALN 20 Y INVOICE BANKACCOUNT
BANKNUM ALN 16 Y INVOICE BANKNUM
SOURCESYSID ALN 10 Y INVOICE SOURCESYSID
OWNERSYSID ALN 10 Y INVOICE OWNERSYSID
EXTERNALREFID ALN 10 Y INVOICE EXTERNALREFID
WFID INTEGER 4 Y INVOICE WFID
WFACTIVE YORN 1 Y INVOICE WFACTIVE
SYSCODE INTEGER 4 Y SYSCODE
APISEQ INTEGER 4 Y INVOICECOST APISEQ
SENDERSYSID ALN 50 Y INVOICE SENDERSYSID
INVOICELINENUM INTEGER 4 Y INVOICELINE INVOICELINENUM
POLINENUM INTEGER 4 Y INVOICELINE POLINENUM
255
Chapter 3
ITEMNUM UPPER 8 Y INVOICELINE ITEMNUM
DESCRIPTION ALN 50 Y INVOICELINE DESCRIPTION
SCHARGECODE UPPER 8 Y INVOICELINE SCHARGECODE
INVOICEQTY DECIMAL 10 Y INVOICELINE INVOICEQTY
INVOICEUNIT ALN 8 Y INVOICELINE INVOICEUNIT
INVOICEUNITCOST DECIMAL 15 Y INVOICELINE UNITCOST
INVOICELINECOST DECIMAL 15 Y INVOICELINE LINECOST
CONVERSION DECIMAL 15 Y INVOICELINE CONVERSION
RECEIPTREQD YORN 1 Y INVOICELINE RECEIPTREQD
SERVICE YORN 1 Y INVOICELINE SERVICE
LOADEDCOST DECIMAL 10 Y INVOICELINE LOADEDCOST
PRORATECOST DECIMAL 10 Y INVOICELINE PRORATECOST
PRORATED ALN 1 Y INVOICELINE PRORATED
PRORATESERVICE ALN 1 Y INVOICELINE PRORATESERVICE
AGREEMENTPONUM ALN 8 Y INVOICELINE AGREEMENTPONUM
AGREEMENTPOTYPE ALN 6 Y INVOICELINE AGREEMENTPOTYPE
LINECOST2 DECIMAL 12 Y INVOICELINE LINECOST2
256
VARVALUE(BASCURREN
GLCREDITACCT ALN 20 Y INVOICECOST GLCREDITACCT
GLDEBITACCT ALN 20 Y INVOICECOST GLDEBITACCT
WONUM UPPER 10 Y INVOICECOST WONUM
WPOPERATION INTEGER 4 Y INVOICECOST WPOPERATION
EQNUM UPPER 8 Y INVOICECOST EQNUM
LINECOST DECIMAL 10 Y INVOICECOST LINECOST
PERCENTAGE DECIMAL 5 Y INVOICECOST PERCENTAGE
MEMO ALN 25 Y INVOICECOST MEMO
COSTLINENUM INTEGER 4 Y INVOICECOST COSTLINENUM
CHARGESTORE YORN 1 Y INVOICECOST CHARGESTORE
QUANTITY DECIMAL 10 Y INVOICECOST QUANTITY
LOCATION UPPER 8 Y INVOICECOST LOCATION
257
Chapter 3
POSITION ALN 24 Y COMPANIES POSITION
258
259
Chapter 3
STORELOC ALN 8 Y POLINE STORELOC
INVOICETRAN
PRICEVAR ALN 8 Y S LINECOST
APLONGDESC ALN 2000 Y
APLINELONGDESC ALN 2000 Y
USERDATA1 ALN 1 Y
USERDATA2 ALN 1 Y
USERDATA3 ALN 1 Y
USERDATA4 ALN 1 Y
USERDATA5 ALN 1 Y
USERDATA6 ALN 1 Y
USERDATA7 ALN 1 Y
USERDATA8 ALN 1 Y
USERDATA9 ALN 1 Y
USERDATA10 ALN 1 Y
BATCHID ALN 25 Y
260
UTRANSTYPE ALN 25 Y
SOURCEID ALN 25 Y INVOICECOST SOURCEID
APISITE ALN 256 Y
EINVOICE ALN 1 Y INVOICE EINVOICE
261
Chapter 3
General Ledger Interface Tables

This section provides the mapping for the interface tables that are used when
transferring general ledger data between MAXIMO and Oracle Financials.
reflect your actual values. Your values are determined by your MAXIMO system
catalogue.
MOUT_GL_INTERFACE Table
The MOUT_GL_INTERFACE table can receive journal entry data from seven
MAXIMO tables: INVTRANS, MATUSETRANS, MATRECTRANS,
SERVRECTRANS, LABTRANS, INVOICETRANS or TOOLTRANS.
Additional data comes from the INVOICELINE and INVOICECOST tables.
Data is sent to Oracle Financials.
The following table shows the mapping for the MOUT_GL_INTERFACE and
INVTRANS tables.
MOUT_GL_INTERFACE Table INVTRANS Table
TRANSDATE DATETIME 10 N TRANSDATE
ENTERDATE DATETIME 10 Y TRANSDATE
TRANSTYPE UPPER 16 Y TRANSTYPE
262
DESCRIPTION ALN 254 Y
STORELOC UPPER 8 Y STORELOC
BINNUM ALN 8 Y BINNUM
UNITCOST AMOUNT 10 Y NEWCOST
LINECOST DECIMAL 10 N LINECOST
PONUM UPPER 8 Y
POLINENUM INTEGER 4 Y
INVOICENUM UPPER 8 Y
INVOICELINENUM INTEGER 4 Y
COSTLINENUM INTEGER 4 Y
WONUM UPPER 10 Y
WPOPERATION INTEGER 4 Y
EQNUM UPPER 8 Y
LOCATION UPPER 8 Y
263
Chapter 3
CLAIMNUM UPPER 8 Y
CURRENCYCODE UPPER 8 Y
CURRENCYUNITCOST DECIMAL 10 Y
CURRENCYLINECOST DECIMAL 10 Y
EXCHANGERATE DECIMAL 10 Y
JE1 ALN 254 Y
JE2 ALN 254 Y
JE3 ALN 254 Y
JE4 ALN 254 Y
JE5 ALN 254 Y
JE6 ALN 254 Y
JE7 ALN 254 Y
JE8 ALN 254 Y
LABORCODE UPPER 8 Y
CRAFT UPPER 8 Y
REGULARHRS DURATION 8 Y
OTHRS DURATION 8 Y
264
TOOLNUM UPPER 8 Y
VENDOR UPPER 8 Y
ENTERBY UPPER 18 N ENTERBY
MEMO ALN 254 Y MEMO
FROMLOT
TOLOT LOTNUM
LOADEDCOST
TAX1CODE
TAX1
TAX2CODE
TAX2
TAX3CODE
TAX3
TAX4CODE
TAX4
TAX5CODE
TAX5
PRORATED
PRORATECOST
265
Chapter 3
STATUS
STATUSDATE
STATUSCHANGEBY
GENAPPRSERVRECEIPT
PAYMENTRANSDATE
AGREEMENTPONUM
AGREEMENTPOTYPE
PRORATESERVICE
CURRENCYCODE2
EXCHANGERATE2 EXCHANGERATE2
LINECOST2 LINECOST2
FINCNTRLID ALN 8 Y
BUDGETID ALN 25 Y
BUDGETLINEID ALN 25 Y
PROJECTID ALN 25 Y
TASKID ALN 25 Y
BUDGETTYPE ALN 30 Y
PROJECTTYPE ALN 30 Y
TASKTYPE ALN 30 Y
266
BUDGETREF ALN 50 Y
BUDGETLINEREF ALN 50 Y
PROJECTREF ALN 50 Y
TASKREF ALN 50 Y
ISCHARGEABLE
FC01
FC02
FC03
FC04
FC05
FC06
FC07
FC08
FC09
FC10
FC11
FC12
FC13
FC14
FC15
PROJDATA1
PROJDATA2
267
Chapter 3
PROJDATA3
PROJDATA4
PROJDATA5
PROJDATA6
PROJDATA7
PROJDATA8
PROJDATA9
PROJDATA10
PROJDATA11
PROJDATA12
PROJDATA13
PROJDATA14
PROJDATA15
ROWSTAMP
USERDATA1 ALN 1 Y
USERDATA2 ALN 1 Y
USERDATA3 ALN 1 Y
USERDATA4 ALN 1 Y
USERDATA5 ALN 1 Y
268
USERDATA6 ALN 1 Y
USERDATA7 ALN 1 Y
USERDATA8 ALN 1 Y
USERDATA9 ALN 1 Y
USERDATA10 ALN 1 Y
BATCHID ALN 25 Y
UTRANSTYPE ALN 25 Y
APISITE
SENDERSYSID SENDERSYSID
SOURCESYSID SOURCESYSID
OWNERSYSID OWNERSYSID
EXTERNALREFID EXTERNALREFID
ISSUEID
INVTRANSID INVTRANSID
269
Chapter 3
270
MATUSETRANS tables.
MOUT_GL_INTERFACE Table MATUSETRANS Table
ENTERDATE DATETIME 10 Y ACTUALDATE
TRANSTYPE UPPER 16 Y ISSUETYPE
STORELOC UPPER 8 Y STORELOC
BINNUM ALN 8 Y BINNUM
UNITCOST AMOUNT 10 Y UNITCOST/ACTUALCOST
271
Chapter 3
CLAIMNUM UPPER 8 Y
JE1 ALN 254 Y IT1
JE2 ALN 254 Y IT2
JE3 ALN 254 Y IT3
272
JE4 ALN 254 Y IT4
JE5 ALN 254 Y IT5
JE6 ALN 254 Y ITIN1
JE7 ALN 254 Y ITIN2
JE8 ALN 254 Y ITIN3
LABORCODE UPPER 8 Y
CRAFT UPPER 8 Y
OTHRS DURATION 8 Y
TOOLNUM UPPER 8 Y
VENDOR UPPER 8 Y
MEMO ALN 254 Y MEMO
FROMLOT LOTNUM
TOLOT
LOADEDCOST
TAX1CODE
273
Chapter 3
TAX1
TAX2CODE
TAX2
TAX3CODE
TAX3
TAX4CODE
TAX4
TAX5CODE
TAX5
PRORATED
PRORATECOST
STATUS
STATUSDATE
STATUSCHANGEBY
GENAPPRSERVRECEIPT
PAYMENTRANSDATE
AGREEMENTPONUM
AGREEMENTPOTYPE
PRORATESERVICE
CURRENCYCODE2
274
LINECOST2 LINECOST2
FINCNTRLID ALN 8 Y
BUDGETID ALN 25 Y
PROJECTID ALN 25 Y
TASKID ALN 25 Y
BUDGETTYPE ALN 30 Y
TASKTYPE ALN 30 Y
BUDGETREF ALN 50 Y
PROJECTREF ALN 50 Y
TASKREF ALN 50 Y
ISCHARGEABLE
FC01
FC02
FC03
FC04
FC05
FC06
275
Chapter 3
FC07
FC08
FC09
FC10
FC11
FC12
FC13
FC14
FC15
PROJDATA1
PROJDATA2
PROJDATA3
PROJDATA4
PROJDATA5
PROJDATA6
PROJDATA7
PROJDATA8
PROJDATA9
PROJDATA10
PROJDATA11
PROJDATA12
PROJDATA13
276
PROJDATA14
PROJDATA15
ROWSTAMP
USERDATA1 ALN 1 Y
USERDATA2 ALN 1 Y
USERDATA3 ALN 1 Y
USERDATA4 ALN 1 Y
USERDATA5 ALN 1 Y
USERDATA6 ALN 1 Y
USERDATA7 ALN 1 Y
USERDATA8 ALN 1 Y
USERDATA9 ALN 1 Y
USERDATA10 ALN 1 Y
BATCHID ALN 25 Y
UTRANSTYPE ALN 25 Y
277
Chapter 3
APISITE
ISSUEID ISSUEID
INVTRANSID
278
MATRECTRANS tables.
MOUT_GL_INTERFACE Table MATRECTRANS Table
ENTERDATE DATETIME 10 Y ACTUALDATE
TRANSTYPE UPPER 16 Y ISSUETYPE
STORELOC UPPER 8 Y TOSTORELOC
BINNUM ALN 8 Y TOBIN
UNITCOST AMOUNT 10 Y UNITCOST/ACTUALCOST
279
Chapter 3
CLAIMNUM UPPER 8 Y
JE1 ALN 254 Y IT1
JE2 ALN 254 Y IT2
JE3 ALN 254 Y IT3
280
JE4 ALN 254 Y IT4
JE5 ALN 254 Y IT5
JE6 ALN 254 Y ITIN1
JE7 ALN 254 Y ITIN2
JE8 ALN 254 Y ITIN3
LABORCODE UPPER 8 Y
CRAFT UPPER 8 Y
OTHRS DURATION 8 Y
TOOLNUM UPPER 8 Y
VENDOR UPPER 8 Y
MEMO ALN 254 Y REMARK
FROMLOT FROMLOT
TOLOT TOLOT
LOADEDCOST LOADEDCOST
TAX1CODE TAX1CODE
281
Chapter 3
TAX1 TAX1
TAX2CODE TAX2CODE
TAX2 TAX2
TAX3CODE TAX3CODE
TAX3 TAX3
TAX4CODE TAX4CODE
TAX4 TAX4
TAX5CODE TAX5CODE
TAX5 TAX5
PRORATED PRORATED
PRORATECOST PRORATECOST
STATUS STATUS
STATUSDATE STATUSDATE
STATUSCHANGEBY STATUSCHANGEBY
GENAPPRSERVRECEIPT
PAYMENTRANSDATE
AGREEMENTPONUM
AGREEMENTPOTYPE
PRORATESERVICE
CURRENCYCODE2
282
LINECOST2 LINECOST2
FINCNTRLID ALN 8 Y
BUDGETID ALN 25 Y
PROJECTID ALN 25 Y
TASKID ALN 25 Y
BUDGETTYPE ALN 30 Y
TASKTYPE ALN 30 Y
BUDGETREF ALN 50 Y
PROJECTREF ALN 50 Y
TASKREF ALN 50 Y
ISCHARGEABLE
FC01
FC02
FC03
FC04
FC05
FC06
283
Chapter 3
FC07
FC08
FC09
FC10
FC11
FC12
FC13
FC14
FC15
PROJDATA1
PROJDATA2
PROJDATA3
PROJDATA4
PROJDATA5
PROJDATA6
PROJDATA7
PROJDATA8
PROJDATA9
PROJDATA10
PROJDATA11
PROJDATA12
PROJDATA13
284
PROJDATA14
PROJDATA15
ROWSTAMP
USERDATA1 ALN 1 Y
USERDATA2 ALN 1 Y
USERDATA3 ALN 1 Y
USERDATA4 ALN 1 Y
USERDATA5 ALN 1 Y
USERDATA6 ALN 1 Y
USERDATA7 ALN 1 Y
USERDATA8 ALN 1 Y
USERDATA9 ALN 1 Y
USERDATA10 ALN 1 Y
BATCHID ALN 25 Y
UTRANSTYPE ALN 25 Y
285
Chapter 3
APISITE
ISSUEID
INVTRANSID
286
SERVRECTRANS tables.
MOUT_GL_INTERFACE Table SERVRECTRANS Table
ENTERDATE DATETIME 10 Y ENTERDATE
TRANSTYPE UPPER 16 Y
ITEMNUM UPPER 8 Y
STORELOC UPPER 8 Y
BINNUM ALN 8 Y
287
Chapter 3
JE1 ALN 254 Y SS1
JE2 ALN 254 Y SS2
JE3 ALN 254 Y SS3
288
JE4 ALN 254 Y SS4
JE5 ALN 254 Y SS5
JE6 ALN 254 Y SSPL1
JE7 ALN 254 Y SSPL2
JE8 ALN 254 Y SSPL3
LABORCODE UPPER 8 Y
CRAFT UPPER 8 Y
OTHRS DURATION 8 Y
TOOLNUM UPPER 8 Y
VENDOR UPPER 8 Y
MEMO ALN 254 Y REMARK
FROMLOT
TOLOT
LOADEDCOST LOADEDCOST
TAX1CODE TAX1CODE
289
Chapter 3
TAX1 TAX1
TAX2CODE TAX2CODE
TAX2 TAX2
TAX3CODE TAX3CODE
TAX3 TAX3
TAX4CODE TAX4CODE
TAX4 TAX4
TAX5CODE TAX5CODE
TAX5 TAX5
PRORATED PRORATED
PRORATECOST PRORATECOST
STATUS
STATUSDATE
STATUSCHANGEBY
GENAPPRSERVRECEIPT
PAYMENTRANSDATE
AGREEMENTPONUM
AGREEMENTPOTYPE
PRORATESERVICE
CURRENCYCODE2
290
LINECOST2 LINECOST2
FINCNTRLID ALN 8 Y
BUDGETID ALN 25 Y
PROJECTID ALN 25 Y
TASKID ALN 25 Y
BUDGETTYPE ALN 30 Y
TASKTYPE ALN 30 Y
BUDGETREF ALN 50 Y
PROJECTREF ALN 50 Y
TASKREF ALN 50 Y
ISCHARGEABLE
FC01
FC02
FC03
FC04
FC05
FC06
291
Chapter 3
FC07
FC08
FC09
FC10
FC11
FC12
FC13
FC14
FC15
PROJDATA1
PROJDATA2
PROJDATA3
PROJDATA4
PROJDATA5
PROJDATA6
PROJDATA7
PROJDATA8
PROJDATA9
PROJDATA10
PROJDATA11
PROJDATA12
PROJDATA13
292
PROJDATA14
PROJDATA15
ROWSTAMP
USERDATA1 ALN 1 Y
USERDATA2 ALN 1 Y
USERDATA3 ALN 1 Y
USERDATA4 ALN 1 Y
USERDATA5 ALN 1 Y
USERDATA6 ALN 1 Y
USERDATA7 ALN 1 Y
USERDATA8 ALN 1 Y
USERDATA9 ALN 1 Y
USERDATA10 ALN 1 Y
BATCHID ALN 25 Y
UTRANSTYPE ALN 25 Y
293
Chapter 3
APISITE
ISSUEID
INVTRANSID
294
LABTRANS tables.
MOUT_GL_INTERFACE Table LABTRANS Table
ITEMNUM UPPER 8 Y
STORELOC UPPER 8 Y
BINNUM ALN 8 Y
QUANTITY DECIMAL 15 Y
UNITCOST AMOUNT 10 Y PAYRATE*OTSCALE
295
Chapter 3
CLAIMNUM UPPER 8 Y
JE1 ALN 254 Y LT1
JE2 ALN 254 Y LT2
JE3 ALN 254 Y LT3
296
JE4 ALN 254 Y LT4
JE5 ALN 254 Y LT5
JE6 ALN 254 Y LTL1
JE7 ALN 254 Y LTL2
JE8 ALN 254 Y LTL3
LABORCODE UPPER 8 Y LABORCODE
CRAFT UPPER 8 Y CRAFT
REGULARHRS DURATION 8 Y REGULARHRS
OTHRS DURATION 8 Y OTHRS
TOOLNUM UPPER 8 Y
VENDOR UPPER 8 Y
MEMO ALN 254 Y MEMO
FROMLOT
TOLOT
LOADEDCOST
TAX1CODE
297
Chapter 3
TAX1
TAX2CODE
TAX2
TAX3CODE
TAX3
TAX4CODE
TAX4
TAX5CODE
TAX5
PRORATED
PRORATECOST
STATUS
STATUSDATE
STATUSCHANGEBY
GENAPPRSERVRECEIPT GENAPPRSERVRECEIPT
PAYMENTRANSDATE PAYMENTTRANSDATE
AGREEMENTPONUM
AGREEMENTPOTYPE
PRORATESERVICE
CURRENCYCODE2
298
LINECOST2 LINECOST2
FINCNTRLID ALN 8 Y
BUDGETID ALN 25 Y
PROJECTID ALN 25 Y
TASKID ALN 25 Y
BUDGETTYPE ALN 30 Y
TASKTYPE ALN 30 Y
BUDGETREF ALN 50 Y
PROJECTREF ALN 50 Y
TASKREF ALN 50 Y
ISCHARGEABLE
FC01
FC02
FC03
FC04
FC05
FC06
299
Chapter 3
FC07
FC08
FC09
FC10
FC11
FC12
FC13
FC14
FC15
PROJDATA1
PROJDATA2
PROJDATA3
PROJDATA4
PROJDATA5
PROJDATA6
PROJDATA7
PROJDATA8
PROJDATA9
PROJDATA10
PROJDATA11
PROJDATA12
PROJDATA13
300
PROJDATA14
PROJDATA15
ROWSTAMP
USERDATA1 ALN 1 Y
USERDATA2 ALN 1 Y
USERDATA3 ALN 1 Y
USERDATA4 ALN 1 Y
USERDATA5 ALN 1 Y
USERDATA6 ALN 1 Y
USERDATA7 ALN 1 Y
USERDATA8 ALN 1 Y
USERDATA9 ALN 1 Y
USERDATA10 ALN 1 Y
BATCHID ALN 25 Y
UTRANSTYPE ALN 25 Y
301
Chapter 3
APISITE
ISSUEID
INVTRANSID
302
The following table shows the mapping for MOUT_GL_INTERFACE and the
INVOICETRANS, INVOICELINE and INVOICECOST tables.
MOUT_GL_INTERFACE Table INVOICETRANS / INVOICELINE

/ INVOICECOST Tables
ENTERDATE DATETIME 10 Y TRANSDATE
ITEMNUM UPPER 8 Y
STORELOC UPPER 8 Y
BINNUM ALN 8 Y
QUANTITY DECIMAL 15 Y
UNITCOST AMOUNT 10 Y
303
Chapter 3

PONUM UPPER 8 Y LINE.PONUM
POLINENUM INTEGER 4 Y LINE.POLINENUM
INVOICELINENUM INTEGER 4 Y INVOICELINENUM
COSTLINENUM INTEGER 4 Y COSTLINENUM
WONUM UPPER 10 Y COST.WONUM
WPOPERATION INTEGER 4 Y COST.WPOPERATION
EQNUM UPPER 8 Y COST.EQNUM
LOCATION UPPER 8 Y COST.LOCATION
CLAIMNUM UPPER 8 Y
JE1 ALN 254 Y
JE2 ALN 254 Y
304

JE3 ALN 254 Y
JE4 ALN 254 Y
JE5 ALN 254 Y
JE6 ALN 254 Y
JE7 ALN 254 Y
JE8 ALN 254 Y
LABORCODE UPPER 8 Y
CRAFT UPPER 8 Y
OTHRS DURATION 8 Y
TOOLNUM UPPER 8 Y
VENDOR UPPER 8 Y VENDOR
MEMO ALN 254 Y
FROMLOT
TOLOT
305
Chapter 3

LOADEDCOST
TAX1CODE
TAX1
TAX2CODE
TAX2
TAX3CODE
TAX3
TAX4CODE
TAX4
TAX5CODE
TAX5
PRORATED
PRORATECOST
STATUS
STATUSDATE
STATUSCHANGEBY
GENAPPRSERVRECEIPT
PAYMENTRANSDATE
AGREEMENTPONUM AGREEMENTPONUM
AGREEMENTPOTYPE AGREEMENTPOTYPE
306

PRORATESERVICE PRORATESERVICE
CURRENCYCODE2
LINECOST2 LINECOST2
FINCNTRLID ALN 8 Y
BUDGETID ALN 25 Y
PROJECTID ALN 25 Y
TASKID ALN 25 Y
BUDGETTYPE ALN 30 Y
TASKTYPE ALN 30 Y
BUDGETREF ALN 50 Y
PROJECTREF ALN 50 Y
TASKREF ALN 50 Y
ISCHARGEABLE
FC01
FC02
307
Chapter 3

FC03
FC04
FC05
FC06
FC07
FC08
FC09
FC10
FC11
FC12
FC13
FC14
FC15
PROJDATA1
PROJDATA2
PROJDATA3
PROJDATA4
PROJDATA5
PROJDATA6
PROJDATA7
PROJDATA8
308

PROJDATA9
PROJDATA10
PROJDATA11
PROJDATA12
PROJDATA13
PROJDATA14
PROJDATA15
ROWSTAMP
USERDATA1 ALN 1 Y
USERDATA2 ALN 1 Y
USERDATA3 ALN 1 Y
USERDATA4 ALN 1 Y
USERDATA5 ALN 1 Y
USERDATA6 ALN 1 Y
USERDATA7 ALN 1 Y
USERDATA8 ALN 1 Y
USERDATA9 ALN 1 Y
USERDATA10 ALN 1 Y
309
Chapter 3

BATCHID ALN 25 Y
UTRANSTYPE ALN 25 Y
APISITE
ISSUEID
INVTRANSID
310
The following table shows the mapping for MOUT_GL_INTERFACE and

TOOLTRANS.
MOUT_GL_INTERFACE Table TOOLTRANS Table
TRANSTYPE UPPER 16 Y
ITEMNUM UPPER 8 Y
STORELOC UPPER 8 Y
BINNUM ALN 8 Y
QUANTITY DECIMAL 15 Y TOOLQTY
UNITCOST AMOUNT 10 Y TOOLRATE
311
Chapter 3
PONUM UPPER 8 Y
POLINENUM INTEGER 4 Y
CLAIMNUM UPPER 8 Y
JE1 ALN 254 Y TT1
JE2 ALN 254 Y TT2
JE3 ALN 254 Y TT3
312
JE4 ALN 254 Y TT4
JE5 ALN 254 Y TT5
JE6 ALN 254 Y
JE7 ALN 254 Y
JE8 ALN 254 Y
LABORCODE UPPER 8 Y
CRAFT UPPER 8 Y
REGULARHRS DURATION 8 Y TOOLHRS
OTHRS DURATION 8 Y
TOOLNUM UPPER 8 Y TOOLNUM
VENDOR UPPER 8 Y
MEMO ALN 254 Y
FROMLOT
TOLOT
LOADEDCOST
TAX1CODE
313
Chapter 3
TAX1
TAX2CODE
TAX2
TAX3CODE
TAX3
TAX4CODE
TAX4
TAX5CODE
TAX5
PRORATED
PRORATECOST
STATUS
STATUSDATE
STATUSCHANGEBY
GENAPPRSERVRECEIPT
PAYMENTRANSDATE
AGREEMENTPONUM
AGREEMENTPOTYPE
PRORATESERVICE
CURRENCYCODE2
314
LINECOST2 LINECOST2
FINCNTRLID ALN 8 Y
BUDGETID ALN 25 Y
PROJECTID ALN 25 Y
TASKID ALN 25 Y
BUDGETTYPE ALN 30 Y
TASKTYPE ALN 30 Y
BUDGETREF ALN 50 Y
PROJECTREF ALN 50 Y
TASKREF ALN 50 Y
ISCHARGEABLE
FC01
FC02
FC03
FC04
FC05
FC06
315
Chapter 3
FC07
FC08
FC09
FC10
FC11
FC12
FC13
FC14
FC15
PROJDATA1
PROJDATA2
PROJDATA3
PROJDATA4
PROJDATA5
PROJDATA6
PROJDATA7
PROJDATA8
PROJDATA9
PROJDATA10
PROJDATA11
PROJDATA12
PROJDATA13
316
PROJDATA14
PROJDATA15
ROWSTAMP
USERDATA1 ALN 1 Y
USERDATA2 ALN 1 Y
USERDATA3 ALN 1 Y
USERDATA4 ALN 1 Y
USERDATA5 ALN 1 Y
USERDATA6 ALN 1 Y
USERDATA7 ALN 1 Y
USERDATA8 ALN 1 Y
USERDATA9 ALN 1 Y
USERDATA10 ALN 1 Y
BATCHID ALN 25 Y
UTRANSTYPE ALN 25 Y
317
Chapter 3
APISITE
ISSUEID
INVTRANSID
318
MAX_COA_INTERFACE Table
MAX_COA_INTERFACE receives chart of accounts data from Oracle
MAX_COA_INTERFACE Table MAXIMO Tables
GLACCOUNT ALN 20 Y CHARTOFACCOUNTS GLACCOUNT
GLCOMP01 ALN 4 Y CHARTOFACCOUNTS GLCOMP01
COMPTEXT01 ALN 30 Y GLCOMPONENTS COMPTEXT
319
Chapter 3
320
ACCOUNTNAME ALN 50 Y CHARTOFACCOUNTS ACCOUNTNAME
GLACCTYPE ALN 3 Y CHARTOFACCOUNTS GLACCTYPE
CH1 ALN 10 Y CHARTOFACCOUNTS CH1
CH4 DECIMAL 15.2 Y CHARTOFACCOUNTS CH4
CH5 INTEGER 4 Y CHARTOFACCOUNTS CH5
DISABLED YORN 1 Y CHARTOFACCOUNTS DISABLED
DISABLED01 YORN 1 Y CHARTOFACCOUNTS DISABLED
321
Chapter 3
SOURCESYSID ALN 10 Y CHARTOFACCOUNTS SOURCESYSID
OWNERSYSID ALN 10 Y CHARTOFACCOUNTS OWNERSYSID
EXTERNALREFID ALN 10 Y CHARTOFACCOUNTS EXTERNALREFID
USERDATA1 ALN 1 Y
USERDATA2 ALN 1 Y
USERDATA3 ALN 1 Y
USERDATA4 ALN 1 Y
USERDATA5 ALN 1 Y
USERDATA6 ALN 1 Y
USERDATA7 ALN 1 Y
USERDATA8 ALN 1 Y
USERDATA9 ALN 1 Y
322
USERDATA10 ALN 1 Y
UTRANSTYPE ALN 25 Y
SOURCEID ALN 25 Y CHARTOFACCOUNTS SOURCEID
APISEQ INTEGER 4 Y CHARTOFACCOUNTS APISEQ
APISITE ALN 256 Y
SENDERSYSID ALN 50 Y CHARTOFACCOUNTS SENDERSYSID
MAX_COAX_INTERFACE Table
MAX_COAX_INTERFACE receives GL component data from Oracle
MAX_COAX_INTERFACE Table MAXIMO Tables
GLCOMP01 ALN 3 Y GLCOMPONENTS COMPVALUE
323
Chapter 3
324
DISABLED01 ALN 1 Y GLCOMPONENTS DISABLED
325
Chapter 3
SOURCESYSID ALN 10 Y CHARTOFACCOUNTS SOURCESYSID
OWNERSYSID ALN 10 Y CHARTOFACCOUNTS OWNERSYSID
EXTERNALREFID ALN 10 Y CHARTOFACCOUNTS EXTERNALREFID
USERDATA1 ALN 1 Y
USERDATA2 ALN 1 Y
USERDATA3 ALN 1 Y
USERDATA4 ALN 1 Y
326
USERDATA5 ALN 1 Y
USERDATA6 ALN 1 Y
USERDATA7 ALN 1 Y
USERDATA8 ALN 1 Y
USERDATA9 ALN 1 Y
USERDATA10 ALN 1 Y
UTRANSTYPE ALN 25 Y
SOURCEID ALN 25 Y CHARTOFACCOUNTS SOURCEID
APISEQ INTEGER 4 Y CHARTOFACCOUNTS APISEQ
APISITE ALN 256 Y
SENDERSYSID ALN 50 Y GLCOMPONENTS SENDERSYSID
327
Chapter 3
General Ledger Code Combinations from Oracle Financials

This section provides the cross mapping for the interface tables that are used when transferring valid general
ledger (GL) account data between MAXIMO and Oracle Financials applications. Data is transferred from several
Oracle Financials general ledger tables to the MAXIMO MAX_COA_INTERFACE table. Note that variable
length code combinations are not supported in MAXIMO.
MAX_COA_ Table.Column API variable

INTERFACE
GLACCOUNT GL_CODE_COMBINATIONS.SEGMENT1..20 gl_segment1..gl_segment20
GLCOMP01 GL_CODE_COMBINATIONS.SEGMENT1 gl_segment1
328

INTERFACE
COMPTEXT01 FND_FLEX_VALUES.DESCRIPTION gl_segment_name1
ACCOUNTNAME GL_CODE_COMBINATIONS.DESCRIPTION gl_desc
329
Chapter 3

INTERFACE
(or if null, concatenate first 15 characters of each COMPTEXT)
GLACCTYPE GL_CODE_COMBINATIONS.ACCOUNT_TYPE gl_account_type
CH1
CH2
CH3
CH4
CH5
DISABLED GL_CODE_COMBINATIONS.ENABLED_FLAG vdisabled
USERDATA1
USERDATA2
USERDATA3
USERDATA4
USERDATA5
USERDATA6
USERDATA7
USERDATA8
USERDATA9
USERDATA10
UTRANSTYPE
330
General Ledger Components from Oracle Financials

This section provides the cross mapping for the interface tables that are used when transferring general ledger
(GL) component data from Oracle Financials to MAXIMO. Data is transferred from several Oracle Financials
general ledger tables to the MAXIMO MAX_COAX_INTERFACE table. This interface will send components to
MAXIMO when a component is added or when the component has a change in its description or enabled flag.
Only one component is interface per transaction. The data is populated into the appropriate columns based on the
component’s segment number within Oracle Financials. If the API disables a component within MAXIMO, it will
search and disable any chart of account that contains that component.
MAX_COAX_INTERFACE Table.Column API variable

GLCOMP01 FND_FLEX_VALUE.flex_value flex_value
331
Chapter 3

COMPTEXT01 FND_FLEX_VALUES.DESCRIPTION description
DISABLED01 FND_FLEX_VALUES.ENABLED_FLAG enabled_flag (Y/N reversed)
332

USERDATA1
USERDATA2
USERDATA3
USERDATA4
USERDATA5
USERDATA6
USERDATA7
USERDATA8
333
Chapter 3

USERDATA9
USERDATA10
UTRANSTYPE
334
Invoices from Oracle Financials

This section provides the cross mapping for the interface tables that are used when transferring invoice data
between MAXIMO and Oracle Financials applications. Data is transferred from several Oracle Financials
accounts payables and purchasing tables to the MAXIMO MAX_AP_INTERFACE table.
MAX_AP_INTERFACE Table.Column API variable

INVOICENUM AP_INVOICES.INVOICE_NUM UPPER(invc_no)
INVOICEDESC AP_INVOICES.DESCRIPTION invc_desc
PONUM PO_HEADERS.SEGMENT1 UPPER(invc_po_no)
VENDOR PO_VENDORS.SEGMENT1 UPPER(invc_vnd_no)||'-
'||UPPER(invc_vndsite_code)
CONTACT
PAYMENTTERMS AP_TERMS.NAME invc_terms
CHECKCODE
CHECKNUM
CURRENCYCODE AP_INVOICES.INVOICE_CURRENCY_CODE UPPER(invc_curcode)
EXCHANGERATE AP_INVOICE_DISTRIBUTIONS.EXCHANGE_RATE invc_d_xchg_rate
EXCHANGEDATE AP_INVOICE_DISTRIBUTIONS.EXCHANGE_DATE invc_d_xchg_date
DOCUMENTTYPE AP_INVOICES.INVOICE_TYPE_LOOKUP_CODE invc_doc_type
ORIGINVOICENUM
STATUS 'APPR'
STATUSDATE AP_INVOICE_DISTRIBUTIONS.CREATION_DATE invc_change_date
APPROVALNUM
INVOICEDATE AP_INVOICES.INVOICE_DATE invc_date
DISCOUNTDATE
DUEDATE
335
Chapter 3

PAIDDATE
PAID AP_INVOICES.AMOUNT_PAID invc_paid_amt
ENTERDATE AP_INVOICES.CREATION_DATE invc_enter_date
ENTERBY FND_USER.USER_NAME invc_enter_by
CHANGEDATE AP_INVOICE_DISTRIBUTIONS.CREATION_DATE invc_change_date
CHANGEBY FND_USER.USER_NAME NVL(invc_change_by,invc_enter_by)
HISTORYFLAG sYes
TOTALTAX1
TAX1GL
TOTALTAX2
TAX2GL
TOTALTAX3
TAX3GL
TOTALTAX4
TAX4GL
INCLUSIVE1
INCLUSIVE2
INCLUSIVE3
DISCOUNT AP_INVOICES.DISCOUNT_AMOUNT_TAKEN invc_disc_amt
TOTALCOST AP_INVOICES.INVOICE_AMOUNT invc_amt
INVOICE1
INVOICE2
INVOICE3
INVOICE4
INVOICE5
TOTALTAX5
TAX5GL
INCLUSIVE4
336

INCLUSIVE5
VENDORINVOICENUM
BASETOTALCOST
APSUSPENSEACCT
APCONTROLACCT
INVOICELINENUM AP_INVOICE_DISTRIBUTIONS.DISTRIBUTION_LINE_NUMBER invc_d_no
POLINENUM PO_LINES.LINE_NUM 1'||LTRIM(TO_CHAR(invc_pl_no,'0999'))
||PO_LINE_LOCATIONS.SHIPMENT_NUM ||LTRIM(TO_CHAR(invc_ps_no,'0999'))
||PO_DISTRIBUTIONS.DISTRIBUTION_NUM ||LTRIM(TO_CHAR(invc_pd_no,'0999'))
ITEMNUM PO_REQ_DISTRIBUTIONS.ATTRIBUTE14,MTL_SYSTEM_ITEM NVL(invc_req_at14,invc_itm_no)
S.SEGMENT1
DESCRIPTION AP_INVOICE_DISTRIBUTIONS.DESCRIPTION,PO_LINES.ITEM NVL(invc_d_desc,invc_itm_desc)
_DESCRIPTION
SCHARGECODE
INVOICEQTY AP_INVOICE_DISTRIBUTIONS.QUANTITY_INVOICED invc_d_qty
INVOICEUNIT
INVOICEUNITCOST AP_INVOICE_DISTRIBUTIONS.UNIT_PRICE invc_d_unit_price
INVOICELINECOST AP_INVOICE_DISTRIBUTIONS.BASE_AMOUNT,AP_INVOICE_ NVL(invc_d_bamt,invc_d_amt);
DISTRIBUTIONS.AMOUNT
CONVERSION
RECEIPTREQD
TAX1CODE
TAX1
TAX2CODE
TAX2
TAX3CODE
TAX3
INVOICELIN1
337
Chapter 3

INVOICELIN2
INVOICELIN3
INVOICELIN4
INVOICELIN5
TAX4CODE
TAX4
TAX5CODE
TAX5
SERVICE
LOADEDCOST
PRORATED
PRORATECOST
PRORATESERVICE
AGREEMENTPONUM
AGREEMENTPOTYPE
GLDEBITACCT GL_CODE_COMBINATIONS.SEGMENT1..30 invc_charge_gl
GLCREDITACCT GL_CODE_COMBINATIONS.SEGMENT1..30 invc_apcontrol_gl
WONUM
WPOPERATION
EQNUM
LINECOST AP_INVOICE_DISTRIBUTIONS.AMOUNT invc_d_amt
PERCENTAGE
MEMO AP_INVOICE_DISTRIBUTIONS.LINE_TYPE_LOOKUP_CODE invc_line_type
COSTLINENUM AP_INVOICE_DISTRIBUTIONS.DISTRIBUTION_LINE_NUMBER invc_d_no
CHARGESTORE
ICT1
ICT2
ICT3
338

QUANTITY AP_INVOICE_DISTRIBUTIONS.QUANTITY_INVOICED invc_d_qty
LOCATION
COMPANYTYPE
NAME
ADDRESS1
ADDRESS2
ADDRESS3
ADDRESS4
POSITION
PHONE
FAX
FOB
FREIGHTTERMS
SHIPVIA
CUSTOMERNUM
CO1
CO2
CO3
CO4
CO5
CO6
CO7
CO8
CO9
CO10
CO11
CO12
CO13
339
Chapter 3

COMPANYLOC
REGISTRATION1
REGISTRATION2
REGISTRATION3
REGISTRATION4
REGISTRATION5
APCONTROLACC
APSUSPENSEACC
RBNIACC
PAYVENDOR
BANKACCOUNT
REMITCONTACT
PAYONRECEIPT
HOMEPAGE
BANKNUM
DUNSNUM
TAXEXEMPTCODE
TAXEXEMPTNUM
ECOMMERCEENABLED
ISSUE
MANUFACTURER
MFGNAME
MODELNUM
STORELOC
FINANCIALPERIOD AP_INVOICE_DISTRIBUTIONS.PERIOD_NAME invc_fp
PRICEVAR AP_INVOICE_DISTRIBUTIONS.BASE_INVOICE_PRICE_VARIA NVL(invc_d_bvar,0)
NCE
DISABLED
340

USERDATA1
USERDATA2
USERDATA3
USERDATA4
USERDATA5
USERDATA6
USERDATA7
USERDATA8
USERDATA9
USERDATA10
UTRANSTYPE
341
Chapter 3
Items from Oracle Financials

This section provides the cross mapping for the interface tables that are used when transferring item data between
MAXIMO and Oracle Financials applications. Data is transferred from several Oracle Financials inventory tables
to the MAXIMO MAX_ITM_INTERFACE table. (Note that the MAXIMO item interface table is also used to
transfer data into the MAXIMO Inventory. The SOURCEID indicates the direction of data and must be present in
order to avoid recursive updates or endless loops.)
MAX_ITM_INTERFACE Table.Column API variable

ITEMNUM MTL_SYSTEM_ITEMS.SEGMENT1 UPPER(mtl_segment1)
DESCRIPTION MTL_SYSTEM_ITEMS.DESCRIPTION mtl_desc
ROTATING sNo
STOCKTYPE MTL_SYSTEM_ITEMS.ITEM_TYPE mtl_itm_type
LOTTYPE MTL_SYSTEM_ITEMS.LOT_CONTROL_CODE mtl_lot_code
CAPITALIZED FA_CATEGORIES.CAPITALIZE_FLAG mtl_cap_asset_f
MSDSNUM PO_HAZARD_CLASSES.HAZARD_CLASS mtl_hazard_class
OUTSIDE sNo
IN1
IN2
IN3
IN4
IN5
IN6
IN7
IN8
IN9
IN10
342

IN11 MTL_SYSTEM_ITEMS.PRIMARY_UOM_CODE mtl_puom_code
IN12 MTL_SYSTEM_ITEMS.VENDOR_WARRANTY_FLAG mtl_warranty_f
IN13 PO_UN_NUMBERS.UN_NUMBER mtl_un_no
IN14 ORG_ORGANIZATION_DEFINITIONS.ORGANIZATION_CODE mtl_masterorg_code
IN15
IN16
IN17
IN18
IN19
IN20
IN21 MTL_SYSTEM_ITEMS.PURCHASING_ITEM_FLAG mtl_purchaseok_f
IN22 MTL_SYSTEM_ITEMS.INTERNAL_ORDER_ENABLED_FLAG mtl_internalok_f
IN23 MTL_SYSTEM_ITEMS.MUST_USE_APPROVED_VENDOR_FLAG mtl_appr_vnd_f
TAX1CODE MTL_SYSTEM_ITEMS.TAX_CODE mtl_tax_code
TAX2CODE
TAX3CODE
TAX4CODE
TAX5CODE
SPAREPARTAUTOADD
HAZARDID
CLASSTRUCTURIED
INSPECTIONREQUIRED
LDKEY
LOCATION ORG_ORGANIZATION_DEFINITIONS.ORGANIZATION_CODE UPPER(mtl_org_code)
BINNUM
MINLEVEL MTL_SYSTEM_ITEMS.MIN_MINMAX_QUANTITY mtl_min
MAXLEVEL MTL_SYSTEM_ITEMS.MAX_MINMAX_QUANTITY mtl_max
CATEGORY
343
Chapter 3

ORDERUNIT MTL_SYSTEM_ITEMS.PRIMARY_UNIT_OF_MEASURE mtl_puom
ISSUEUNIT MTL_SYSTEM_ITEMS.UNIT_OF_ISSUE mtl_issue_unit
CONVERSION
QUANTITY
LOTNUM
CURBAL
PHYSCNT
PHYSCNTDATE
IB1
IB2
IB3
IB4
IB5
RECONCILED
ORDERQTY MTL_SYSTEM_ITEMS.MAXIMUM_ORDER_QUANTITY mtl_order_max
STDCOST MTL_SYSTEM_ITEMS.LIST_PRICE_PER_UNIT mtl_unit_price
AVGCOST MTL_SYSTEM_ITEMS.LIST_PRICE_PER_UNIT mtl_unit_price
LASTCOST MTL_SYSTEM_ITEMS.MARKET_PRICE mtl_market_price
LASTISSUEDATE
ISSUEYTD
ISSUE1YRAGO
ISSUE2YRAGO
ISSUE3YRAGO
ABCTYPE
CCF
SSTOCK
DELIVERYTIME
IL1 MTL_SYSTEM_ITEMS.SOURCE_TYPE mtl_source_type
344

IL2 ORG_ORGANIZATION_DEFINITIONS.ORGANIZATION_CODE mtl_sourceorg_code
IL3 MTL_SYSTEM_ITEMS.SOURCE_SUBINVENTORY mtl_sourceinv_code
IL4
IL5
IL6
IL7
IL8
IL9
IL10
GLACCOUNT
CONTROLACC GL_CODE_COMBINATIONS.SEGMENT1..30 mtl_item_gl
SHRINKAGEACC GL_CODE_COMBINATIONS.SEGMENT1..30 mtl_shrink_gl
INVCOSTADJACC GL_CODE_COMBINATIONS.SEGMENT1..30 mtl_avgvar_gl
COSTCENTER
VENDOR
MANUFACTURER
MODELNUM
CATALOGCODE
IV1
IV2
IV3
IVCO1
IVCO2
IVCO3
BIDPRICE
BIDDATE
PROMDELIVERYTIME
VENDORLASTCOST
345
Chapter 3

LASTDATE
CATALOGWEBPAGE
COMPANYTYPE
NAME
ADDRESS1
ADDRESS2
ADDRESS3
ADDRESS4
CONTACT
POSITION
PHONE
FAX
FOB
FREIGHTTERMS
SHIPVIA
PAYMENTTERMS
CUSTOMERNUM
CO1
CO2
CO3
CO4
CO5
CO6
CO7
CO8
CO9
CO10
CO11
346

CO12
CO13
CHANGEBY FND_USER.USER_NAME mtl_change_by
CHANGEDATE MTL_SYSTEM_ITEMS.LAST_UPDATE_DATE mtl_change_date
INCLUSIVE1
INCLUSIVE2
INCLUSIVE3
INCLUSIVE4
INCLUSIVE5
CURRENCYCODE
COMPANYLOC
REGISTRATION1
REGISTRATION2
REGISTRATION3
REGISTRATION4
REGISTRATION5
APCONTROLACC
APSUSPENSEACC
RBNIACC
PAYVENDOR
BANKACCOUNT
REMITCONTACT
PAYONRECEIPT
HOMEPAGE
BANKNUM
DUNSNUM
TAXEXEMPTCODE
TAXEXEMPTNUM
347
Chapter 3

ECOMMERCEENABLED
DISABLED
MFGNAME
LODESC
PUTCHVARACC
INVOICEVARACC
CURVARACC
RECEIPTVARACC
USERDATA1
USERDATA2
USERDATA3
USERDATA4
USERDATA5
USERDATA6
USERDATA7
USERDATA8
USERDATA9
USERDATA10
UTRANSTYPE
348
Issues from Oracle Financials

This section provides the cross mapping for the interface tables that are used when transferring Issue data between
Oracle Financials and MAXIMO. Data is transferred from Oracle Financials’
MTL_MATERIAL_TRANSACTION to the MAXIMO MAX_ISU_INTERFACE table.
MTL_MATERIAL_TRANSACTION MAX_ISU_INTERFACE
Column Name Column Name Type Length COMMENTS
INVENTORY_ITEM_ID ITEMNUM UPPER 40 Mapped to
MTL_SYSTEM_ITEMS.SEGMENT for
the inventory_item_id of the
organization_id in Oracle Financial.
ORGANIZATION_ID STORELOC UPPER 8 Mapped to
MTL_PARAMETERS.ORGANIZATION
_CODE for the ORGANIZATION_ID.
TRANSACTION_DATE TRANSDATE DATETIME
LAST_UPDATE_DATE ACTUALDATE DATETIME
TRANSACTION_QUANTITY QUANTITY DECIMAL 15 NVL(TRANSACTION_QUANTITY,0) * -
1
CURBAL DECIMAL 15
PHYSCNT DECIMAL 15
ACTUAL_COST UNITCOST AMOUNT 10
ACTUAL_COST ACTUALCOST AMOUNT 10 NVL(ACTUAL_COST,0)
PONUM UPPER 20
CONVERSION DECIMAL 15
349
Chapter 3

WONUM UPPER 10 Obtained from INVRESERVE.WONUM
for the REQUESTNUM in MAXIMO
EQNUM UPPER 8
CREATED_BY ENTERBY UPPER 18 Mapped to FND_USER.USER_NAME
for CREATED_BY in Oracle Financial.
IT1 ALN 10
IT2 ALN 10
IT3 ALN 10
IT4 ALN 25
IT5 ALN 1
METERREADING DECIMAL 15
METERREADING2 DECIMAL 15
TRANSACTION_SOURCE_NAME MEMO ALN 254
OUTSIDE YORN 1
WPOPERATION INTEGER 4
ISSUETO UPPER 8
PACKINGSLIPNUM ALN 20
POLINENUM INTEGER 4
ROLLUP YORN 1
ITIN1 ALN 10
ITIN2 ALN 10
ITIN3 ALN 10
SUBINVENTORY_CODE BINNUM ALN 10 Mapped to SUBINVENTORY_CODE.
LOCATOR_ID BINNUM ALN 10 Mapped to SUBINVENTORY_CODE ||
Vdelimeter || LOCATOR_ID.
350

LOTNUM UPPER 30
ISSUETYPE UPPER 8 ‘ISSUE’
DISTRIBUTION_ACCOUNT_ID GLDEBITACCT ALN 36 Mapped to the GL code combination for
DISTRIBUTION_ACCOUNT_ID in
Oracle Financial
GLCREDITACCT ALN 36
LINECOST AMOUNT 10 UNITCOST*QUANTITY
LINECOST2 DECIMAL 10
FINANCIALPERIOD ALN 15
CURRENCYCODE UPPER 1
CURRENCYCODE2 UPPER 1
CURRENCYUNITCOST DECIMAL 10
ROTEQNUM UPPER 8
CURRENCYLINECOST DECIMAL 10
LOCATION UPPER 10
DESCRIPTION ALN 240
EXCHANGERATE DECIMAL 14
EXCHANGERATE2 DECIMAL 14
SPAREPARTADDED YORN 1
TRANSACTION_SOURCE_NAME REQUESTNUM UPPER 8 Mapped to the sub-string of

TRANSACTION_SOURCE_NAME.
DELLOCATION UPPER 8
DIRECTREQ YORN 1
IBUPD ALN 1
351
Chapter 3

ROWSTAMP DATETIME 10 SYSDATE
USERDATA1 ALN 1
USERDATA2 ALN 1
USERDATA3 ALN 1
USERDATA4 ALN 1
USERDATA5 ALN 1
USERDATA6 ALN 1
USERDATA7 ALN 1
USERDATA8 ALN 1
USERDATA9 ALN 1
USERDATA10 ALN 1
BATCHID ALN 25
BATCHLINEID INTEGER 4
UTRANSTYPE ALN 25
SOURCEID ALN 25 ‘I’
APISEQ INTEGER 4
APISEITE ALN 256
IMPORTSTATUS ALN 25
IMPORTTIMESTAMP DATETIME 10
IMPORTMESSAGE ALN 2000
352
Balances from Oracle Financials

This section provides the cross mapping for the interface tables that are used when transferring Balance data
between Oracle Financials and MAXIMO. Data is transferred from Oracle Financials’
MTL_MATERIAL_TRANSACTION to the MAXIMO MAX_ITM_INTERFACE table.
MTL_MATERIAL_TRANSACTION MAX_ITM_INTERFACE

INVENTORY_ITEM_ID ITEMNUM UPPER 40 Mapped to
UPPER(MTL_SYSTEM_ITEMS.SEGM
ENT1) of the item
(MTL_MATERIAL_TRANSACTIONS.N
VENTORY_ITEM_ID of the
ORGANIZATION_ID in Oracle
Financial).
DESCRIPTION ALN 240
ROTATING YORN 1
STOCKTYPE ALN 30
LOTTYPE UPPER 5
CAPITALIZED YORN 1 ‘Y’ if
FA_CATEGORIES.CAPITALIZE_FLAG
of
MTL_SYSTEM_ITEMS.ASSET_CATE
GORY_ID of the item
VENTORY ITEM ID) is ‘YES’,
353
Chapter 3

otherwise, it is set to ‘N’.
MSDSNUM ALN 40 Mapped to
PO_HAZARD_CLASSES.HAZARD_CL
ASS correspondent to
MTL_SYSTEM_ITEMS.HAZARD_CLA
SS_ID of the item
VENTORY_ITEM_ID)
OUTSIDE YORN 1 ‘N’
IN1 ALN 10
IN2 ALN 10
IN3 ALN 10
IN4 ALN 10
IN5 ALN 10
IN6 ALN 10
IN7 ALN 10
IN8 ALN 10
IN9 AMOUNT 10
IN10 DATETIME 10
IN11 ALN 3 Mapped to
MTL_SYSTEM_ITEMS.PRIMARY_UO
M_CODE of the item
VENTORY_ITEM_ID)
MTL_SYSTEM_ITEMS.VENDOR_WA
RRANTY_FLAG of the item
(MTL MATERIAL TRANSACTIONS.N
354

VENTORY_ITEM_ID)
PO_UN_NUMBERS.UN_NUMBER
correspondent to
MTL_SYSTEM_ITEMS.UN_NUMBER_
ID of the item
VENTORY_ITEM_ID)
ORGANIZATION_ID IN14 ALN 3 Mapped to
_CODE correspondent to the
MASTER_ORGANIZATION_ID of
MTL_MATERIAL_TRANSACTIONS.O
RGANIZATION_ID’s1
IN15 YORN 1
IN16 ALN 10
IN17 AMOUNT 10
IN18 ALN 10
IN19 ALN 10
IN20 ALN 10
MTL_SYSTEM_ITEMS.PURCHASING
_ITEM_FLAG of the item
VENTORY_ITEM_ID)
MTL_SYSTEM_ITEMS.INTERNAL_OR
DER_FLAG of the item
355
Chapter 3

VENTORY_ITEM_ID)
MTL_SYSTEM_ITEMS.MUST_USE_A
PPROVED_VENDOR_FLAG of the
item
VENTORY_ITEM_ID)
TAX1CODE UPPER 50 Mapped to
MTL_SYSTEM_ITEMS.TAX_CODE of
the item
VENTORY_ITEM_ID)
TAX2CODE UPPER 50
TAX3CODE UPPER 50
TAX4CODE UPPER 50
TAX5CODE UPPER 50
LDKEY INTEGER 4
SPAREPARTAUTOADD YORN 1
HAZARDID UPPER 8
CLASSSTRUCTUREID UPPER 8
INSPECTIONREQUIRED YORN 1
LOCATION UPPER 8 Mapped to
UPPER(MTL_PARAMETERS.ORGANI
ZATION_CODE) of
RGANIZATION_ID
SUBINVENTORY_CODE BINNUM ALN 10 If
MTL_MATERIAL_TRANSACTIONS.LO
CATOR_ID is null
356

LOCATOR_ID BINNUM ALN 10 If
CATOR_ID is not null, mapped to
SUBINVENTORY_CODE concatenated
by LOCATOR_ID with a delimiter
provided by OFCTL control variable
SUBLOCDEL
MINLEVEL DECIMAL 15 Mapped to
MTL_SYSTEM_ITEMS.MIN_MINMAX_
QUANTITY of the item
VENTORY_ITEM_ID)
MAXLEVEL DECIMAL 15 Mapped to
MTL_SYSTEM_ITEMS.MAX_MINMAX
_QUANTITY of the item
VENTORY_ITEM_ID)
CATEGORY UPPER 4 ‘STK’ if
MTL_SYSTEM_ITEMS.STOCK_ENAB
LED_FLAG of the item
VENTORY_ITEM_ID) is ‘Y’ or NULL,
otherwise, set to ‘NS’
ORDERUNIT ALN 25 Mapped to
MTL_SYSTEM_ITEMS.PRIMARY_UNI
T_OF_MEASURE of the item
VENTORY_ITEM_ID)
ISSUEUNIT ALN 25 Mapped to
MTL_SYSTEM_ITEMS.UNIT_OF_ISS
UE of the item
357
Chapter 3

VENTORY_ITEM_ID)
CONVERSION DECIMAL 15
QUANTITY DECIMAL 15
LOTNUM UPPER 30
CURBAL DECIMAL 15 Mapped to the sum of the
MTL_ONHAND_QUANTITIES.TRANS
ACTION_QUANTITY of the item of the
organization, sub-inventory, and
locator2
PHYSCNT DECIMAL 15
PHYSCNTDATE DATETIME 10
IB1 ALN 100 Concatenations of all the location
segment of
CATOR_ID3
IB2 ALN 10
IB3 ALN 10
IB4 DATETIME 10
IB5 INTEGER 4
RECONCILED YORN 1
ORDERQTY DECIMAL 15 Mapped to
MTL_SYSTEM_ITEMS.MAXIMUM_OR
DER_QUANTITY of the item
STDCOST AMOUNT 10 Mapped to the most recent
CST_ITEM_COSTS.MATERIAL_COST
for the item in the organization.4
AVGCOST AMOUNT 10 Mapped to the most recent
358

CST_ITEM_COSTS.ITEM_COST for
the item in the organization.4
LASTCOST AMOUNT 10 Mapped to
MTL_SYSTEM_ITEMS.LIST_PRICE_P
ER_UNIT of the item
VENTORY_ITEM_ID)
COSTCURRENCYCODE UPPER 15
COSTCURRENCYCODE2 UPPER 15
EXCHANGERATE2 DECIMAL 14
LASTISSUEDATE DATETIME 10
ISSUEYTD DECIMAL 15
ISSUE1YRAGO DECIMAL 15
ABCTYPE UPPER 1
CCF INTEGER 4
SSTOCK DECIMAL 15
DELIVERYTIME INTEGER 4
IL1 ALN 22 Mapped to
MTL_SYSTEM_ITEMS.SOURCE_TYP
E of the item
VENTORY_ITEM_ID)
_CODE correspondent to
MTL SYSTEM ITEMS.SOURCE OR
359
Chapter 3

GANIZATION_ID of the item
VENTORY_ITEM_ID)
MTL_SYSTEM_ITEMS.SOURCE_SUB
INVENTORY of the item
VENTORY_ITEM_ID)
IL4 DATETIME 10
IL5 DECIMAL 15
IL6 ALN 1
IL7 ALN 1
IL8 ALN 1
IL9 ALN 1
IL10 ALN 1
GLACCOUNT ALN 36
CONTROLACC ALN 36 Mapped to combination of GL code
correspondent to
MTL_PARAMETERS.MTL_ITEM_GL_I
D of the
RGANIZATION_ID’s5
SHRINKAGEACC ALN 36 Mapped to combination of GL code
correspondent to
MTL_PARAMETERS.MTL_SHRINK_G
L_ID of the
MTL MATERIAL TRANSACTIONS.O
360

RGANIZATION_ID’s5
INVCOSTADJACC ALN 36 Mapped to combination of GL code
correspondent to
MTL_PARAMETERS.MTL_AVGVAR_
GL_ID of the
MTL_MATERIAL_TRANSACTIONS.
ORGANIZATION_ID’s5
VENDOR UPPER 46
MANUFACTURER UPPER 46
MODELNUM ALN 25
CATALOGCODE ALN 12
IV1 ALN 10
IV2 ALN 10
IV3 ALN 1
IVCO1 ALN 10
IVCO2 ALN 25
IVCO3 ALN 25
BIDPRICE DECIMAL 10
BIDDATE DATE 4
PROMDELIVERYTIME INTEGER 4
VENDORLASTCOST DECIMAL 10
LASTDATE DATE 4
CATALOGWEBPAGE ALN 124
COMPANYTYPE UPPER 25
361
Chapter 3

NAME ALN 80
ADDRESS1 ALN 240
ADDRESS2 ALN 36
ADDRESS3 ALN 36
ADDRESS4 ALN 125
CONTACT ALN 240
POSITION ALN 30
PHONE ALN 26
FAX ALN 26
FOB ALN 25
FREIGHTTERMS ALN 50
SHIPVIA ALN 25
PAYMENTTERMS ALN 52
CUSTOMERNUM ALN 25
CO1 ALN 15
CO2 ALN 10
CO3 ALN 10
CO4 ALN 10
CO5 ALN 10
CO6 ALN 10
CO7 AMOUNT 10
CO8 DATETIME 10
362

CO9 INTEGER 4
CO10 YORN 1
CO11 ALN 10
CO12 ALN 25
CO13 ALN 25
LAST_UPDATED_BY CHANGEBY UPPER 18 NVL(FND_USER.USER_NAME, ‘API’)
correspondent to
MTL_MATERIAL_TRANSACTIONS.LA
ST_UPDATED_BY
CHANGEDATE DATETIME 10 SYSDATE
INCLUSIVE1 YORN 1
INCLUSIVE2 YORN 1
INCLUSIVE3 YORN 1
INCLUSIVE4 YORN 1
INCLUSIVE5 YORN 1
CURRENCYCODE UPPER 15
COMPANYLOC UPPER 8
REGISTRATION1 ALN 20
APCONTROLACC ALN 36
APSUSPENSEACC ALN 36
363
Chapter 3

RBNIACC ALN 36
PAYVENDOR UPPER 46
BANKACCOUNT UPPER 56
DISABLED YORN 1
REMITCONTACT ALN 240
PAYONRECEIPT YORN 1
HOMEPAGE ALN 124
BANKNUM ALN 16
DUNSNUM ALN 16
TAXEXEMPTCODE ALN 1
TAXEXEMPTNUM ALN 20
ECOMMERCEENABLED YORN 1
MFGNAME ALN 80
LODESC ALN 50
PURCHVARACC ALN 36
INVOICEVARACC ALN 36
CURVARACC ALN 36
RECEIPTVARACC ALN 36
LONGDESC ALN 2000
USERDATA1 ALN 1
USERDATA2 ALN 1
USERDATA3 ALN 1
364

USERDATA4 ALN 1
USERDATA5 ALN 1
USERDATA6 ALN 1
USERDATA7 ALN 1
USERDATA8 ALN 1
USERDATA9 ALN 1
USERDATA10 ALN 1
BATCHID ALN 25
BATCHLINEID INTEGER 4
UTRANSTYPE ALN 25 'XSB'
SOURCEID ALN 25 'I'
APISEQ INTEGER 4 Sequence APISEG.NEXTVAL
APISITE ALN 256
IMPORTSTATUS ALN 25
IMPORTTIMESTAMP DATETIME 10
IMPORTMESSAGE ALN 2000
365
Chapter 3
Reservations from MAXIMO

This section provides the cross mapping for the interface tables that are used when transferring Reservation data
between MAXIMO and Oracle Financials applications. Data is transferred from the MAXIMO
MOUT_RSV_INTERFACE table to Oracle Financials’ MTL_RESERVATIONS_INTERFACE table.

MOUT_RSV_INTERFACE MTL_RESERVATIONS_INTERFACE
RESERVATION_INTERFACE_ Number IntRec.APISEQ
ID
RESERVATION_BATCH_ID Number apiseq.nextval from Dual.
DEMAND_SOURCE_TYPE_ID Number MTL_TXN_SOURCE_TYPES.TRANSA
CTION_SOURCE_TYPE_ID whose
TRANSACTION_SOURCE_TYPE_NA
ME is ‘Inventory’
WONUM DEMAND_SOURCE_NAME Varchar2 40 ‘MISC’ ||
MOUT_RSV_INTERFACE.REQUESTN
UM. or 'WO:'||
MOUT_RSV_INTERFACE.WONUM
REQUESTNUM DEMAND_SOURCE_LINE_ID Number MOUT_RSV_INTERFACE.REQUESTN
UM
SUPPLY_SOURCE_TYPE_ID Number MTL_TXN_SOURCE_TYPES.TRANSA
CTION_SOURCE_TYPE_ID whose
TRANSACTION_SOURCE_TYPE_NA
ME is ‘Inventory’
366

SUPPLY_SOURCE_NAME Varchar2 MTL_RESERVATIONS_INTERFACE
.DEMAND_SOURCE_NAME
SUBINVENTORY_CODE Varchar2 Mapped to BINNUM form the
ITEM/LOCATION.
LOCATOR_ID Number Mapped to BINNUM form the
ITEM/LOCATION.
ROW_STATUS_CODE Number 1 (1-Active 2 -Inactive 3-Error)
LOCK_FLAG Number 2 (1-yes 2 –no)
RESERVATION_ACTION_CO Number 1 (1-ins, 2-upd, 3-del, 4-xfr)
DE
TRANSACTION_MODE Number 3 (3-background)
VALIDATION_FLAG Number 1 (1-yes, 2-no)
PARTIAL_QUANTITIES_ALLO Number 1 (1-yes, 2-no)
WED
LAST_UPDATE_DATE Date SYSDATE
ITEMNUM INVENTORY_ITEM_ID Number

LOCATION ORGANIZATION_ID Number MTL_PARAMETERS.ORGANIZATION
_ID whose ORGANIZATION_CODE is
MOUT_RSV_INTERFACE.LOCATION
WPOPERATION
ACTUALQTY
RESERVEDQTY RESERVATION_QUANTITY Number
PRIMARY_RESERVATION_Q Number MOUT_RSV_INTERFACE.
UANTITY RESERVEDQTY
367
Chapter 3

INITFLAG
.DIRECTREQ
GLACCOUNT
REQUESTEDBY CREATED_BY Number FND_USER.USER_ID for
REQUESTEDBY or ‘MAXIMO1’.
REQUESTEDDATE CREATION_DATE Date
REQUIREDDATE REQUIREMENT_DATE Date
PONUM
POLINENUM
DELLOCATION
DESCRIPTION
LDKEY
IR1
IR2
IR3
IR4
IR5
IN1
IN2
IN3
IN4
IN5
IN6
IN7
368

IN8
IN9
IN10
IN11
IN12
IN13
IN14
IN15
IN16
IN17
IN18
IN19
IN20
IN21
IN22
IN23
VENDOR
MANUFACTURER
MODELNUM
CATALOGCODE
CATEGORY
ORDERUNIT PRIMARY_UOM_CODE Varchar2 3 MTL_UOM_COVERSIONS.UOM_COD
E WHERE
UNIT_OF_MEASURE =
‘MOUT RSV INTERFACE.ORDERUNI
369
Chapter 3

T’
ISSUEUNIT RESERVATION_UOM_CODE Varchar2 3 MTL_UOM_COVERSIONS.UOM_COD
E WHERE
UNIT_OF_MEASURE =
‘MOUT_RSV_INTERFACE.ISSUEUNIT
’
CONVERSION
STDCOST
AVGCOST
LASTCOST
PARENT
STATUS
STATUSDATE
WORKTYPE
LEADCRAFT
WODESC
EQNUM
WOLOCATION
JPNUM
FAILDATE
CHANGEBY LAST_UPDATED_BY Number FND_USER.USER_ID for CHANGEBY
or ‘MAXIMO1’.
CHANGEDATE
PMNUM
HISTORYFLAG
CONTRACT
370

WOPRIORITY
WOPM6
WOPMM7
TARGCOMPDATE
TARGSTARTDATE
WOEQ1
WOEQ2
WOEQ3
WOEQ4
WOEQ5
WOEQ6
WOEQ7
WOEQ8
WOEQ9
WOEQ10
WOEQ11
WOEQ12
WO1
WO2
WO3
WO4
WO5
WO6
WO7
WO8
371
Chapter 3

WO9
WO10
REPORTEDBY
REPORTDATE
PHONE
PROBLECODE
CALENDAR
INTERRUPTABLE
ACTSTART
ACTFINISH
SCHEDSTART
SCHEDFINISH
CREWID
SUPERVISOR
WOEQ13
WOEQ14
WOPM1
WOPM2
WOPM3
WOPM4
WOPM5
WOJP1
WOJP2
WOJP3
372

WOJP4
WOJP5
WOL1
WOL2
WOL3
WOL4
RESPONDBY
EQLOCPRIORITY
CALCPRIORITY
CHARGESTORE
FAILURECODE
WOLO1
WOLO2
WOLO3
WOLO4
WOLO5
WOLO6
WOLO7
WOLO8
WOLO9
WOLO10
DISABLED
CURRENCYCODE
ROWSTAMP
373
Chapter 3

USERDATA1
USERDATA2
USERDATA3
USERDATA4
USERDATA5
USERDATA6
USERDATA7
USERDATA8
USERDATA9
USERDATA10
BATCHID
BATCHLINEID
UTRANSTYPE
SOURCEID
APISEQ
APISITE
APISYNC
IMPORTSTATUS
IMPORTTIMESTAMP
IMPORTMESSAGE
374
Purchase Orders from Oracle Financials

This section provides the cross mapping for the interface tables that are used when transferring purchase order
data between MAXIMO and Oracle Financials applications. Data is transferred from Oracle Financials purchasing
tables to the MAXIMO MAX_PO_INTERFACE table. Note that the purchase order data is transferred to
MAXIMO for completeness of the purchase requisition-purchase order-receipt-invoice cycle in MAXIMO. No
modification of the purchase order is supported.

MAX_PO_INTERFACE Table.Column API variable
PONUM PO_HEADERS.SEGMENT1 (PO NUM) UPPER(po_no)
(CONCATENATED WITH RELEASE NUMBER, FOR RELEASE
POs)
PRNUM PO_REQ_DISTRIBUTIONS.ATTRIBUTE15 rd_at15
PRLINENUM PO_REQ_DISTRIBUTIONS.ATTRIBUTE12 rd_at12
PODESCRIPTION PO_HEADERS.COMMENTS NVL(po_comments,
'Purchase Order from Oracle
FInancials')
PURCHASEAGENT PER_PEOPLE_F.FULL_NAME po_buyer
ORDERDATE PO_HEADERS.FIRM_DATE po_order_date
REQUIREDDATE
FOLLOWUPDATE
POTYPE PO_HEADERS.TYPE_LOOKUP_CODE po_type
ORIGINALPONUM
STATUS
STATUSDATE PO_HEADERS.LAST_UPDATE_DATE po_change_date
VENDOR PO_VENDORS.SEGMENT1||- UPPER(po_vnd_no)||'-
||PO_VENDOR_SITES.VENDOR_SITE_CODE '||UPPER(po_vndsite_no)
CONTACT PO VENDOR CONTACTS.FIRST NAME||MIDDLE NAME||LAST po_vndctc_no
375
Chapter 3

NAME
FREIGHTTERMS PO_HEADERS.FREIGHT_TERMS_LOOKUP_CODE po_freight
PAYMENTTERMS AP_TERMS.NAME po_terms
SHIPVIA PO_HEADERS.SHIP_VIA_LOOKUP_CODE po_shipvia
CUSTOMERNUM PO_HEADERS.VENDOR_ORDER_NUM po_vndord_no
FOB PO_HEADERS.FOB_LOOKUP_CODE po_fob
SHIPTO HR_LOCATIONS.LOCATION_CODE po_shipto
SHIPTOATTN PER_PEOPLE_F.FULL_NAME po_shiptoattn
BILLTO HR_LOCATIONS.LOCATION_CODE po_billto
BILLTOATTN
TOTALCOST 0
CHANGEBY FND_USER.USER_NAME po_change_by
CHANGEDATE PO_HEADERS.LAST_UPDATE_DATE po_change_date
PRIORITY 0
HISTORYFLAG sYes,sNo
PO1
PO2
PO3
PO4
PO5
PO6
PO7
PO8
PO9
PO10
CURRENCYCODE PO_HEADERS.CURRENCY_CODE UPPER(po_currency)
EXCHANGERATE PO_HEADERS.RATE po_xchg
EXCHANGEDATE PO_HEADERS.RATE_DATE po_xchg_date
BUYAHEAD
376

TOTALTAX1
TOTALTAX2
TOTALTAX3
INCLUSIVE1
INCLUSIVE2
INCLUSIVE3
INTERNAL
TOTALTAX4
TOTALTAX5
INCLUSIVE4
INCLUSIVE5
STARTDATE
ENDDATE
PAYONRECEIPT
WFID
WFACTIVE
BAYERCOMPANY
ITEMNUM PO_REQ_DISTRIBUTIONS.ATTRIBUTE14,MTL_SYSTEM_ITEMS. NVL(rd_at14,UPPER(pl_itm_no))
SEGMENT1
STORELOC PO_REQ_DISTRIBUTIONS.ATTRIBUTE13 rd_at13
MODELNUM PO_LINES.VENDOR_PRODUCT_NUM pl_vnd_itm_no
CATALOGCODE
ORDERQTY PO_DISTRIBUTIONS.QUANTITY_ORDERED pd_ordqty
ORDERUNIT PO_LINES.UNIT_MEAS_LOOKUP_CODE pl_uom
UNITCOST PO_LINES.UNIT_PRICE pl_unit_price
CONVERSION
RECEIVEDQTY
RECEIVEDUNITCOST
RECEIVEDTOTALCOST
377
Chapter 3

REJECTEDQTY
COSTCENTER
VENDELIVERYDATE PO_LINE_LOCATIONS.PROMISED_DATE pl_vnd_date
TAXED PO_LINE_LOCATIONS.TAXABLE_FLAG ps_taxed
ENTERDATE PO_HEADERS.LAST_UPDATE_DATE pl_change_date
ENTERBY FND_USER.USER_NAME pl_change_by
DESCRIPTION PO_LINES.ITEM_DESCRIPTION pl_itm_desc
PL1 MAXPOREC.PLIN1 OFPOAPIRec.pl_cat_id; holds the
cat id for item and service
PL2
PL3
PL4 PO_LINES.CONTRACT_NUM pl_contract_no
PL5 PO_LINES.CAPITAL_EXPENSE_FLAG pl_capital
WONUM
REQUESTEDBY
REQDELIVERYDATE
ISSUE
POLINENUM PO_LINES.LINE_NUM 1'||LTRIM(TO_CHAR(pl_no,'0999'))
||PO_LINE_LOCATIONS.SHIPMENT_NUM ||LTRIM(TO_CHAR(ps_no,'0999'))
||PO_DISTRIBUTIONS.DISTRIBUTION_NUM ||LTRIM(TO_CHAR(pd_no,'0999'))
WPOPERATION
PLIN1
PLIN2
PLIN3
PLIN4
PLIN5
EQNUM
CHARGESTORE
GLDEBITACCT GL_CODE_COMBINATIONS.SEGMENT1..30 pd_charge_gl
378

GLCREDITACCT
LINECOST
TAX1CODE PO_LINE_LOCATIONS.TAX_NAME ps_tax_name
TAX1 PO_LINE_LOCATIONS.ESTIMATED_TAX_AMOUNT ps_tax_amt
TAX2CODE
TAX2
TAX3CODE
TAX3
SCHARGECODE
RECEIPTREQD
MANUFACTURER
SERVICE
TAX4CODE
TAX4
TAX5CODE
TAX5
SUPERVISOR
CATEGORY
REMARK
LOCATION
LOADEDCOST
PRORATESERVICE
AGREEMENTPONUM
AGREEMENTPOTYPE
RECEIPTSCOMPLETE
INSPECTIONREQUIRED
PRORATECOST
POLINEID
COMPANYTYPE
379
Chapter 3

NAME
ADDRESS1
ADDRESS2
ADDRESS3
ADDRESS4
PHONE
FAX
CO1
CO2
CO3
CO4
CO5
CO6
CO7
CO8
CO9
CO10
CO11
CO12
CO13
COMPANYLOC
REGISTRATION1
REGISTRATION2
REGISTRATION3
APCONTROLACC
APSUSPENSEACC
RBNIACC
PAYVENDOR
BANKACCOUNT
380

REGISTRATION4
REGISTRATION5
POLONGDESC
POLINELONGDESC
USERDATA1
USERDATA2
USERDATA3
USERDATA4
USERDATA5
USERDATA6
USERDATA7
USERDATA8
USERDATA9
USERDATA10
UTRANSTYPE 'HEADER','LINE'
APISYNC PO_REQ_DISTRIBUTIONS.ATTRIBUTE11 rd_at11
381
Chapter 3
Receipts from Oracle Financials

This section provides the cross mapping for the interface tables that are used when transferring receipt data
between MAXIMO and Oracle Financials applications. Data is transferred from several Oracle Financials
purchasing tables to the MAXIMO MAX_RCV_INTERFACE table.
MAX_RCV_INTERFACE Table.Column API variable

ITEMNUM PO_REQ_DISTRIBUTIONS.ATTRIBUTE14, NVL(rcv_req_at14,
MTL_SYSTEM_ITEMS.SEGMENT1 UPPER(rcv_itm_no))
TOSTORELOC PO_REQ_DISTRIBUTIONS.ATTRIBUTE13 rcv_req_at13
TRANSDATE RCV_TRANSACTIONS.LAST_UPDATE_DATE rcv_change_date
ACTUALDATE RCV_TRANSACTIONS.TRANSACTION_DATE rcv_enter_date
QUANTITY RCV_TRANSACTIONS.QUANTITY rcv_quantity
RECEIVEDUNIT RCV_TRANSACTIONS.UNIT_OF_MEASURE rcv_uom
ISSUETYPE
UNITCOST RCV_TRANSACTIONS.PO_UNIT_PRICE rcv_po_unitcost
ACTUALCOST RCV_SHIPMENT_LINES.SHIPMENT_UNIT_PRICE,RCV_TRANSA NVL(shp_unit_cost,
CTIONS.PO_UNIT_PRICE rcv_po_unitcost)
PONUM PO_HEADERS.SEGMENT1 UPPER(rcv_po_no)
INVOICENUM
REJECTCODE RCV_TRANSACTIONS.RMA_REFERENCE rcv_rma_ref
REJECTQTY
REJECTCOST
CONVERSION RCV_SHIPMENT_LINES.UOM_CONVERSION_RATE NVL(shp_uom_rate,1)
WONUM
EQNUM
ENTERBY FND_USER.USER_NAME rcv_change_by
382

IT1
IT2
IT3
IT4
IT5
OUTSIDE
WPOPERATION
COSTCENTER
ISSUETO
PACKINGSLIPNUM RCV_SHIPMENT_LINES.PACKING_SLIP,RCV_SHIPMENT_HEAD NVL(shp_pack_slip,
ERS.WAYBILL_AIRBILL_NUM shp_waybill_no)
POLINENUM PO_LINES.LINE_NUM 1'||LTRIM(TO_CHAR(rcv_pl_no,'0
||PO_LINE_LOCATIONS.SHIPMENT_NUM 999'))
||PO_DISTRIBUTIONS.DISTRIBUTION_NUM ||LTRIM(TO_CHAR(rcv_ps_no,'09
99'))
||LTRIM(TO_CHAR(rcv_pd_no,'09
99'))
ISSUE
REQUESTEDBY
TOTALCURBAL
OLDAVGCOST
ITIN1
ITIN2
ITIN3
TOBIN RCV_TRANSACTIONS.SUBINVENTORY rcv_inv
TOLOT RCV_TRANSACTIONS.VENDOR_LOT_NUM rcv_vnd_lot
FROMLOT RCV_TRANSACTIONS.VENDOR_LOT_NUM rcv_vnd_lot
GLDEBITACCT GL_CODE_COMBINATIONS.SEGMENT1..30 rcv_charge_gl
383
Chapter 3

GLCREDITACCT
LINECOST (RCV_SHIPMENT_LINES.SHIPMENT_UNIT_PRICE,RCV_TRANSA NVL(NVL(shp_unit_cost,
CTIONS.PO_UNIT_PRICE) rcv_po_unitcost),0)
*RCV_TRANSACTIONS.QUANTITY *NVL(rcv_quantity,1)
FINANCIALPERIOD
CURRENCYCODE RCV_TRANSACTIONS.CURRENCY_CODE rcv_currency
EXCHANGERATE RCV_TRANSACTIONS.CURRENCY_CONVERSION_RATE NVL(rcv_xchg,1)
CURRENCYUNITCOST (RCV_SHIPMENT_LINES.SHIPMENT_UNIT_PRICE,RCV_TRANSA vcur_unit_cost
CTIONS.PO_UNIT_PRICE)
*RCV_TRANSACTIONS.CURRENCY_CONVERSION_RATE
MANUFACTURER
MODELNUM RCV_SHIPMENT_LINES.VENDOR_ITEM_NUM shp_vnditm_no
CURRENCYLINECOST ((RCV_SHIPMENT_LINES.SHIPMENT_UNIT_PRICE,RCV_TRANS NVL(vcur_unit_cost,0)
ACTIONS.PO_UNIT_PRICE) *NVL(rcv_quantity,1)
*RCV_TRANSACTIONS.CURRENCY_CONVERSION_RATE)
*RCV_TRANSACTIONS.QUANTITY
LOCATION
DESCRIPTION PO_LINES.ITEM_DESCRIPTION rcv_itm_desc
REMARK RCV_TRANSACTIONS.COMMENTS rcv_comment
FROMSTORELOC ORG_ORGANIZATION_DEFINITIONS.ORGANIZATION_CODE UPPER(shp_forg_code)
FROMBIN
QTYHELD
LOADEDCOST
TAX1CODE
TAX1
TAX2CODE
TAX2
TAX3CODE
384

TAX3
TAX4CODE
TAX4
TAX5CODE
TAX5
PRORATED
PRORATEDCOST
STATUS
STATUSDATE
STATUSCHANGEBY
VENDORINVOICENUM
CURBAL
CLAIMNUM
APPROVED
APPROVEDATE
APPROVEBY
USERDATA1
USERDATA2
USERDATA3
USERDATA4
USERDATA5
USERDATA6
USERDATA7
USERDATA8
USERDATA9
USERDATA10
UTRANSTYPE
APISYNC PO_REQ_DISTRIBUTIONS.ATTRIBUTE11 rcv_req_at11
385
Chapter 3
Vendors from Oracle Financials

This section provides the cross mapping for the interface tables that are used when transferring vendor data
between MAXIMO and Oracle Financials applications. Data is transferred from several Oracle Financials vendor
tables to the MAXIMO MAX_COM_INTERFACE table. (Note that the MAXIMO interface table is also used to
transfer data from the MAXIMO Companies table. The SOURCEID indicates the direction of data and must be
present in order to aviod recursive updates or endless loops.)
MAX_COM_INTERFACE Table.Column API variable

COMPANY PO_VENDORS.SEGMENT1 UPPER(vnd_segment1)
||'-'||PO_VENDOR_SITES.VENDOR_SITE_CODE ||'-'||UPPER(vnd_site)
TYPE PO_VENDORS.VENDOR_TYPE_LOOKUP_CODE vnd_type
NAME PO_VENDORS.VENDOR_NAME vnd_name
ADDRESS1 PO_VENDOR_SITES.ADDRESS_LINE1 vnd_addr1
ADDRESS4 PO_VENDOR_SITES.CITY vnd_city
||PO_VENDOR_SITES.STATE ||' '||vnd_state
||PO_VENDOR_SITES.PROVINCE ||' '||vnd_province
||PO_VENDOR_SITES.ZIP ||' '||vnd_zip
||PO_VENDOR_SITES.COUNTRY ||' '||vnd_country
CONTACT PO_VENDOR_CONTACTS.FIRST_NAME vnd_ctc_fname|
||PO_VENDOR_CONTACTS.MIDDLE_NAME |' '||vnd_ctc_mname
||PO_VENDOR_CONTACTS.LAST_NAME ||' '||vnd_ctc_lname
POSITION PO_VENDOR_CONTACTS.TITLE vnd_ctc_title
PHONE
FAX
386

FOB PO_VENDORS.FOB_LOOKUP_CODE vnd_fob
FREIGHTTERMS PO_VENDORS.FREIGHT_TERMS_LOOKUP_CODE vnd_freight
SHIPVIA PO_VENDORS.SHIP_VIA_LOOKUP_CODE vnd_ship_via
PAYMENTTERMS PO_VENDORS.TERMS_ID vnd_terms
CUSTOMERNUM PO_VENDORS.CUSTOMER_NUM vnd_cst_num
CO1 PO_VENDOR_SITES.VENDOR_SITE_CODE UPPER(vnd_site)
CO2
CO3
CO4
CO5
CO6
CO7
CO8
CO9
CO10
CO11
CO12 PO_VENDORS.ORGANIZATION_TYPE_LOOKUP_CODE vnd_org
CO13 PO_VENDORS.STANDARD_INDUSTRY_CLASS vnd_class
CHANGEBY FND_USER.USER_NAME vnd_change_by
CHANGEDATE PO_VENDORS.LAST_UPDATE_DATE vnd_change_date
INCLUSIVE1
INCLUSIVE2
INCLUSIVE3
INCLUSIVE4
INCLUSIVE5
TAX1CODE
TAX2CODE
TAX3CODE
387
Chapter 3

TAX4CODE
TAX5CODE
CURRENCYCODE PO_VENDORS.INVOICE_CURRENCY_CODE vnd_invc_currency
LOCATION
REGISTRATION1
REGISTRATION2
REGISTRATION3
REGISTRATION4
REGISTRATION5
APCONTROLACC GL_CODE_COMBINATIONS.SEGMENT1..30 vnd_apcontrol_gl
APSUSPENSEACC
RBNIACC
PAYVENDOR PO_VENDORS.BANK_ACCOUNT_NAME vnd_bank_acname
BANKACCOUNT PO_VENDORS.BANK_NUM vnd_bank_num
||PO_VENDORS.BANK_ACCOUNT_NUM ||vnd_bank_acnum
DISABLED
LDKEY
REMITADDRESS1
REMITADDRESS2
REMITADDRESS3
REMITADDRESS4
REMITCONTACT
PAYONRECEIPT
HOMEPAGE
BANKNUM
DUNSNUM
TAXEXEMPTCODE
TAXEXEMPTNUM
388

ECOMMERCEENABLED
VOICEPHONE
FAXPHONE
EMAIL
HOMEPHONE
PAGERPHONE
CNT1
CNT2
CNT3
CNT4
CNT5
PROCUREMENTCARDNUM
PROCARDEXPIREDATE
USERDATA1
USERDATA2
USERDATA3
USERDATA4
USERDATA5
USERDATA6
USERDATA7
USERDATA8
USERDATA9
USERDATA10
UTRANSTYPE
389
Chapter 3
Journal Transactions from MAXIMO

This section provides the cross mapping for the interface tables that are used when transferring journal entry data
MOUT_GL_INTERFACE table to Oracle Financials’ GL_INTERFACE table.
GL_INTERFACE MOUT_GL_INTERFACE
STATUS 'NEW'
SET_OF_BOOKS_ID OFCTL:GLSOBID
ACCOUNTING_DATE NVL(ENTERDATE,TRANSDATE)
CURRENCY_CODE NVL(CURRENCYCODE,'USD')
DATE_CREATED TRANSDATE
CREATED_BY APISEQ
ACTUAL_FLAG 'A'
USER_JE_CATEGORY_NAME OFCTL:JE???
USER_JE_SOURCE_NAME 'MAXIMO1'
CURRENCY_CONVERSION_DATE NVL(ENTERDATE,TRANSDATE)
ENCUMBRANCE_TYPE_ID
BUDGET_VERSION_ID
USER_CURRENCY_CONVERSION_TYPE OFCTL:GLCURNCYTYPE
CURRENCY_CONVERSION_RATE EXCHANGERATE
SEGMENT1
SEGMENT2
SEGMENT3
SEGMENT4
SEGMENT5
SEGMENT6
390
SEGMENT7
SEGMENT8
SEGMENT9
SEGMENT10
SEGMENT11
SEGMENT12
SEGMENT13
SEGMENT14
SEGMENT15
SEGMENT16
SEGMENT17
SEGMENT18
SEGMENT19
SEGMENT20
SEGMENT21
SEGMENT22
SEGMENT23
SEGMENT24
SEGMENT25
SEGMENT26
SEGMENT27
SEGMENT28
SEGMENT29
SEGMENT30
ENTERED_DR LINECOST for GLDEBITACCT if LINECOST is +ve
LINECOST for GLCREDITACCT if LINECOST is -ve
ENTERED_CR LINECOST for GLCREDITACCT if LINECOST is +ve
LINECOST for GLDEBITACCT if LINECOST is -ve
391
Chapter 3
ACCOUNTED_DR CURRENCYLINECOST for GLDEBITACCT if LINECOST is +ve
CURRENCYLINECOST for GLCREDITACCT if LINECOST is -ve
ACCOUNTED_CR CURRENCYLINECOST for GLCREDITACCT if LINECOST is +ve
CURRENCYLINECOST for GLDEBITACCT if LINECOST is -ve
TRANSACTION_DATE
REFERENCE1 BATCHID
REFERENCE2
REFERENCE3
REFERENCE4
REFERENCE5
REFERENCE6 APISEQ
REFERENCE7
REFERENCE8
REFERENCE9
REFERENCE10 DESCRIPTION
REFERENCE11
REFERENCE12
REFERENCE13
REFERENCE14
REFERENCE15
REFERENCE16
REFERENCE17
REFERENCE18
REFERENCE19
REFERENCE20
REFERENCE21 WONUM
REFERENCE22 WPOPERATION
REFERENCE23 EQNUM
392
REFERENCE24 LOCATION
REFERENCE25 PONUM
REFERENCE26 JE1
REFERENCE27 JE2
REFERENCE28 JE3
REFERENCE29 JE4
REFERENCE30 JE5
JE_BATCH_ID
PERIOD_NAME
JE_HEADER_ID
JE_LINE_NUM
CHART_OF_ACCOUNTS_ID OFCTL:GLCOAID
FUNCTIONAL_CURRENCY_CODE OFCTL:GLCURNCY
CODE_COMBINATION_ID GLDEBITACCT/GLCREDITACCT
,i.e., one row for Debit and one row for Credit
DATE_CREATED_IN_GL
WARNING_CODE
STATUS_DESCRIPTION
STAT_AMOUNT
GROUP_ID
REQUEST_ID
SUBLEDGER_DOC_SEQUENCE_ID
SUBLEDGER_DOC_SEQUENCE_VALUE
ATTRIBUTE1
ATTRIBUTE2
ATTRIBUTE3
ATTRIBUTE4
ATTRIBUTE5
393
Chapter 3
ATTRIBUTE6
ATTRIBUTE7
ATTRIBUTE8
ATTRIBUTE9
ATTRIBUTE10
ATTRIBUTE11
ATTRIBUTE12
ATTRIBUTE13
ATTRIBUTE14
ATTRIBUTE15
ATTRIBUTE16
ATTRIBUTE17
ATTRIBUTE18
ATTRIBUTE19
ATTRIBUTE20
CONTEXT
CONTEXT2
INVOICE_DATE
TAX_CODE
INVOICE_IDENTIFIER
INVOICE_AMOUNT
CONTEXT3
USSGL_TRANSACTION_CODE
DESCR_FLEX_ERROR_MESSAGE
394
Items from MAXIMO

This section provides the cross mapping for the interface tables that are used when transferring item data between
MAXIMO and Oracle Financials applications. Data is transferred from the MAXIMO MAX_ITM_INTERFACE
table to Oracle Financials’ MTL_SYSTEM_ITEMS_INTERFACE table. (Note that the MAXIMO interface table
is also used to transfer data into the MAXIMO Inventory. The SOURCEID indicates the direction of data and
must be present in order to aviod recursive updates or endless loops.)
MTL_SYSTEM_ITEMS_INTERFACE MAX_ITM_INTERFACE
INVENTORY_ITEM_ID
ORGANIZATION_ID
LAST_UPDATE_DATE SYSDATE
LAST_UPDATED_BY MAXIMO1 ID
CREATION_DATE SYSDATE
CREATED_BY MAXIMO1 ID
LAST_UPDATE_LOGIN
SUMMARY_FLAG
ENABLED_FLAG 'Y'
START_DATE_ACTIVE
END_DATE_ACTIVE
DESCRIPTION DESCRIPTION
BUYER_ID
ACCOUNTING_RULE_ID
INVOICING_RULE_ID
SEGMENT1 ITEMNUM
SEGMENT2
SEGMENT3
395
Chapter 3

SEGMENT4
SEGMENT5
SEGMENT6
SEGMENT7
SEGMENT8
SEGMENT9
SEGMENT10
SEGMENT11
SEGMENT12
SEGMENT13
SEGMENT14
SEGMENT15
SEGMENT16
SEGMENT17
SEGMENT18
SEGMENT19
SEGMENT20
ATTRIBUTE_CATEGORY
ATTRIBUTE1
ATTRIBUTE2
ATTRIBUTE3
ATTRIBUTE4
ATTRIBUTE5
ATTRIBUTE6
ATTRIBUTE7
ATTRIBUTE8
ATTRIBUTE9
ATTRIBUTE10
ATTRIBUTE11
ATTRIBUTE12
396

ATTRIBUTE13
ATTRIBUTE14
ATTRIBUTE15
PURCHASING_ITEM_FLAG NVL(IN21,'Y')
SHIPPABLE_ITEM_FLAG OFCTL.ITMINT
CUSTOMER_ORDER_FLAG
INTERNAL_ORDER_FLAG OFCTL.ITMINT
SERVICE_ITEM_FLAG
INVENTORY_ITEM_FLAG If OFCTL.ITMINV and INVENTORY.CATEGORY = 'STK' then 'Y' Else 'N'
ENG_ITEM_FLAG
INVENTORY_ASSET_FLAG
PURCHASING_ENABLED_FLAG NVL(IN21,'Y')
CUSTOMER_ORDER_ENABLED_FLAG
INTERNAL_ORDER_ENABLED_FLAG OFCTL.ITMINT
SO_TRANSACTIONS_FLAG
MTL_TRANSACTIONS_ENABLED_FLAG 'Y'
STOCK_ENABLED_FLAG
BOM_ENABLED_FLAG
BUILD_IN_WIP_FLAG
REVISION_QTY_CONTROL_CODE
ITEM_CATALOG_GROUP_ID
CATALOG_STATUS_FLAG
RETURNABLE_FLAG 'Y'
DEFAULT_SHIPPING_ORG
COLLATERAL_FLAG
TAXABLE_FLAG 'Y'
QTY_RCV_EXCEPTION_CODE
ALLOW_ITEM_DESC_UPDATE_FLAG 'Y'
INSPECTION_REQUIRED_FLAG
RECEIPT_REQUIRED_FLAG 'Y'
397
Chapter 3

MARKET_PRICE
HAZARD_CLASS_ID
RFQ_REQUIRED_FLAG
QTY_RCV_TOLERANCE
LIST_PRICE_PER_UNIT
UN_NUMBER_ID
PRICE_TOLERANCE_PERCENT
ASSET_CATEGORY_ID
ROUNDING_FACTOR
UNIT_OF_ISSUE
ENFORCE_SHIP_TO_LOCATION_CODE
ALLOW_SUBSTITUTE_RECEIPTS_FLAG
ALLOW_UNORDERED_RECEIPTS_FLAG
ALLOW_EXPRESS_DELIVERY_FLAG
DAYS_EARLY_RECEIPT_ALLOWED
DAYS_LATE_RECEIPT_ALLOWED
RECEIPT_DAYS_EXCEPTION_CODE
RECEIVING_ROUTING_ID
INVOICE_CLOSE_TOLERANCE
RECEIVE_CLOSE_TOLERANCE
AUTO_LOT_ALPHA_PREFIX
START_AUTO_LOT_NUMBER
LOT_CONTROL_CODE
SHELF_LIFE_CODE
SHELF_LIFE_DAYS
SERIAL_NUMBER_CONTROL_CODE
START_AUTO_SERIAL_NUMBER
AUTO_SERIAL_ALPHA_PREFIX
SOURCE_TYPE
SOURCE_ORGANIZATION_ID
398

SOURCE_SUBINVENTORY
EXPENSE_ACCOUNT
ENCUMBRANCE_ACCOUNT
RESTRICT_SUBINVENTORIES_CODE '2'
UNIT_WEIGHT
WEIGHT_UOM_CODE
VOLUME_UOM_CODE
UNIT_VOLUME
RESTRICT_LOCATORS_CODE '2'
LOCATION_CONTROL_CODE '1'
SHRINKAGE_RATE
ACCEPTABLE_EARLY_DAYS
PLANNING_TIME_FENCE_CODE
DEMAND_TIME_FENCE_CODE
LEAD_TIME_LOT_SIZE
STD_LOT_SIZE
CUM_MANUFACTURING_LEAD_TIME
OVERRUN_PERCENTAGE
MRP_CALCULATE_ATP_FLAG
ACCEPTABLE_RATE_INCREASE
ACCEPTABLE_RATE_DECREASE
CUMULATIVE_TOTAL_LEAD_TIME
PLANNING_TIME_FENCE_DAYS
DEMAND_TIME_FENCE_DAYS
END_ASSEMBLY_PEGGING_FLAG
REPETITIVE_PLANNING_FLAG
PLANNING_EXCEPTION_SET
BOM_ITEM_TYPE
PICK_COMPONENTS_FLAG
REPLENISH_TO_ORDER_FLAG
399
Chapter 3

BASE_ITEM_ID
ATP_COMPONENTS_FLAG
ATP_FLAG
FIXED_LEAD_TIME
VARIABLE_LEAD_TIME
WIP_SUPPLY_LOCATOR_ID
WIP_SUPPLY_TYPE
WIP_SUPPLY_SUBINVENTORY
PRIMARY_UOM_CODE
PRIMARY_UNIT_OF_MEASURE
ALLOWED_UNITS_LOOKUP_CODE
COST_OF_SALES_ACCOUNT
SALES_ACCOUNT
DEFAULT_INCLUDE_IN_ROLLUP_FLAG
INVENTORY_ITEM_STATUS_CODE
INVENTORY_PLANNING_CODE
PLANNER_CODE
PLANNING_MAKE_BUY_CODE
FIXED_LOT_MULTIPLIER
ROUNDING_CONTROL_TYPE
CARRYING_COST
POSTPROCESSING_LEAD_TIME
PREPROCESSING_LEAD_TIME
FULL_LEAD_TIME
ORDER_COST
MRP_SAFETY_STOCK_PERCENT
MRP_SAFETY_STOCK_CODE
MIN_MINMAX_QUANTITY
MAX_MINMAX_QUANTITY
MINIMUM_ORDER_QUANTITY
400

FIXED_ORDER_QUANTITY
FIXED_DAYS_SUPPLY
MAXIMUM_ORDER_QUANTITY
ATP_RULE_ID
PICKING_RULE_ID
RESERVABLE_TYPE
POSITIVE_MEASUREMENT_ERROR
NEGATIVE_MEASUREMENT_ERROR
ENGINEERING_ECN_CODE
ENGINEERING_ITEM_ID
ENGINEERING_DATE
SERVICE_STARTING_DELAY
VENDOR_WARRANTY_FLAG
SERVICEABLE_COMPONENT_FLAG
SERVICEABLE_PRODUCT_FLAG
BASE_WARRANTY_SERVICE_ID
PAYMENT_TERMS_ID
PREVENTIVE_MAINTENANCE_FLAG
PRIMARY_SPECIALIST_ID
SECONDARY_SPECIALIST_ID
SERVICEABLE_ITEM_CLASS_ID
TIME_BILLABLE_FLAG
MATERIAL_BILLABLE_FLAG
EXPENSE_BILLABLE_FLAG
PRORATE_SERVICE_FLAG
COVERAGE_SCHEDULE_ID
SERVICE_DURATION_PERIOD_CODE
SERVICE_DURATION
WARRANTY_VENDOR_ID
MAX_WARRANTY_AMOUNT
401
Chapter 3

RESPONSE_TIME_PERIOD_CODE
RESPONSE_TIME_VALUE
NEW_REVISION_CODE
INVOICEABLE_ITEM_FLAG
TAX_CODE TAX1CODE
INVOICE_ENABLED_FLAG
MUST_USE_APPROVED_VENDOR_FLAG
REQUEST_ID
PROGRAM_APPLICATION_ID
PROGRAM_ID
PROGRAM_UPDATE_DATE
OUTSIDE_OPERATION_FLAG
OUTSIDE_OPERATION_UOM_TYPE
SAFETY_STOCK_BUCKET_DAYS
AUTO_REDUCE_MPS
COSTING_ENABLED_FLAG
CYCLE_COUNT_ENABLED_FLAG
DEMAND_SOURCE_LINE
COPY_ITEM_ID
SET_ID
REVISION
AUTO_CREATED_CONFIG_FLAG
ITEM_TYPE STOCKTYPE
MODEL_CONFIG_CLAUSE_NAME
SHIP_MODEL_COMPLETE_FLAG
MRP_PLANNING_CODE
RETURN_INSPECTION_REQUIREMENT
DEMAND_SOURCE_TYPE
DEMAND_SOURCE_HEADER_ID
TRANSACTION_ID
402

PROCESS_FLAG '1'
ORGANIZATION_CODE If OFCTL.GENSTORE or LOCATION is null then OFCTL.ITMORG
Else LOCATION
ITEM_NUMBER
COPY_ITEM_NUMBER
TEMPLATE_ID
TEMPLATE_NAME
COPY_ORGANIZATION_ID
COPY_ORGANIZATION_CODE
ATO_FORECAST_CONTROL
TRANSACTION_TYPE 'CREATE'
MATERIAL_COST
MATERIAL_SUB_ELEM
MATERIAL_OH_RATE
MATERIAL_OH_SUB_ELEM
MATERIAL_SUB_ELEM_ID
MATERIAL_OH_SUB_ELEM_ID
403
Chapter 3
Purchase Orders from MAXIMO with the CAI PO Interface Tables

This section provides the cross mapping for the CAI PO interface tables that are used when transferring PO data
between MAXIMO and Oracle Financials. Data is transferred from the MAXIMO MOUT_PO_INTERFACE
table to Oracle Financials’ PO_HEADERS_INTERFACE_CAI_ALL, PO_LINES_INTERFACE_CAI_ALL,
PO_RELEASES_INTERFACE_CAI_ALL, PO_SHIPMENTS_INTERFACE_CAI_ALL, and
PO_DISTRIB_INTERFACE_CAI_ALL table.
MOUT_PO_INTERFACE PO_HEADERS_INTERFACE_CAI_ALL

po_header_id NUMBER 15 Null
REQUESTEDBY agent_id NUMBER Employee ID for the PO.REQUESTEDBY if
not null and GENUSR = N, else Employee ID
for ‘MAXIMO1’
POTYPE type_lookup_code ALN 25 If PO.POTYPE = STD, then value is
‘STANDARD’
If PO.POTYPE = BLK or REL, then value is
‘BLANKET’
last_update_date DATE SYSDATE
ENTERBY last_updated_by NUMBER 15 User ID for the PO.ENTERBY if not null and
GENUSR = N, else User ID for ‘MAXIMO1’
PONUM segment1 ALN 20 If PO.POTYPE is REL, then the
PO.ORIGINALPONUM is used to populate
this column
summary_flag ALN 1 ‘N’
404

enabled_flag ALN 1 ‘Y’
segment2 ALN 20 Null
start_date_active DATE Null
end_date_active DATE Null
last_update_login NUMBER 15 Null
ORDERDATE creation_date DATE
created_by NUMBER 15 Last_updated_by
VENDOR vendor_id NUMBER 15 Vendor Id associated to PO.VENDOR (pos 1
to delimiter ‘-‘)
VENDOR vendor_site_id NUMBER 15 Vendor Site Id associated to PO.VENDOR
(pos after delimiter ‘-‘ to the end)
vendor_contact_id NUMBER 15 Null
SHIPTO ship_to_location_id NUMBER 15 Ship to Id associated to PO.SHIPTO
BILLTO bill_to_location_id NUMBER 15 Bill to Id associated to PO.BillTO
PAYMENTTERMS terms_id NUMBER 15 Terms Id associated to
PO.PAYMENTTERMS, If null, uses value
from OFCTL/PAYTERMSID
SHIPVIA ship_via_lookup_code ALN 25
FOB fob_lookup_code ALN 25
FREIGHTTERMS freight_terms_lookup_code ALN 25
status_lookup_code ALN 25 ‘APPROVED’
CURRENCYCODE currency_code ALN 15
rate_type ALN 25 Value from OFCTL/GLCURNCYTYPE
405
Chapter 3

EXCHANGEDATE rate_date DATE
EXCHANGERATE rate NUMBER
from_header_id NUMBER 15 Null
from_type_lookup_code ALN 25 Null
start_date DATE Null
end_date DATE Null
TOTALCOST blanket_total_amount NUMBER Populated only when po.potype = ‘BLANK’
authorization_status ALN 20 ‘APPROVED’
revision_num NUMBER 0
revised_date ALN 25 Null
approved_flag ALN 1 ‘Y’
STATUSDATE approved_date DATE If po.statusdate is null then loads sysdate
amount_limit NUMBER Blanket_total_amount
min_release_amount NUMBER 1
note_to_vendor ALN 240 Null
note_to_receiver ALN 240 'Approved MAXIMO1 Purchase Order :
'||PO.PONUM
print_count NUMBER 15 0
printed_date DATE Null
vendor_order_num ALN 25 Null
confirming_order_flag ALN 1 ‘N’
PODESCRIPTION comments ALN 240
reply_date DATE Null
reply_method_lookup_code ALN 25 Null
406

rfq_close_date DATE Null
quote_type_lookup_code ALN 25 Null
quotation_class_code ALN 25 Null
quote_warning_delay_unit ALN 25 Null
quote_warning_delay NUMBER 15 Null
quote_vendor_quote_number ALN 25 Null
acceptance_required_flag ALN 1 ‘N’
acceptance_due_date DATE Null
closed_date DATE Null
user_hold_flag ALN 1 Null
approval_required_flag ALN 1 Null
cancel_flag ALN 1 ‘N’
firm_status_lookup_code ALN 30 ‘N’
frozen_flag ALN 1 ‘N’
attribute_category ALN 30 ‘Default’
attribute1 ALN 150 Segment1
attribute2 ALN 150 Null
407
Chapter 3

PONUM attribute15 ALN 150 Populated only if po.potype = ‘REL’
closed_code ALN 25 ‘OPEN’
ussgl_transaction_code ALN 30 Null
government_context ALN 30 Null
request_id NUMBER Null
program_application_id NUMBER Null
program_id NUMBER Null
program_update_date DATE Null
APISYNC transaction_id NUMBER
transaction_type ALN 20 Either ‘CREATE’ or ‘UPDATE’ based on po
already sent to Oracle
delete_after_process ALN 1 ‘N’
status_code ALN 15 Null
org_id NUMBER Operating unit – from either
OFCTL/OPERUNITID or entered in extra
column (PO1-PO10) on PO form
408

MOUT_PO_INTERFACE PO_LINES_INTERFACE_CAI_ALL
po_line_id NUMBER 15 Null
last_update_date DATE Sysdate
ENTERBY last_updated_by NUMBER 15 User ID for the PO.ENTERBY if not null
and GENUSR = N, else User ID for
‘MAXIMO1’
line_type_id NUMBER 15 If Service uses value in
OFCTL/PRSERVLINETYPE
For non-Services uses value in
OFCTL/POLINETYPE
POLINENUM line_num NUMBER
ITEMNUM item_id NUMBER 15 Item ID associated to ITEMNUM
item_revision ALN 3 Null
category_id NUMBER For service uses value from
OFCTL/SERVCATID or retrieves id
based on PLIN1
For non-service uses value from
OFCTL/ITEMCATID or retrieves id
based on PLIN1
DESCRIPTION item_description ALN 240
409
Chapter 3

ORDERUNIT unit_meas_lookup_code ALN 25
quantity_committed NUMBER Null
committed_amount NUMBER 19 Null
allow_price_override_flag ALN 1 ‘N’
not_to_exceed_price NUMBER Null
UNITCOST list_price_per_unit NUMBER
UNITCOST unit_price NUMBER If POTYPE = ‘BLANK’ then
UNIT_PRICE =
(QUANTITY * UNIT_PRICE)
ORDERQTY quantity NUMBER If POTYPE = ‘BLANK’ then QUANTITY
=0
un_number_id NUMBER 15 Null
hazard_class_id NUMBER 15 Null
from_line_id NUMBER 15 Null
min_order_quantity NUMBER Null
max_order_quantity NUMBER Null
qty_rcv_tolerance NUMBER Null
over_tolerance_error_flag ALN 1 Null
UNITCOST market_price NUMBER
unordered_flag ALN 1 ‘N’
user_hold_flag ALN 1 Null
410

cancelled_by NUMBER 15 Null
cancel_date DATE Null
cancel_reason ALN 240 Null
firm_status_lookup_code ALN 30 Null
vendor_product_num ALN 25 Null
contract_num ALN 25 Null
taxable_flag ALN 1 ‘N’
tax_name ALN 15 Null
type_1099 ALN 10 Null
capital_expense_flag ALN 1 ‘N’
negotiated_by_preparer_flag ALN 1 ‘N’
attribute_category ALN 30 Null
attribute1 ALN 150 Segment1 from Header record
POLINENUM attribute2 ALN 150
411
Chapter 3

reference_num ALN 25 Null
min_release_amount NUMBER Null
price_type_lookup_code ALN 25 Null
price_break_lookup_code ALN 25 Null
closed_reason ALN 240 Null
closed_by NUMBER Null
transaction_reason_code ALN 25 Null
transaction_type ALN 20 Either ‘CREATE’ or ‘UPDATE’ based
on po already sent to Oracle
412

OFCTL/OPERUNITID or entered in
extra column (PO1-PO10) on PO form
413
Chapter 3
NOTE: This table is populated only when the POTYPE = ‘REL’ (processing a MAXIMO Release PO).

MOUT_PO_INTERFACE PO_RELEASES_INTERFACE_CAI_ALL
APISEQ Po_release_id NUMBER For a new release, uses APISEQ
For updates, retrieves release from
Oracle base table
‘MAXIMO1’
po_header_id NUMBER Retrieved from Oracle using
ORIGINALPONUM
APISEQ release_num NUMBER
REQUESTEDBY agent_id NUMBER Employee ID for the
PO.REQUESTEDBY if not null and
GENUSR = N, else Employee ID for
‘MAXIMO1’
release_date DATE SYSDATE
ORDERDATE create_date DATE
revised_date ALN 25 Null
STATUSDATE approved_date DATE
print_count NUMBER 0
414

cancelled_by NUMBER Null
attribute1 ALN 150 Segment1 from Header
attribute2 ALN 150 Line_Num from Line
attribute15 ALN 150 Concatenate PONUM||POLINENUM
last_update_login NUMBER Null
creation_date DATE Null
created_by NUMBER Null
hold_by NUMBER Null
415
Chapter 3

hold_date DATE Null
hold_reason ALN 240 Null
hold_flag ALN 1 Null
firm_status_lookup_code ALN 25 Null
firm_date DATE Null
acceptance_required_flag ALN 1 Null
authorization_status ALN 25 ‘APPROVED’
frozen_flag ALN 1 Null
release_type ALN 25 ‘BLANKET’
delete_after_process ALN 1 Null
on po already sent to Oracle
416

417
Chapter 3

MOUT_PO_INTERFACE PO_SHIPMENTS_INTERFACE_CAI_ALL
line_location_id NUMBER 15 Null
‘MAXIMO1’
ORDERQTY quantity NUMBER
quantity_received NUMBER 0
ORDERQTY quantity_accepted NUMBER
quantity_rejected NUMBER 0
quantity_billed NUMBER 0
quantity_cancelled NUMBER 0
ORDERUNIT unit_meas_lookup_code ALN 25
po_release_id NUMBER 15 From the release record when created
SHIPTO ship_to_location_id NUMBER 15 Ship to Id associated to PO.SHIPTO
ship_via_lookup_code ALN 25 Null
REQDELIVERYDATE need_by_date DATE If Null, used REQUIREDDATE
promised_date DATE Null
418

last_accept_date DATE Null
UNITCOST price_override NUMBER
encumbered_date DATE Null
encumbered_flag ALN 1 ‘N’
unencumbered_quantity NUMBER Null
fob_lookup_code ALN 25 Null
freight_terms_lookup_code ALN 25 Null
taxable_flag ALN 1 If TAX1CODE is not null then set to Y
Else set to N
TAX1CODE tax_name ALN 15
from_line_id NUMBER 15 Null
from_line_location_id NUMBER 15 Null
start_date DATE Null
end_date DATE Null
lead_time NUMBER 15 Null
lead_time_unit ALN 25 Null
price_discount NUMBER Null
terms_id NUMBER 15 Null
STATUSDATE approved_date DATE
cancelled_by NUMBER 15 Null
419
Chapter 3

firm_status_lookup_code ALN 25 ‘N’
firm_date DATE Null
attribute1 ALN 150 Segment1 from Header
attribute2 ALN 150 Line_Num from Line
unit_of_measure_class ALN 25 Null
encumber_now ALN 1 Null
inspection_required_flag ALN 1 ‘N’
RECEIPTREQD receipt_required_flag ALN 1
420

qty_rcv_exception_code ALN 25 Null
enforce_ship_to_location_co ALN 25 Null
allow_substitute_receipts_f ALN 1 Null
days_early_receipt_allowed NUMBER Null
days_late_receipt_allowed NUMBER Null
receipt_days_exception_code ALN 25 Null
invoice_close_tolerance NUMBER Null
receive_close_tolerance NUMBER Null
STORELOC ship_to_organization_id NUMBER Uses ID for Storeloc, if storeloc is null,
uses org id associated to the shipto
POLINENUM shipment_num NUMBER
source_shipment_id NUMBER Null
shipment_type ALN 25 Null
receiving_routing_id NUMBER Null
accrue_on_receipt_flag ALN 1 ‘N’
closed_reason ALN 240 Null
421
Chapter 3

on PO already sent to Oracle
422

MOUT_PO_INTERFACE PO_DISTRIB_INTERFACE_CAI_ALL
po_distribution_id NUMBER 15 Null
‘MAXIMO1’
line_location_id NUMBER 15 Null
set_of_books_id NUMBER 15 Value from OFCTL/GLSOBID
GLDEBITACCT code_combination_id NUMBER 15 Uses ID associated to debit account
ORDERQTY quantity_ordered NUMBER
po_release_id NUMBER 15 From the Release record when created
ORDERQTY quantity_delivered NUMBER
quantity_billed NUMBER 0
quantity_cancelled NUMBER 0
req_header_reference_num ALN 25 Null
req_line_reference_num ALN 25 Null
req_distribution_id NUMBER 15 Null
SHIPTO Deliver_to_location_id NUMBER 15 Ship to Id associated to PO.SHIPTO
423
Chapter 3

REQUESTEDBY Deliver_to_person_id NUMBER Employee ID for the PO.REQUESTEDBY if
not null and GENUSR = N, else Employee
ID for ‘MAXIMO1’
amount_billed NUMBER Null
accrued_flag ALN 1 Null
encumbered_flag ALN 1 ‘N’
encumbered_amount NUMBER 19 Null
unencumbered_amount NUMBER 19 Null
failed_funds_lookup_code ALN 25 Null
gl_encumbered_date DATE Null
gl_encumbered_period_name ALN 15 Null
gl_cancelled_date DATE Null
destination_type_code ALN 25 For Inventory items use OFCTL/PRSTOCK
if Storelocis not nulland PRGENITEM = N
and PRGENSTORE = N
All other conditions use OFCTL/PRDIRECT
destination_subinventory ALN 10 Null
attribute1 ALN 150 SEGMENT1 from Header
attribute2 ALN 150 Line_num from Line
attribute3 ALN 150 Shipment_num from Shipment
424

Attribute8 ALN 150 Null
Attribute9 ALN 150 Null
wip_entity_id NUMBER Null
wip_operation_seq_num NUMBER Null
wip_resource_seq_num NUMBER Null
wip_repetitive_schedule_id NUMBER Null
wip_line_id NUMBER Null
bom_resource_id NUMBER Null
budget_account_id NUMBER Null
GLCREDITACCT accrual_account_id NUMBER Uses ID associated to credit account
GLDEBITACCT variance_account_id NUMBER Uses ID associated to debit account
prevent_encumberence_flag ALN 1 ‘N’
destination_context ALN 30 Null
POLINENUM distribution_num NUMBER
425
Chapter 3

source_distribution_id NUMBER Null
project_id NUMBER Null
task_id NUMBER Null
expenditure_type ALN 30 Null
project_accounting_context ALN 30 Null
expenditure_organization_id NUMBER Null
gl_closed_date DATE Null
accrue_on_receipt_flag ALN 1 ‘N’
expenditure_item_date DATE Null
STORELOC Destination_organization_id NUMBER Uses ID for Storeloc, if storeloc is null, uses
org id associated to the shipto
APISYNC Transaction_id NUMBER
Transaction_type ALN 20 Either ‘CREATE’ or ‘UPDATE’ based on po
already sent to Oracle
OFCTL/OPERUNITID or entered in extra
column (PO1-PO10) on PO form
426
Purchase Orders from MAXIMO to the Oracle Standard Purchasing Documents

Open Interface Tables
This section provides the cross mapping for the interface tables that are used when transferring PO data between
MAXIMO and Oracle Standard Purchasing Documents Open Interface tables. Data is transferred from the
MAXIMO MOUT_PO_INTERFACE table to the Oracle Financials PO_HEADERS_Interface,
PO_LINES_Interface, PO_RELEASES_Interface_CAI_ALL and PO_DISTRIBUTIONS_Interface tables.
NOTE: The Standard Purchasing Documents Open Interface is available for Oracle versions 11.5.3 and later.
MOUT_PO_INTERFACE PO_HEADERS_INTERFACE

interface_header_id NUMBER Obtained from Oracle sequence
PO_HEADERS_INTERFACE_S in Oracle
Financial PO module
batch_id NUMBER PO_HEADERS_INTERFACE.interface_head
er_id
interface_source_code VARCHAR2 25 Null
process_code VARCHAR2 25 Null
action VARCHAR2 25 'ORIGINAL'
group_code VARCHAR2 25 'DEFAULT'
org_id NUMBER clnt_info which is operating unit
POTYPE document_type_code VARCHAR2 25 If PO.POTYPE = STD, then value is
‘STANDARD’
427
Chapter 3

If PO.POTYPE = BLANK, then value is
‘BLANKET’
document_subtype VARCHAR2 25 Null
PONUM document_num VARCHAR2 20
po_header_id NUMBER Null
release_num NUMBER Null
po_release_id NUMBER Null
release_date DATE Null
CURRENCYCODE currency_code VARCHAR2 15
rate_type VARCHAR2 30 MaxValLPack.GetValue('OFCTL','GLCURNC
YTYPE')
rate_type_code VARCHAR2 30 Null
agent_name VARCHAR2 240 Null
REQUESTEDBY agent_id NUMBER Employee ID for the PO.REQUESTEDBY if
not null and GENUSR = N, else Employee ID
for ‘MAXIMO1’
vendor_name VARCHAR2 80 Null
VENDOR vendor_id NUMBER Vendor Id associated to PO.VENDOR (pos 1
to delimiter ‘-‘)
vendor_site_code VARCHAR2 15 Null
VENDOR vendor_site_id NUMBER Vendor Site Id associated to PO.VENDOR
(pos after delimiter ‘-‘ to the end)
vendor_contact VARCHAR2 240 Null
vendor_contact_id NUMBER Null
ship_to_location VARCHAR2 20 Null
428

SHIPTO ship_to_location_id NUMBER Ship to Id associated to PO.SHIPTO
bill_to_location VARCHAR2 20 Null
BILLTO bill_to_location_id NUMBER Bill to Id associated to PO.BillTO
payment_terms VARCHAR2 50 Null
PAYMENTTERMS terms_id NUMBER Terms Id associated to
PO.PAYMENTTERMS, If null, uses value
from OFCTL/PAYTERMSID
SHIPVIA freight_carrier VARCHAR2 25
FOB fob VARCHAR2 25
FREIGHTTERMS freight_terms VARCHAR2 25
approval_status VARCHAR2 25 If PO.POTYPE = 'BLANKET' then value is
‘APPROVED’ else it is Null
STATUSDATE approved_date DATE If PO.POTYPE = 'BLANKET' then value is
nvl(PO.STATUSDATE,sysdate) else it is Null
TOTALCOST amount_agreed NUMBER Populated only if PO.POTYPE = 'BLANKET'
TOTALCOST amount_limit NUMBER Populated only if PO.POTYPE = 'BLANKET'
min_release_amount NUMBER 1
revised_date DATE Null
note_to_vendor VARCHAR2 240 Null
note_to_receiver VARCHAR2 240 'Approved MAXIMO Purchase Order :
'||PO.PONUM
confirming_order_flag VARCHAR2 1 'N'
PODESCRIPTION comments VARCHAR2 240
acceptance_required_flag VARCHAR2 1 'N'
effective_date DATE Null
429
Chapter 3

expiration_date DATE Null
print_count NUMBER 0
firm_flag VARCHAR2 25 Null
frozen_flag VARCHAR2 1 'N'
closed_code VARCHAR2 25 'OPEN'
reply_date DATE Null
reply_method VARCHAR2 25 Null
RFQ_close_date DATE Null
quote_warning_delay NUMBER Null
vendor_doc_num VARCHAR2 25 Null
approval_required_flag VARCHAR2 1 Null
vendor_list VARCHAR2 25 Null
vendor_list_header_id NUMBER Null
from_header_id NUMBER Null
from_type_lookup_code VARCHAR2 25 Null
ussgl_transaction_code VARCHAR2 30 Null
attribute_category VARCHAR2 30 'Default'
attribute1 VARCHAR2 150 PO_HEADERS_INTERFACE.document_num
attribute2 VARCHAR2 150
attribute15 VARCHAR2 150 'MAXIMO:'||PO.PONUM
created_by NUMBER Last_updated_by
430

ENTERBY last_updated_by NUMBER User ID for the PO.ENTERBY if not null and
GENUSR = N, else User ID for ‘MAXIMO’
reference_num VARCHAR2 25 Null
load_sourcing_rules_flag VARCHAR2 1 Null
vendor_num VARCHAR2 30 Null
from_RFQ_num VARCHAR2 25 Null
wf_group_id NUMBER Null
pcard_id NUMBER 15 Null
pay_on_code VARCHAR2 25 Null
431
Chapter 3

MOUT_PO_INTERFACE PO_LINES_INTERFACE
interface_line_id NUMBER Obtained from Oracle sequence
PO_LINES_INTERFACE_S in Oracle
Financial PO module
interface_header_id NUMBER PO_Headers_Interface.interface_head
er_id
action VARCHAR2 25 Null
group_code VARCHAR2 25 Null
POLINENUM line_num NUMBER
po_line_id NUMBER Null
shipment_num NUMBER 1
line_location_id NUMBER Null
shipment_type VARCHAR2 25 'STANDARD'
requisition_line_id NUMBER Null
document_num NUMBER Null
release_num NUMBER Null
source_shipment_id NUMBER Null
contract_num VARCHAR2 25 Null
line_type VARCHAR2 25 Null
line_type_ID NUMBER If Service uses value in
OFCTL/PRSERVLINETYPE
432

For non-Services uses value in
OFCTL/POLINETYPE
item VARCHAR2 1000 Null
ITEMNUM item_id NUMBER Item ID associated to ITEMNUM
item_revision VARCHAR2 3 Null
category VARCHAR2 2000 Null
category_id NUMBER For service uses value from
OFCTL/SERVCATID or retrieves id
based on PO.PLIN1
For non-service uses value from
OFCTL/ITEMCATID or retrieves id
based on PO.PLIN1
DESCRIPTION item_description VARCHAR2 240
vendor_product_num VARCHAR2 25 Null
uom_code VARCHAR2 3 Null
ORDERUNIT unit_of_measure VARCHAR2 25
ORDERQTY quantity NUMBER If PO.potype = 'BLANK' then the value
is O, otherwise it is PO.ORDERQTY
committed_amount NUMBER Null
min_order_quantity NUMBER Null
max_order_quantity NUMBER Null
UNITCOST unit_price NUMBER
list_price_per_unit NUMBER PO_Lines_Interface.unit_price
UNITCOST market_price NUMBER
allow_price_override_flag VARCHAR2 1 'N'
433
Chapter 3

not_to_exceed_price NUMBER Null
negotiated_by_preparer_flag VARCHAR2 1 'N'
un_number VARCHAR2 25 Null
un_number_id NUMBER Null
hazard_class VARCHAR2 40 Null
hazard_class_id NUMBER Null
note_to_vendor VARCHAR2 240 Null
transaction_reason_code VARCHAR2 25 Null
taxable_flag VARCHAR2 1 If TAX1CODE is not null then set to Y
Else set to N
TAX1CODE tax_name VARCHAR2 15 PO.TAX1CODE
type_1099 VARCHAR2 10 Null
capital_expense_flag VARCHAR2 1 'N'
inspection_required_flag VARCHAR2 1 'N'
receipt_required_flag VARCHAR2 1 If PO.RECEIPTREQD flag is ‘N’ then
the value is ‘N’ else it is ‘Y’.
payment_terms VARCHAR2 50 Null
terms_id NUMBER Null
price_type VARCHAR2 25 Null
min_release_amount NUMBER Null
price_break_lookup_code VARCHAR2 25 Null
closed_code VARCHAR2 25 ‘OPEN’
closed_reason VARCHAR2 240 Null
434

invoice_close_tolerance NUMBER Null
receive_close_tolerance NUMBER Null
firm_flag VARCHAR2 25 Null
days_early_receipt_allowed NUMBER Null
days_late_receipt_allowed NUMBER Null
enforce_ship_to_location_code VARCHAR2 25 Null
allow_substitute_receipts_flag VARCHAR2 1 Null
receiving_routing VARCHAR2 30 Null
receiving_routing_id NUMBER Null
over_tolerance_error_flag VARCHAR2 1 Null
qty_rcv_exception_code VARCHAR2 25 Null
receipt_days_exception_code VARCHAR2 25 Null
ship_to_organization_code VARCHAR2 3 Null
STORELOC ship_to_organization_id NUMBER Uses ID for Storeloc, if storeloc is null,
uses org id associated to the shipto or
the org_id associated with the
('OFCTL','ITMORG').
ship_to_location VARCHAR2 20 Null
SHIPTO ship_to_location_id NUMBER Ship to Id associated to PO.SHIPTO
REQDELIVERYDATE need_by_date DATE If Null, used REQUIREDDATE
435
Chapter 3

promised_date DATE Null
accrue_on_receipt_flag VARCHAR2 1 ('OFCTL','POACCRUAL')
lead_time NUMBER Null
lead_time_unit VARCHAR2 25 Null
price_discount NUMBER Null
freight_carrier VARCHAR2 80 Null
fob VARCHAR2 25 Null
freight_terms VARCHAR2 25 Null
effective_date DATE Null
expiration_date DATE Null
from_header_id NUMBER Null
from_line_id NUMBER Null
from_line_location_id NUMBER Null
line_attribute_category_lines VARCHAR2 30 Null
line_attribute1 VARCHAR2 150 PO_Headers_Interface.document_num
line_attribute2 VARCHAR2 150 PO_Lines_Interface.line_num
line_attribute3 VARCHAR2 150 'MAXIMO:'||PO.ItemNum
line_attribute4 VARCHAR2 150 If Inventory.ownersysid =’M’ and
('OFCTL','GENSTORE')=’Y’ then
populate the column with 'MAXIMO:'||
PO.STORELOC. Else null.
line_attribute15 VARCHAR2 150 Null
shipment_attribute_category VARCHAR2 30 Null
shipment_attribute1 VARCHAR2 150 PO_Headers_Interface.document_num
436

shipment_attribute2 VARCHAR2 150 PO_Lines_Interface.line_num
shipment_attribute3 VARCHAR2 150 PO_Lines_Interface. shipment_num
shipment_attribute4 VARCHAR2 150 Null
shipment_attribute15 VARCHAR2 150 Null
ENTERBY last_updated_by NUMBER User ID for the PO.ENTERBY if not null

‘MAXIMO’
creation_date DATE PO_Headers_Interface.creation_date
ENTERBY created_by NUMBER User ID for the PO.ENTERBY if not null
‘MAXIMO’
organization_id DATE Null
item_attribute_category VARCHAR2 30 Null
item_attribute1 VARCHAR2 150 Null
437
Chapter 3

MOUT_PO_INTERFACE PO_DISTRIBUTIONS_INTERFACE
interface_header_id NUMBER PO_Headers_interface.interface_header_id
interface_line_id NUMBER PO_Lines_interface.interface_line_id
interface_distribution_id NUMBER Obtained from Oracle sequence
PO_DISTRIBUTIONS_INTERFACE_S in
Oracle Financial PO module
po_line_id NUMBER Null
line_location_id NUMBER Null
po_distribution_id NUMBER Null
distribution_num NUMBER 1
source_distribution_id NUMBER Null
org_id NUMBER clnt_info which is the Operating_Unit.
quantity_ordered NUMBER PO_Lines_interface.quantity
quantity_delivered NUMBER Null
quantity_billed NUMBER Null
quantity_cancelled NUMBER Null
EXCHANGEDATE rate_date DATE PO. EXCHANGEDATE
EXCHANGERATE rate NUMBER PO.EXCHANGERATE
deliver_to_location VARCHAR2 20 Null
deliver_to_location_id NUMBER PO_Lines_interface.ship_to_location_id
438

deliver_to_person_full_name VARCHAR2 240 Null
REQUESTEDBY deliver_to_person_id NUMBER Employee ID for the PO.REQUESTEDBY if
not null and GENUSR = N, else Employee
ID for ‘MAXIMO’
destination_type VARCHAR2 25 Null
destination_type_code VARCHAR2 25 For Inventory items use OFCTL/PRSTOCK
if Storelocis not nulland PRGENITEM = N
and PRGENSTORE = N
All other conditions use OFCTL/PRDIRECT
destination_organization VARCHAR2 60 Null
STORELOC destination_organization_id NUMBER Uses ID for Storeloc, if storeloc is null, uses
org id associated to the shipto or the org_id
associated with the ('OFCTL','ITMORG').
destination_subinventory VARCHAR2 10 Null
destination_context VARCHAR2 30 Null
set_of_books VARCHAR2 30 Null
set_of_books_id NUMBER Value from OFCTL/GLSOBID
charge_account VARCHAR2 2000 Null
GLDEBITACCT charge_account_id NUMBER PO.GLDEBITACCT
budget_account VARCHAR2 2000 Null
budget_account_id NUMBER Null
GLCREDITACCT accrual_account VARCHAR2 2000 Null
accrual_account_id NUMBER Uses ID associated to credit account
variance_account VARCHAR2 2000 Null
GLDEBITACCT variance_account_id NUMBER Uses ID associated to debit account
amount_billed NUMBER Null
439
Chapter 3

accrue_on_receipt_flag VARCHAR2 1 PO_Lines_interface.accrue_on_receipt_fla
g
accrued_flag VARCHAR2 1 Null
prevent_encumbrance_flag VARCHAR2 1 Null
encumbered_flag VARCHAR2 1 'N'
encumbered_amount NUMBER Null
unencumbered_amount NUMBER Null
failed_funds VARCHAR2 25 Null
failed_funds_lookup_code VARCHAR2 25 Null
gl_encumbered_date DATE Null
gl_encumbered_period_name VARCHAR2 15 Null
gl_cancelled_date DATE Null
gl_closed_date DATE Null
req_header_reference_num VARCHAR2 25 Null
req_line_reference_num VARCHAR2 25 Null
req_distribution_id NUMBER Null
wip_entity VARCHAR2 240 Null
wip_entity_id NUMBER Null
wip_operation_seq_num NUMBER Null
wip_resource_seq_num NUMBER Null
wip_repetitive_schedule VARCHAR2 240 Null
wip_repetitive_schedule_id NUMBER Null
wip_line_code VARCHAR2 10 Null
440

wip_line_id NUMBER Null
bom_resource_code VARCHAR2 10 Null
bom_resource_id NUMBER Null
government_context VARCHAR2 30 Null
project VARCHAR2 25 Null
Project_id NUMBER If ('OFCTL','PROJPO') is ‘Yes’ and if

PO.wonum is not null then populate this
field else it is Null.
Task VARCHAR2 20 Null
Task_id NUMBER If ('OFCTL','PROJPO') is ‘Yes’ and if
expenditure VARCHAR2 60 Null
expenditure_type VARCHAR2 30 If ('OFCTL','PROJPO') is ‘Yes’ and if
project_accounting_context VARCHAR2 30 If ('OFCTL','PROJPO') is ‘Yes’ and if
expenditure_organization VARCHAR2 60 Null
expenditure_organization_id NUMBER If ('OFCTL','PROJPO') is ‘Yes’ and if
project_releated_flag VARCHAR2 1 Null
expenditure_item_date DATE If ('OFCTL','PROJPO') is ‘Yes’ and if
441
Chapter 3

attribute_category VARCHAR2 30 Null

attribute1 VARCHAR2 150 PO_Headers_interface.document_num
Attribute2 VARCHAR2 150 PO_Lines_interface.line_num
Attribute3 VARCHAR2 150 PO_Lines_interface.shipment_num
Attribute4 VARCHAR2 150 PO_Distributions_interface.distribution_nu
m
Attribute15 VARCHAR2 150 Null
ENTERBY last_updated_by NUMBER User ID for the PO.ENTERBY if not null
‘MAXIMO’
last_update_login NUMBR Null
creation_date DATE PO_Headers_interface.creation_date
created_by NUMBER Last_updated_by
442
Receipt Transfer from MAXIMO to Oracle Financials

This section provides the cross mapping for the interface tables that are used when transferring Receipt data
between MAXIMO and Oracle Financials. Data is transferred from the MAXIMO MAX_RCV_INTERFACE
table to Oracle Financials’ RCV_HEADERS_INTERFACE and RCV_TRANSACTIONS_INTERFACE tables.
MAX_RCV_INTERFACE RCV_HEADERS_INTERFACE
RCV_TRANSACTIONS_INTERFACE
Column Name Column Name Table Type Length COMMENTS
Names
HEADER_INTERFACE_ID H Number Obtained from Oracle sequence
RCV_HEADERS_INTERFACE_S in
GROUP_ID H Number Obtained from Oracle sequence
RCV_INTERFACE_GROUPS_S in
VENDOR_ID H Number PO_VENDORS.VENDOR_ID of the
vendor of the PO1
PROCESSING_STATUS_CODE H Varchar2 ‘PENDING’
RECEIPT_SOURCE_CODE H Varchar2 ‘VENDOR’
TRANSACTION_TYPE H Varchar2 ‘NEW’
LAST_UPDATE_DATE H Date SYSDATE
VALIDATION_FLAG H Varchar2 ‘Y’
HEADER_INTERFACE_ID T Number Same as
RCV_HEADERS_INTERFACE.
HEADER_INTERFACE_ID
GROUP_ID T Number Same as
RCV HEADERS INTERFACE.GROU
443
Chapter 3
Names
P_ID
INTERFACE_TRANSACTION_ID T Number Obtained from Oracle sequence
RCV_TRANSACTIONS_INTERFACE_
S in Oracle Financial PO module
LAST_UPDATE_DATE T date SYSDATE
TRANSACTION_TYPE T Varchar2 ‘RECEIVE’
PROCESSING_STATUS_CODE T Varchar2 ‘PENDING’
PROCESSING_MODE_CODE T Varchar2 ‘BATCH’
TRANSACTION_STATUS_CODE T Varchar2 ‘PENDING’
AUTO_TRANSACT_CODE T Varchar2 ‘DELIVER’
RECEIPT_SOURCE_CODE T Varchar2 ‘VENDOR’
SOURCE_DOCUMENT_CODE T Varchar2 ‘PO’
VALIDATION_FLAG T Varchar2 ‘Y’
COMMENTS T Varchar2 ‘MAXIMO1 RECEIPT’
VENDOR_ID T Number Same as
RCV_HEADERS_INTERFACE.VENDO
R_ID
DELIVER_TO_LOCATION_CODE T Varchar2 PO.SHIPTO in MAXIMO1
SHIP_TO_LOCATION_CODE T Varchar2 Same as
RCV_TRANSACTIONS_INTERFACE.
DELIVER_TO_LOCATION_CODE
EXPECTED_RECEIPT_DATE T Varchar2 NVL(PO.REQUREDDATE, SYSDATE)
in Oracle Financial
ITEMNUM ITEM_ID T Number MTL_SYSTEM_ITEMS.INVENTORY_I
TEM_ID in Oracle Financial4
444
Names
TOSTORELOC SHIP_TO_ORGANIZATION_CODE H Varchar2
TRANSDATE TRANSACTION_DATE T Date
ACTUALDATE CREATION_DATE H DATE
CREATION_DATE T DATE
QUANTITY QUANTITY T Number
RECEIVEDUNIT UNIT_OF_MEASURE T Varchar2
ISSUETYPE
UNITCOST
ACTUALCOST
PONUM PO_HEADER_ID H Number PO_HEADERS.PO_HEADER_ID
INVOICENUM SHIPMENT_NUM H Varchar2
REJECTCODE
REJECTQTY
REJECTCOST
CONVERSION
WONUM
EQNUM
ENTERBY EMPLOYEE_ID H Number PER_ALL_PEOPLE_F.PERSON_ID for
ENTERBY or ‘MAXIMO1’2
LAST_UPDATED_BY H Number FND_USER.USER_ID for ENTERBY or
‘MAXIMO1’2
CREATED_BY H Number Same as
RCV_HEADERS_INTERFACE.LAST_
445
Chapter 3
Names
UPDATE_BY2
LAST_UPDATED_BY T Number Same as
UPDATE_BY2
CREATED_BY T Number Same as
UPDATE_BY2
LAST_UPDATE_LOGIN T Number Same as
UPDATE_BY2
IT1
IT2
IT3
IT4
IT5
OUTSIDE
WPOPERATION
ISSUETO
PACKINGSLIPNUM SHIPMENT_NUM H Varchar2
POLINENUM
ISSUE
REQUESTEDBY
TOTALCURBAL
OLDAVGCOST
446
Names
ITIN1
ITIN2
ITIN3
TOBIN SUBINVENTORY T Varchar2
LOCATOR_ID T Varchar2
LOTNUM
GLCREDITACCT
GLDEBITACCT
LINECOST
LINECOST2
FINANCIALPERIOD
CURRENCYCODE
CURRENCYCODE2
EXCHANGERATE
EXCHANGERATE2
CURRENCYUNITCOST
MANUFACTURER
MODELNUM
CURRENCYLINECOST
LOCATION
DESCRIPTION ITEM_DESCRIPTION T Varchar2
447
Chapter 3
Names
REMARK
FROMSTORELOC
FROMBIN
QTYHELD
CLAIMNUM
APPROVED
APPROVEDATE
APPROVEBY
LONGDESC
USERDATA1
USERDATA2
USERDATA3
USERDATA4
USERDATA5
USERDATA6
USERDATA7
USERDATA8
USERDATA9
USERDATA10
BATCHID
BATCHLINEID
UTRANSTYPE
448
Names
SOURCEID
APISEQ
APISYNC
IMPORTSTATUS
IMPORTTIMESTAMP
IMPORTMESSAGE
Key to Tables
H RCV_HEADERS_INTERFACE
S RCV_TRANSACTIONS_INTERFACE
449
Chapter 3
Purchase Requisition from MAXIMO

This section provides the cross mapping for the interface tables that are used when transferring purchase
requisition data between MAXIMO and Oracle Financials. Data is transferred from the MAXIMO
MOUT_PR_INTERFACE table to Oracle Financials’ PO_REQUISITIONS_INTERFACE table.
PO_REQUISITIONS_INTERFACE MOUT_PR_INTERFACE
TRANSACTION_ID
PROCESS_FLAG
REQUEST_ID
PROGRAM_ID
PROGRAM_APPLICATION_ID
PROGRAM_UPDATE_DATE
LAST_UPDATED_BY ENTERBY ID
LAST_UPDATE_DATE SYSDATE
LAST_UPDATE_LOGIN
CREATION_DATE ISSUEDATE
INTERFACE_SOURCE_CODE 'MAXIMO1'
INTERFACE_SOURCE_LINE_ID APISEQ
SOURCE_TYPE_CODE If PR.INTERNAL = 'N' or Null Then 'VENDOR'
If PR.INTERNAL = 'Y' Then 'INVENTORY'
REQUISITION_HEADER_ID
REQUISITION_LINE_ID
REQ_DISTRIBUTION_ID
REQUISITION_TYPE
DESTINATION_TYPE_CODE If PRLINE.ISSUE = 'N' or Null Then 'INVENTORY'
450
If PRLINE.ISSUE = 'Y' Then 'EXPENSE'
ITEM_DESCRIPTION PRLDESCRIPTION
QUANTITY ORDERQTY
UNIT_PRICE UNITCOST
AUTHORIZATION_STATUS 'APPROVED'
BATCH_ID
GROUP_CODE PRNUM
DELETE_ENABLED_FLAG
UPDATE_ENABLED_FLAG
APPROVER_ID
APPROVER_NAME
APPROVAL_PATH_ID
NOTE_TO_APPROVER 'APPROVED MAXIMO1 REQUISITION'
PREPARER_ID
AUTOSOURCE_FLAG
REQ_NUMBER_SEGMENT1 PRNUM optional
REQ_NUMBER_SEGMENT2
REQ_NUMBER_SEGMENT3
REQ_NUMBER_SEGMENT4
REQ_NUMBER_SEGMENT5
HEADER_DESCRIPTION DESCRIPTION
HEADER_ATTRIBUTE_CATEGORY
HEADER_ATTRIBUTE1 PR1
HEADER_ATTRIBUTE6
451
Chapter 3
HEADER_ATTRIBUTE7
HEADER_ATTRIBUTE8
HEADER_ATTRIBUTE9
HEADER_ATTRIBUTE10
HEADER_ATTRIBUTE11
HEADER_ATTRIBUTE12
HEADER_ATTRIBUTE13
HEADER_ATTRIBUTE14
URGENT_FLAG
HEADER_ATTRIBUTE15
RFQ_REQUIRED_FLAG PR6
JUSTIFICATION PR7
NOTE_TO_BUYER PR8
NOTE_TO_RECEIVER PR9
ITEM_ID
ITEM_SEGMENT1 ITEMNUM optional
ITEM_SEGMENT2
ITEM_SEGMENT3
ITEM_SEGMENT4
ITEM_SEGMENT5
ITEM_SEGMENT6
ITEM_SEGMENT7
ITEM_SEGMENT8
ITEM_SEGMENT9
ITEM_SEGMENT10
ITEM_SEGMENT11
ITEM_SEGMENT12
ITEM_SEGMENT13
452
ITEM_SEGMENT14
ITEM_SEGMENT15
ITEM_SEGMENT16
ITEM_SEGMENT17
ITEM_SEGMENT18
ITEM_SEGMENT19
ITEM_SEGMENT20
ITEM_REVISION
CHARGE_ACCOUNT_ID GLDEBITACCT
CHARGE_ACCOUNT_SEGMENT1
453
Chapter 3
CATEGORY_ID
CATEGORY_SEGMENT1 IN19 (Parsed)
454
UNIT_OF_MEASURE ORDERUNIT
UOM_CODE
LINE_TYPE_ID
LINE_TYPE OFCTL.PRSERVLINETYPE for service lines.
Null for all others.
UN_NUMBER_ID
UN_NUMBER
HAZARD_CLASS_ID
HAZARD_CLASS
MUST_USE_SUGG_VENDOR_FLAG
REFERENCE_NUM PRNUM
WIP_ENTITY_ID
WIP_LINE_ID
WIP_OPERATION_SEQ_NUM
WIP_RESOURCE_SEQ_NUM
WIP_REPETITIVE_SCHEDULE_ID
PROJECT_NUM
TASK_NUM
EXPENDITURE_TYPE
SOURCE_ORGANIZATION_ID
SOURCE_ORGANIZATION_CODE VENDOR if PR.INTERNAL = 'Y'
SOURCE_SUBINVENTORY
DESTINATION_ORGANIZATION_ID
DESTINATION_ORGANIZATION_CODE BILLTO
455
Chapter 3
DESTINATION_SUBINVENTORY
DELIVER_TO_LOCATION_ID
DELIVER_TO_LOCATION_CODE SHIPTO
DELIVER_TO_REQUESTOR_ID
DELIVER_TO_REQUESTOR_NAME SHIPTOATTN
SUGGESTED_BUYER_ID
SUGGESTED_BUYER_NAME
SUGGESTED_VENDOR_NAME NAME
SUGGESTED_VENDOR_ID
SUGGESTED_VENDOR_SITE CO1
SUGGESTED_VENDOR_SITE_ID
SUGGESTED_VENDOR_CONTACT CONTACT
SUGGESTED_VENDOR_CONTACT_ID
SUGGESTED_VENDOR_PHONE PHONE
SUGGESTED_VENDOR_ITEM_NUM MODELNUM
LINE_ATTRIBUTE_CATEGORY
LINE_ATTRIBUTE1 RL1
LINE_ATTRIBUTE2 RL2
LINE_ATTRIBUTE3 RL3
LINE_ATTRIBUTE4 RL4
LINE_ATTRIBUTE5 RL5
LINE_ATTRIBUTE6 RLIN1
LINE_ATTRIBUTE11
LINE_ATTRIBUTE12
456
LINE_ATTRIBUTE13
LINE_ATTRIBUTE14
LINE_ATTRIBUTE15
NEED_BY_DATE nvl(REQDELIVERYDATE,nvl(requiredate,sysdate))
NOTE1_ID
NOTE2_ID
NOTE3_ID
NOTE4_ID
NOTE5_ID
NOTE6_ID
NOTE7_ID
NOTE8_ID
NOTE9_ID
NOTE10_ID
NOTE1_TITLE
NOTE2_TITLE
NOTE3_TITLE
NOTE4_TITLE
NOTE5_TITLE
NOTE6_TITLE
NOTE7_TITLE
NOTE8_TITLE
NOTE9_TITLE
NOTE10_TITLE
GL_DATE
DIST_ATTRIBUTE_CATEGORY
DISTRIBUTION_ATTRIBUTE1
457
Chapter 3
DISTRIBUTION_ATTRIBUTE11 APISYNC
DISTRIBUTION_ATTRIBUTE12 PRLINENUM
DISTRIBUTION_ATTRIBUTE13 STORELOC
DISTRIBUTION_ATTRIBUTE14 ITEMNUM
DISTRIBUTION_ATTRIBUTE15 PRNUM
PREPARER_NAME 'MAXIMO1,'
BOM_RESOURCE_ID
ACCRUAL_ACCOUNT_ID
VARIANCE_ACCOUNT_ID
BUDGET_ACCOUNT_ID
GOVERNMENT_CONTEXT
CURRENCY_CODE CURRENCYCODE
CURRENCY_UNIT_PRICE API calculated value
RATE EXCHANGERATE
RATE_DATE EXCHANGEDATE
RATE_TYPE OFCTL:GLCURNCYTYPE
PREVENT_ENCUMBRANCE_FLAG
AUTOSOURCE_DOC_HEADER_ID
AUTOSOURCE_DOC_LINE_NUM
458
PROJECT_ACCOUNTING_CONTEXT
EXPENDITURE_ORGANIZATION_ID
PROJECT_ID
TASK_ID
EXPENDITURE_ITEM_DATE
DOCUMENT_TYPE_CODE
ORG_ID * From PR window or from ofctl/operunitid or null if single org
*Oracle Version 10.6 and later only
459
Chapter 3
Invoices from MAXIMO

This section provides the cross mapping for the interface tables that are used when transferring invoice data
MOUT_AP_INTERFACE table to Oracle Financials’ AP_EXPENSE_REPORT_HEADER and
AP_EXPENSE_REPORT_LINE tables.
AP_EXPENSE_REPORT_HEADERS MOUT_AP_INTERFACE
REPORT_HEADER_ID API calculated value
EMPLOYEE_ID
WEEK_END_DATE CHANGEDATE
LAST_UPDATE_DATE TRANSDATE
VOUCHNO '0'
TOTAL TOTALCOST
VENDOR_ID VENDOR (Parsed)
VENDOR_SITE_ID VENDOR (Parsed)
EXPENSE_CHECK_ADDRESS_FLAG
REFERENCE_1
REFERENCE_2
INVOICE_NUM INVOICENUM
EXPENSE_REPORT_ID
ACCTS_PAY_CODE_COMBINATION_ID APCONTROLACCT
SET_OF_BOOKS_ID OFCTL.GLSOBID
SOURCE 'MAXIMO1'
460
PURGEABLE_FLAG
ACCOUNTING_DATE INVOICEDATE
MAXIMUM_AMOUNT_TO_APPLY
ADVANCE_INVOICE_TO_APPLY
APPLY_ADVANCES_DEFAULT
EMPLOYEE_CCID
DESCRIPTION INVOICEDESC
REJECT_CODE
HOLD_LOOKUP_CODE
ATTRIBUTE_CATEGORY
ATTRIBUTE1
ATTRIBUTE2
ATTRIBUTE3
ATTRIBUTE4
ATTRIBUTE5
ATTRIBUTE6
ATTRIBUTE7
ATTRIBUTE8
ATTRIBUTE9
ATTRIBUTE10
ATTRIBUTE11
ATTRIBUTE12
ATTRIBUTE13
ATTRIBUTE14
ATTRIBUTE15
DEFAULT_CURRENCY_CODE OFCTL.GLCURNCY,
CURRENCYCODE
DEFAULT_EXCHANGE_RATE_TYPE OFCTL.GLCURNCYTYPE
461
Chapter 3
DEFAULT_EXCHANGE_RATE EXCHANGERATE
DEFAULT_EXCHANGE_DATE EXCHANGEDATE
LAST_UPDATE_LOGIN
VOUCHER_NUM
USSGL_TRX_CODE_CONTEXT
DOC_CATEGORY_CODE
AP_EXPENSE_REPORT_LINES MOUT_AP_INTERFACE
REPORT_HEADER_ID API calculated value
LAST_UPDATE_DATE CHANGEDATE
CODE_COMBINATION_ID APSUSPENSEACCT
ITEM_DESCRIPTION 'Approved MAXIMO1 Invoice: '||InvoiceRec.INVOICENUM;
SET_OF_BOOKS_ID OFCTL.GLSOBID
AMOUNT LINECOST
ATTRIBUTE_CATEGORY
ATTRIBUTE1
ATTRIBUTE2
ATTRIBUTE3
ATTRIBUTE4
ATTRIBUTE5
ATTRIBUTE6
462
ATTRIBUTE7
ATTRIBUTE8
ATTRIBUTE9
ATTRIBUTE10
ATTRIBUTE11
ATTRIBUTE12
ATTRIBUTE13
ATTRIBUTE14
ATTRIBUTE15
CURRENCY_CODE CURRENCYCODE
EXCHANGE_RATE_TYPE OFCTL.GLCURNCYTYPE
EXCHANGE_RATE EXCHANGERATE
EXCHANGE_DATE CHANGEDATE
VAT_CODE
LINE_TYPE_LOOKUP_CODE OFCTL.APLINETYPE
LAST_UPDATE_LOGIN
STAT_AMOUNT
USSGL_TRX_CODE_CONTEXT
PROJECT_ACCOUNTING_CONTEXT
PROJECT_ID
TASK_ID
EXPENDITURE_ORGANIZATION_ID
EXPENDITURE_TYPE
EXPENDITURE_ITEM_DATE
PA_QUANTITY
463
Chapter 3
DISTRIBUTION_LINE_NUMBER
REFERENCE_1
REFERENCE_2
464
CHAPTER 4
SYSTEM MAINTENANCE
This chapter provides both system maintenance instructions and troubleshooting

information. The system maintenance instructions include procedures and tasks
that your system administrator or database administrator should routinely
perform at your site to help keep your system running smoothly. The
troubleshooting section lists error messages that you might see in the interface
tables and provides information on how to correct the related errors.
Configuring the Database

The interface tables contain columns that match the MAXIMO database table
columns. When you use the Database Configuration application in the MAXIMO
Setup module, you might reconfigure the tables and invalidate the database
triggers. If so, you might see a dialog box telling you to run the
AFTCONFO.SQL script. You use this script to recompile the API triggers and
procedures and you must run it if any of your database changes affected the
APIs. To find out whether your database changes affected the APIs, you should
look at the output file SHOWINT.OUT. If that file references any tables that you
just reconfigured, you must run the script. If the file does not reference any tables
that you reconfigured, you do not have to run the script.
For complete instructions on running the script and testing the results, see
Installation of Packages, Procedures, and Triggers (including the section
465
Chapter 4
Checking for Errors) in the Installation manual. This manual is available in the
APIDOCS directory.
Customizing the Integration APIS

MRO Software provides user exit procedures with the integration APIs so that
you can customize the APIs. User exit procedures are templates for custom
procedures that you can add that allow you to manipulate data being sent to an
interface table. For example, a user exit procedure might rearrange data in a new
format required by the financial application, or it might get additional data and
write it to an extra table.
When you perform a task that activates an integration API (e.g., when you
approve a purchase requisition), the API first copies data from the MAXIMO
tables or from the financial application. Before it writes the data to the interface
table, the integration API calls the user exit procedure and passes the data to that
exit procedure. The user exit procedure then manipulates the data as specified by
the user. When the user exit procedure is complete, the integration API inserts
the data into the appropriate interface table.
If you need to modify MAXIMO data so that your financial application can use
it, you can customize the user exit procedures we provide so that they contain
your procedures.
WARNING: Do not customize the standard integration APIs provided by
MRO Software except by using the user exit procedures
provided for that purpose.
466
System Maintenance
There are six file types in the integration module; you can identify each by its
filename extension:
.TRG—Files containing triggers
.SP—Files containing stored procedures
.USP—Files containing user stored procedures, including user exit procedures
.PKG and .PSP—PL/SQL packages
.SQL—Scripts that run as part of the installation.
WARNING: You should modify only .USP files.
Using UTRANSTYPE Values with User Exit Procedures

You can use a UTRANSTYPE value in your user exit procedure to cancel entire
data transactions or to cancel the transfer of some data in a transaction. Using
UTRANSTYPE values allows you to control the exchange of data in a
transaction.
To cancel the transfer of data, assign the value ABORT to UTRANSTYPE in
your custom procedure. You can use this method to cancel the transfer of data to
MAXIMO from Oracle Financials or from MAXIMO to Oracle Financials.
Using Extra Tables in User Exits

You can create an extra table in a user exit that is directly associated with the
corresponding interface table. You can use the extra table to maintain more data
than the integration API sends to the interface table.
To add an extra table to a user exit procedure, you first create a column in your
extra table called APISEQ. This column is the same as the APISEQ column in
the corresponding interface table. You must have the APISEQ column in your
extra table to capture additional data from one of the standard integration APIs
and to associate the extra table with the interface table.
467
Chapter 4
Any time the integration API calls the user exit procedure and writes MAXIMO
data to the custom procedure, it also writes the APISEQ value. Therefore when
your custom procedure writes data to the extra table, it also must write the
APISEQ value to that table.
If you would like your extra tables to be purged automatically when you use the
CLEANUP.SQL script to purge MAXIMO interface tables, add _EXT_INT to
the end of the table names. For more information about purging tables, see
“Purging the Interface Tables” on page 474.
For more information on the MAXIMO extra table features, refer to the
MAXIMO System Administrator’s Guide.
Using Batch Routines

You can use custom batch routines to process outbound MAXIMO data. You can
either manually run a batch process or use a scheduler program to run the batch
process for you. MRO Software has designed the MAXIMO integration APIs to
provide your batch processes with batch coding information.
The first thing you must do before you can run batch processes is to define those
processes for the integration APIs. During the integration module installation, the
installation script creates two batch-related tables called MAXBATCH and
APIBATCH. Use these tables to define your batch processes. Every MAXIMO
integration API has a corresponding batch name that you can enter in the tables.
You must also define the values or parameters that each process will use. You
can define most of the global parameters in the MAXBATCH table. This table
identifies global batch processes that many APIs may share. For example, the
accounts payable and general ledger (journal transactions) APIs might share a
batch numbering scheme. In that case, when accounts payable transactions are
posted from the accounts payable system to the general ledger, the batch numbers
remain unique.
468
System Maintenance
MAXBATCH Table Columns
Name Type Null Description
BTCHNAME UPPER N Batch name (required)

BTCHDESC ALN Y Batch description (optional)
BTCHNUM INT N Current batch number (required)
BTCHMIN INT N Batch number minimum (required)
BTCHMAX INT N Batch number maximum (required)
BTCHSTEP INT N Batch number increment value
(required)
BTCHLINENUM INT N Current batch line number (required)
BTCHLINEMIN INT N Batch line number minimum
(required)
BTCHLINEMAX INT N Batch line number maximum
(required)
BTCHLINESTEP INT N Batch line number increment value
(required)
BTCHNUMPREFIX ALN Y Batch number prefix (optional)
BTCHNUMPOSTFIX ALN Y Batch number suffix (optional)
469
Chapter 4
Parameter Description
BTCHNAME Name of the batch routine.

BTCHDESC Description of the batch routine.
BTCHNUM Current number of the batch routine.
BTCHMIN Starting point for batch numbering. Lowest value for
batch number cycling.
BTCHMAX Highest value for batch numbering before recycling to
the minimum value. Must be greater than BTCHMIN.
BTCHSTEP Value to add to obtain the next batch number. When a
batch line number reaches the value in
BTCHLINEMAX, the batch number is incremented with
the value in BTCHSTEP. If this causes the batch number
to reach the value in BTCHMAX, then the batch number
is reset to the value in BTCHMIN.
BTCHLINENUM Current line number of the batch routine.
BTCHLINEMIN Minimum value for batch line numbering in the cycle.
BTCHLINEMAX Maximum value for batch line numbering before
recycling to the minimum value. Must be greater than
BTCHLINEMIN.
BTCHLINESTEP Value to add to obtain the next batch line number. Every
transaction that is registered to a batch name will
increment BTCHLINENUM with the value in
BTCHLINESTEP. If this causes the batch line number
to reach the value in BTCHLINEMAX, then the batch
line number is reset to the value in BTCHLINEMIN.
BTCHNUMPREFIX Value to add to the front of the batch number.
470
System Maintenance
BTCHNUMPOSTFIX Value to add to the end of the batch number.

The APIBATCH table associates the integration APIs with a batch process from
the MAXBATCH table above.
APIBATCH Table Columns
Name Type Null Description
APINAME UPPER N API name (required)

BTCHNAME UPPER N Batch name (required)
XBTCHNUMPREFIX ALN Y Batch number prefix (optional)
XBTCHNUMPOSTFIX ALN Y Batch number suffix (optional)
Parameter Description
APINAME Common name of the API.

BTCHNAME Name of the batch routine.
XBTCHNUMPREFIX Value to add to the front of the batch number. Overrides
the value from the batch record.
XBTCHNUMPOSTFIX Value to add to the end of the batch number. Overrides
the value from the batch record.
471
Chapter 4
The APIBATCH table must contain the integration API common name and the
batch name.
Common API names:
• APOUT – Invoice/accounts payable interface
• JEOUT – Journal transaction (all sources) interface
• PROUT – Purchase requisition interface
• ITMOUT – All item (item, store, vendor, and manufacturer) interface
• COMOUT – Company/vendor interface
• WOOUT – Work order interface
You can specify that the common name contains a batch number prefix and
suffix. Batch number prefixes and suffixes you enter here override those listed in
the MAXBATCH table.
You can only define the integration API common name once in APIBATCH.
However, you can have multiple integration APIs that use the same batch routine.
The Batch Routine Process

Any time there is a data transfer from MAXIMO to Oracle Financials, the
integration API first copies data from the MAXIMO tables. Before it writes the
data to the interface tables, the integration API calls the batch routine GetBatch.
GetBatch has the integration API common name associated with it.
GetBatch verifies that the APIBATCH table contains the same integration API
name and batch name. If it does not find the correct integration API name and
batch name, it returns a Null value and continues the usual processing. If it does
fine the correct integration API name and batch name, it continues to the
MAXBATCH table.
472
System Maintenance
After the GetBatch continues to the MAXBATCH table, it executes the batch
routine. When the batch routine is complete, GetBatch returns the batch number
and the batch line number (the next batch number and batch line number after the
ones currently listed in MAXBATCH) to the integration API that called it.
When the integration API writes data to the interface table, it adds the batch
number to the BATCHID column and the batch line number to the
BATCHLINEID column of the interface table.
Maintaining the Batch Files

MRO Software provides with the integration module MAXBATCH and
APIBATCH tables that do not contain predefined data. If you want to use batch
routines to transfer data from MAXIMO, you must define the parameters for
each batch routine you want to use. Use SQL tools to define those parameters.
You can use the same batch routine for many integration APIs.
In MAXBATCH, you must set parameters for the maximum allowable batch
number and batch line number for your application. Then, whenever a batch
routine exceeds the maximum batch number you specified in MAXBATCH, the
batch number automatically recycles to the specified minimum batch number.
The same is true for the batch line number. If you do not want the batch number
or batch line number to automatically reset to the minimum numbers, you must
track the number of batch routines that have been processed and reset the
numbers before they automatically recycle.
If you use a complex batch routine that is controlled by a central system, you
may want to create a MAXBATCH table interface that updates the batch number
and batch line number to ensure the use of unique batch numbers and batch line
numbers.
473
Chapter 4
Maintaining the Interface Tables

This section provides information about how to purge and to maintain the
interface tables. For more information about the interface tables, see “MAXIMO
You should use SQL*Plus, SQLTalk, or Quest to query the interface tables or to
update their contents.
Purging the Interface Tables

All data that has been inserted in the interface tables remains in the tables until
you purge them. All new data is appended to the existing data in the tables to
provide an audit trail of activity.
You should purge the interface tables periodically to prevent them from getting
too large. The following tables are the ones you should purge:
• MAX_AP_INTERFACE
• MAX_COAX_INTERFACE
• MAX_COA_INTERFACE
• MAX_COM_INTERFACE
• MAX_ICF_INTERFACE
• MAX_ISU_INTERFACE
• MAX_ITM_INTERFACE
• MAX_LPY_INTERFACE
• MAX_LS_INTERFACE
• MAX_POX_INTERFACE
• MAX_PO_INTERFACE
• MAX_PRX_INTERFACE
• MAX_PR_INTERFACE
• MAX_RCV_INTERFACE
• MAX_SRV_INTERFACE
• MAX_WOX_INTERFACE
• MOUT_AP_INTERFACE
• MOUT_GL_INTERFACE
474
System Maintenance
• MOUT_PO_INTERFACE
• MOUT_PR_INTERFACE
• MOUT_RSV_INTERFACE
• MOUT_WO_INTERFACE
You can purge all MAXIMO interface tables at one time by running the
SQL*Plus script called CLEANUP.SQL. This script purges the tables listed
above and also purges extra tables that have names ending in _EXT_INT. For
information about naming extra tables, see “Using Extra Tables in User Exits” on
page 467.
You may wish to create a batch routine that selectively removes data from the
interface tables on a regular schedule.
Running Reports
You can periodically run reports on the MAXIMO interface log table to check
for error statuses in the log. Use the error status columns to identify transactions
that were not completed successfully.
You should use SQL*Plus or Quest to run these reports.
For a description of the MAXIMO interface log table, see “MAXIMO Interface
Log” on page 477.
475
Chapter 4
Troubleshooting
This section provides information about troubleshooting the software integration
process and solving problems that may occur during a transaction between
MAXIMO and Oracle Financials.
General Troubleshooting Procedures

If data that was sent from the source application does not appear in the
destination application, refer to the following list to troubleshoot the problem:
1. Did you recently reconfigure the database?
If you did not, continue to step 2.
If you did, check the map file to determine whether you need to run the
AFTCONFO script. For more information, see “Configuring the Database” on
page 465.
2. Check the MAXIMO interface tables and interface log table for errors.
You can check the interface tables for an error status code. To get more
details or to search for general failures, check the interface log table. For more
information about the status codes, see “Checking Status Columns” on page
478. For more information about the interface log table, see “MAXIMO
Interface Log” on page 477.
You should correct all errors listed. If you need help understanding the error
messages, see “Error Messages” on page 480.
If you do not see any errors, continue to step 3.
3. Verify that all interface table columns are correctly mapped between the two
applications. The column type and length must be compatible. If you have
not mapped the interface table columns, map them now.
476
System Maintenance
For more information on coordinating column length and type, see

“Reconfiguring MAXIMO Table Columns” on page 18.
For more information on mapping, see Chapter 3, “Using the Integration
Module.”
4. If your transactions occur in real-time rather than by batch mode, verify that
all interface table columns are correctly mapped between the two
applications—column type and length must be compatible.
If you have not mapped the interface table columns, map them now. For more
information about mapping columns, see “Reconfiguring MAXIMO Table
Columns” on page 18.
If you have correctly mapped the interface table columns, continue to step 5.
5. Verify that the user objects (triggers and procedures) are still valid.
MAXIMO Interface Log

The MAXIMO interface log table, called MAX_INTERFACE_LOG, records the
status of all transactions that occur between MAXIMO and your external
application. The interface log contains detailed information about the
transactions.
To see more information about an error in one of the interface tables, check the
interface log table for the full text of the error and the error history. You can also
see the following two sections, Checking Status Columns and Debugging Errors
Using MAXIMO Interface Flow for more error information.
477
Chapter 4
Checking Status Columns

Each interface table has three status columns to contain information on the status
of a transaction. The status columns indicate whether or not a transaction was
successfully completed. If a transaction failed, you can refer to the status
columns for the time of the failure and for a general error message about the
failure.
All interface tables contain the following three status columns:
• IMPORTSTATUS shows the status of the transaction.
DONE—the transaction was successful.
ERROR—errors were detected during the transaction and the data transfer did
not occur. Check IMPORTMESSAGE for error messages.
WARNING—the data was transferred but there was a problem during the
transfer. Check IMPORTMESSAGE for error messages.
• IMPORTTIMESTAMP shows the date and time the transaction completed or
failed.
• IMPORTMESSAGE shows a general message.
Debugging Errors Using MAXIMO Interface Flow

If there is a database rollback, MAXIMO does not write relevant information to
the interface log. If you need more information than is provided by
MAX_INTERFACE_LOG and the status columns in the interface tables, you can
produce a detailed set of API transaction information by using the MAXIMO
interface flow.
To produce an output file that contains information on your transactions, you
must enable the MAXIMO interface flow so that it “captures” the transaction
information. This means that you should repeat the error transaction with the
478
System Maintenance
interface flow turned on. You should disable the interface flow after you produce
the information you need.
1. Enable the MAXIMO interface flow by connecting to SQL*Plus as the
MAXIMO user and issuing this command:
SQL>EXEC MAXAPISET.FLOWON
2. Exit MAXIMO then restart MAXIMO.
3. Redo the error transaction.
4. Use SQL*Plus to issue this command:
SQL>start C:\MAXIMO\INTERFAC\SETEXVAR
(maximo1 –remove this whole line after determining if ‘maximo’ stays in the path above)
5. Then, issue this command:

SQL>start &MAXIMODIR.SHOWFLOW
(maximo1 –remove this whole line after determining if ‘maximo’ stays in the command above)
6. The script SHOWFLOW.SQL in the INTERFAC directory produces an

output file that contains the data from the MAX_INTERFACE_FLOW table.
7. View the output file, SHOWFLOW.OUT that the SHOWFLOW script wrote
to the LOG directory. This output file contains the detailed information on the
error transaction.
WARNING: Do not leave the MAXIMO interface flow enabled. Whenever
the interface flow in enabled, errors from MAXIMO to the
APIs are not propagated.
479
Chapter 4
To disable the MAXIMO interface flow, complete the following steps in

SQL*Plus:
1. Connect as the MAXIMO user.
2. Issue the following command:
SQL>EXEC MAXAPISET.FLOWOFF
Error Messages
This section describes some of the error messages that you might see when you
use the APIs. Errors are grouped according to their associated integration APIs.
Transferring Purchase Requisition Changes into MAXIMO

For each error shown below, an invalid status change was given to
MAX_PRX_INTERFACE:
PR is CurrentPRStatus, it must be waiting approval to be approved.
PR is CurrentPRStatus, it must be APPR or PRINT to be unapproved.
PR is CurrentPRStatus, it must be APPR or PRINT to be Canceled or Closed.
Transferring Purchase Orders into MAXIMO

Invalid PrNum: PRNumber
The PR number does not exist in MAXIMO.
PO cannot be created for PR: PRNumber with status: PRStatus
The PR does not have a status of APPR (approved). The PR must be approved
before a PO can be created.
480
System Maintenance
Transferring Purchase Order Changes into MAXIMO

For each error shown below, an invalid status change was given to
MAX_POX_INTERFACE:
PO is CurrentPOStatus, it must be waiting approval to be approved.
PO is CurrentPOStatus, it must be APPR or PRINT to be unapproved.
PO is CurrentPOStatus, it must be APPR or PRINT to be Canceled or Closed.
Transferring Receipts into MAXIMO

Invalid GLDEBITACCT: DebitAcct PrLine: PRLineNumber.
An invalid GL account was given for the GLDEBITACCT field. Enter a valid
GL account.
Warning 101 Found Shipvia: ShipVia Replaced with: 'OTHER'.
The value in the Ship Via field does not exist in SHIPVIA value list. The
value was replaced with default 'OTHER'.
Invalid PrNum: PRNumber.
The PR number does not exist in MAXIMO.
PO cannot be created for PR: PRNumber with status: PRStatus.
The PR does not have a status of APPR (approved). The PR must be approved
before a PO can be created.
481
Chapter 4
Transferring Invoices into MAXIMO

Invalid Item Number
When an invoice row is sent to MAXIMO with an invalid ITEM number, the
ERROR value is written to the IMPORTSTATUS column of the
MAX_AP_INTERFACE table. The APIs do not insert the invoice row into
the MAXIMO tables.
Action: If the item number is correct then you must add it to MAXIMO. If
it is an invalid item number, determine the correct one by researching the
data in the external system, or if the invoice line is associated with a PO
Line, by checking the item number on the PO line in MAXIMO.
Determine the value of APISEQ in the table for the row in error. Next,
update the MAX_AP_INTERFACE table so it sends the invoice row to
MAXIMO:
Issue these commands in SQL*Plus:
Update MAX_AP_INTERFACE
Set IMPORTSTATUS = NULL,
ITEMNUM = ‘correct item number’ (do this only if the item number
was incorrect)
Where APISEQ = value for the row in error; (this ensures that you
only update the one row in error).
Commit;
After you run this script, the update to the table causes the API triggers to
import the row into MAXIMO.
Verify the update was done successfully by checking the IMPORTSTATUS
column of the interface table.
482
System Maintenance
Error: Unapproved Service Receipt

When an invoice row is sent to MAXIMO for a service receipt that has not been
approved, the error is caught and the IMPORTSTSATUS column of the
MAX_AP_INTERFACE table is updated with the value “ERROR.” The invoice
row is not inserted into the MAXIMO tables.
In the MAX_AP_INTERFACE table , the IMPORTMESSAGE status column
provides the PO number and PO line number on the service receipt. Determine
the value of APISEQ for the row in error.
Action: In MAXIMO, open the Purchase Orders application and query for the
purchase order named in the IMPORTMESSAGE column. Click the Service
Receipt tab and highlight the row for unapproved service receipts. Select
Actions/Approve Service Receipts.
Next, you must update the MAX_AP_INTERFACE table so it can send data
for the invoice row to MAXIMO:
Issue these commands in SQL*Plus:
Update MAX_AP_INTERFACE;
Set IMPORTSTATUS = NULL,
Where APISEQ = value for the row in error; (this ensures that you only
update the one row in error).
Commit;
Check the IMPORTSTATUS column of the interface table to verify that the
update was successful.
483
Chapter 4
Error: Disqualified Vendor

When an invoice row is sent to MAXIMO that contains a vendor that has been
updated as DISABLED in the COMPANIES table, the error is caught and the
IMPORTSTATUS column of the MAX_AP_INTERFACE is updated with the
value ERROR. The invoice row is not inserted into the MAXIMO tables.
In the MAX_AP_INTERFACE table, the IMPORTMESSAGE status column
shows the vendor identifier of the disqualified vendor. Determine the value of
APISEQ for the row in error.
Action: There are two ways to resolve this error. You can use the Companies
application in MAXIMO to qualify the vendor or you can change the
identifier of the vendor listed in the MAX_AP_INTERFACE table to a
vendor that is qualified in MAXIMO.
After you take either of these steps, you will update the
MAX_AP_INTERFACE table to send the invoice row to MAXIMO:
Update MAX_AP_INTERFACE
Set IMPORTSTATUS= NULL,
(if you are changing the vendor identifier insert the column updates here)
Where APISEQ = value for the row in error; (this ensures that you only
update the one row in error)
Commit;
Verify the update was successful by checking the IMPORTSTATUS column
of the interface table.
484
System Maintenance
Oracle Errors
The following Oracle user errors occur when records are not found or there is a
violation of Oracle constraints:
ORA-20100 ProgramName ORA-ErrorNumber ErrorMessage
In these messages:
• ProgramName is the name of the procedure in which the error occurred.
• ErrorNumber is the Oracle error number.
• ErrorMessage is the Oracle error message.
You might see one of the following error messages when transferring data from
MAXIMO to Oracle Financials.
Invalid Debit/Credit GL Code Combinations
The GL account value failed Oracle Financials validation. Enter a valid GL
account.
Invalid BillTo
BillTo must have a valid organization in Oracle Financials. Specify a valid
organization defined in Oracle Financials.
Invalid enter by user
The user ID value failed Oracle Financials validation. If GENUSR is set to N, the
user ID being passed may be invalid or not authorized for the function being
performed in Oracle Financials. Enter a valid user ID. If GENUSR is Y, set up
the MAXIMO ID in Oracle Financials to have access to the function being
performed.
485
Chapter 4
Invalid vendor or Invalid vendor header

The component in the MAXIMO vendor key that makes up the vendor ID failed
Oracle Financials validation. Enter a valid vendor.
Invalid vendor site
The component in the MAXIMO vendor key that makes up the vendor site ID
failed Oracle Financials validation. Enter a valid vendor.
486
Notes
487
MPD0741-max411orafn11i-02-ENG-09/2002

Oracle 11i Financial Integer at Ion

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oracle 11i Financial Integer at Ion

Uploaded by

Copyright:

Available Formats

Integration Guide

Oracle Financials 11i

Copyright 2002, MRO Software, Inc.

United States Patent No. 6,325,522 B2

Trademarks: MAXIMO®, INTERMAT®, Struxure®, MAXIMO® Enterprise™, MAXIMO®

MAXIMO Portions © 1998, 1999 NETRONIC Software GmbH.

Transferring Item Confirmations to MAXIMO........................................................103

Item Interface Tables ..............................................................................................198

CHAPTER 4: SYSTEM MAINTENANCE ................................................................465

This manual provides information about the MAXIMO financial application

1. Introduction Provides an overview of the MAXIMO

3. Using the Integration Module Explains how to use the integration

4. System Maintenance Describes how to maintain the interface

MAXIMO MAXIMO Integration Oracle Oracle

The Oracle Financials integration API is an extension of the standard MAXIMO

The following diagram illustrates this exchange of purchasing information.

MAXIMO Oracle Financials

Approved MOUT_PR_INTERFACE PO_REQUISITIONS_INTERFACE

MOUT_PO_INTERFACE Approved Purchase Order Oracle

IMPLEMENTING THE SOFTWARE

This section describes the system changes necessary to integrate

Reconfiguring MAXIMO Table Columns

Modifying Integration API Control Codes

APINADJINV Adjusts inventory cost if there is variance.

Configuration 1 and Configuration 2. For some controls, the control

API Control Applicable for Control Description

APICTL COA Y Y Receive chart of

API Control Applicable for Control Description

APICTL COMIN Y Y Receive companies

API Control Applicable for Control Description

APICTL ITMSTOREIN Y Y Receive item store

API Control Applicable for Control Description

APICTL ITMBALXFRIN Y N When Y, receive

API Control Applicable for Control Description

APICTL RCVIBUPD Y Y When N, bypass the

API Control Applicable for Control Description

APICTL JELABOR Y Y Send labor journal

API Control Applicable for Control Description

APICTL APIN Y Y for Receive invoice

API Control Applicable for Control Description

APICTL APINAUTORCV N Y Auto receipt on

API Control Applicable for Control Description

APICTL PRINT Y N Send internal PR

API Control Applicable for Control Description

APICTL RCVINADJDIREC N (Y) Regardless of

API Control Applicable for Control Description

APICTL RCVSVCAPPR Y Y Update Service

API Control Applicable for Control Description

APICTL WOUNAPPACTUA N Y When N, a change

API Control Applicable for Control Description

APICTL RSVONLIN Y N When Y, accept

API Control Applicable for Control Description

APICTL ERCVOUT Y Y When Y, send

API Control Applicable for Control Description

APICTL SYSTEMIN N N When Y, receive

API Control Applicable to Control Description

APICTL ACTUALSOUT Y Y Project Actuals

Use MAXIMO Application Setup to change the control code values.

Oracle Financials Control Codes

value automatically written to Set of Books ID with your derived Set of

Note that currently there is no integration API for transferring receipts

Vendor APIs between MAXIMO and Oracle Financials implement

Oracle Control Control Value Description