Documente Academic
Documente Profesional
Documente Cultură
Release 4.1.1
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.
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).
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.
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
APICTL Control Values for Configuration 2 .............................................................70
Configuration 3 ..........................................................................................................71
APICTL Control Values for Configuration 3 .............................................................72
Configuration 4 ..........................................................................................................73
APICTL Control Values for Configuration 4 .............................................................74
Configuration 5 ..........................................................................................................75
APICTL Control Values for Configuration 5 .............................................................76
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
5
Contents
6
Contents
7
Contents
8
CHAPTER 1
INTRODUCTION
• 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
2. Implementing the Software Integration Describes the system changes you need
to make in order to integrate MAXIMO
and Oracle Financials.
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
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
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
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.
18
Implementing the Software Integration
19
Chapter 2
20
Implementing the Software Integration
21
Chapter 2
22
Implementing the Software Integration
23
Chapter 2
24
Implementing the Software Integration
25
Chapter 2
26
Implementing the Software Integration
27
Chapter 2
28
Implementing the Software Integration
29
Chapter 2
30
Implementing the Software Integration
31
Chapter 2
32
Implementing the Software Integration
33
Chapter 2
34
Implementing the Software Integration
35
Chapter 2
36
Implementing the Software Integration
37
Chapter 2
38
Implementing the Software Integration
39
Chapter 2
40
Implementing the Software Integration
41
Chapter 2
42
Implementing the Software Integration
43
Chapter 2
44
Implementing the Software Integration
45
Chapter 2
46
Implementing the Software Integration
47
Chapter 2
48
CHAPTER 3
49
Chapter 3
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.
50
Using the Integration Module
Query results:
• Items with INVOWNER = E are treated as Oracle owned inventory by the
APIs.
51
Chapter 3
MAXIMO No MAXIMO
owned owned
Inventory No
Inventory
Oracle No Oracle
owned owned
Inventory Yes Inventory
52
Using the Integration Module
53
Chapter 3
54
Using the Integration Module
55
Chapter 3
56
Using the Integration Module
57
Chapter 3
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.
(B/O) Both
ISUIN B/O N N Y
JEINVENTORY B/O N Y N
JEMATUSE B/O Y Y N
58
Using the Integration Module
(B/O) Both
59
Chapter 3
60
Using the Integration Module
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.
61
Chapter 3
62
Using the Integration Module
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.
64
Using the Integration Module
APIN Y Y N Y N
APOUT N N Y N Y
PROUT Y N N N N
65
Chapter 3
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
Using the Integration Module
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
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
Using the Integration Module
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 chart of accounts data from your financial system to the MAXIMO
Chart of Accounts application.
• Transfer purchasing-related general ledger journal entries from MAXIMO to
your financial system.
• Exchange vendor information.
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
Using the Integration Module
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.
• Exchange vendor information.
• 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
Using the Integration Module
Configuration 4
Configuration 4 supports distributed requisitioning, purchasing, and receiving in
MAXIMO, and centralized invoicing and accounts payable activities.
In the fourth configuration:
• Create and process purchase requisitions in MAXIMO.
• 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.
• Send the invoice summary or detail to MAXIMO after accounts payable
processing by the Oracle Financials system.
• Transfer chart of accounts data from your financial system to the MAXIMO
Chart of Accounts application.
• Transfer purchasing-related general ledger journal entries from MAXIMO to
your financial system.
• Exchange vendor information.
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
Using the Integration Module
Configuration 5
Configuration 5 supports distributed requisitioning, purchasing, receiving, and
invoicing in MAXIMO, and centralized accounts payable activities.
In the fifth configuration:
• Create and process purchase requisitions in MAXIMO.
• Create purchase orders in MAXIMO and send them to the Oracle Financials
system; process receipts in MAXIMO.
• Receive invoices and process them in MAXIMO.
• Send the invoice summary or detail to MAXIMO after accounts payable
processing by the Oracle Financials system.
• Transfer chart of accounts data from your financial system to the MAXIMO
Chart of Accounts application.
• Transfer purchasing-related general ledger journal entries from MAXIMO to
your financial system.
• Exchange vendor information.
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
Using the Integration Module
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
78
Using the Integration Module
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.
79
Chapter 3
80
Using the Integration Module
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.
For more information on customizing user exit procedures, see “Customizing the
Integration APIS” on page 466.
No UTRANSTYPE codes are defined.
MAXIMO-related data is available from the following MAXIMO tables:
• PR
• PRLINE
• ITEM
• INVENTORY
• COMPANIES
82
Using the Integration Module
MAX_PRX_INTERFACE calls
MAXIMO internal procedures to
update the PR status or delete the PR
in MAXIMO.
For more information on customizing user exit procedures, see “Customizing the
Integration APIS” on page 466.
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.
83
Chapter 3
The API does not use any UTRANSTYPE codes for this process.
For more information on customizing user exit procedures, see “Customizing the
Integration APIS” on page 466.
84
Using the Integration Module
MAX_POX_INTERFACE calls
MAXIMO internal procedures to
update the PO status or delete the PO
in MAXIMO.
85
Chapter 3
The API does not use any UTRANSTYPE codes for this process.
For more information on customizing user exit procedures, see “Customizing the
Integration APIS” on page 466.
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
Using the Integration Module
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.
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.
For more information about the UTRANSTYPE values, see “The User Control
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
Using the Integration Module
The table below shows the differences between the CAI PO Interface and the
Oracle 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.
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.
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
The Oracle Receiving Transaction Processor is used to import data into Oracle.
Refer to Oracle Applications documentation for further information.
90
Using the Integration Module
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.
The API copies relevant purchasing data from these tables:
• 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.
For more information about the UTRANSTYPE values, see “The User Control
Column” on page 126. For more information on customizing user exit
procedures, see chapter 2.
91
Chapter 3
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.
92
Using the Integration Module
is the loaded cost. Refer to the on-line MAXIMO documentation for more
information on loaded costs.
93
Chapter 3
OR
94
Using the Integration Module
95
Chapter 3
The Oracle Item Interface is used to import data into Oracle. Refer to Oracle
Applications documentation for further information.
96
Using the Integration Module
The API can update the following tables from this transaction:
• ITEM
• INVVENDOR
• COMPANIES
The API uses the following values in the UTRANSTYPE column of the interface
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.
The API uses the following values in the UTRANSTYPE column of the interface
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.
The API uses the following values in the UTRANSTYPE column of the interface
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
Column” on page 126.
For more information on customizing user exit procedures, see “Customizing the
Integration APIS” on page 466.
97
Chapter 3
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
Using the Integration Module
99
Chapter 3
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.
100
Using the Integration Module
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.
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.
For more information about the UTRANSTYPE values, see “The User Control
Column” on page 126. For more information on customizing user exit
procedures, see Chapter 2, “Implementing the Software Integration.”
102
Using the Integration Module
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.”
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
Using the Integration Module
For more information on customizing user exit procedures, see “Customizing the
Integration APIS” on page 466.
The UTRANSTYPE column in the interface table indicates the API process for
vendor using the following values:
• XCI – Insert the vendor record. Default process.
• XCU – Update the vendor record. Default process.
• XCD – Delete the vendor record.
For more information about the UTRANSTYPE column, see “MAXIMO
Interface Tables” on page 125.
MAXIMO-related data is available from the following MAXIMO table:
• COMPANIES
105
Chapter 3
The Oracle Invoice Import is used to import data into Oracle. Refer to Oracle
Applications documentation for further information.
The API uses one value in the UTRANSTYPE column to process the change:
• INVOICEAPPR – Insert an invoice record.
106
Using the Integration Module
107
Chapter 3
variance if none is provided, but it may not be the same amount that your
accounts payable system has calculated.
The API does not use any UTRANSTYPE codes for this process.
For more information on customizing user exit procedures, see “Customizing the
Integration APIS” on page 466.
108
Using the Integration Module
109
Chapter 3
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
Using the Integration Module
For more information about the UTRANSTYPE values see “The User Control
Column” on page 126. For more information on customizing user exit
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
INSERTITEM
PCOUNTADJ
112
Using the Integration Module
113
Chapter 3
MOUT_GL_INTERFACE MXO_USR_MOUT_GL_
copies the data to the INTERFACE_SP
GL_INTERFACE table in
Oracle Financials for further
processing.
114
Using the Integration Module
MOUT_GL_INTERFACE MXO_USR_MOUT_GL_
copies the data to the INTERFACE_SP
GL_INTERFACE table in
Oracle Financials for further
processing.
115
Chapter 3
WORK
NON-WORK
116
Using the Integration Module
117
Chapter 3
MOUT_GL_INTERFACE MXE_GL_SP
calls external procedure for
further processing.
118
Using the Integration Module
For more information on customizing user exit procedures, see “Customizing the
Integration APIS” on page 466.
The UTRANSTYPE column in the interface table indicates the API process for
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.
For more information about the UTRANSTYPE column, see “MAXIMO
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.
120
Using the Integration Module
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.
121
Chapter 3
Thus, if transferring this account from one system to another, you must
make the following changes to the user exit procedures.
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.
OFGLSegs(2) := LTRIM(OFGLSegs(2),’0’);
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.
OFGLSegs(2) := LPAD(OFGLSegs(2),3,’0’);
122
Using the Integration Module
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.
Segment1 = null
Segment2 = size(2)
Segment3 = size(3)
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
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(2) := OFGLSegs(1);
OFGLSegs(1) := Null;
Taking note of the order of movements, add the following statements to the
procedure MXE_USR_GLINX_SP in file OFGLINX.USP:
OFGLSegs(1) := OFGLSegs(2);
OFGLSegs(2) := OFGLSegs(3);
OFGLSegs(3) := Null;
124
Using the Integration Module
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.
126
Using the Integration Module
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.
• 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.
127
Chapter 3
• 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
Using the Integration Module
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
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.
130
Using the Integration Module
131
Chapter 3
132
Using the Integration Module
133
Chapter 3
134
Using the Integration Module
135
Chapter 3
VARVALUE(BASCURREN
CURRENCYCODE2 UPPER 8 Y MAXVAR CY2)
VENDORPACKQUANTIT VENDORPACKQUANTIT
Y ALN 12 Y PRLINE Y
136
Using the Integration Module
FINCNTRLID ALN 8 Y
137
Chapter 3
138
Using the Integration Module
139
Chapter 3
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
140
Using the Integration Module
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
IMPORTSTATUS ALN 25 Y
IMPORTTIMESTAMP DATETIME 10 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.
Empty rows in the table are not physical rows in the database. They are there to
separate information coming from different tables or to group sets of data.
142
Using the Integration Module
143
Chapter 3
144
Using the Integration Module
145
Chapter 3
146
Using the Integration Module
CURRENCYCODE2 UPPER 8 Y
VENDORPACKQUANTI VENDORPACKQUANTIT
TY ALN 12 Y PRLINE Y
147
Chapter 3
148
Using the Integration Module
149
Chapter 3
ROWSTAMP ALN 40
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
Using the Integration Module
USERDATA9 ALN 1 Y
USERDATA10 ALN 1 Y
TOTALLINES INTEGER 4 Y
BATCHID ALN 25 Y
BATCHLINEID INTEGER 4 Y
UTRANSTYPE ALN 25 Y
IMPORTSTATUS ALN 25 Y
IMPORTTIMESTAMP DATETIME 10 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.
Empty rows in the table are not physical rows in the database. They are there to
separate information coming from different tables or to group sets of data.
152
Using the Integration Module
153
Chapter 3
154
Using the Integration Module
155
Chapter 3
156
Using the Integration Module
157
Chapter 3
158
Using the Integration Module
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
BATCHLINEID INTEGER 4 Y
UTRANSTYPE ALN 25 Y
IMPORTSTATUS ALN 40 Y
IMPORTTIMESTAMP DATETIME 10 Y
160
Using the Integration Module
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.
Empty rows in the table are not physical rows in the database. They are there to
separate information coming from different tables or to group sets of data.
161
Chapter 3
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
BATCHLINEID INTEGER 4 Y
UTRANSTYPE ALN 25 Y
IMPORTSTATUS ALN 25 Y
IMPORTTIMESTAMP DATETIME 10 Y
162
Using the Integration Module
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.
Empty rows in the table are not physical rows in the database. They are there to
separate information coming from different tables or to group sets of data.
REJECTCOST DECIMAL 15 Y
163
Chapter 3
SERIALNUM UPPER 15 Y
TOTALCURBAL AMOUNT 15 Y
OLDAVGCOST AMOUNT 10 Y
164
Using the Integration Module
CURRENCYCODE2 UPPER 8 Y
165
Chapter 3
INVOICEDQTY DECIMAL 15 Y
CLAIMNUM UPPER 8 Y
APPROVED YORN 1 Y
APPROVEDATE DATETIME 10 Y
APPROVEBY UPPER 18 Y
166
Using the Integration Module
SERVRECTRANSID INTEGER 4 Y
RECID ALN 1 Y
ROLLUP ALN 1 Y
IBUPD YORN 1 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
BATCHLINEID INTEGER 4 Y
UTRANSTYPE ALN 25 Y
IMPORTSTATUS ALN 25 Y
IMPORTTIMESTAMP DATETIME 10 Y
168
Using the Integration Module
The following table shows the mapping for the MAX_RCV_INTERFACE and
SERVRECTRANS tables.
Empty rows in the table are not physical rows in the database. They are there to
separate information coming from different tables or to group sets of data.
ITEMNUM UPPER 30 Y
TOSTORELOC UPPER 8 Y
RECEIVEDUNIT ALN 8 Y
ISSUETYPE UPPER 8 Y
ACTUALCOST AMOUNT 10 Y
REJECTCODE UPPER 6 Y
CONVERSION DECIMAL 15 Y
SERIALNUM UPPER 15 Y
169
Chapter 3
IT2 ALN 10 Y
IT3 ALN 10 Y
IT4 AMOUNT 15 Y
IT5 ALN 10 Y
ISSUETO UPPER 8 Y
PACKINGSLIPNUM ALN 20 Y
ISSUE YORN 1 Y
REQUESTEDBY ALN 20 Y
TOTALCURBAL AMOUNT 15 Y
OLDAVGCOST AMOUNT 10 Y
TOBIN ALN 8 Y
170
Using the Integration Module
CURRENCYCODE2 UPPER 8 Y
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
MATRECTRANSID NUMBER 10 Y
172
Using the Integration Module
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
IBUPD YORN 1 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
BATCHLINEID INTEGER 4 Y
UTRANSTYPE ALN 25 Y
IMPORTSTATUS ALN 25 Y
IMPORTTIMESTAMP DATETIME 10 Y
174
Using the Integration Module
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.
175
Chapter 3
176
Using the Integration Module
VARVALUE(BASCURREN
CURRENCYCODE2 UPPER 8 Y MAXVAR CY2)
177
Chapter 3
178
Using the Integration Module
179
Chapter 3
180
Using the Integration Module
181
Chapter 3
182
Using the Integration Module
ROWSTAMP ALN 40 Y
183
Chapter 3
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
VENDORPACKQUANTI VENDORPACKQUANTIT
TY ALN 12 Y POLINE Y
TOTALLINES INTEGER 4 Y
BATCHID ALN 25 Y
BATCHLINEID INTEGER 10 Y
184
Using the Integration Module
UTRANSTYPE ALN 25 Y
IMPORTSTATUS ALN 25 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.
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.
186
Using the Integration Module
REJECTCOST DECIMAL 15 Y
187
Chapter 3
CLAIMNUM UPPER 8 Y
188
Using the Integration Module
APPROVED YORN 1 Y
APPROVEDATE DATETIME 10 Y
APPROVEBY UPPER 18 Y
ROWSTAMP ALN 40 N
189
Chapter 3
SERVRECTRANSID INTEGER 4 Y
190
Using the Integration Module
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
BATCHLINEID INTEGER 4 Y
UTRANSTYPE ALN 25 Y
IMPORTSTATUS ALN 25 Y
IMPORTTIMESTAMP DATETIME 10 Y
191
Chapter 3
ITEMNUM UPPER 30 Y
TOSTORELOC UPPER 8 Y
RECEIVEDUNIT ALN 8 Y
ISSUETYPE UPPER 8 Y
ACTUALCOST AMOUNT 10 Y
REJECTCODE UPPER 6 Y
CONVERSION DECIMAL 15 Y
192
Using the Integration Module
IT2 ALN 10 Y
IT3 ALN 10 Y
IT4 DECIMAL 15 Y
IT5 ALN 10 Y
ISSUETO UPPER 8 Y
PACKINGSLIPNUM ALN 20 Y
ISSUE YORN 1 Y
REQUESTEDBY ALN 20 Y
TOTALCURBAL AMOUNT 15 Y
OLDAVGCOST AMOUNT 10 Y
TOBIN ALN 8 Y
LOTNUM UPPER 8 Y
193
Chapter 3
MANUFACTURER UPPER 8 Y
MODELNUM ALN 8 Y
FROMSTORELOC UPPER 8 Y
FROMBIN ALN 8 Y
QTYHELD DECIMAL 15 Y
194
Using the Integration Module
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
MATRECTRANSID NUMBER 10 Y
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
USERDATA1 ALN 1 Y
196
Using the Integration Module
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
BATCHLINEID INTEGER 4 Y
UTRANSTYPE ALN 25 Y
IMPORTSTATUS ALN 25 Y
IMPORTTIMESTAMP DATETIME 10 Y
197
Chapter 3
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.
Empty rows in the table are not physical rows in the database. They are there to
separate information coming from different tables or to group sets of data.
198
Using the Integration Module
199
Chapter 3
200
Using the Integration Module
201
Chapter 3
202
Using the Integration Module
203
Chapter 3
204
Using the Integration Module
205
Chapter 3
206
Using the Integration Module
207
Chapter 3
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
BATCHLINEID INTEGER 4 Y
UTRANSTYPE ALN 25 Y
208
Using the Integration Module
IMPORTSTATUS ALN 40 Y
IMPORTTIMESTAMP DATETIME 10 Y
209
Chapter 3
210
Using the Integration Module
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.
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.
211
Chapter 3
ISSUETO ALN 8 Y
212
Using the Integration Module
213
Chapter 3
214
Using the Integration Module
215
Chapter 3
216
Using the Integration Module
217
Chapter 3
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
BATCHLINEID INTEGER 4 Y
218
Using the Integration Module
UTRANSTYPE ALN 25 Y
IMPORTSTATUS ALN 40 Y
IMPORTTIMESTAMP DATETIME 10 Y
219
Chapter 3
220
Using the Integration Module
ISSUETO ALN 8 Y
221
Chapter 3
222
Using the Integration Module
223
Chapter 3
224
Using the Integration Module
225
Chapter 3
226
Using the Integration Module
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
BATCHLINEID INTEGER 4 Y
227
Chapter 3
UTRANSTYPE ALN 25 Y
IMPORTSTATUS ALN 40 Y
IMPORTTIMESTAMP DATETIME 10 Y
228
Using the Integration Module
229
Chapter 3
230
Using the Integration Module
IBUPD YORN 1 Y
231
Chapter 3
ISSUEID INTEGER 4 Y
ROWSTAMP ALN 40 Y
USERDATA1 ALN 1 Y
232
Using the Integration Module
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
BATCHLINEID INTEGER 4 Y
UTRANSTYPE ALN 25 Y
IMPORTSTATUS ALN 25 Y
IMPORTTIMESTAMP DATETIME 10 Y
233
Chapter 3
234
Using the Integration Module
MAX_COM_INTERFACE
The MAX_COM_INTERFACE table receives vendor data from Oracle
Financials and sends it to the following MAXIMO tables.
Empty rows in the table are not physical rows in the database. They are there to
separate information coming from different tables or to group sets of data.
235
Chapter 3
236
Using the Integration Module
237
Chapter 3
238
Using the Integration Module
PROCUREMENTCARDN PROCUREMENTCARDNU
UM ALN 30 Y COMPCONTACT M
PROCCARDEXPAIREDA PROCCARDEXPAIREDAT
TE DATETIME 4 Y COMPCONTACT E
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
BATCHLINEID INTEGER 4 Y
UTRANSTYPE ALN 25 Y
240
Using the Integration Module
IMPORTSTATUS ALN 40 Y
IMPORTTIMESTAMP DATETIME 10 Y
241
Chapter 3
MOUT_AP_INTERFACE
MOUT_AP_INTERFACE receives invoice data from the following MAXIMO
tables. Data is transferred to Oracle Financials.
Empty rows in the table are not physical rows in the database. They are there to
separate information coming from different tables or to group sets of data.
242
Using the Integration Module
243
Chapter 3
244
Using the Integration Module
SYSCODE INTEGER 4 Y
APISEQ INTEGER 4 Y
245
Chapter 3
246
Using the Integration Module
247
Chapter 3
248
Using the Integration Module
249
Chapter 3
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
Using the Integration Module
USERDATA9 ALN 1 Y
USERDATA10 ALN 1 Y
TOTALLINES INTEGER 4 Y
BATCHID ALN 25 Y
BATCHLINEID INTEGER 4 Y
UTRANSTYPE ALN 25 Y
IMPORTSTATUS ALN 40 Y
IMPORTTIMESTAMP DATETIME 10 Y
251
Chapter 3
MAX_AP_INTERFACE
MAX_AP_INTERFACE receives invoice data from Oracle Financials. Data is
sent to the following MAXIMO tables.
Empty rows in the table are not physical rows in the database. They are there to
separate information coming from different tables or to group sets of data.
252
Using the Integration Module
253
Chapter 3
254
Using the Integration Module
255
Chapter 3
256
Using the Integration Module
VARVALUE(BASCURREN
CURRENCYCODE2 UPPER 8 Y MAXVAR CY2)
257
Chapter 3
258
Using the Integration Module
259
Chapter 3
INVOICETRAN
PRICEVAR ALN 8 Y S LINECOST
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
TOTALLINES INTEGER 4 Y
BATCHID ALN 25 Y
260
Using the Integration Module
BATCHLINEID INTEGER 4 Y
UTRANSTYPE ALN 25 Y
IMPORTSTATUS ALN 40 Y
IMPORTTIMESTAMP DATETIME 10 Y
261
Chapter 3
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.
Empty rows in the table are not physical rows in the database. They are there to
separate information coming from different tables or to group sets of data.
262
Using the Integration Module
FROMSTORELOC UPPER 8 Y
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
LABORCODE UPPER 8 Y
CRAFT UPPER 8 Y
REGULARHRS DURATION 8 Y
OTHRS DURATION 8 Y
264
Using the Integration Module
TOOLNUM UPPER 8 Y
VENDOR UPPER 8 Y
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
Using the Integration Module
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
Using the Integration Module
USERDATA6 ALN 1 Y
USERDATA7 ALN 1 Y
USERDATA8 ALN 1 Y
USERDATA9 ALN 1 Y
USERDATA10 ALN 1 Y
BATCHID ALN 25 Y
BATCHLINEID INTEGER 4 Y
UTRANSTYPE ALN 25 Y
APISITE
SENDERSYSID SENDERSYSID
SOURCESYSID SOURCESYSID
OWNERSYSID OWNERSYSID
EXTERNALREFID EXTERNALREFID
ISSUEID
INVTRANSID INVTRANSID
269
Chapter 3
IMPORTSTATUS ALN 40 Y
IMPORTTIMESTAMP DATETIME 10 Y
270
Using the Integration Module
The following table shows the mapping for the MOUT_GL_INTERFACE and
MATUSETRANS tables.
Empty rows in the table are not physical rows in the database. They are there to
separate information coming from different tables or to group sets of data.
FROMSTORELOC UPPER 8 Y
271
Chapter 3
INVOICENUM UPPER 8 Y
INVOICELINENUM INTEGER 4 Y
COSTLINENUM INTEGER 4 Y
CLAIMNUM UPPER 8 Y
272
Using the Integration Module
LABORCODE UPPER 8 Y
CRAFT UPPER 8 Y
REGULARHRS DURATION 8 Y
OTHRS DURATION 8 Y
TOOLNUM UPPER 8 Y
VENDOR UPPER 8 Y
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
Using the Integration Module
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
BUDGETREF ALN 50 Y
BUDGETLINEREF 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
Using the Integration Module
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
BATCHLINEID INTEGER 4 Y
UTRANSTYPE ALN 25 Y
277
Chapter 3
APISITE
SENDERSYSID SENDERSYSID
SOURCESYSID SOURCESYSID
OWNERSYSID OWNERSYSID
EXTERNALREFID EXTERNALREFID
ISSUEID ISSUEID
INVTRANSID
IMPORTSTATUS ALN 40 Y
IMPORTTIMESTAMP DATETIME 10 Y
278
Using the Integration Module
The following table shows the mapping for the MOUT_GL_INTERFACE and
MATRECTRANS tables.
Empty rows in the table are not physical rows in the database. They are there to
separate information coming from different tables or to group sets of data.
279
Chapter 3
INVOICELINENUM INTEGER 4 Y
COSTLINENUM INTEGER 4 Y
CLAIMNUM UPPER 8 Y
280
Using the Integration Module
LABORCODE UPPER 8 Y
CRAFT UPPER 8 Y
REGULARHRS DURATION 8 Y
OTHRS DURATION 8 Y
TOOLNUM UPPER 8 Y
VENDOR UPPER 8 Y
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
Using the Integration Module
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
BUDGETREF ALN 50 Y
BUDGETLINEREF 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
Using the Integration Module
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
BATCHLINEID INTEGER 4 Y
UTRANSTYPE ALN 25 Y
285
Chapter 3
APISITE
SENDERSYSID SENDERSYSID
SOURCESYSID SOURCESYSID
OWNERSYSID OWNERSYSID
EXTERNALREFID EXTERNALREFID
ISSUEID
INVTRANSID
IMPORTSTATUS ALN 40 Y
IMPORTTIMESTAMP DATETIME 10 Y
286
Using the Integration Module
The following table shows the mapping for the MOUT_GL_INTERFACE and
SERVRECTRANS tables.
Empty rows in the table are not physical rows in the database. They are there to
separate information coming from different tables or to group sets of data.
TRANSTYPE UPPER 16 Y
ITEMNUM UPPER 8 Y
STORELOC UPPER 8 Y
BINNUM ALN 8 Y
FROMSTORELOC UPPER 8 Y
287
Chapter 3
INVOICELINENUM INTEGER 4 Y
COSTLINENUM INTEGER 4 Y
288
Using the Integration Module
LABORCODE UPPER 8 Y
CRAFT UPPER 8 Y
REGULARHRS DURATION 8 Y
OTHRS DURATION 8 Y
TOOLNUM UPPER 8 Y
VENDOR UPPER 8 Y
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
Using the Integration Module
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
BUDGETREF ALN 50 Y
BUDGETLINEREF 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
Using the Integration Module
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
BATCHLINEID INTEGER 4 Y
UTRANSTYPE ALN 25 Y
293
Chapter 3
APISITE
SENDERSYSID SENDERSYSID
SOURCESYSID SOURCESYSID
OWNERSYSID OWNERSYSID
EXTERNALREFID EXTERNALREFID
ISSUEID
INVTRANSID
IMPORTSTATUS ALN 40 Y
IMPORTTIMESTAMP DATETIME 10 Y
294
Using the Integration Module
The following table shows the mapping for the MOUT_GL_INTERFACE and
LABTRANS tables.
Empty rows in the table are not physical rows in the database. They are there to
separate information coming from different tables or to group sets of data.
ITEMNUM UPPER 8 Y
STORELOC UPPER 8 Y
BINNUM ALN 8 Y
QUANTITY DECIMAL 15 Y
FROMSTORELOC UPPER 8 Y
295
Chapter 3
INVOICENUM UPPER 8 Y
INVOICELINENUM INTEGER 4 Y
COSTLINENUM INTEGER 4 Y
CLAIMNUM UPPER 8 Y
CURRENCYCODE UPPER 8 Y
CURRENCYUNITCOST DECIMAL 10 Y
CURRENCYLINECOST DECIMAL 10 Y
EXCHANGERATE DECIMAL 10 Y
296
Using the Integration Module
TOOLNUM UPPER 8 Y
VENDOR UPPER 8 Y
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
Using the Integration Module
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
BUDGETREF ALN 50 Y
BUDGETLINEREF 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
Using the Integration Module
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
BATCHLINEID INTEGER 4 Y
UTRANSTYPE ALN 25 Y
301
Chapter 3
APISITE
SENDERSYSID SENDERSYSID
SOURCESYSID SOURCESYSID
OWNERSYSID OWNERSYSID
EXTERNALREFID EXTERNALREFID
ISSUEID
INVTRANSID
IMPORTSTATUS ALN 40 Y
IMPORTTIMESTAMP DATETIME 10 Y
302
Using the Integration Module
The following table shows the mapping for MOUT_GL_INTERFACE and the
INVOICETRANS, INVOICELINE and INVOICECOST tables.
Empty rows in the table are not physical rows in the database. They are there to
separate information coming from different tables or to group sets of data.
ITEMNUM UPPER 8 Y
STORELOC UPPER 8 Y
BINNUM ALN 8 Y
QUANTITY DECIMAL 15 Y
FROMSTORELOC UPPER 8 Y
UNITCOST AMOUNT 10 Y
303
Chapter 3
CLAIMNUM UPPER 8 Y
CURRENCYUNITCOST DECIMAL 10 Y
304
Using the Integration Module
LABORCODE UPPER 8 Y
CRAFT UPPER 8 Y
REGULARHRS DURATION 8 Y
OTHRS DURATION 8 Y
TOOLNUM UPPER 8 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
Using the Integration Module
PRORATESERVICE 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
BUDGETREF ALN 50 Y
BUDGETLINEREF 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
Using the Integration Module
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
BATCHLINEID INTEGER 4 Y
UTRANSTYPE ALN 25 Y
APISITE
SENDERSYSID SENDERSYSID
SOURCESYSID SOURCESYSID
OWNERSYSID OWNERSYSID
EXTERNALREFID EXTERNALREFID
ISSUEID
INVTRANSID
IMPORTSTATUS ALN 40 Y
IMPORTTIMESTAMP DATETIME 10 Y
310
Using the Integration Module
TRANSTYPE UPPER 16 Y
ITEMNUM UPPER 8 Y
STORELOC UPPER 8 Y
BINNUM ALN 8 Y
FROMSTORELOC UPPER 8 Y
311
Chapter 3
PONUM UPPER 8 Y
POLINENUM INTEGER 4 Y
INVOICENUM UPPER 8 Y
INVOICELINENUM INTEGER 4 Y
COSTLINENUM INTEGER 4 Y
CLAIMNUM UPPER 8 Y
CURRENCYCODE UPPER 8 Y
CURRENCYUNITCOST DECIMAL 10 Y
CURRENCYLINECOST DECIMAL 10 Y
EXCHANGERATE DECIMAL 10 Y
312
Using the Integration Module
LABORCODE UPPER 8 Y
CRAFT UPPER 8 Y
OTHRS DURATION 8 Y
VENDOR UPPER 8 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
Using the Integration Module
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
BUDGETREF ALN 50 Y
BUDGETLINEREF 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
Using the Integration Module
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
BATCHLINEID INTEGER 4 Y
UTRANSTYPE ALN 25 Y
317
Chapter 3
APISITE
SENDERSYSID SENDERSYSID
SOURCESYSID SOURCESYSID
OWNERSYSID OWNERSYSID
EXTERNALREFID EXTERNALREFID
ISSUEID
INVTRANSID
IMPORTSTATUS ALN 40 Y
IMPORTTIMESTAMP DATETIME 10 Y
318
Using the Integration Module
MAX_COA_INTERFACE Table
MAX_COA_INTERFACE receives chart of accounts data from Oracle
Financials. Data is sent to the following MAXIMO tables.
Empty rows in the table are not physical rows in the database. They are there to
separate information coming from different tables or to group sets of data.
319
Chapter 3
320
Using the Integration Module
321
Chapter 3
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
Using the Integration Module
USERDATA10 ALN 1 Y
UTRANSTYPE ALN 25 Y
IMPORTSTATUS ALN 40 Y
IMPORTTIMESTAMP DATETIME 10 Y
MAX_COAX_INTERFACE Table
MAX_COAX_INTERFACE receives GL component data from Oracle
Financials. Data is sent to the following MAXIMO tables.
Empty rows in the table are not physical rows in the database. They are there to
separate information coming from different tables or to group sets of data.
323
Chapter 3
324
Using the Integration Module
325
Chapter 3
USERDATA1 ALN 1 Y
USERDATA2 ALN 1 Y
USERDATA3 ALN 1 Y
USERDATA4 ALN 1 Y
326
Using the Integration Module
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
IMPORTSTATUS ALN 40 Y
IMPORTTIMESTAMP DATETIME 10 Y
327
Chapter 3
328
Using the Integration Module
329
Chapter 3
330
Using the Integration Module
331
Chapter 3
332
Using the Integration Module
333
Chapter 3
334
Using the Integration Module
335
Chapter 3
336
Using the Integration Module
337
Chapter 3
338
Using the Integration Module
339
Chapter 3
340
Using the Integration Module
341
Chapter 3
342
Using the Integration Module
343
Chapter 3
344
Using the Integration Module
345
Chapter 3
346
Using the Integration Module
347
Chapter 3
348
Using the Integration Module
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
350
Using the Integration Module
351
Chapter 3
352
Using the Integration Module
MTL_MATERIAL_TRANSACTION MAX_ITM_INTERFACE
353
Chapter 3
354
Using the Integration Module
355
Chapter 3
356
Using the Integration Module
357
Chapter 3
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
MTL_MATERIAL_TRANSACTIONS.LO
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
Using the Integration Module
359
Chapter 3
360
Using the Integration Module
361
Chapter 3
362
Using the Integration Module
363
Chapter 3
364
Using the Integration Module
365
Chapter 3
366
Using the Integration Module
WPOPERATION
ACTUALQTY
RESERVEDQTY RESERVATION_QUANTITY Number
PRIMARY_RESERVATION_Q Number MOUT_RSV_INTERFACE.
UANTITY RESERVEDQTY
367
Chapter 3
368
Using the Integration Module
369
Chapter 3
370
Using the Integration Module
371
Chapter 3
372
Using the Integration Module
373
Chapter 3
374
Using the Integration Module
375
Chapter 3
376
Using the Integration Module
377
Chapter 3
378
Using the Integration Module
379
Chapter 3
380
Using the Integration Module
381
Chapter 3
382
Using the Integration Module
383
Chapter 3
384
Using the Integration Module
385
Chapter 3
386
Using the Integration Module
387
Chapter 3
388
Using the Integration Module
389
Chapter 3
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
Using the Integration Module
GL_INTERFACE MOUT_GL_INTERFACE
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
GL_INTERFACE MOUT_GL_INTERFACE
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
Using the Integration Module
GL_INTERFACE MOUT_GL_INTERFACE
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
GL_INTERFACE MOUT_GL_INTERFACE
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
Using the Integration Module
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
396
Using the Integration Module
397
Chapter 3
398
Using the Integration Module
399
Chapter 3
400
Using the Integration Module
401
Chapter 3
402
Using the Integration Module
403
Chapter 3
MOUT_PO_INTERFACE PO_HEADERS_INTERFACE_CAI_ALL
404
Using the Integration Module
405
Chapter 3
406
Using the Integration Module
407
Chapter 3
408
Using the Integration Module
409
Chapter 3
410
Using the Integration Module
411
Chapter 3
412
Using the Integration Module
413
Chapter 3
NOTE: This table is populated only when the POTYPE = ‘REL’ (processing a MAXIMO Release PO).
414
Using the Integration Module
415
Chapter 3
416
Using the Integration Module
417
Chapter 3
418
Using the Integration Module
419
Chapter 3
420
Using the Integration Module
421
Chapter 3
422
Using the Integration Module
423
Chapter 3
424
Using the Integration Module
425
Chapter 3
426
Using the Integration Module
NOTE: The Standard Purchasing Documents Open Interface is available for Oracle versions 11.5.3 and later.
MAXIMO Oracle Financials
MOUT_PO_INTERFACE PO_HEADERS_INTERFACE
427
Chapter 3
428
Using the Integration Module
429
Chapter 3
430
Using the Integration Module
431
Chapter 3
432
Using the Integration Module
433
Chapter 3
434
Using the Integration Module
435
Chapter 3
436
Using the Integration Module
437
Chapter 3
438
Using the Integration Module
439
Chapter 3
440
Using the Integration Module
441
Chapter 3
442
Using the Integration Module
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
Oracle Financial PO module
GROUP_ID H Number Obtained from Oracle sequence
RCV_INTERFACE_GROUPS_S in
Oracle Financial PO module
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
MAX_RCV_INTERFACE RCV_HEADERS_INTERFACE
RCV_TRANSACTIONS_INTERFACE
Column Name Column Name Table Type Length COMMENTS
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
Using the Integration Module
MAX_RCV_INTERFACE RCV_HEADERS_INTERFACE
RCV_TRANSACTIONS_INTERFACE
Column Name Column Name Table Type Length COMMENTS
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
MAX_RCV_INTERFACE RCV_HEADERS_INTERFACE
RCV_TRANSACTIONS_INTERFACE
Column Name Column Name Table Type Length COMMENTS
Names
UPDATE_BY2
LAST_UPDATED_BY T Number Same as
RCV_HEADERS_INTERFACE.LAST_
UPDATE_BY2
CREATED_BY T Number Same as
RCV_HEADERS_INTERFACE.LAST_
UPDATE_BY2
LAST_UPDATE_LOGIN T Number Same as
RCV_HEADERS_INTERFACE.LAST_
UPDATE_BY2
IT1
IT2
IT3
IT4
IT5
OUTSIDE
WPOPERATION
ISSUETO
PACKINGSLIPNUM SHIPMENT_NUM H Varchar2
POLINENUM
ISSUE
REQUESTEDBY
TOTALCURBAL
OLDAVGCOST
446
Using the Integration Module
MAX_RCV_INTERFACE RCV_HEADERS_INTERFACE
RCV_TRANSACTIONS_INTERFACE
Column Name Column Name Table Type Length COMMENTS
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
MAX_RCV_INTERFACE RCV_HEADERS_INTERFACE
RCV_TRANSACTIONS_INTERFACE
Column Name Column Name Table Type Length COMMENTS
Names
REMARK
FROMSTORELOC
FROMBIN
QTYHELD
CLAIMNUM
APPROVED
APPROVEDATE
APPROVEBY
LONGDESC
USERDATA1
USERDATA2
USERDATA3
USERDATA4
USERDATA5
USERDATA6
USERDATA7
USERDATA8
USERDATA9
USERDATA10
BATCHID
BATCHLINEID
UTRANSTYPE
448
Using the Integration Module
MAX_RCV_INTERFACE RCV_HEADERS_INTERFACE
RCV_TRANSACTIONS_INTERFACE
Column Name Column Name Table Type Length COMMENTS
Names
SOURCEID
APISEQ
APISYNC
IMPORTSTATUS
IMPORTTIMESTAMP
IMPORTMESSAGE
Key to Tables
H RCV_HEADERS_INTERFACE
S RCV_TRANSACTIONS_INTERFACE
449
Chapter 3
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
CREATED_BY MAXIMO1 ID
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
Using the Integration Module
PO_REQUISITIONS_INTERFACE MOUT_PR_INTERFACE
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_ATTRIBUTE2 PR2
HEADER_ATTRIBUTE3 PR3
HEADER_ATTRIBUTE4 PR4
HEADER_ATTRIBUTE5 PR5
HEADER_ATTRIBUTE6
451
Chapter 3
PO_REQUISITIONS_INTERFACE MOUT_PR_INTERFACE
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
Using the Integration Module
PO_REQUISITIONS_INTERFACE MOUT_PR_INTERFACE
ITEM_SEGMENT14
ITEM_SEGMENT15
ITEM_SEGMENT16
ITEM_SEGMENT17
ITEM_SEGMENT18
ITEM_SEGMENT19
ITEM_SEGMENT20
ITEM_REVISION
CHARGE_ACCOUNT_ID GLDEBITACCT
CHARGE_ACCOUNT_SEGMENT1
CHARGE_ACCOUNT_SEGMENT2
CHARGE_ACCOUNT_SEGMENT3
CHARGE_ACCOUNT_SEGMENT4
CHARGE_ACCOUNT_SEGMENT5
CHARGE_ACCOUNT_SEGMENT6
CHARGE_ACCOUNT_SEGMENT7
CHARGE_ACCOUNT_SEGMENT8
CHARGE_ACCOUNT_SEGMENT9
CHARGE_ACCOUNT_SEGMENT10
CHARGE_ACCOUNT_SEGMENT11
CHARGE_ACCOUNT_SEGMENT12
CHARGE_ACCOUNT_SEGMENT13
CHARGE_ACCOUNT_SEGMENT14
CHARGE_ACCOUNT_SEGMENT15
CHARGE_ACCOUNT_SEGMENT16
CHARGE_ACCOUNT_SEGMENT17
CHARGE_ACCOUNT_SEGMENT18
CHARGE_ACCOUNT_SEGMENT19
453
Chapter 3
PO_REQUISITIONS_INTERFACE MOUT_PR_INTERFACE
CHARGE_ACCOUNT_SEGMENT20
CHARGE_ACCOUNT_SEGMENT21
CHARGE_ACCOUNT_SEGMENT22
CHARGE_ACCOUNT_SEGMENT23
CHARGE_ACCOUNT_SEGMENT24
CHARGE_ACCOUNT_SEGMENT25
CHARGE_ACCOUNT_SEGMENT26
CHARGE_ACCOUNT_SEGMENT27
CHARGE_ACCOUNT_SEGMENT28
CHARGE_ACCOUNT_SEGMENT29
CHARGE_ACCOUNT_SEGMENT30
CATEGORY_ID
CATEGORY_SEGMENT1 IN19 (Parsed)
CATEGORY_SEGMENT2 IN19 (Parsed)
CATEGORY_SEGMENT3 IN19 (Parsed)
CATEGORY_SEGMENT4 IN19 (Parsed)
CATEGORY_SEGMENT5 IN19 (Parsed)
CATEGORY_SEGMENT6 IN19 (Parsed)
CATEGORY_SEGMENT7 IN19 (Parsed)
CATEGORY_SEGMENT8 IN19 (Parsed)
CATEGORY_SEGMENT9 IN19 (Parsed)
CATEGORY_SEGMENT10 IN19 (Parsed)
CATEGORY_SEGMENT11 IN19 (Parsed)
CATEGORY_SEGMENT12 IN19 (Parsed)
CATEGORY_SEGMENT13 IN19 (Parsed)
CATEGORY_SEGMENT14 IN19 (Parsed)
CATEGORY_SEGMENT15 IN19 (Parsed)
CATEGORY_SEGMENT16 IN19 (Parsed)
454
Using the Integration Module
PO_REQUISITIONS_INTERFACE MOUT_PR_INTERFACE
CATEGORY_SEGMENT17 IN19 (Parsed)
CATEGORY_SEGMENT18 IN19 (Parsed)
CATEGORY_SEGMENT19 IN19 (Parsed)
CATEGORY_SEGMENT20 IN19 (Parsed)
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
PO_REQUISITIONS_INTERFACE MOUT_PR_INTERFACE
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_ATTRIBUTE7 RLIN2
LINE_ATTRIBUTE8 RLIN3
LINE_ATTRIBUTE9 RLIN4
LINE_ATTRIBUTE10 RLIN5
LINE_ATTRIBUTE11
LINE_ATTRIBUTE12
456
Using the Integration Module
PO_REQUISITIONS_INTERFACE MOUT_PR_INTERFACE
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
DISTRIBUTION_ATTRIBUTE2
457
Chapter 3
PO_REQUISITIONS_INTERFACE MOUT_PR_INTERFACE
DISTRIBUTION_ATTRIBUTE3
DISTRIBUTION_ATTRIBUTE4
DISTRIBUTION_ATTRIBUTE5
DISTRIBUTION_ATTRIBUTE6
DISTRIBUTION_ATTRIBUTE7
DISTRIBUTION_ATTRIBUTE8
DISTRIBUTION_ATTRIBUTE9
DISTRIBUTION_ATTRIBUTE10
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
USSGL_TRANSACTION_CODE
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
Using the Integration Module
PO_REQUISITIONS_INTERFACE MOUT_PR_INTERFACE
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
AP_EXPENSE_REPORT_HEADERS MOUT_AP_INTERFACE
REPORT_HEADER_ID API calculated value
EMPLOYEE_ID
WEEK_END_DATE CHANGEDATE
CREATION_DATE SYSDATE
CREATED_BY MAXIMO1 ID
LAST_UPDATE_DATE TRANSDATE
LAST_UPDATED_BY ENTERBY ID
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
Using the Integration Module
AP_EXPENSE_REPORT_HEADERS MOUT_AP_INTERFACE
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
AP_EXPENSE_REPORT_HEADERS MOUT_AP_INTERFACE
DEFAULT_EXCHANGE_RATE EXCHANGERATE
DEFAULT_EXCHANGE_DATE EXCHANGEDATE
LAST_UPDATE_LOGIN
VOUCHER_NUM
USSGL_TRANSACTION_CODE
USSGL_TRX_CODE_CONTEXT
DOC_CATEGORY_CODE
AP_EXPENSE_REPORT_LINES MOUT_AP_INTERFACE
REPORT_HEADER_ID API calculated value
LAST_UPDATE_DATE CHANGEDATE
LAST_UPDATED_BY ENTERBY ID
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
Using the Integration Module
AP_EXPENSE_REPORT_LINES MOUT_AP_INTERFACE
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
CREATION_DATE SYSDATE
CREATED_BY MAXIMO1 ID
STAT_AMOUNT
USSGL_TRANSACTION_CODE
USSGL_TRX_CODE_CONTEXT
PROJECT_ACCOUNTING_CONTEXT
PROJECT_ID
TASK_ID
EXPENDITURE_ORGANIZATION_ID
EXPENDITURE_TYPE
EXPENDITURE_ITEM_DATE
PA_QUANTITY
463
Chapter 3
AP_EXPENSE_REPORT_LINES MOUT_AP_INTERFACE
DISTRIBUTION_LINE_NUMBER
REFERENCE_1
REFERENCE_2
464
CHAPTER 4
SYSTEM MAINTENANCE
465
Chapter 4
Checking for Errors) in the Installation manual. This manual is available in the
APIDOCS directory.
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.
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.
468
System Maintenance
469
Chapter 4
Parameter Description
Parameter Description
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.
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.
473
Chapter 4
• 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.
476
System Maintenance
477
Chapter 4
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)
479
Chapter 4
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.
480
System Maintenance
481
Chapter 4
482
System Maintenance
483
Chapter 4
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
ORA-20101 ProgramName ORA-ErrorNumber ErrorMessage
ORA-20102 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
486
Notes
487
MPD0741-max411orafn11i-02-ENG-09/2002