Integration Guide Oracle Financials 11i

Release 4.1.1
Copyright 2002, MRO Software, Inc.

1

This document and its publication do not constitute or create a contract. MRO Software, Inc., makes no warranties, express or implied, regarding the accuracy or completeness of this document or of the related program material.
© 2001 MRO Software, Inc. All rights reserved. Contains confidential and trade secret information

of MRO Software, Inc. Use, transfer, disclosure, or copying without MRO Software, Inc.’s express written permission is strictly forbidden. United States Patent No. 6,325,522 B2 Restricted Rights - Use, duplication, and disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 (OCT 1998). Trademarks: MAXIMO®, INTERMAT®, Struxure®, MAXIMO® Enterprise™, MAXIMO® Extended Enterprise™, MAXIMO® for Integrated Supply™, MAXIMO® Scheduler™, MAXIMO® Workflow™, MAXIMO® Analyzer™, MAXIMO® Buyer™, MAXIMO® Fleet Manager™, MAXIMO® Aviation Manager™, MRO Online Commerce ServicesSM, MRO Software Operations CenterSM, Supplier e-Commerce Adapter™, Illustrated Parts Catalog™, Collego™ Catalog Manager™, Standard Modifier Dictionary™, and Autocon™ are trademarks of MRO Software, Inc. Other products and brand names are trademarks or registered trademarks of their respective companies; some are noted below. Third-Party Technology: Certain MRO Software, Inc., products contain technology provided under license from third parties, as noted below: MRO Software Products
MAXIMO All Products

Third-Party Technology Information
Portions © 2000 Brio Technology, Inc. Brio Report Builder™ provided by Brio Technology, Inc. Portions © 1996 Centura Software Corporation. Portions © 1995-2000 Actuate Corporation. 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. Portions © 1989-1998 Cimmetry Systems, Inc. AutoVue™, AutoVue Professional provided by Cimmetry Systems, Inc. Portions © 1998, 1999 NETRONIC Software GmbH. Portions © 1999-2001 Snowbound Software™ Corporation. RasterMaser™ provided by Snowbound Software Corporation. Portions © TAXWARE International, Inc. TAXWARE® VERAZIP™ Sales/User, STEP provided by TAXWARE International, Inc.

AutoVue

MAXIMO Workflow Illustrated Parts Catalog Online Commerce Services

CONTENTS

CHAPTER 1: INTRODUCTION....................................................................................9 Overview...................................................................................................................10 Related Documentation.............................................................................................11 Integration Overview ................................................................................................13 CHAPTER 2: IMPLEMENTING THE SOFTWARE INTEGRATION...................17 Reconfiguring MAXIMO Table Columns ................................................................18 Modifying Integration API Control Codes............................................................19 Oracle Financials Control Codes ..........................................................................35 Customizing Integration Procedures .........................................................................47 CHAPTER 3: USING THE INTEGRATION MODULE ...........................................49 Inventory Ownership.................................................................................................50 Determining Inventory Ownership .......................................................................50 Viewing Inventory Ownership..............................................................................51 Changing Inventory Ownership ............................................................................51 Inventory Balance Transactions................................................................................52 APICTLs for Inventory Balance Transactions......................................................53 Importing and Exporting Inventory Balance Data ................................................56 Summary of Item Balance Transactions Using Default Settings of the APIs .......56 Recommended API Settings for Exchanging Item Balances ................................58 Purchasing Transactions ...........................................................................................61 Purchase Order Ownership ...................................................................................61
APICTLs for PO Ownership ......................................................................................62 Viewing PO Ownership..............................................................................................63 Changing PO Ownership............................................................................................63

3

Contents

Purchasing Configurations....................................................................................64
Comparison of APICTLs for the Configurations........................................................65 Configuration 1 ..........................................................................................................67 APICTL Control Values for Configuration 1 .............................................................68 Configuration 2 ..........................................................................................................69 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

Transferring Item Confirmations to MAXIMO........................................................103 Inventory Ownership with Item Confirmations Sent to MAXIMO..........................103

Vendors...............................................................................................................104
Transferring Vendor Data from Oracle Financials to MAXIMO .............................105

Accounts Payable Data Transfers .......................................................................106
Transferring Invoices from MAXIMO to Oracle Financials ....................................106 Transferring Invoices from Oracle Financials to MAXIMO ....................................107

General Ledger Data Exchanges.........................................................................109
Transferring Journal Entries from MAXIMO to Oracle Financials..........................110 Transferring Entries from INVTRANS to Oracle Financials ...................................112 Transferring Journal Entries from MATRECTRANS to Oracle Financials .............112 Transferring Journal Entries from MATUSETRANS to Oracle Financials .............114 Transferring Entries from SERVRECTRANS to Oracle Financials ........................115 Transferring Entries from LABTRANS to Oracle Financials ..................................116 Transferring Entries from TOOLTRANS to Oracle Financials................................117 Transferring Entries from INVOICETRANS to Oracle Financials ..........................118 Transferring Chart of Accounts Data from Oracle Financials to MAXIMO ............119 GL Synchronization Transformations ......................................................................120 Transferring Accounts from MAXIMO to Oracle Financials...................................120 Transferring Accounts from Oracle Financials to MAXIMO...................................121 MAXIMO Support for the Transformation of the GL Accounts..............................121 Cases Requiring Transformation of GL Accounts....................................................121

MAXIMO Interface Tables.....................................................................................125 Data Columns......................................................................................................125 User Columns......................................................................................................126 Batch Control Columns.......................................................................................126 The User Control Column...................................................................................126 Interface Control Columns..................................................................................127 Status Columns ...................................................................................................128 Error Messages........................................................................................................129 Purchasing Interface Tables ....................................................................................130 MOUT_PR_INTERFACE Table ........................................................................130 MAX_PRX_INTERFACE Table........................................................................142 MAX_PO_INTERFACE Table ..........................................................................152 MAX_POX_INTERFACE Table .......................................................................161 MAX_RCV_INTERFACE Table .......................................................................163 MOUT_PO_INTERFACE Table........................................................................175 MOUT_RCV_INTERFACE Table.....................................................................186

5

Contents

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

6

Contents

CHAPTER 4: SYSTEM MAINTENANCE ................................................................465 Configuring the Database........................................................................................465 Customizing the Integration APIS ..........................................................................466 Using UTRANSTYPE Values with User Exit Procedures .................................467 Using Extra Tables in User Exits ........................................................................467 Using Batch Routines..............................................................................................468 The Batch Routine Process .................................................................................472 Maintaining the Batch Files ................................................................................473 Maintaining the Interface Tables ............................................................................474 Purging the Interface Tables ...............................................................................474 Running Reports .................................................................................................475 Troubleshooting ......................................................................................................476 General Troubleshooting Procedures ..................................................................476 MAXIMO Interface Log.....................................................................................477 Checking Status Columns ...................................................................................478 Debugging Errors Using MAXIMO Interface Flow ...........................................478 Error Messages....................................................................................................480
Transferring Purchase Requisition Changes into MAXIMO....................................480 Transferring Purchase Orders into MAXIMO..........................................................480 Transferring Purchase Order Changes into MAXIMO.............................................481 Transferring Receipts into MAXIMO ......................................................................481

Transferring Invoices into MAXIMO .................................................................482 Oracle Errors.......................................................................................................485

7

Contents

8

CHAPTER 1 INTRODUCTION

This manual provides information about the MAXIMO financial application integration module. Use this integration module to exchange information between Oracle Financials and MAXIMO. This manual is intended for the following audience:
• • •

System administrators Implementation team members MAXIMO users

MAXIMO and Oracle Financials users include people having many types of jobs, including:
• • • • • • •

Project manager Maintenance manager Accountant Industrial engineer Inventory manager Purchasing manager MIS specialist

9

Describes the system changes you need to make in order to integrate MAXIMO and Oracle Financials. Introduction Description Provides an overview of the MAXIMO financial application integration module. Explains how to use the integration APIs in an integrated system. Implementing the Software Integration 3. System Maintenance There is a separate installation manual that provides information on your system requirements. describes the interface tables. run batch routines. Describes how to maintain the interface tables. 2. preparatory procedures for a successful installation. and troubleshoot the system. described below: Chapter 1. Details error messages and error resolutions. 10 . and installation instructions. Using the Integration Module 4.Chapter 1 Overview The information in this manual is presented in four sections. and provides the mappings between MAXIMO database tables and the integration module interface tables.

For more information about using MAXIMO. • • • You will also need the relevant manuals for Oracle Financials. Therefore. Through its application programming interfaces (APIs). refer to the following sources: • The MAXIMO User’s Manual describes how to use the MAXIMO maintenance system features. this integration module facilitates access to MAXIMO data and application functions. By using the MAXIMO Oracle Financials integration module. 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. 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.DOC in the APIDOC directory.Introduction Related Documentation For a list of verification procedures to follow after you install the integration module. You can mix and match the documented integration points within the limitations of Oracle Financials. please note that the standard 11 . the APIs improve the efficiency of specific business functions performed by MAXIMO customers. It also gives instructions for setting up general ledger accounting features within MAXIMO. see the file GENVERIF. Processes and transactions are described from both a user perspective and a database management perspective. The standard MAXIMO APIs are transparent to users and designed for flexibility. you can create an integrated system in which MAXIMO interfaces with Oracle Financials. 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. However.

12 . The integration module processes are modeled after those in MAXIMO. the module is synchronized with MAXIMO when MAXIMO is updated. as well as the location of the data in each system. The integration module tracks events that cause data to be transferred between systems. you maintain it in only one application. Thus.Chapter 1 MAXIMO APIs provide only the documented integration points. By eliminating duplicate functions and processes. Although a copy of the information is stored in both applications. and not unlimited integration points. the integration module ensures users maximum efficiency. The integration module manages the MAXIMO internal functions to ensure that transfers occur smoothly and consistently.

Furthermore. The APIs will. reduce the integration development life cycle for the customer as well as expedite future MAXIMO upgrades.Introduction Integration Overview As shown below. 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. the APIs work “behind the scenes.” so that MAXIMO and Oracle Financials work together seamlessly. which extract data from the financial system and import data into the financial system from MAXIMO Oracle Financials MAXIMO MAXIMO API Integration Oracle Applications API Oracle Applications • • • The Oracle Financials integration API is an extension of the standard MAXIMO API and is developed and supported jointly by MRO Software. which passes and validates the data between the two APIs Oracle Financials APIs. however. and Oracle. Inc. you can both coordinate processes and exchange information between MAXIMO and Oracle Financials. Business practices will vary from site to site as will the complexity of the integration. The integration module keeps track of events that will 13 . Using the MAXIMO integration APIs. MRO Software is responsible for the MAXIMO API and integration components while Oracle is responsible for support and changes to the external system API Installation and upgrade of the Oracle Financials API will still require integration work. • • The MAXIMO application The MAXIMO APIs. there are five components in an integration between MAXIMO and Oracle Financials.

MAXIMO sends processed data to the destination application. The purchase requisition information is placed in an interface table. The integration APIs move data from the source application to the destination application by way of interface tables. or both. The data usually has completed its processing in Oracle Financials before being passed to the destination. MAXIMO receives data from the source application. • For example. storage. You can send an approved purchase requisition from MAXIMO to Oracle Financials so that a purchase order can be generated in Oracle Financials. for the item originally requested in MAXIMO. for further processing. When the purchase order is approved. the information can be sent to MAXIMO via an interface table. MAXIMO provides the interface tables.Chapter 1 cause data to be transferred between systems and where data is located in the systems. The MAXIMO integration APIs transfer inbound and outbound data between applications. 14 . which store the data and any related processing information. • As a destination application. or both. for processing. Oracle Financials. can be sent back to MAXIMO using another interface table. it generates a receipt record. It also manages the MAXIMO internal functions to ensure that transfers occur smoothly and consistently. The receipt information. When Oracle Financials receives the item. Oracle Financials. An integration API sends the information from the interface table to Oracle Financials. storage. As a source application. you can coordinate the purchasing process between MAXIMO and Oracle Financials. The purchase order is generated in Oracle Financials.

see Chapter 3. “Using the Integration Module.” MAXIMO and Oracle Financials can share several types of information.Introduction The following diagram illustrates this exchange of purchasing information. In the integrated system. see Chapter 3.” 15 . MAXIMO Oracle Financials Approved Requisition MAXIMO MOUT_PR_INTERFACE Table MOUT_PO_INTERFACE Table MOUT_RCV_INTERFACE Table PO_REQUISITIONS_INTERFACE Table Approved Purchase Order Oracle Financials Receipt For more information about transferring data between applications and the interface tables. “Using the Integration Module. 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.

Chapter 1 16 .

In this case. You should make these changes after installing the integration APIs. especially those that affect multiple departments. You must decide how to match the following information shared by the two applications: • • • • • financial calendars currencies tax rates units of measure user names You do not have to match these settings if you are going to maintain the data separately in the two applications. The system or database administrator should also be part of the team. you will manually add the information to each application. The integration team should include individuals that have an understanding of the technical and functional capabilities of both MAXIMO and Oracle Financials. 17 . Implementing the integration of MAXIMO and Oracle Financials consists of evaluating your integration requirements in each of several areas shared between the products. At least one member of the team should be familiar with your organization’s business processes.CHAPTER 2 IMPLEMENTING THE SOFTWARE INTEGRATION This section describes the system changes necessary to integrate MAXIMO and Oracle Financials. and choosing the implementation method that best suits your needs. Your choices affect how the two applications will share certain information.

You may reconfigure the columns either before or after data transactions have occurred. If you will be using the software integration via batch routines.sql file to see the fields that the adapter configures during installation. Compare the MAXIMO tables to the tables in Oracle Financials. depending on whether you process transactions in real time or in batches. the transactions will fail. For example. You can look in the oramaxcf. nulls setting. table and column mapping must be synchronized first. if Oracle Financials defines currency in terms of the British pound and MAXIMO is configured to use the U. use the MAXIMO Database Configuration application to reconfigure the length. and you do not reconfigure the table columns. then you can later use an external process to transform the data to a compatible format.S. Reconfiguring MAXIMO Table Columns You must reconfigure MAXIMO columns to be compatible with Oracle Financials. you must decide how to make the settings compatible.Chapter 2 If the two applications will share data. data type. 18 . dollar. Do this before selecting Configure Changes from the Actions option of the Database Configuration Application. The integration does not include a method for matching settings. For example. If you will be using the software integration in real-time (data transactions will occur in real-time.maxconf COMPANIES COMPANY 46 If the installation has decreased the length of any of your MAXIMO table columns. not in batch routines). start &&md. Otherwise. you must decide which currency definition to use and make it the consistent definition for both applications. Any columns containing data shared between MAXIMO and the financial application must be compatible with respect to these attributes: column length. the following statement in that file sets the COMPANY column in the COMPANIES record to a length of 46 characters.

Most of the API control codes switch the API on or off. You can further modify some integration APIs with the API controls. Refer to the following table for a complete list of external API control codes that are installed with Oracle Financials API. set the code to N. The control code settings regulate data transfers between MAXIMO and Oracle Financials. PROLDSTAT indicates the status that a purchase requisition must be in prior to changing status. Use PROLDSTAT and PRNEWSTAT control codes to specify the status of purchase requisitions pending transfers.Implementing the Software Integration Modifying Integration API Control Codes You can modify the integration API control codes and the Oracle Financials control codes to configure the integration module for your system needs. the following control codes will further qualify the incoming data: APINADJINV APINADJDIRECT APINUPDTVND APINAUTORCV Adjusts inventory cost if there is variance. PRNEWSTAT indicates the purchase requisition status that triggers the data transfer. To stop that transfer. To stop the transfer of item data from MAXIMO to Oracle Financials. the item data is entered into MAXIMO. Allows invoicing of services not yet received by automatically recording receipt during invoicing. Updates vendor’s unit price. If the control code for ITMIN is Y and if a new item is inserted into Oracle Financials. For example. Not all API control codes are on/off switches. As discussed at the beginning of Chapter 3. there are two purchasing Configurations: 19 . providing that the prior status is PROLDSTAT. you can do more than turn invoice transfers on or off with APIN and/or APOUT. Use the GLDELIMITER control code to specify the general ledger account segment delimiter used in Oracle Financials. For example. if you do not want to synchronize item data between MAXIMO and Oracle Financials. set the ITMIN or ITMOUT controls to N. The delimiter is a hyphen (-) by default. If invoice data is being transferred in. set the control code for ITMOUT to N. Adjusts direct cost if there is variance.

The middle column in the following table indicates whether the APICTL for that row has any impact on Oracle Financials. For example. the control value in Configuration 2 must be the opposite of the default control value in Configuration 1.” The default values column shows the values as they are when the external APIs are installed. COMOUT is set to ‘N’. API Control Group Control Applicable for Control the Oracle Value Financials API? Default Y Y Description APICTL COA Receive chart of accounts and account segment data from Oracle Financials to MAXIMO. N for Configuration 2. For example. since Oracle Financials will not accept updates for companies/vendors from MAXIMO. This GL delimiter is used as a placeholder identifier for GL processing (and replaced with the GL delimiter specified in MAXIMO if the delimiter is to be stored in the database). the cell in the Control Value column reads “Y for Configuration 1. For some controls. the value for APIN is Y under Configuration 1. for APICTL. GL account segment delimiter for GL data coming from an Oracle Financials.Chapter 2 Configuration 1 and Configuration 2. Thus. but N under Configuration 2. APICTL GLDELIMITER Y - 20 .

Global switch. Send non-stocked item from MAXIMO to Oracle Financials. Send item catalog data from MAXIMO to Oracle Financials. Receive item catalog data from Oracle Financials to MAXIMO. Send item without storeroom information from MAXIMO to Oracle Financials. APICTL COMOUT N Y APICTL ITMCATIN Y Y APICTL ITMCATOUT Y Y APICTL ITMNOSTORE Y Y APICTL STOCKITEM Y Y APICTL NONSTOCKITEM Y Y APICTL SPITEM Y Y 21 .Implementing the Software Integration API Control Group Control Applicable for Control the Oracle Value Financials API? Default Y Y Description APICTL COMIN Receive companies data from Oracle Financials to MAXIMO. Send companies data from MAXIMO to Oracle Financials. Send special order item from MAXIMO to Oracle Financials. Send stocked item from MAXIMO to Oracle Financials.

Send item store data from MAXIMO to Oracle Financials. When Y. Receive item manufacturer data from Oracle Financials to MAXIMO. Receive item vendor data from Oracle Financials to MAXIMO. APICTL ITMSTOREOUT Y Y APICTL ITMMFGIN N Y APICTL ITMMFGOUT N Y APICTL ITMVNDIN Y Y APICTL ITMVNDOUT N Y APICTL ITMBALXFROUT N N 22 . Send item vendor data from MAXIMO to Oracle Financials.Chapter 2 API Control Group Control Applicable for Control the Oracle Value Financials API? Default Y Y Description APICTL ITMSTOREIN Receive item store data from Oracle Financials to MAXIMO. send item balance data from MAXIMO to Oracle Financials for MAXIMOowned inventory only. Send item manufacturer data from MAXIMO to Oracle Financials.

allow issues for externally-owned inventory to be sent to Oracle Financials. APICTL EXTRCVOUT Y N APICTL EXTISSOUT N N APICTL MAXRCVIN Y N APICTL MAXISSIN Y N 23 . When Y. allow receipts for MAXIMO-owned inventory to be received into MAXIMO.Implementing the Software Integration API Control Group Control Applicable for Control the Oracle Value Financials API? Default Y N Description APICTL ITMBALXFRIN When Y. When Y. When Y. allow Issues for MAXIMO-owned inventory to be received into MAXIMO. When Y. receive item balance data from Oracle Financials to MAXIMO for externally-owned inventory only. allow receipts for externally-owned inventory to be sent to Oracle Financials.

bypass the inventory balance and cost updates associated with an issue transaction for externally owned inventory coming into MAXIMO. Receive material issue data from Oracle Financials to MAXIMO. all updates occur. When Y.When Y. When N. Send item usage journal data from MAXIMO to Oracle Financials. all updates occur. bypass the inventory balance and cost updates associated with a receipt transaction for externally owned inventory coming into MAXIMO. APICTL ISSIBUPD Y Y APICTL ISUIN Y Y APICTL JESERVREC Y Y APICTL JEMATUSE Y Y 24 . Send service receipt journal data from MAXIMO to Oracle Financials.Chapter 2 API Control Group Control Applicable for Control the Oracle Value Financials API? Default Y Y Description APICTL RCVIBUPD When N.

Send invoice journal data from MAXIMO to Oracle Financials. Send item receipt journal data from MAXIMO to Oracle Financials for a receipt against a MAXIMO-owned PO. APICTL JEMATREC Y Y APICTL EJEMATREC Y Y APICTL JETOOL Y Y APICTL JEINVOICE Y Y APICTL JEINVENTORY Y Y 25 . Send inventory journal data from MAXIMO to Oracle Financials. Send tool journal data from MAXIMO to Oracle Financials. Send item receipt journal data from MAXIMO to Oracle Financials for a receipt against an Oracle-owned PO.Implementing the Software Integration API Control Group Control Applicable for Control the Oracle Value Financials API? Default Y Y Description APICTL JELABOR Send labor journal data from MAXIMO to Oracle Financials.

Update vendor last cost (when required) for invoice data received by MAXIMO from Oracle Financials.Chapter 2 API Control Group Control Applicable for Control the Oracle Value Financials API? Default Y Description APICTL APIN Y for Receive invoice Config 1 data from Oracle Financials to N for MAXIMO (invoice Config 2 details with variance precalculated. Close PO on full invoice (when required) for invoice data received by MAXIMO from Oracle Financials. Adjust direct cost (when required) for invoice data received by MAXIMO from Oracle Financials. APICTL APINADJINV Y APICTL APINADJDIRECT Y Y APICTL APINCLOSEPO N Y APICTL APINUPDTVND Y Y 26 . Global switch Y Adjust inventory cost (when required) for invoice data received by MAXIMO from Oracle Financials.

APICTL APOUT Y N for Send invoice data Config 1 from MAXIMO to Oracle Financials. N for Config 2 Global switch. When set to N. Auto receipt is for service receipt only (as in the MAXIMO application). If invoice status is equal or greater than control value and not previously sent. only invoice summary information will be sent. Y for Config 2 Y Send invoice detail data from MAXIMO to Oracle Financials. APICTL APDETAILS Y APICTL APSTART Y APPR APICTL PROUT Y Y for Send PR data from Config 1 MAXIMO to Oracle Financials.Implementing the Software Integration API Control Group Control Applicable for Control the Oracle Value Financials API? Default N Y Description APICTL APINAUTORCV Auto receipt on invoice (when required) for invoice data received by MAXIMO from Oracle Financials. invoice will be sent to Oracle Financials. 27 .

Send service PR data from MAXIMO to Oracle Financials. APICTL PRSERV Y N APICTL PRXIN Y Y for Receive PR status Config 1 updates from Oracle Financials to N for Config 2 MAXIMO.Chapter 2 API Control Group Control Applicable for Control the Oracle Value Financials API? Default Y N Description APICTL PRINT Send internal PR data from MAXIMO to Oracle Financials. N Send PO data from MAXIMO to Oracle Financials. adjust inventory cost (when required) for receipt data received by MAXIMO. APICTL RCVINADJINV N 28 . from Oracle Financials. Y for Receive PO data Config 1 from Oracle Financials to N for Config 2 MAXIMO. APICTL POIN Y APICTL POOUT Y APICTL RCVIN Y Y for Receive receipt Config 1 data from Oracle Financials to N for MAXIMO. Config 2 (Y) Regardless of control value.

APICTL RCVINCLOSEPO Y (Y) APICTL RCVINUPDTVND N (Y) APICTL RCVOUT Y Y for Send receipt data Config 1 from MAXIMO to Oracle Financials. from Oracle Financials. update vendor last cost (when required) for receipt data received by MAXIMO.Implementing the Software Integration API Control Group Control Applicable for Control the Oracle Value Financials API? Default (Y) Description APICTL RCVINADJDIREC N T Regardless of control value. from Oracle Financials. Regardless of control value. adjust direct cost (when required) for receipt data received by MAXIMO. from Oracle Financials. N for Config 2 N Replace MAXIMO item number with “MAXITEM. close PO on full receipt (when required) for receipt data received by MAXIMO. Regardless of control value.” the MAXIMO generic value for requisitioned items. APICTL PRGENITEM Y 29 .

this prevents the Pay On Receipt update from occurring (regardless of the setting on the PO). When Y. When Y. receive work order status updates from Oracle Financials to MAXIMO. To allow payment on receipt to occur. When work order status is equal to or beyond the status in the control value. When set to N. set the control to Y. send work order data to Oracle Financials. work order data is sent from MAXIMO to Oracle Financials.Chapter 2 API Control Group Control Applicable for Control the Oracle Value Financials API? Default Y Y Description APICTL RCVSVCAPPR Update Service Receipts on a PO to be approved at the time of receipt. APICTL PAYONRCPT Y N APICTL WOOUT N N APICTL WOSTART N APPR APICTL WOXIN N N 30 .

send work order labor pay data to Oracle Financials from MAXIMO. APICTL RSVOUT Y N APICTL SRVIN N N APICTL LPYOUT N N APICTL ICFIN Y N 31 . receive reservation confirmation/updat e from Oracle Financials to MAXIMO. receive work order service receipts from Oracle Financials to MAXIMO. When Y. send material reservations for externally owned inventory to Oracle Financials from MAXIMO. When Y. When Y. a change to the work order status in MAXIMO to Unapprove (WAPPR) will not be allowed when work order actuals exists.Implementing the Software Integration API Control Group Control Applicable for Control the Oracle Value Financials API? Default Y Description APICTL WOUNAPPACTUA N LS When N. When Y.

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

APICTL ISUOUT N Y APICTL WOIN N N APICTL LPYIN N Y APICTL PRIN N N APICTL GLUPDATE N Y APICTL SYSTEMOUT N N 33 . accept Labor Pay transactions from Oracle Financials into MAXIMO. When Y. send receipts from MAXIMO to Oracle for a receipt against an Oracleowned PO. Send Material Issues from MAXIMO to Oracle Financials. send systems from MAXIMO to Oracle Financials.Implementing the Software Integration API Control Group Control Applicable for Control the Oracle Value Financials API? Default Y Y Description APICTL ERCVOUT When Y. When Y. allow online changes to the WO GL account after the WO has been sent to the external system (WOOUT = Y). When Y. When Y. accept work orders from Oracle Financials to MAXIMO. accept Purchase Requisitions from Oracle Financials into MAXIMO. When Y.

Chapter 2 API Control Group Control Applicable for Control the Oracle Value Financials API? Default N N Description APICTL SYSTEMIN When Y. When Y. receive systems from Oracle Financials to MAXIMO. insert to MAX_API_TRAN S for outbound interface transactions defined in the API. Journal Receipt Journal Inventory Adjustment Journal Direct Adjustment APICTL APITRANS N N APICTL RCVINGL APICTL RCVINGLINV Y Y Y Y Y N N Y N Y APICTL RCVINGLDIRECT Y APICTL APINGL APICTL APINVARGL APICTL APINGLINV APICTL APINGLDIRECT APICTL JESPLITDBCR Y Y Y Y Y API Control Group APICTL Control Applicable to Oracle Projects? Y Control Value Default Y Description FCIN Financial Control to MAXIMO Projects from MAXIMO Tasks from MAXIMO APICTL APICTL PROJECTOUT TASKOUT Y Y Y Y 34 .

Replace the 35 . However.GLCOAID. For more information about how the data is transferred. Choose APICTL from the value list to access the control codes.GLSOBID. “Using the Integration Module. Some Oracle Financials control codes may turn the APIs on or off based upon qualifiers that are unique to Oracle Financials. data passing from MAXIMO to Oracle Financials may need a unique ID for each set of books. The MAXIMO Chart of Accounts application supports only one Chart of Accounts ID from Oracle Financials.SP to support multiple sets of books. the Set of Books ID is the value in OFCTL.Implementing the Software Integration APICTL APICTL APICTL ACTUALSOUT LCIN BUDGETOUT Y Y Y Y Y Y Project Actuals from MAXIMO Labor to MAXIMO Budget from MAXIMO Use MAXIMO Application Setup to change the control code values. For more information about using the MAXIMO Application Setup application.” Oracle Financials Control Codes The Oracle Financials control codes modify the integration APIs between MAXIMO and Oracle Financials. and for invoices transferred to the tables AP_EXPENSE_REPORT_HEADERS and AP_EXPENSE_REPORT_LINES. if each set of books has the same Chart of Accounts ID. for journal transactions to the GL_INTERFACE table. see Chapter 3. but MAXIMO only supports one set of books. In contrast.SP and OAPX. Thus. MAXIMO accepts code combinations for multiple sets of books. Many of the Oracle Financials control codes either further control the behavior of the APIs or provide defaults specific to Oracle Financials that are not available in MAXIMO. by default. The APIs filter code combination values coming from Oracle Financials to MAXIMO according to the value set in the value list OFCTL. refer to the MAXIMO System Administrator’s Guide. However. you can write your own user exits in OGLX.

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

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

Refer to the following table for a list of the integration API control codes. purchase order line numbers in MAXIMO are also made on concatenated values. their descriptions. Refer to the mapping for further details. and default settings. the identifier (PONUM in MAXIMO) consists of the blanket PO number concatenated with the release number. Oracle Financials Control Group OFCTL OFCTL OFCTL OFCTL OFCTL OFCTL Control Control Value Description GLSOBID GLSOBID2 GLCOAID GLCURNCY GLCURNCYTYPE GLRCVECUMBID 0 0 0 USD User 0 Set of Books ID Reporting Set of Books ID Chart of Accounts ID Default currency code Currency conversion type Receipt encumbrance type ID. Thus. for release purchase orders sent from Oracle Financials to MAXIMO. Similarly. This is the internal ID for the encumbrance type code used for purchase order encumbrance 38 .Chapter 2 Vendor APIs between MAXIMO and Oracle Financials implement additional logic to compensate for differences between the two systems. any release PO has a different identifier than the originating blanket PO. In Oracle Financials. The Vendor code in MAXIMO is a concatenated value consisting of VENDOR_SEGMENT1 and VENDOR_SITE_CODE.

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

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

Implementing the Software Integration Oracle Financials Control Group OFCTL Control Control Value Description JEITMISSRET MAXIMO1 Journal category for item usage returns Journal category for item usage (transfers) Journal category for inventory average cost adjustments Journal category for inventory capital cost adjustments Journal category for inventory current balance adjustments Journal category for inventory standard cost adjustments Journal category for inventory standard receipt adjustments Journal category for labor (work) reporting Journal category for labor (nonwork) reporting OFCTL JEITMISSTRANS MAXIMO1 OFCTL JEITMAVGADJ MAXIMO1 OFCTL JEITMCAPADJ MAXIMO1 OFCTL JEITMBALADJ MAXIMO1 OFCTL JEITMSTDADJ MAXIMO1 OFCTL JEITMRECADJ MAXIMO1 OFCTL JELABWORK MAXIMO1 OFCTL JELABNWORK MAXIMO1 41 .

Chapter 2 Oracle Financials Control Group OFCTL Control Control Value Description JESERVREC MAXIMO1 Journal category for service receipts (commitment/ encumbrance) Journal category for invoice currency variances Journal category for invoice variances Journal category for invoice TAX 1 type transactions Journal category for invoice TAX 2 type transactions Journal category for invoice TAX 3 type transactions Journal category for invoice TAX 4 type transactions Journal category for invoice TAX 5 type transactions Journal category for invoice payables OFCTL JEINVCCVAR MAXIMO1 OFCTL JEINVCIVAR MAXIMO1 OFCTL JEINVCTAX1 MAXIMO1 OFCTL JEINVCTAX2 MAXIMO1 OFCTL JEINVCTAX3 MAXIMO1 OFCTL JEINVCTAX4 MAXIMO1 OFCTL JEINVCTAX5 MAXIMO1 OFCTL JEINVOICE MAXIMO1 42 .

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

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

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

Chapter 2 Oracle Projects Control Group OFCTL OFCTL OFCTL OFCTL OFCTL OFCTL OFCTL OFCTL Control Control Value Description CONVHRS PROJAPPR PROJCOMP PROJCLOS PROJPR PROJPO PROJAP WOHEIRVAL 2080 APPROVED PENDING_C LOSE CLOSED No No No No Annual Converted to Hourly Rate Proj Status for WO Appr Proj Status for WO COMP Proj Status for WO CLOSE Send Projects Data on PR Send Projects Data on PO Send Projects Data on AP Validate FC/WO Heirarchies Use the MAXIMO Application Setup application to change the control code values. Choose OFCTL from the value list to access the control codes. For more information about how the data is transferred.” 46 . see Chapter 3. For more information about using the MAXIMO Application Setup application. refer to the MAXIMO System Administrator’s Guide. “Using the Integration Module.

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

Chapter 2 48 .

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

The system administrator must set user-level security for anyone who needs to process transactions for that storeroom in MAXIMO. MAXIMO does not automatically grant user access to that storeroom. Oracle owned inventory is created in MAXIMO by the Integration Gateway. which is defined by the combination of an item and its location. inventory created via the integration module is owned by your Oracle Financials system and inventory created by a MAXIMO table in MAXIMO contains the column INVOWNER.Chapter 3 NOTE: If a storeroom location in MAXIMO is created by an API (rather than by MAXIMO). As explained above. • MAXIMO owned inventory is inventory that is created in MAXIMO by a MAXIMO application.0 as MAXIMO owned. • Determining Inventory Ownership The APIs determine the inventory ownership by identifying how the inventory was created in MAXIMO. the inventory is treated in all transactions as though it is MAXIMO owned. WARNING: The integration module treats all inventory records that were created in versions of MAXIMO before Release 4. If the value is anything other than E. This security is set in the usual manner in theMAXIMO Signature Security application. The value in the INVOWNER column is set to E (external) for an inventory record that the integration module creates. determines the direction of the data flow for inventory balance and cost transactions. 50 . Inventory Ownership The inventory ownership.

Using the Integration Module Viewing Inventory Ownership To view the owners of your inventory data. perform the following query using SQL*Plus or any other SQL language: Select INVOWNER from INVENTORY where ITEMNUM = ‘your item number’ and LOCATION = ‘your storeroom location’. enter the following SQL statement: Update INVENTORY Set INVOWNER = ‘E’ (for Oracle owned. Commit. use any other value for MAXIMO owned) Where ITEMNUM = ‘your item number’ and LOCATION = ‘your storeroom location’. the APIs treat the associated item number as MAXIMO owned. • Changing Inventory Ownership To change the owner of the inventory. including NULL values and spaces. When INVOWNER is set to any value other than E. 51 . Items with INVOWNER ≠ E are treated as MAXIMO owned inventory by the APIs. Query results: • Items with INVOWNER = E are treated as Oracle owned inventory by the APIs.

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

the APIs provide capabilities for receipt and issue transactions on the system that does not own the inventory. Also creates the location in MAXIMO if it doesn’t exist. Value ITMSTOREIN ITMSTOREOUT ITMBALXFRIN Default Y Y N Description Adds item to a location in MAXIMO. 53 . it imports item balances and cost updates for Oracle owned inventory. The table below shows the default settings for the API controls associated with inventory transactions. Allows MAXIMO to import item balances for Oracle owned inventory. when the inventory balances are updated in Oracle. the application that is the owner of the inventory performs all transactions (including receipts and issues) that affect the balances of that inventory.Using the Integration Module APICTLs for Inventory Balance Transactions Usually. If set to Y. Exports item and storeroom location updates to the Oracle Financials system. However.

it exports item balance and inventory cost updates from MAXIMO for MAXIMO owned inventory. All cost adjustments (both standard and average). 54 . When the value is set to Y. but it will NOT update the Oracle Inventory tables. allows item receipts for Oracle owned inventory to be exported. since the inventory is not MAXIMO owned. Allows item balances of MAXIMO owned inventory to be exported from MAXIMO. EXTRCVOUT N If set to Y when RCVOUT = Y. If you set these switches to Y. and physical count adjustments performed by MAXIMO for Oracle owned inventory cause an API error that you see on the user screen in MAXIMO and cause a database rollback. data will update the MAX_ITM_INTERFACE table. balance adjustments. If set to Y.Chapter 3 Value ITMBALXFROUT Default N Description NOTE: This transaction is not supported by the current integration between MAXIMO and Oracle Inventory. You can override this condition by setting the EXTRCVOUT and EXTISSOUT switches to Y. All receipt and issue transactions performed by MAXIMO for Oracle owned inventory cause a database rollback and an API error that you see on the user screen in MAXIMO. MAXIMO does not send the inventory balance update that occurs as part of the transaction to your Oracle Financials system. MAXIMO completes the transactions and sends them to your Oracle Financials system. However.

allows item issues for MAXIMO owned inventory to be imported. If set to Y when ISUIN = Y. allows item receipts for MAXIMO owned inventory to be imported. performs the inventory balance updates for Oracle owned inventory as part of the issue transaction when the issue transaction is imported into MAXIMO. allows item issues for Oracle owned inventory to be exported. When the value is set to Y. When set to Y. but it will NOT update the Oracle Inventory tables. data will update the MOUT_ISU_INTERFACE table. When set to Y. If set to Y when ISSOUT = Y. performs the inventory balance updates for Oracle owned inventory as part of the receipt transaction when the receipt is imported into MAXIMO. ISSIBUPD N 55 . MAXRCVIN MAXISSIN RCVIBUPD Y Y N If set to Y when RCVIN = Y.Using the Integration Module Value EXTISSOUT Default N Description Note: This transaction is not supported by the current integration between MAXIMO and Oracle Inventory.

Using the Default API settings: • Item storeroom information is exchanged between MAXIMO and your financial system. You also cannot import into MAXIMO any item balance and cost adjustments performed on MAXIMO owned inventory. You cannot transfer item balances. The APIs prevent MAXIMO from completing these transactions and display an error message on the relevant MAXIMO screen.Chapter 3 Importing and Exporting Inventory Balance Data Importing MAXIMO can import balance data only for Oracle owned inventory and only when the ITMBALXFRIN and ITMSTOREIN controls are set to Y. The APIs hold these transactions in the MAX_ITM_INTERFACE table and display an error in that table’s IMPORTSTATUS column. MAXIMO can export balance data only for MAXIMO owned inventory and only when the ITMBALXFROUT and ITMSTOREOUT controls are set to Y. • • 56 . Exporting Summary of Item Balance Transactions Using Default Settings of the APIs The information below summarizes how the APIs transfer item balance data when the default API settings are in place. Note: Sending balance transactions from MAXIMO to Oracle Inventory is not supported by the current integration. MAXIMO creates locations in its applications if they don’t already exist. You cannot perform item balance and cost adjustments on Oracle owned inventory in any MAXIMO application. You can modify this activity by using the ITMSTOREIN and ITMSTOREOUT controls. You can modify this activity by using the ITMBALXFROUT(not currently supported) and ITMBALXFRIN controls.

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

) Y (For Spot Buys) N N/A Y Y Y ITMCATOUT ISUIN ISUOUT JEINVENTORY JEMATUSE B/O B/O B B/O B/O N/A Y N/A N N 58 . APICTL Applicable to: (B) MAXIMO (O) Oracle Financials (B/O) Both Not in Oracle Financials System In Oracle Financials System View is in MAXIMO MAXIMOowned MAXIMOowned Oracleowned ITMCATIN B/O Y (Optional – for standardized or centralized part numbers. i.) N N N/A N Y Y (For standardized or centralized part numbers.Chapter 3 We make this feature available because balance transfers to MAXIMO of Oracle owned items usually follow receipt and issue transactions and overwrite the inventory balances in MAXIMO. Recommended API Settings for Exchanging Item Balances We recommend the following settings for the APICTL control switches when you want to exchange item balance information between MAXIMO and your Oracle Financials system.. NOTE: You can choose to send information one way only.e. send only Oracle owned inventory to MAXIMO or send only MAXIMO owned inventory to your Oracle Financials system.

The APIs prevent these transactions from being completed and display an error message on the relevant MAXIMO screen. You cannot use MAXIMO to perform item balance and cost adjustments on Oracle owned inventory. MAXIMO does not import item balance and cost adjustments on MAXIMO • • 59 . the APIs will work as follows: • You can transfer item storeroom information between MAXIMO and your Oracle Financials system.) N/A N/A N/A N/A N/A N/A ICFIN RSVOUT ITMBALXFRIN ITMSTOREIN E E E E N/A N/A N/A N/A Y Y Y Y With these settings. You can control this activity with the ITMBALXFRIN control. You can modify this activity with the ITMSTOREIN and ITMSTOREOUT controls. The APIs will import the item balances of Oracle owned inventory into MAXIMO after your Oracle Financials system inserts them into the MAX_ITM_INTERFACE table.Using the Integration Module APICTL Applicable to: (B) MAXIMO (O) Oracle Financials (B/O) Both MAXIMOowned Not in Oracle Financials System MAXIMOowned In Oracle Financials System Oracleowned View is in MAXIMO ITMBALXFROUT ITMSTOREOUT B B N/A N N/A Y (For centralized inventory visibility. The integration module creates locations in MAXIMO if the locations do not already exist.

See “Inventory Ownership” on page 50 for information on modifying inventory ownership. You can control this activity with the MAXRCVIN and MAXISSIN controls. • If needed. 60 .Chapter 3 owned inventory. You can control this with the EXTRCVOUT control. see the information on the API settings RCVIBUPD and ISSIBUPD. this activity is based on inventory ownership. • If you are using the standard integration control settings. the integration module does not do the usual inventory balance update as part of the item receipt and issue transaction for Oracle owned inventory that is imported into MAXIMO. the table displays an error in the IMPORTSTATUS column. you can import item receipt and issue transactions for MAXIMO owned inventory. the APIs send updates to your Oracle Financials system. you can use MAXIMO to perform item receipt transactions on Oracle owned inventory. which control updates to inventory balances (“APICTLs for Inventory Balance Transactions” on page 53). You cannot control these processes with control switches. This data is stopped in the MAX_ITM_INTERFACE table. If you want to modify this activity. If needed. NOTE: Externally owned inventory costs in MAXIMO may not match costs in Oracle if processes in Oracle Financials affect the costs without sending the transaction information to MAXIMO via the API.

you can exchange purchase requisition data. Several interface tables are used for these transactions. purchase order data. MAXIMO owned purchase orders were created in MAXIMO by a MAXIMO application. and service receipt journal entries.0. and receipt data between the systems. • Since the integration module can both send and receive purchase orders. there can be both MAXIMO and Oracle owned POs in the MAXIMO system at one time. We provide several APICTLs that allow you to control the POs for which you send receipts. Using the APIs.3 of the integration module. Purchase Order Ownership As of Release 4. See “Purchasing Interface Tables” on page 130 for more information on these transactions. material receipt journal entries. purchase orders are considered to be “owned” by the application that creates them: • Oracle owned purchase orders were created in MAXIMO by the Integration Gateway. 61 .Using the Integration Module Purchasing Transactions The APIs provide the interface tables as integration points for purchasing transactions.

0. WARNING: The integration module treats all PO records that were created in versions of MAXIMO before Release 4. “Implementing the Software Integration.3 as MAXIMO owned. ERCVOUT JEMATREC EJMATREC JESERVREC EJSERVREC MATERIAL RECEIPT JOURNAL ENTRIES SERVICE RECEIPT JOURNAL ENTRIES See Chapter 2. Controls sending service receipt journal entries for MAXIMO owned POs. Controls sending receipts for Oracle owned POs.Chapter 3 APICTLs for PO Ownership RCVOUT RECEIPTS Controls sending receipts for MAXIMO owned POs.” for more information on these controls. Controls sending service receipt journal entries for Oracle owned POs. Controls sending material receipt journal entries for MAXIMO owned POs. 62 . Controls sending material receipt journal entries for Oracle owned POs.

use Null for MAXIMO owned) Where PONUM = ‘your PO number’. Commit. enter the following SQL statement: Update PO Set OWNERSYSID = ‘OA’ (‘OA’ for Oracle owned.Using the Integration Module Viewing PO Ownership To view the owners of your purchase order data. 63 . POs with OWNERSYSID = OA are treated as Oracle owned POs by the APIs. Query results: • POs with OWNERSYSID = Null are treated as MAXIMO owned POs by the APIs. • Changing PO Ownership To change the owner of the purchase order. perform the following query using SQL*Plus or any other SQL language: Select OWNERSYSID from PO where PONUM = ‘your purchase order number’.

Related Configuration(s) All Configuration 1 Configuration 1 Configurations 2. Send approved purchase orders from MAXIMO to your financial system. Common purchasing transactions supported by configurations in the integration module are summarized in the following table. 4. Purchasing Transaction Create purchase requisitions in MAXIMO. and 5 Configurations 4 and 5 64 . Several of the transactions apply to more than one configuration. You should review all the APICTLs and their settings. Send purchase requisitions from MAXIMO to your financial system. but you cannot change any of the processes in a configuration. you must match your control settings to those listed. Process receipts in MAXIMO and transfer the receipt data to your financial system. To implement a specific configuration. You can choose not to implement specific processes in the configuration you use. NOTE: Chapter 2 includes a list of all APICTLs and their default settings. Send approved purchase orders from your financial system to MAXIMO. You should evaluate which configuration is the best model of your purchasing management practices. then implement the APIs for it. Each configuration is explained in more detail in the sections following this table.Chapter 3 Purchasing Configurations Purchasing data transactions are supported by five configurations in the Integration Gateway. Each discussion of the configurations lists the primary API control settings for that configuration. Most of the transactions are labeled to specify the configuration to which they apply. as they may affect other processes you use. The configuration processes are supported by a set of API controls.

Send invoice variances from the Oracle Financials system to MAXIMO. Exchange vendor information. See Chapter 2. API Control 1 Setting for Configuration: 2 3 4 5 APIN APOUT PROUT Y N Y Y N N N Y N Y N N N Y N 65 . 2. Note that there are additional APICTL values that affect how the two systems exchange information. and 4 Configurations 3 and 5 All All Configuration 3 Comparison of APICTLs for the Configurations The table below compares some of the most important APICTL settings for each configuration. “Implementing the Software Integration. Generate invoices in the Oracle Financials financial system and transfer the invoice data to MAXIMO. Transfer chart of accounts data from your financial system to the MAXIMO Chart of Accounts application.” for a list of all APICTLs and their default values. Generate invoices in MAXIMO and transfer the invoice data to your financial system. Transfer purchasing-related general ledger journal entries from MAXIMO to your financial system. Related Configuration(s) Configurations 1 and 2 All Configurations 1.Using the Integration Module Purchasing Transaction Process receipts in your financial system and transfer the receipt data to MAXIMO.

Chapter 3 API Control 1 Setting for Configuration: 2 3 4 5 POIN POOUT RCVIN RCVOUT JEMATREC JESERVREC JEINVOICE APDETAILS APINADJINV APINADJDIRECT Y N Y N N N N N Y Y N Y Y N N N N N Y Y N N N N Y Y Y Y/N Y Y N Y N Y N N N N Y Y N Y N Y N N N N Y Y 66 .

• • • • • • 67 . centralized purchasing. Use your purchasing system if you receive items at a central location. and invoicing activities. Generate purchase orders at a central location with your purchasing system and send them to MAXIMO. including variances. MAXIMO will use this data to update inventory and direct costs at the decentralized location. In the first configuration: • Create purchase requisitions with MAXIMO at the decentralized location and send them to your financial system. Send details. of approved/matched invoices from your accounts payable system to MAXIMO for further processing. Exchange vendor information.Using the Integration Module Configuration 1 Configuration 1 supports distributed (decentralized) requisitioning. Receive invoices and process them at a central location using your accounts payable system. Transfer chart of accounts data from your financial system to the MAXIMO Chart of Accounts application. receiving.

However. The controls listed below are the “primary” controls for this configuration. Use Application Setup in MAXIMO to view or change these codes. you should review all the control codes listed in chapter 2 and set them according to the configuration that you implement. you should set your APICTL control code values as shown below.Chapter 3 APICTL Control Values for Configuration 1 If your processes are the same as those described for Configuration 1. Control APIN APOUT PROUT POIN POOUT RCVIN RCVOUT JEMATREC JESERVREC JEINVOICE APDETAILS APINADJINV APINADJDIRECT Control Value Y N Y Y N Y N N N N N Y Y 68 .

Using the Integration Module Configuration 2 Configuration 2 supports distributed requisitioning and purchasing in MAXIMO. Exchange vendor information. Transfer purchasing-related general ledger journal entries from MAXIMO to your financial system. invoicing. Send the invoice summary or detail to MAXIMO after accounts payable processing by the Oracle Financials system. Receive invoices and process them at the centralized location. and centralized receiving. Process receipts at a centralized location. In the second configuration: • • Create and process purchase requisitions in MAXIMO. Transfer chart of accounts data from your financial system to the MAXIMO Chart of Accounts application. and accounts payable activities. • • • • • • 69 . Create purchase orders in MAXIMO send them to the Oracle Financials system.

However. you should set your APICTL control code values as shown below. Use Application Setup in MAXIMO to view or change these codes. you should review all the control codes listed in chapter 2 and set them according to the configuration that you implement. Control APIN APOUT PROUT POIN POOUT RCVIN RCVOUT JEMATREC JESERVREC JEINVOICE APDETAILS APINADJINV APINADJDIRECT Control Value Y N N N Y Y N N N N N Y Y 70 .Chapter 3 APICTL Control Values for Configuration 2 If your processes are the same as those described for Configuration 2. The controls listed below are the “primary” controls for this configuration.

Using the Integration Module Configuration 3 Configuration 3 supports distributed requisitioning. receipts. receiving and inventory management. Exchange vendor information. Send invoice information from MAXIMO to the centralized Accounts Payables system for payment. all done within MAXIMO. purchase orders. In the third configuration: • Use MAXIMO to create and process purchase requisitions. purchasing. • • • 71 . and invoices at a decentralized location. In addition. Send purchasing and inventory-related general ledger journal entries from MAXIMO to your financial system. this configuration supports distributed invoice matching with invoice details sent to your accounts payable system.

Control APIN APOUT PROUT POIN POOUT RCVIN RCVOUT JEMATREC JESERVREC JEINVOICE APDETAILS APINADJINV APINADJDIRECT Control Value N Y N N N N N Y Y Y Y/N Y Y 72 . Use Application Setup in MAXIMO to view or change these codes. The controls listed below are the “primary” controls for this configuration. you should review all the control codes listed in chapter 2 and set them according to the configuration that you implement. you should set your APICTL control code values as shown below. However.Chapter 3 APICTL Control Values for Configuration 3 If your processes are the same as those described for Configuration 1.

Send the invoice summary or detail to MAXIMO after accounts payable processing by the Oracle Financials system.Using the Integration Module Configuration 4 Configuration 4 supports distributed requisitioning. Create purchase orders in MAXIMO and send them to the Oracle Financials system. process receipts in MAXIMO. Transfer purchasing-related general ledger journal entries from MAXIMO to your financial system. Exchange vendor information. • • • • • 73 . In the fourth configuration: • • Create and process purchase requisitions in MAXIMO. and centralized invoicing and accounts payable activities. Transfer chart of accounts data from your financial system to the MAXIMO Chart of Accounts application. and receiving in MAXIMO. Receive invoices and process them at the centralized location. purchasing.

Use Application Setup in MAXIMO to view or change these codes.Chapter 3 APICTL Control Values for Configuration 4 If your processes are the same as those described for Configuration 4. The controls listed below are the “primary” controls for this configuration. you should set your APICTL control code values as shown below. However. Control APIN APOUT PROUT POIN POOUT RCVIN RCVOUT JEMATREC JESERVREC JEINVOICE APDETAILS APINADJINV APINADJDIRECT Control Value Y N N N Y N Y N N N N Y Y 74 . you should review all the control codes listed in chapter 2 and set them according to the configuration that you implement.

purchasing. In the fifth configuration: • • Create and process purchase requisitions in MAXIMO. Exchange vendor information. Transfer purchasing-related general ledger journal entries from MAXIMO to your financial system. and centralized accounts payable activities. Transfer chart of accounts data from your financial system to the MAXIMO Chart of Accounts application. and invoicing in MAXIMO.Using the Integration Module Configuration 5 Configuration 5 supports distributed requisitioning. Create purchase orders in MAXIMO and send them to the Oracle Financials system. Send the invoice summary or detail to MAXIMO after accounts payable processing by the Oracle Financials system. Receive invoices and process them in MAXIMO. • • • • • 75 . process receipts in MAXIMO. receiving.

Control APIN APOUT PROUT POIN POOUT RCVIN RCVOUT JEMATREC JESERVREC JEINVOICE APDETAILS APINADJINV APINADJDIRECT Control Value N Y N N Y N Y N N N N Y Y 76 . Use Application Setup in MAXIMO to view or change these codes. you should set your APICTL control code values as shown below. The controls listed below are the “primary” controls for this configuration. you should review all the control codes listed in chapter 2 and set them according to the configuration that you implement.Chapter 3 APICTL Control Values for Configuration 5 If your processes are the same as those described for Configuration 5. However.

purchasing. you may decide that Configuration 2 most closely matches your business processes. inventory and accounts payables transactions. your RCVOUT setting would differ from the standard Configuration 2 setting.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. 77 . 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. If so. but you need to do some receiving in MAXIMO.

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

The default processes generally are insert followed by update. see “Customizing the Integration APIS” on page 466. All transactions moving from Oracle Financials to MAXIMO have default processes. API Integration Points. If the record already exists. 79 . the API updates it instead. The API’s first action is to insert a record as a new record. the UTRANSTYPE setting overrides the default process for an API. outbound APIs are your APIs that transfer data from the interface tables to Oracle Financials. For more information about the UTRANSTYPE values.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. The API does not delete the record unless the delete code is listed in the UTRANSTYPE column. see “The User Control Column” on page 126. We provide sample external procedures you can customize for your own use. Default Processes. In some cases. and the UTRANSTYPE Control You can specify the integration points you use by setting the value of the UTRANSTYPE user control column of the interface tables. Inbound APIs are your APIs that transfer data from Oracle Financials to the interface tables. For more information on customizing external procedures. Each integration point has a corresponding UTRANSTYPE setting which provides instructions to MAXIMO or Oracle Financials on how to process a record.

The UTRANSTYPE values for each API are listed in each section. materials without item numbers. You can use the integration APIs to: • Transfer purchase requisitions from MAXIMO to Oracle Financials’ purchasing system (Configuration 1). Transfer receipts from Oracle Financials’ purchasing system to MAXIMO (Configuration 1). This column is hidden by default in MAXIMO. Purchasing Data Transfers The two applications can exchange data from purchase requisitions. 80 . Associated purchasing configurations are also indicated. Transfer changes in purchase requisitions from Oracle Financials’ purchasing system to MAXIMO (Configuration 1). The API then places the purchase requisition in the Oracle Financials requisitions interface table. and receipts. the integration API places the purchase requisition in the MAXIMO purchase requisition interface table. Special order items. Transfer purchase orders and changes in purchase orders from Oracle Financials’ purchasing system to MAXIMO (Configuration 1).Chapter 3 API Processing of Shared Information The following sections describe how the integration module APIs process the information shared by MAXIMO and Oracle Financials. and services require a valid purchasing category. Note that PR line items in MAXIMO that have no valid item ID in Oracle Financials need a valid purchasing category in the RLIN1 column. • • • Transferring Purchase Requisitions from MAXIMO to Oracle Financials When the status of a purchase requisition changes to indicate transfer to Oracle Financials. purchase orders.

The API copies relevant purchasing data from these tables: • • • • • PR PRLINE ITEM INVENTORY COMPANIES For more information on customizing user exit procedures. This transaction is generated if APICTL. see “Customizing Integration Procedures” on page 47. Copies relevant company. MOUT_PR_INTERFACE copies the data to the PO_REQUISITIONS_INTERFACE table in Oracle Financials for further processing. 81 . item. Refer to Oracle Applications documentation for further information. All copied to MOUT_PR_INTERFACE table. MXE_USR_PR_SP The Oracle Requisition Import is used to import data into Oracle. see “Customizing the Integration APIS” on page 466.Using the Integration Module User Action Approves PR in MAXIMO. and inventory data. The API does not use any UTRANSTYPE codes for this process. API Action User Exit Copies a composite record consisting MXO_USR_PR_SP of PR header and PR line for each PR line record.PROUT is set to Y. and appropriate API coding. For more information on customizing external integration procedures.

For more information on customizing user exit procedures. you should either cancel the requisition in Oracle Financials or create a duplicate PR in MAXIMO that does not contain the already imported lines. MAXIMO-related data is available from the following MAXIMO tables: • • • • • PR PRLINE ITEM INVENTORY COMPANIES 82 . Thus. Otherwise.Chapter 3 Import errors When an error is detected in the import. No UTRANSTYPE codes are defined. where ‘nnnnnn’ is the request_id in the Purchasing view request ID. before reapproving the PR in MAXIMO. If some of the PR lines were successfully imported to Oracle Financials. then there exists a PR in Oracle Financials with those lines. see “Customizing the Integration APIS” on page 466. Oracle Financials contains two copies of each line that originally imported successfully. the PR status in MAXIMO is reset to WAPPR and the CHANGEBY field in the PR is set to ‘REQnnnnnn’. Check the Requisitions Import Exceptions report. after you import the PR again.

see “Customizing the Integration APIS” on page 466. MAX_PRX_INTERFACE calls User Exit MXI_USR_PRX_SP MAXIMO internal procedures to update the PR status or delete the PR in MAXIMO. The UTRANSTYPE column in the interface table indicates the API process for the purchase requisition change using the following values: D – Delete the purchase requisition.Using the Integration Module Transferring Purchase Requisition Change of Status from Oracle Financials to MAXIMO When the status of a purchase requisition changes in Oracle Financials (for example. User Action Updates PR status or deletes PR in MAX_PRX_INTERFACE table. S – Update the purchase requisition status. This transaction is generated if APICTL. The integration API copies the data and updates the purchase requisition’s status in MAXIMO. 83 .PRIN is set to Y. see “MAXIMO Interface Tables” on page 125. when an error is detected in the requisition import process in Oracle Financials. the error is sent here to update the PR. API Action Oracle’s API calls the MAXIMO partner API stub that writes the received data into MAX_PRX_INTERFACE table. Also. For more information on customizing user exit procedures. it is closed or canceled). Status can be either canceled (CAN) or closed (CLOSE). • • For more information about the UTRANSTYPE column. • X – Follow a user-defined special process. it sends the purchase requisition data to the MAXIMO purchase requisition update interface table.

User Action Approves PO in Oracle Financials. see “Customizing the Integration APIS” on page 466. The integration API then creates all the necessary records for the purchase order in MAXIMO. the internal procedures can also record a new vendor. 84 . Oracle Financials should place a copy of the data in the MAXIMO purchase order interface table. The API does not use any UTRANSTYPE codes for this process. MAX_PO_INTERFACE calls MAXIMO internal procedures to record the PO in MAXIMO. MAX_PO_INTERFACE.Chapter 3 Transferring Purchase Orders from Oracle Financials to MAXIMO To transfer data for a purchase order to MAXIMO. Optionally. API Action Oracle’s API calls the MAXIMO partner API stub that writes the received data into MAX_PO_INTERFACE table. This transaction is generated if APICTL. User Exit / External API MXI_USR_PO_SP MOF_USR_PO_SP Note: This API only provides informational PO data. For more information on customizing user exit procedures.POIN is set to Y. This is part of purchasing Configuration 1. No further PO processing occurs in MAXIMO.

This transaction is generated if APICTL. The UTRANSTYPE column in the interface table indicates the API process for the purchase order change using the following values: D – Delete the purchase order. “Customizing the Integration APIS” on page 466. This is part of purchasing Configuration 1. User Action Updates PO status or deletes PO in MAX_POX_INTERFACE table. it is closed or canceled). For more information on customizing user exit procedures. • • • For more information about the UTRANSTYPE column. The integration API copies the data and updates the purchase order’s status in MAXIMO. MAX_POX_INTERFACE calls User Exit MXI_USR_POX_SP MAXIMO internal procedures to update the PO status or delete the PO in MAXIMO.POIN is set to Y. • X – Follow a user-defined special process. it sends the purchase order data to the MAXIMO purchase order update interface table. S – Update the purchase order status. Status can be either canceled (CAN) or closed (CLOSE). API Action Oracle’s API calls the MAXIMO partner API stub that writes the received data into MAX_POX_INTERFACE table. see “MAXIMO Interface Tables” on page 125. DI – Delete the purchase order for reinsert. 85 .Using the Integration Module Transferring Purchase Order Change of Status from Oracle Financials to MAXIMO When the status of a purchase order changes in Oracle Financials (for example.

This is part of purchasing Configuration 1. set both the Pay On Receipt flag on the purchase order and the APICTL. MAX_RCV_INTERFACE. partner API stub that writes the received data into MAX_RCV_INTERFACE table. regardless of the flag on the purchase order. MAX_RCV_INTERFACE calls MAXIMO internal procedures to record the receipt in MAXIMO. 86 . For more information on customizing user exit procedures. see “Customizing the Integration APIS” on page 466. This transaction is generated if APICTL. User Action API Action User Exit / External API Records receipts in Oracle Oracle’s API calls the MAXIMO Financials. 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.RCVIN is set to Y. The MAXIMO APIs have a feature that automatically generates an invoice for a receipt. MAXIMO does not generate an invoice. To use this feature. MXI_USR_RCV_SP The API does not use any UTRANSTYPE codes for this process. If the APICTL.PAYONRCPT control is not set to Y. The integration API then creates all necessary records for the receipt in MAXIMO.Chapter 3 Transferring Receipts from Oracle Financials to MAXIMO To transfer receipt data to MAXIMO.PAYONRCPT control to Y. Oracle Financials must write the data to the MAXIMO receipt interface table.

User Action Approves PO in MAXIMO (User definable – see chapter 2. The API copies relevant purchasing data from the following MAXIMO tables: • PO • POLINE • ITEM • COMPANIES 87 . and appropriate batch and API coding to MOUT_PO_INTERFACE table.POOUT is set to Y. If you are sending the PO to Oracle. item. Copies a composite record consisting MOF_USR_PO_APP_SP of PO header and PO line for each PO line record and copies relevant company.) API Action User Exit / External API Updates the PO header once it has been sent to the The API generates this transaction if external system. the integration API places a copy of the data in the MAXIMO purchase order interface table. MXE_PO_SP The custom PO Validate and Import process is used to import data into Oracle. MOUT_PO_INTERFACE. APICTL. A PO loaded into Oracle via the API will not reference a PR that exists in Oracle. you should not send the corresponding PR from MAXIMO to Oracle. Refer to the Integration Setup documentation for further information.Using the Integration Module Transferring Purchase Orders from MAXIMO to Oracle Financials To transfer data for a purchase order from MAXIMO to Oracle Financials. and inventory data. MOUT_PO_INTERFACE calls external procedure for further processing.

” You have the option to implement either the CAI PO Interface or the Oracle Standard PO Interface. see Chapter 2. For more information on customizing user exit procedures.5. then the Oracle Standard PO interface is installed. whereas the Standard PO Interface is the Oracle Standard Purchasing Documents Open Interface. If the parameter OFPOApi= 'n'. see “The User Control Column” on page 126. • MPOS – PO record status change.SQL (as described in the Installation guide. The Oracle Standard PO Interface is available with Oracle version 11.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. 88 . The CAI interface is installed by setting the parameters OFPOApi= 'y' in the script SETOFVAR. For more information about the UTRANSTYPE values.3 and greater. The CAI PO interface is provided by Oracle CAI group. “Implementing the Software Integration. • MPOU – MAXIMO updated the PO record.

so the updates can be only done in Oracle. Once the PO is approved in MAXIMO. 89 . but the Releases for Blanket PO’s must be created in Oracle. Blanket POs are created in MAXIMO and imported to Oracle as Approved. Blanket POs are created in MAXIMO and imported to Oracle as Approved. Cancellations must be done in Oracle.Using the Integration Module The table below shows the differences between the CAI PO Interface and the Oracle Standard PO Interface: CAI Interface The concurrent process for importing POs from MAXIMO to Oracle should be created as described in Appendix C of the Installation guide. The PO can be cancelled in MAXIMO and imported to Oracle. the API inserts the records into these tables: PO_HEADERS_INTERFACE_CAI_ALL PO_LINES_INTERFACE_CAI_ALL PO_DISTRIBUTIONS_INTERFACE_CAI_ALL PO_RELEASES_INTERFACE_CAI_ALL The PO updates can be done in MAXIMO and the updates can be imported back to Oracle. It is called “Purchasing Documents Open Interface”. the new API inserts the records into the Oracle standard interface tables: PO_HEADERS_INTERFACE PO_LINES_INTERFACE PO_DISTRIBUTIONS_INTERFA CE The PO updates cannot be done in MAXIMO. You also can create releases for Blanket POs in MAXIMO and import them to Oracle. The PO’s created in MAXIMO are imported into Oracle as Incomplete status and then approved in Oracle system. The POs created in MAXIMO are imported into Oracle as Approved status. Standard PO Interface The standard concurrent process is available. Once the PO is approved in MAXIMO.

API Action User Exit / External API Copies material receipt data and MXO_USR_MATRECTRAN appropriate batch and API coding to S_RCV_SP MOUT_RCV_INTERFACE.ERCVOUT is set to Y.Chapter 3 Transferring Receipts from MAXIMO to Oracle Financials When you enter receipt records in MAXIMO. Copies service receipt data and MXO_USR_SERVRECTRA appropriate batch and API coding to NS_RCV_SP MOUT_RCV_INTERFACE.RCVOUT is set to Y. The API generates these transaction for externally owned POs if APICTL. MOUT_RCV_INTERFACE. This is part of purchasing Configuration 1. the integration API places a copy of the receipt data in the MAXIMO receipt interface table. MXE_RCV_SP The Oracle Receiving Transaction Processor is used to import data into Oracle. Inserts service receipt record in MAXIMO. The API generates these transactions for MAXIMO-owned POs if APICTL. negative receipts (returns/corrections) cannot be sent from MAXIMO to Oracle. NOTE: Due to limitations in the Oracle Receiving interface. MOUT_RCV_INTERFACE calls external procedure for further processing. These must be done in Oracle. Refer to Oracle Applications documentation for further information. 90 . User Action Inserts materials receipt record in MAXIMO.

The API copies relevant purchasing data from these tables: • MATRECTRANS NOTE: When sending receipt transactions to Oracle. 91 . there are no application rules in MAXIMO to prevent it from processing a receipt transaction for inventory that is “owned” by your external system. However. Because of this. be sure the corresponding Journal transactions. See “Item Data Exchanges ” on page 94 for more information on the inventory balance interface and inventory ownership. the APIs do not send receipt transactions for externally owned inventory to an external system unless the API control value setting APICTL. For more information on customizing user exit procedures. see “The User Control Column” on page 126. MATREC – Specifies a material receipt record. Inventory Ownership for Material Receipts Sent to Oracle Financials MAXIMO processes receipt transactions for inventory records that originate in MAXIMO. controlled by JEMATREC and EJEMATREC. For more information about the UTRANSTYPE values.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. are set appropriately so that you do not get duplicate journal entries in Oracle for your receipt transactions.EXTRCVOUT is Y. see chapter 2. The default value for this switch is N.

an error is recorded in the in the MAX_RCV_INTERFACE table. You can add a loaded cost to an item’s cost to account for things like taxes or services. this action sets the item’s loaded cost equal to the item’s line cost plus the service’s line cost (assuming you pro-rate the service cost at 100%). the cost that MAXIMO adds to the work order 92 . not on the line cost.1. Loaded Costs for Material Receipts that are Imported into MAXIMO In MAXIMO Release 4. 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.Chapter 3 Impact of Inventory Ownership on Material Receipts Imported into MAXIMO Usually. it calculates the item’s average based on the loaded cost. To account for this situation. only transactions for externally owned inventory are imported to MAXIMO from Oracle Financials. 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. The loaded cost of the service line is zero (0). If the setting is No. there are no application rules in your external system to prevent a receipt transaction for MAXIMO-owned inventory from being processed there. If the item is a direct issue item to a work order. the MAXIMO APIs do not accept receipt transactions for MAXIMO-owned inventory being sent to MAXIMO unless you set APICTL/MAXRVCIN to Yes.1. You pro-rate the cost of the service to the cost of the item. or invoice line. When you receive the item in MAXIMO. functionality allows you to add a loaded cost to a PO line. Loaded Costs in MAXIMO See the following example of adding a loaded cost to a PO in MAXIMO: In MAXIMO you may enter a PO line for a stocked item and a PO line for a standard service. However. Loaded costs do not affect invoice costs. See “Item Data Exchanges” on page 94 for more details on the inventory balance interface and inventory ownership. PO receipt line. The default setting for the MAXRCVIN switch is Yes.

the APIs use it to recalculate average costs and to update work order costs. set the value of the loaded cost to Null in the appropriate interface table. If the loaded cost is provided. Loaded Cost in the APIs The APIs accept a loaded cost for a transaction if Oracle Financials provides it in the interface table. If you do not wish to add loaded costs to an item or if you do not wish the APIs to accept a loaded cost on a transaction. The APIs do not calculate a loaded cost value. Refer to the on-line MAXIMO documentation for more information on loaded costs. 93 .Using the Integration Module is the loaded cost. Your external system also must provide the rules for adding a loaded cost to the cost of an item in a transaction.

or deletes item(s) in MAXIMO. or delete item data in the MAXIMO Inventory module. update.ITMVNDOUT is set to Y. all item and company data. and thus maintain a consistent view of the data in both systems. Copies item’s vendor/manufacturer data. MXO_USR_ITM_SP 94 . updates. MAX_ITM_INTERFACE copies the data to MTL_SYSTEM_ITEMS_INTERFACE table in Oracle Financials for further processing. API Action User Exit / External API Copies item data with appropriate batch MXO_USR_ITM_SP and API coding to MAX_ITM_INTERFACE table. Transferring Item Data from MAXIMO to Oracle Financials When you insert. MAX_ITM_INTERFACE. or deletes item’s vendor(s) and/or manufacturer(s) in MAXIMO. and appropriate batch and API coding to MAX_ITM_INTERFACE table. User Action Inserts. This transaction is generated if APICTL.Chapter 3 Item Data Exchanges You can use the integration APIs to exchange item data between MAXIMO and Oracle Financials. updates.ITMCAOUT is set to Y. The vendor transaction is generated if APICTL. OR Inserts. the integration API places a copy of the data in the MAXIMO item interface table.

MVU – MAXIMO updates the item’s vendor record. The API uses the following values in the UTRANSTYPE column of the interface tables to determine how to process the change to the manufacturer data: • • • MMI – MAXIMO inserts the item’s manufacturer record. see “The User Control Column” on page 126. For more information on customizing external exit procedures. see “Customizing Integration Procedures” on page 47.Using the Integration Module The API copies relevant purchasing data from these tables: • • • ITEM INVVENDOR COMPANIES The API uses the following values in the UTRANSTYPE column of the interface tables to determine how to process the change to the item data: • • • MII – MAXIMO inserts the item record. MMD – MAXIMO deletes the item’s manufacturer record. MMU – MAXIMO updates the item’s manufacturer record. MID – MAXIMO deletes the item record. For more information about the UTRANSTYPE values. The API uses the following values in the UTRANSTYPE column of the interface tables to determine how to process the change to the vendor data: • • • MVI – MAXIMO inserts the item’s vendor record. For more information on customizing user exit procedures. MVD – MAXIMO deletes the item’s vendor record. see “Customizing the Integration APIS” on page 466. MIU – MAXIMO updates the item record. 95 .

Chapter 3 The Oracle Item Interface is used to import data into Oracle.ITMCATIN is set to Y. MAX_ITM_INTERFACE calls MXI_USR_ITM_SP MAXIMO internal procedures to record the item and/or item’s vendor/manufacturer in MAXIMO.ITMVNDIN is set to Y. Optionally. The integration API then creates all the necessary records for the item in MAXIMO. the internal procedures can also record a new vendor and/or manufacturer. MAX_ITM_INTERFACE. The vendor transaction is generated if APICTL. User Action Inserts or updates item(s) in Oracle Financials. User Exit / External API 96 . Transferring Item Data from Oracle Financials to MAXIMO To transfer data for an item record to MAXIMO. API Action Oracle’s CAI API calls the MAXIMO partner API stub that writes the received data into MAX_ITM_INTERFACE table. Refer to Oracle Applications documentation for further information. Oracle Financials must write to the MAXIMO item interface table. The item transaction is generated if APICTL.

For more information about the UTRANSTYPE values see “The User Control Column” on page 126. XVD – Delete the vendor record. XIU – Update the item record. XMD – Delete the manufacturer 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. 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. XMU – Update the manufacturer record. XVU – Update the vendor record. For more information on customizing user exit procedures. see “Customizing the Integration APIS” on page 466. 97 . Default process. Default process. Default process.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.

The Oracle Reservations Interface is used to import data into Oracle. Refer to Oracle Applications documentation for further information. MOUT_RSV_INTERFACE calls the external procedure for further processing. The API places a copy of the material reservation in the MAXIMO reservations interface table. MXE_INVRESERVE_SP User Exit / External API MO_USR_INVRESERVE_SP 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. MOUT_RSV_INTERFACE. API Action Copies the material reservations data into the MOUT_RSV_INTERFACE.Chapter 3 Transferring Material Reservations/ Demands to Oracle Financials The API transfers material reservations to Oracle Financials with work orders that contain them or after users enter them on work orders that the API has already transferred to Oracle Financials. 98 .RSVOUT is set to Y. MRSVU – MAXIMO updated the material reservations record. The API generates this transaction if APICTL. User Action Approves a work order in MAXIMO.

Using the Integration Module

Inventory Ownership for Material Reservations Sent to Your System Only transactions for externally owned inventory are exported from MAXIMO to your external system. See “Item Data Exchanges” on page 94 for more details on the inventory balance interface and inventory ownership. 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.”

99

Chapter 3

Transferring Material Issues from Oracle Financials to MAXIMO To transfer data for a material issue record to MAXIMO, your external application must write to the MAXIMO issue interface table, MAX_ISU_INTERFACE. The integration API then creates all the necessary records for the item in MAXIMO.
User Action Inserts or updates a record in the MAX_ISU_INTERFACE table. API Action User Exit

MAX_ISU_INTERFACE makes a MXI_USR_ISU_SP programming call to MAXIMO internal procedures to record the issue and update inventory and work order data. The API generates the item transaction if APICTL.ISUIN is set to Y. If APICTL.RSVONLIN is set to Y, the procedures will only accept issues that are associated with item reservations.

The API does not use any UTRANSTYPE codes for this process. For more information on customizing user exit procedures, see Chapter 2, “Implementing the Software Integration.” The column DIRECTWO in the MAX_ISU_INTERFACE table acts as Yes or No flag; when it is set to Yes, MAXIMO updates inventory reservations for the item on the work order. When the flag is set to No, MAXIMO does not update the inventory reservation update table, INVRESERVE, but does perform other updates for this transaction. Inventory Ownership for Material Issues Sent to MAXIMO Only transactions for externally owned inventory are imported into MAXIMO from Oracle Financials. However, there may be cases where a non-MAXIMO application could be used to issue items on behalf of MAXIMO. To account for

100

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. Transferring Item Balance Data from Oracle Financials to MAXIMO To transfer data for an item balance record to MAXIMO, Oracle Financials must write to the MAXIMO item interface table, MAX_ITM_INTERFACE. The integration API then creates all the necessary records for the item balance update in MAXIMO.
User Action Inserts or updates a record in the MAX_ITM_INTERFACE table. API Action MAX_ITM_INTERFACE makes a programming call to MAXIMO internal procedures to update the item balance and item cost in MAXIMO. The API generates the item balance transaction if APICTL.ITMSTOREIN is set to Y and APICTL.ITMBALXFRIN is set to Y. User Exit MXI_USR_ITM_SP

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

Transferring Item Confirmations to MAXIMO To transfer data from an item confirmation record to MAXIMO, Oracle Financials must write to the MAXIMO item confirmation interface table, MAX_ICF_INTERFACE. The integration API then creates all the necessary records for the item in MAXIMO.
User Action Inserts or updates an inventory balance in MAXIMO. API Action User Exit

MAX_ICF_INTERFACE makes a MXI_USR_ICF_SP programming call to the MAXIMO internal procedure to record the item confirmation. The API generates the item transaction if APICTL.ICFIN is set to Y.

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.” Inventory Ownership with Item Confirmations Sent to MAXIMO Only transactions for externally owned inventory are imported into MAXIMO from your external system. See “Item Data Exchanges” on page 94 for more information on the inventory balance interface and inventory ownership.

103

Chapter 3

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

104

Using the Integration Module

Transferring Vendor Data from Oracle Financials to MAXIMO When a company is inserted, updated, or deleted in Oracle Financials, the company data is placed in the MAXIMO company interface table. The integration API copies the data and updates company records in MAXIMO.
User Action Inserts or updates vendor(s) and/or vendor site(s) in Oracle Financials. API Action Oracle’s CAI API calls the MAXIMO partner API stub that writes the received data into MAX_COM_INTERFACE table. This transaction is generated if APICTL.COMIN is set to Y. MAX_COM_INTERFACE calls MAXIMO internal procedures to record the vendor in MAXIMO. MXI_USR_COM_SP User Exit

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

Accounts Payable Data Transfers
You can exchange invoice data between MAXIMO and Oracle Financials accounts payable system. Transferring Invoices from MAXIMO to Oracle Financials When you approve an invoice in MAXIMO, the integration API places a copy of it in the MAXIMO accounts payable interface table, MOUT_AP_INTERFACE. In purchasing Configuration 2, you enter, match, and approve invoices in MAXIMO. When you approve the invoice, the integration API places it in the MAXIMO accounts payable interface table. Furthermore, summary data is passed to Oracle Financials Accounts Payable for payment processing. Resulting journal entries are passed to Oracle Financials General Ledger.
User Action API Action User Exit / External API

Approves invoice in Copies invoice payment summary MXO_USR_APTRANS_GL_ data from APTRANS, required SP MAXIMO. data from invoice header and companies, and appropriate batch and API coding to MOUT_AP_INTERFACE table. This transaction is generated if APICTL.APOUT is set to Y. MOUT_AP_INTERFACE calls Oracle Financials’ procedure for further processing. MXE_AP__SP

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

The API copies relevant purchasing data from these tables:
• • • •

INVOICE INVOICELINE INVOICECOST COMPANIES

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. For more information about the UTRANSTYPE values see “The User Control Column” on page 126. Transferring Invoices from Oracle Financials to MAXIMO To transfer invoice data to MAXIMO, Oracle Financials must write to the MAXIMO accounts payable interface table, MAX_AP_INTERFACE. NOTE: You should consider carefully how to determine when an invoice is ready to be sent to MAXIMO as there is no reverse or corrective process available after MAXIMO has processed the invoice. After Oracle Financials puts the invoice data in the interface table, the integration API creates all the necessary records for the invoice in MAXIMO. This is part of purchasing Configuration 1. It adds all invoice data to MAXIMO to maintain consistency between the two applications. The primary function of this API is to apply all invoice variances to inventory, work order, and equipment records so that MAXIMO can calculate all costs accurately. Thus it is important that you provide the value of the invoice variance in the PRICVAR column of the MAX_AP_INTERFACE table. Since your accounts payable system has already calculated the variance during invoice approval, we recommend that you use only that variance rather than have MAXIMO recalculate the variance. MAXIMO does attempt to calculate a

107

Chapter 3

variance if none is provided, but it may not be the same amount that your accounts payable system has calculated.
User Action Approves invoice in Oracle Financials. API Action Oracle’s CAI API calls the MAXIMO partner API stub that writes the received data into MAX_INVC_INTERFACE table. This transaction is generated if APICTL.APIN is set to Y. MAX_INVC_INTERFACE calls MAXIMO internal procedures to record the invoice in MAXIMO. Optionally, internal procedures could also record a new vendor. MXI_USR_INVC_SP User Exit

Note: This API only processes invoice data necessary for variance processing. No further processing occurs in MAXIMO. 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

General Ledger Data Exchanges
MAXIMO and Oracle Financials can exchange general ledger information as described below:
• •

Transfer journal entries from MAXIMO to Oracle Financials. Transfer chart of accounts data from Oracle Financials to MAXIMO to synchronize this data between the two applications.

The integration API passes all GL code combinations created in Oracle Financials into MAXIMO. However, please observe the following: 1. You must configure MAXIMO to support the Oracle account structure. Within MAXIMO, to specify the basic format of the GL account codes, use the GL Account Configuration option in the Database Configuration application. 2. MAXIMO can support only one GL account structure. Thus, MAXIMO, as distributed, supports none of the following.
• • •

Multiple account templates Multiple sets of books Multiple organizations

However, you can use extra fields in MAXIMO both to store and to track different sets of books or organizations. Furthermore, you may want to use the MAXIMO Developer’s Kit to validate sets of books or organizations, i.e., cross-validation between sets of books, organizations, general ledger accounts, employees, projects, work orders, etc.

109

110 . You can also use the user exit procedures to filter out transactions for specific GL accounts from reaching the MOUT_GL_INTERFACE table. one of the following integration APIs places a copy of it in the MAXIMO journal interface table. If you use purchasing Configuration 1. your purchasing system may process the material receipt. The API uses the following UTRANSTYPE values to specify the general ledger transaction table: UTRANSTYPE Value INV MATREC MATUSE SERVREC LABOR TOOL INVOICE Table INVTRANS MATRECTRANS MATUSETRANS SERVRECTRANS LABTRANS TOOLTRANS INVOICETRANS Table Description Inventory transactions Material receipt transactions Material usage (issue) transactions Service receipt transactions Labor transactions Tools transactions Invoice transactions You may not need all of the journal entries APIs. The only API process that occurs in this transaction is INSERT. and invoice transactions. service receipts. If you do not use the associated APIs you should turn them off with the API controls. depending on the purchasing Configuration that you use.Chapter 3 Transferring Journal Entries from MAXIMO to Oracle Financials When a user inserts a record in any of the MAXIMO journal transaction tables.

see “Customizing the Integration APIS” on page 466. 111 . see “Customizing Integration Procedures” on page 47. For more information on customizing external exit procedures.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.

User Action Enters inventory transaction API Action Copies data from INVTRANS where Debit GL Account is not the same as Credit GL Account. This transaction is generated if APICTL. the integration API places a copy of it in the MAXIMO general ledger interface table.Chapter 3 Transferring Entries from INVTRANS to Oracle Financials When a user enters a record in the INVTRANS table. LINECOST is not 0.JEINVENTORY is set to Y. MOUT_GL_INTERFACE. MOUT_GL_INTERFACE. the integration API places a copy of it in the MAXIMO general ledger interface table. MOUT_GL_INTERFACE copies MXO_USR_MOUT_GL_ the data to the GL_INTERFACE INTERFACE_SP table in Oracle Financials for further processing. 112 . and the account is not of the following transaction types: INSERTITEM PCOUNTADJ Adds appropriate batch and API coding to the MOUT_GL_INTERFACE table. User Exit / External API MXO_USR_INVTRANS_ GL_SP The API copies relevant data from the following table: • INVTRANS Transferring Journal Entries from MATRECTRANS to Oracle Financials When a user inserts a record in the MATRECTRANS table.

This transaction is generated if APICTL. This transaction is generated if APICTL.EJESERVREC is set to Y and the PO is Oracle-owned. MOUT_GL_INTERFACE copies the MXO_USR_MOUT_GL_ data to the GL_INTERFACE table in INTERFACE_SP Oracle Financials for further processing.Using the Integration Module User Action API Action Enters material usage User Exit / External API Copies data from MATUSETRANS MXO_USR_MATUSETRA where Debit GL Account is not the same NS_GL_SP as Credit GL Account and LINECOST is not 0. Adds appropriate batch and API coding to the MOUT_GL_INTERFACE table.JESERVREC is set to Y and the PO is MAXIMO-owned. The API copies relevant data from this table: • MATRECTRANS 113 .

This transaction is generated if APICTL. MOUT_GL_INTERFACE copies the data to the GL_INTERFACE table in Oracle Financials for further processing.Chapter 3 Transferring Journal Entries from MATUSETRANS to Oracle Financials When a user inserts a record in the MATUSETRANS table. User Action API Action User Exit / External API Enters material usage Copies data from MXO_USR_MATUSETRA MATUSETRANS where Debit NS_GL_SP GL Account is not the same as Credit GL Account and LINECOST is not 0. the integration API places a copy of it in the MAXIMO general ledger interface table.JEMATUSE is set to Y. MOUT_GL_INTERFACE. MXO_USR_MOUT_GL_ INTERFACE_SP The API copies relevant data from this table: • MATUSETRANS 114 . Adds appropriate batch and API coding to the MOUT_GL_INTERFACE table.

Using the Integration Module Transferring Entries from SERVRECTRANS to Oracle Financials When a user inserts a record in the SERVRECTRANS table. User Action Enters service receipt. Adds appropriate batch and API coding to the MOUT_GL_INTERFACE table.JESERVREC is set to Y. This transaction is generated if APICTL. MOUT_GL_INTERFACE copies the data to the GL_INTERFACE table in Oracle Financials for further processing. the integration API places a copy of it in the MAXIMO general ledger interface table. MXO_USR_MOUT_GL_ INTERFACE_SP User Exit / External API MXO_USR_SERVRECTRANS_ GL_SP The API copies relevant data from this table: • SERVRECTRANS 115 . API Action Copies data from SERVRECTRANS where Debit GL Account is not the same as Credit GL Account and LINECOST is not 0.

JELABOR is set to Y.Chapter 3 Transferring Entries from LABTRANS to Oracle Financials When a user inserts a record in the LABTRANS table. API Action User Exit / External API MXO_USR_LABTRANS_ Copies data from LABTRANS where Debit GL Account is not the GL_SP same as Credit GL Account. LINECOST is not 0. MOUT_GL_INTERFACE. and the account is of the following transaction type: WORK NON-WORK Adds appropriate batch and API coding to the MOUT_GL_INTERFACE table. MOUT_GL_INTERFACE copies the data to the GL_INTERFACE table in Oracle Financials for further processing. This transaction is generated if APICTL. User Action Enters labor usage. the integration API places a copy of it in the MAXIMO general ledger interface table. MXO_USR_MOUT_GL_ INTERFACE_SP The API copies relevant data from this table: • LABTRANS 116 .

Using the Integration Module Transferring Entries from TOOLTRANS to Oracle Financials When a user inserts a record in the TOOLTRANS table. User Exit / External API MXO_USR_TOOLTRANS _GL_SP The API copies relevant data from the following table: • TOOLTRANS 117 . User Action Enters tool usage. MOUT_GL_INTERFACE copies MXO_USR_MOUT_GL_ the data to the GL_INTERFACE INTERFACE_SP table in Oracle Financials for further processing. Adds appropriate batch and API coding to the MOUT_GL_INTERFACE table. This transaction is generated if APICTL. the integration API places a copy of it in the MAXIMO general ledger interface table. API Action Copies data from TOOLTRANS where Debit GL Account is not the same as Credit GL Account and LINECOST is not 0. MOUT_GL_INTERFACE.JETOOL is set to Y.

The API generates this transaction if APICTL. Adds appropriate batch and API coding to the MOUT_GL_INTERFACE table. MXE_GL_SP The API copies relevant data from these tables: • • • INVOICETRANS INVOICELINE INVOICECOST: The Oracle GL Interface is used to import data into Oracle. the integration API places a copy of it in the MAXIMO general ledger interface table.JEINVOICE is set to Y. MOUT_GL_INTERFACE. Refer to Oracle Applications documentation for further information. API Action User Exit / External API MXO_USR_INVOICETRANS_ Copies data from INVOICETRANS where the GL_SP debit GL account is not the same as the credit GL account and LINECOST is not 0. User Action Approves invoice in MAXIMO.Chapter 3 Transferring Entries from INVOICETRANS to Oracle Financials When a user inserts a record in the INVOICETRANS table. MOUT_GL_INTERFACE calls external procedure for further processing. 118 .

This transaction is generated if APICTL. the chart of accounts data is placed in the MAXIMO chart of accounts interface table.Using the Integration Module Transferring Chart of Accounts Data from Oracle Financials to MAXIMO When a chart of accounts record or a general ledger component for the chart of accounts record is inserted. or deleted in Oracle Financials. see “Customizing the Integration APIS” on page 466. 119 . Default process. User Action API Action User Exit / External API Inserts or updates GL(s) in Oracle’s CAI API calls the Oracle Financials. MXI_USR_COA_SP For more information on customizing user exit procedures. XGD – Delete the chart of accounts record. The integration API copies the data and updates chart of accounts records in MAXIMO. XGU – Update the chart of accounts record. The following values modify the chart of accounts: • • • XGI – Insert the chart of accounts record. Default process. updated. 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.COA is set to Y. MAX_COA_INTERFACE calls MAXIMO internal procedures to populate the MAXIMO CHARTOFACCOUNTS table and/or GLCOMPONENTS table. MAXIMO partner API stub that writes the received data into MAX_COA_INTERFACE table.

there are two user exit procedures for transforming GL accounts from one system to the other. Default process. In the APIUSER directory.Chapter 3 The following values modify general ledger components of the chart of accounts: • XCI – Insert the general ledger account component record. XCD – Delete the general ledger account component record. use user exit procedure MXE_USR_GLOUTX_SP. when transferring accounts from one system to the other. • • For more information about the UTRANSTYPE column. 120 . Therefore. Transferring Accounts from MAXIMO to Oracle Financials If you are transferring accounts from MAXIMO to Oracle Financials. Default process. see “MAXIMO Interface Tables”on page 125. This section both outlines the cases in which you need to perform the account transformation and explains how to make the transformation. XCU – Update the general ledger account component record. you must transform those accounts. This procedure is in the OFGLOUTX.USP file. 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.

not fixed length. there are two relevant differences between the account structure in Oracle Financials and the account structure in MAXIMO: Oracle Financials Segment length Null segments allowed May be variable In any part of the account MAXIMO Always fixed Only after all non-nulls The remainder of the section contains examples of these two relevant differences. The first segment is fixed at two characters long. but does not support Dependent or Table Validated segments. In Oracle Financials some segments are of variable length. you can enter an account number of 22-4444. If necessary. Cases Requiring Transformation of GL Accounts As shown in the following table. One particular account is 22-333. Thus. the second segment can be variable in length. This procedure is in file OFGLINX. using Oracle Financials. we cannot guarantee the accuracy of the description for these segments coming to MAXIMO. in MAXIMO all segments are of fixed length. Example Your accounts have two segments. In Oracle Financials. However. 1. Thus. including the specific changes to the user exits.Using the Integration Module Transferring Accounts from Oracle Financials to MAXIMO If you are transferring accounts from Oracle Financials to MAXIMO. MAXIMO Support for the Transformation of the GL Accounts MAXIMO supports Independent GL Segments. you can use zeros to pad the account segments in MAXIMO. the second segment must always be three characters long. Because of this. 22-4444 is not a valid account in MAXIMO. in MAXIMO. 121 .USP. use user exit procedure MXI_USR_GLINX_SP.

3. In Oracle Financials. Thus. 22-22 is a valid account in Oracle Financials. you need to pad the second segment with zeros. Add the following statement to the procedure MXE_USR_GLOUTX_SP in file OFGLOUTX. you must make the following changes to the user exit procedures. but not in MAXIMO. Add the following statement to the procedure MXE_USR_GLINX_SP in file OFGLINX. Transferring from MAXIMO to Oracle Financials Before transferring the account to Oracle Financials. The segment becomes a fixed-length segment in MAXIMO. 122 . the account 22-022 in MAXIMO becomes 22-22 in Oracle Financials.Chapter 3 Similarly.’0’). In MAXIMO. you must trim the zeros from the fixed-length segment. the Oracle Financials account 22-22 becomes MAXIMO account 22-022. you must pad the variablelength segment in Oracle Financials. if transferring this account from one system to another. Thus.USP: OFGLSegs(2) := LTRIM(OFGLSegs(2).’0’). the segment becomes a variable-length segment. Transferring from Oracle Financials to MAXIMO Before transferring the account to MAXIMO. Thus. the MAXIMO account needs to be 22-022.USP: OFGLSegs(2) := LPAD(OFGLSegs(2). Thus.

null segments are permitted in any part of the account. these accounts must consist of only two segments: Segment1 = size(2) Segment2 = size(3) Thus. Example Your accounts in Oracle Financials have three segments: Segment1 = null Segment2 = size(2) Segment3 = size(3) In MAXIMO. you must make the following changes to the user exit procedures. 123 . In Oracle Financials. if transferring this account from one system to another.Using the Integration Module 2. Thus. However. a null segment cannot precede a non-null segment. MAXIMO does not allow a null segment to precede a non-null segment.

OFGLSegs(2) := OFGLSegs(3). you must convert the two-segment account in MAXIMO to a three-segment account for Oracle Financials. Taking note of the order of movements. (change the number of segments from three to two) 124 . nSegs := 2. you must convert the three-segment account in Oracle Financials to a two-segment account for MAXIMO. Taking note of the order of movements.USP: OFGLSegs(3) := OFGLSegs(2). nSegs := 3. and the first segment of the account in Oracle Financials is created as a null. add the following statements to the procedure MXE_USR_GLINX_SP in file OFGLINX. OFGLSegs(2) := OFGLSegs(1). add the following statements to the procedure MXE_USR_GLOUTX_SP in file OFGLOUTX. The existing two segments are shifted down.USP: OFGLSegs(1) := OFGLSegs(2). and the third segment of the account in MAXIMO becomes a null.Chapter 3 Transferring from MAXIMO to Oracle Financials Before transferring the account. The two non-null segments are shifted up. OFGLSegs(3) := Null. (change the number of segments from two to three) Transferring from Oracle Financials to MAXIMO Before transferring the account. OFGLSegs(1) := Null.

Some columns are conditionally required. on a vendor 125 . In addition to the interface tables. see “Troubleshooting ” on page 476. For example. Y indicates that the data is not required. Data Columns Data columns store the specific attributes that the source application is sending to the destination application.Using the Integration Module MAXIMO Interface Tables Interface tables are the intermediate locations where data resides while it is being transferred between MAXIMO and Oracle Financials. N indicates that the data is required. an integration API processes the data and places it in its destination. For example. but the destination application can use it for additional value-added functionality beyond the basics. Once it is validated. which store different kinds of information. For example. The log table tracks transactions between the two applications and keeps records of transaction errors. Data is sent to an interface table. Required columns store the minimum information needed by the destination application to process the interface row. price is required for all purchase orders. The required or optional status is indicated under the Nulls heading in the interface tables. one attribute of a purchase order is the order quantity. the integration module keeps a log table called MAX_INTERFACE_LOG. For more information about the interface log. Data columns contain information that is either required or optional. For details about the mapping between MAXIMO and Oracle Financials interface tables. refer to the APIDOC subdirectory. a copy of the data remains in the interface table. Interface tables contain several types of columns. where it remains while it is validated. Information stored in optional columns is not necessarily required by the destination application. based on the specifics of the system integration. For audit trail purposes.

USERDATA1 – USERDATA10. All of the API tables appear in the table list box. select the INTERFACE application. refer to the MAXIMO System Administrator’s Guide. The User Control Column The user control column. Choose each table and configure the user data columns in it. available for general use. called UTRANSTYPE. see “Using Batch Routines” on page 468. Only transactions from Oracle Financials to MAXIMO have default processes. In some cases. Run MAXIMO and choose Setup Database Configuration. but you can optionally use it to collect additional information about a vendor. For instructions on how to configure columns using the Database Configuration application. Batch columns identify the batch number and the transaction line number within the batch routine. By default the columns are alphanumeric with a column length of one (ALN1). Users can specify an integration API process by inserting a value in this column. the CO1 column is not required. To configure the columns. User Columns There are 10 user data columns. the integration API process overrides a default API process. Use the MAXIMO Database Configuration application to reconfigure the MAXIMO columns for your use. stores user-defined program directives. you must access their tables using the Database Configuration application. Batch Control Columns Batch columns store information about the batch routine transferring of data to the destination application. The default processes generally are insert and update. For information about batch routines.Chapter 3 transaction. The API first tries to insert the 126 . In the application list box.

Three interface control columns are APISEQ. This APISEQ value links each MAXIMO record with its associated record in the interface table. updated. and the source and destination applications. When you transfer the purchase requisition to Oracle Financials. the default processes for the vendor API are insert or update. UTRANSTYPE values for transactions sent from MAXIMO to Oracle Financials must be processed by Oracle Financials. These columns also provide details about the data being transferred. APISEQ is inserted into tables PRLINE and MOUT_PR_INTERFACE The APISYNC value links records across different applications and systems. The API does not delete the record unless the delete value is listed in the UTRANSTYPE column. it deletes the record in MAXIMO if the XCD value is in the control column. For example. When you create a purchase order in Oracle Financials and transfer the PO to 127 . If a vendor record is deleted in Oracle Financials. When the API processes the transaction. with receipts and with invoices. or deleted in the source application. UTRANSTYPE values for transactions sent from Oracle Financials to MAXIMO are automatically processed. For example. • The APISEQ column contains an internally generated value from the Oracle sequence APISEQ. the interface control columns for a purchase order transaction would specify whether the purchase order was just created. the value XCD (external vendor delete) may be inserted in the control column. Interface Control Columns Interface control columns identify the integration API used in the transaction. APISYNC links records associated with purchase requisitions. each line is assigned an APISYNC value. If the record already exists. the APISYNC value is transferred with it. Example When you generate a purchase requisition in MAXIMO. the API updates it. Example • When a PR is approved. with purchase orders. providing an audit trail.Using the Integration Module record. and SOURCEID. APISYNC.

For information about other error messages.Chapter 3 MAXIMO. and general messages. Therefore. Status Columns Status columns provide information about the status of a transaction. The status columns also provide the date and time of transaction completion or failure. 128 . A SOURCEID of ‘I’ indicates data imported from Oracle Financials. see “Troubleshooting ” on page 476. the APISYNC value is stored in the APISYNC column in the MAXIMO table POLINE. Either a null SOURCEID or a SOURCEID of ‘M’ indicates data from MAXIMO. the purchase order can be traced back to the PRLINE record. such as error messages. They indicate whether or not a transaction was completed successfully. • The SOURCEID column identifies the source of the data.

Enter a valid user ID. For information about other messages. the user ID being passed may be invalid or not authorized for the function being performed in Oracle Financials. Invalid Debit/Credit GL Code Combinations The GL account value failed Oracle Financials validation. see “Troubleshooting” on page 476. Invalid enter by user The user ID value failed Oracle Financials validation. You might see one of the following error messages when transferring data from MAXIMO to Oracle Financials. Enter a valid vendor. If GENUSR is set to N. Specify a valid organization defined in Oracle Financials. If GENUSR is Y. set up the MAXIMO ID in Oracle Financials to have access to the function being performed. Invalid vendor site The component in the MAXIMO vendor key that makes up the vendor site ID failed Oracle Financials validation. Invalid BillTo BillTo must have a valid organization in Oracle Financials. 129 . Enter a valid GL account. Invalid vendor or Invalid vendor header The component in the MAXIMO vendor key that makes up the vendor ID failed Oracle Financials validation.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. Enter a valid vendor.

They are there to group sets of data or to separate information that comes from different tables.Chapter 3 Purchasing Interface Tables This section provides the mapping for the interface tables the APIs use when transferring purchasing data between MAXIMO and Oracle Financials. MOUT_PR_INTERFACE Table The MOUT_PR_INTERFACE table receives purchase requisition data from the following MAXIMO tables when a purchase requisition is approved. Empty rows in the table are not physical rows in the database. The values displayed in the following tables are examples. and do not necessarily reflect your values. MOUT_PR_INTERFACE Table Column Name PRNUM ISSUEDATE REQUIREDDATE REQUESTEDBY VENDOR CONTACT CUSTOMERNUM FOB FREIGHTTERMS SHIPVIA PAYMENTTERMS MAXIMO Tables Length Nulls Table 8 S Y Y Y Y Y Y Y Y Y Y PR PR PR PR PR PR PR PR PR PR PR Type UPPER Column Name PRNUM ISSUEDATE REQUIREDDATE REQUESTEDBY VENDOR CONTACT CUSTOMERNUM FOB FREIGHTTERMS SHIPVIA PAYMENTTERMS DATETIME 10 DATETIME 10 UPPER UPPER ALN ALN ALN ALN ALN ALN 18 8 50 16 20 50 20 20 130 . Data is transferred to Oracle Financials. Your MAXIMO system catalogue determines your values.

2 4 1 131 .Using the Integration Module MOUT_PR_INTERFACE Table Column Name SHIPTO SHIPTOATTN BILLTO BILLTOATTN DESCRIPTION STATUS STATUSDATE CHANGEDATE CHANGEBY TOTALCOST PRIORITY HISTORYFLAG PR1 PR2 PR3 PR4 PR5 PR6 PR7 PR8 PR9 PR10 MAXIMO Tables Length Nulls Table 8 50 8 50 50 6 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y PR PR PR PR PR PR PR PR PR PR PR PR PR PR PR PR PR PR PR PR PR PR Type UPPER ALN UPPER ALN ALN UPPER Column Name SHIPTO SHIPTOATTN BILLTO BILLTOATTN DESCRIPTION STATUS STATUSDATE CHANGEDATE CHANGEBY TOTALCOST PRIORITY HISTORYFLAG PR1 PR2 PR3 PR4 PR5 PR6 PR7 PR8 PR9 PR10 DATETIME 10 DATETIME 10 UPPER DECIMAL INTEGER YORN ALN ALN ALN ALN ALN AMOUNT 18 10.2 4 1 10 10 10 10 10 10.2 DATETIME 10 DECIMAL INTEGER YORN 15.

2 10.2 1 1 Y Y Y Y Y Y Y Y Y Y Y Y Y PR PR PR PR PR PR PR PR PR PR PR PR PR EXCHANGEDATE BUYAHEAD TOTALTAX1 TOTALTAX2 TOTALTAX3 INCLUSIVE1 INCLUSIVE2 INCLUSIVE3 INTERNAL TOTALTAX4 TOTALTAX5 INCLUSIVE4 INCLUSIVE5 PAYONRECEIPT ALN 1 Y PR PAYONRECEIPT 132 .Chapter 3 MOUT_PR_INTERFACE Table Column Name PRLONGDESC PRLINELONGDESC SUPERVISOR CURRENCYCODE MAXIMO Tables Length Nulls Table 2000 2000 8 8 Y Y Y Y PR PR SUPERVISOR CURRENCYCODE Type ALN ALN UPPER UPPER Column Name EXCHANGERATE DECIMAL 14.2 10.2 1 1 1 1 10.7 Y PR EXCHANGERATE EXCHANGEDATE BUYAHEAD TOTALTAX1 TOTALTAX2 TOTALTAX3 INCLUSIVE1 INCLUSIVE2 INCLUSIVE3 INTERNAL TOTALTAX4 TOTALTAX5 INCLUSIVE4 INCLUSIVE5 DATE YORN DECIMAL DECIMAL DECIMAL YORN YORN YORN YORN DECIMAL DECIMAL YORN YORN 4 1 10.2 10.

2 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y PR PR PR PR PR PR PR PR PR PR PR PR PR PR PRLINE PRLINE PR PRLINE PRLINE PRLINE PRLINE PRLINE Type INTEGER ALN DECIMAL ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN INTEGER ALN UPPER UPPER DECIMAL ALN DECIMAL Column Name WFID WFACTIVE EXCHANGERATE2 SOURCESYSID OWNERSYSID EXTERNALREFID PRLA1 PRLA2 PRLA3 PRLA4 PRLA5 PCARDNUM PCARDTYPE PCARDEXPDATE PCARDVERIFICATION APISEQ SENDERSYSID ITEMNUM STORELOC ORDERQTY ORDERUNIT UNITCOST 133 .2 8 10.Using the Integration Module MOUT_PR_INTERFACE Table Column Name WFID WFACTIVE EXCHANGERATE2 SOURCESYSID OWNERSYSID EXTERNALREFID PRLA1 PRLA2 PRLA3 PRLA4 PRLA5 PCARDNUM PCARDTYPE PCARDEXPDATE PCARDVERIFICATION APISEQ SENDERSYSID ITEMNUM STORELOC ORDERQTY ORDERUNIT UNITCOST MAXIMO Tables Length Nulls Table 4 1 14.7 10 10 10 10 10 10 10 10 30 20 7 4 4 50 30 8 15.

2 10 10 18 1 4 10 10 10 DATETIME 10 DECIMAL UPPER 15.Chapter 3 MOUT_PR_INTERFACE Table Column Name CONVERSION PONUM REQDELIVERYDATE VENDELIVERYDATE ENTERDATE ENTERBY PRLDESCRIPTION RL1 RL2 RL3 RL4 RL5 WONUM PRLREQUESTEDBY ISSUE WPOPERATION RLIN1 RLIN2 RLIN3 RLIN4 RLIN5 EQNUM MAXIMO Tables Length Nulls Table 15.2 8 4 4 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE Type DECIMAL ALN DATE DATE Column Name CONVERSION PONUM REQDELIVERYDATE VENDELIVERYDATE ENTERDATE ENTERBY DESCRIPTION RL1 RL2 RL3 RL4 RL5 WONUM REQUESTEDBY ISSUE WPOPERATION RLIN1 RLIN2 RLIN3 RLIN4 RLIN5 EQNUM DATETIME 10 UPPER ALN ALN ALN ALN DECIMAL ALN UPPER UPPER YORN INTEGER ALN ALN ALN 18 80 10 10 10 15.2 8 134 .

2 8 10.2 Y Y Y Y PRLINE PRLINE PRLINE PRLINE Type YORN ALN ALN DECIMAL Column Name CHARGESTORE GLDEBITACCT GLCREDITACCT LINECOST TAX1CODE TAX1 TAX2CODE TAX2 TAX3CODE TAX3 SCHARGECODE RECEIPTREQD MANUFACTURER MODELNUM CATALOGCODE TAX4CODE TAX4 TAX5CODE TAX5 PRLINENUM POLINENUM UPPER DECIMAL UPPER DECIMAL UPPER DECIMAL UPPER YORN UPPER ALN ALN UPPER DECIMAL UPPER DECIMAL INTEGER INTEGER 8 10.2 4 4 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE TAX1CODE TAX1 TAX2CODE TAX2 TAX3CODE TAX3 SCHARGECODE RECEIPTREQD MANUFACTURER MODELNUM CATALOGCODE TAX4CODE TAX4 TAX5CODE TAX5 PRLINENUM POLINENUM 135 .2 8 10.Using the Integration Module MOUT_PR_INTERFACE Table Column Name CHARGESTORE GLDEBITACCT GLCREDITACCT LINECOST MAXIMO Tables Length Nulls Table 1 20 20 10.2 8 10.2 8 1 8 8 30 8 10.

2 8 8 4 1 12 12 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE MAXVAR PRLINE PRLINE PRLINE PRLINE PRLINE Type UPPER ALN YORN UPPER AMOUNT ALN ALN ALN ALN ALN INTEGER ALN INTEGER INTEGER DECIMAL UPPER ALN INTEGER YORN ALN Column Name CATEGORY REMARK SERVICE LOCATION LOADEDCOST PRORATESERVICE AGREEMENTPONUM AGREEMENTPOTYPE CONVERTTORFQ RFQNUM RFQLINENUM INSPECTIONREQUIRED RFQLINEID POLINEID LINECOST VARVALUE(BASCURREN CY2) MRNUM MRLINENUM MKTPLCITEM VENDORPACKCODE VENDORPACKQUANTIT Y VENDORPACKQUANTIT ALN Y 136 .2 1 8 6 1 8 4 1 4 4 10.Chapter 3 MOUT_PR_INTERFACE Table Column Name CATEGORY REMARK SERVICE LOCATION LOADEDCOST PRORATESERVICE AGREEMENTPONUM AGREEMENTPOTYPE CONVERTTORFQ RFQNUM RFQLINENUM INSPECTIONREQUIRED RFQLINEID POLINEID LINECOST2 CURRENCYCODE2 MRNUM MRLINENUM MKTPLCITEM VENDORPACKCODE MAXIMO Tables Length Nulls Table 4 50 1 8 10.

Using the Integration Module MOUT_PR_INTERFACE Table Column Name VENDORWAREHOUSE RL6 RL7 RL8 RL9 RL10 RLIN6 RLIN7 RLIN8 RLIN9 PRLALN1 PRLALN2 PRLALN3 PRLALN4 PRLALN5 PRLPRPCARDNUM PRLPRPCARDTYPE PRLPRPCARDEXPDATE MAXIMO Tables Length Nulls Table 12 10 10 10 10 10 10 10 10 10 10 10 10 10 10 30 20 7 4 8 1 50 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y COMPANIES COMPANIES TYPE NAME PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE Type ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN Column Name VENDORWAREHOUSE RL6 RL7 RL8 RL9 RL10 RLIN6 RLIN7 RLIN8 RLIN9 PRLALN1 PRLALN2 PRLALN3 PRLALN4 PRLALN5 PCARDNUM PCARDTYPE PCARDEXPDATE PCARDVERIFICATION RPCARDVERIFICATION ALN FINCNTRLID COMPANYTYPE MFGNAME ALN ALN ALN 137 .

Chapter 3 MOUT_PR_INTERFACE Table Column Name NAME ADDRESS1 ADDRESS2 ADDRESS3 ADDRESS4 PHONE FAX CO1 CO2 CO3 CO4 CO5 CO6 CO7 CO8 CO9 CO10 CO11 CO12 CO13 COMPANYLOC REGISTRATION1 MAXIMO Tables Length Nulls Table 50 36 36 36 36 20 20 10 10 10 10.2 8 20 138 .2 DATETIME 10 INTEGER YORN ALN 4 1 10 DATETIME 10 DECIMAL UPPER ALN 15.2 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES Type ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN DECIMAL Column Name NAME ADDRESS1 ADDRESS2 ADDRESS3 ADDRESS4 PHONE FAX CO1 CO2 CO3 CO4 CO5 CO6 CO7 CO8 CO9 CO10 CO11 CO12 CO13 LOCATION REGISTRATION1 DATETIME 10 ALN AMOUNT 10 10.

Using the Integration Module MOUT_PR_INTERFACE Table Column Name REGISTRATION2 REGISTRATION3 APCONTROLACC APSUSPENSEACC RBNIACC PAYVENDOR BANKACCOUNT REGISTRATION4 REGISTRATION5 REMITADDRESS1 REMITADDRESS2 REMITADDRESS3 REMITADDRESS4 REMITCONTACT HOMEPAGE BANKNUM DUNSNUM TAXEXEMPTCODE TAXEXEMPTNUM MAXIMO Tables Length Nulls Table 20 20 20 20 20 8 20 20 20 36 36 36 36 50 124 16 16 1 20 1 1 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES Type ALN ALN ALN ALN ALN UPPER UPPER ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN Column Name REGISTRATION2 REGISTRATION3 APCONTROLACC APSUSPENSEACC RBNIACC PAYVENDOR BANKACCOUNT REGISTRATION4 REGISTRATION5 REMITADDRESS1 REMITADDRESS2 REMITADDRESS3 REMITADDRESS4 REMITCONTACT HOMEPAGE BANKNUM DUNSNUM TAXEXEMPTCODE TAXEXEMPTNUM ECOMMERCEENABLED DISABLED ECOMMERCEENABLED ALN DISABLED ALN 139 .

Chapter 3 MOUT_PR_INTERFACE Table Column Name POSITION MAXIMO Tables Length Nulls Table 24 Y Type ALN Column Name COMPCONTACT POSITION ITMDESCRIPTION ITEMLONGDESC STOCKTYPE LOTTYPE CAPITALIZED ROTATING ALN ALN ALN UPPER YORN ALN 80 2000 8 5 1 1 Y Y Y Y Y Y ITEM DESCRIPTION ITEM ITEM ITEM ITEM STOCKTYPE LOTTYPE CAPITALIZED ROTATING ISSUEUNIT ALN 8 Y INVENTORY ISSUEUNIT ROWSTAMP ALN 40 Y MEMO ALN 40 Y POSTATUS MEMO USERDATA1 USERDATA2 USERDATA3 USERDATA4 USERDATA5 USERDATA6 USERDATA7 ALN ALN ALN ALN ALN ALN ALN 1 1 1 1 1 1 1 Y Y Y Y Y Y Y 140 .

Using the Integration Module MOUT_PR_INTERFACE Table Column Name USERDATA8 USERDATA9 USERDATA10 TOTALLINES MEMO BATCHID BATCHLINEID MAXIMO Tables Length Nulls Table 1 1 1 4 25 25 4 Y Y Y Y Y Y Y Type ALN ALN ALN INTEGER ALN ALN INTEGER Column Name UTRANSTYPE ALN 25 Y SOURCEID ALN 25 Y PR SOURCEID APISITE ALN 256 Y IMPORTSTATUS IMPORTTIMESTAMP IMPORTMESSAGE ALN 25 Y Y Y DATETIME 10 ALN 2000 141 .

Data is sent to the following MAXIMO tables.Chapter 3 MAX_PRX_INTERFACE Table The MAX_PRX_INTERFACE table receives purchase requisition update data from 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. MAX_PR_INTERFACE Table Column Name PRNUM ISSUEDATE REQUIREDDATE REQUESTEDBY VENDOR CONTACT CUSTOMERNUM FOB FREIGHTTERMS SHIPVIA PAYMENTTERMS SHIPTO SHIPTOATTN BILLTO BILLTOATTN DESCRIPTION STATUS MAXIMO Tables Length Nulls Table 8 N Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y PR PR PR PR PR PR PR PR PR PR PR PR PR PR PR PR PR Type UPPER Column Name PRNUM ISSUEDATE REQUIREDDATE REQUESTEDBY VENDOR CONTACT CUSTOMERNUM FOB FREIGHTTERMS SHIPVIA PAYMENTTERMS SHIPTO SHIPTOATTN BILLTO BILLTOATTN DESCRIPTION STATUS DATETIME 10 DATETIME 10 UPPER UPPER ALN ALN ALN ALN ALN ALN UPPER ALN UPPER ALN ALN UPPER 18 8 50 16 20 50 20 20 8 50 8 50 50 6 142 .

7 10 143 .2 DATETIME 10 DECIMAL INTEGER YORN ALN ALN UPPER UPPER DECIMAL DATE 15.Using the Integration Module MAX_PR_INTERFACE Table Column Name STATUSDATE CHANGEDATE CHANGEBY TOTALCOST PRIORITY HISTORYFLAG PR1 PR2 PR3 PR4 PR5 PR6 PR7 PR8 PR9 PR10 PRLONGDESC PRLINELONGDESC SUPERVISOR CURRENCYCODE EXCHANGERATE EXCHANGEDATE MAXIMO Tables Length Nulls Table Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y PR PR PR PR SUPERVISOR CURRENCYCODE EXCHANGERATE EXCHANGEDATE PR PR PR PR PR PR PR PR PR PR PR PR PR PR PR PR Type Column Name STATUSDATE CHANGEDATE CHANGEBY TOTALCOST PRIORITY HISTORYFLAG PR1 PR2 PR3 PR4 PR5 PR6 PR7 PR8 PR9 PR10 DATETIME 10 DATETIME 10 UPPER DECIMAL INTEGER YORN ALN ALN ALN ALN ALN AMOUNT 18 10.2 4 1 2000 2000 8 8 14.2 4 1 10 10 10 10 10 10.

2 10.2 10.2 1 1 Y Y Y Y Y Y Y Y Y Y Y Y PR PR PR PR PR PR PR PR PR PR PR PR Type YORN DECIMAL DECIMAL DECIMAL YORN YORN YORN YORN DECIMAL DECIMAL YORN YORN Column Name BUYAHEAD TOTALTAX1 TOTALTAX2 TOTALTAX3 INCLUSIVE1 INCLUSIVE2 INCLUSIVE3 INTERNAL TOTALTAX4 TOTALTAX5 INCLUSIVE4 INCLUSIVE5 PAYONRECEIPT WFID WFACTIVE EXCHANGERATE2 APISEQ SENDERSYSID ITEMNUM STORELOC ORDERQTY ALN INTEGER ALN DECIMAL INTEGER ALN UPPER UPPER DECIMAL 1 4 1 14.2 10.Chapter 3 MAX_PR_INTERFACE Table Column Name BUYAHEAD TOTALTAX1 TOTALTAX2 TOTALTAX3 INCLUSIVE1 INCLUSIVE2 INCLUSIVE3 INTERNAL TOTALTAX4 TOTALTAX5 INCLUSIVE4 INCLUSIVE5 MAXIMO Tables Length Nulls Table 1 10.2 1 1 1 1 10.2 Y Y Y Y Y Y Y Y Y PR PR PR PR PRLINE PR PRLINE PRLINE PRLINE PAYONRECEIPT WFID WFACTIVE EXCHANGERATE2 APISEQ SENDERSYSID ITEMNUM STORELOC ORDERQTY 144 .7 4 50 30 8 15.

Using the Integration Module

MAX_PR_INTERFACE Table Column Name
ORDERUNIT UNITCOST CONVERSION PONUM REQDELIVERYDATE VENDELIVERYDATE ENTERDATE ENTERBY PRLDESCRIPTION RL1 RL2 RL3 RL4 RL5 WONUM PRLREQUESTEDBY ISSUE WPOPERATION RLIN1 RLIN2 RLIN3 RLIN4

MAXIMO Tables Length Nulls Table
8 10.2 15.2 8 4 4 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE

Type
ALN DECIMAL DECIMAL ALN DATE DATE

Column Name
ORDERUNIT UNITCOST CONVERSION PONUM REQDELIVERYDATE VENDELIVERYDATE ENTERDATE ENTERBY DESCRIPTION RL1 RL2 RL3 RL4 RL5 WONUM REQUESTEDBY ISSUE WPOPERATION RLIN1 RLIN2 RLIN3 RLIN4

DATETIME 10 UPPER ALN ALN ALN ALN DECIMAL ALN UPPER UPPER YORN INTEGER ALN ALN ALN 18 80 10 10 10 15.2 10 10 18 1 4 10 10 10

DATETIME 10

145

Chapter 3

MAX_PR_INTERFACE Table Column Name
RLIN5 EQNUM CHARGESTORE GLDEBITACCT GLCREDITACCT LINECOST

MAXIMO Tables Length Nulls Table
15.2 8 1 20 20 10.2 Y Y Y Y Y Y PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE

Type
DECIMAL UPPER YORN ALN ALN DECIMAL

Column Name
RLIN5 EQNUM CHARGESTORE GLDEBITACCT GLCREDITACCT LINECOST

TAX1CODE TAX1 TAX2CODE TAX2 TAX3CODE TAX3 SCHARGECODE RECEIPTREQD MANUFACTURER MODELNUM CATALOGCODE TAX4CODE TAX4 TAX5CODE TAX5

UPPER DECIMAL UPPER DECIMAL UPPER DECIMAL UPPER YORN UPPER ALN ALN UPPER DECIMAL UPPER DECIMAL

8 10.2 8 10.2 8 10.2 8 1 8 8 30 8 10.2 8 10.2

Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y

PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE

TAX1CODE TAX1 TAX2CODE TAX2 TAX3CODE TAX3 SCHARGECODE RECEIPTREQD MANUFACTURER MODELNUM CATALOGCODE TAX4CODE TAX4 TAX5CODE TAX5

146

Using the Integration Module

MAX_PR_INTERFACE Table Column Name
PRLINENUM POLINENUM CATEGORY REMARK SERVICE LOCATION LOADEDCOST PRORATESERVICE AGREEMENTPONUM AGREEMENTPOTYPE CONVERTTORFQ RFQNUM RFQLINENUM

MAXIMO Tables Length Nulls Table
4 4 4 50 1 8 10.2 1 8 6 1 8 4 1 4 4 10.2 8 1 12 12 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y PRLINE PRLINE PRLINE MKTPLCITEM VENDORPACKCODE VENDORPACKQUANTIT Y PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE PRLINE

Type
INTEGER INTEGER UPPER ALN YORN UPPER AMOUNT ALN ALN ALN ALN ALN INTEGER

Column Name
PRLINENUM POLINENUM CATEGORY REMARK SERVICE LOCATION LOADEDCOST PRORATESERVICE AGREEMENTPONUM AGREEMENTPOTYPE CONVERTTORFQ RFQNUM RFQLINENUM INSPECTIONREQUIRED RFQLINEID POLINEID LINECOST

INSPECTIONREQUIRED ALN RFQLINEID POLINEID LINECOST2 CURRENCYCODE2 MKTPLCITEM VENDORPACKCODE INTEGER INTEGER DECIMAL UPPER YORN ALN

VENDORPACKQUANTI TY ALN

147

Chapter 3

MAX_PR_INTERFACE Table Column Name Type

MAXIMO Tables Length Nulls Table
12 1 50 50 36 36 36 36 20 20 10 10 10 10.2 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y PRLINE COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES

Column Name
VENDORWAREHOUSE TYPE NAME NAME ADDRESS1 ADDRESS2 ADDRESS3 ADDRESS4 PHONE FAX CO1 CO2 CO3 CO4 CO5 CO6 CO7 CO8 CO9 CO10 CO11 CO12

VENDORWAREHOUSE ALN COMPANYTYPE MFGNAME NAME ADDRESS1 ADDRESS2 ADDRESS3 ADDRESS4 PHONE FAX CO1 CO2 CO3 CO4 CO5 CO6 CO7 CO8 CO9 CO10 CO11 CO12 ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN DECIMAL

DATETIME 10 ALN AMOUNT 10 10.2

DATETIME 10 INTEGER YORN ALN 4 1 10

DATETIME 10

148

Using the Integration Module

MAX_PR_INTERFACE Table Column Name
CO13 COMPANYLOC REGISTRATION1 REGISTRATION2 REGISTRATION3 APCONTROLACC APSUSPENSEACC RBNIACC PAYVENDOR BANKACCOUNT REGISTRATION4 REGISTRATION5 REMITADDRESS1 REMITADDRESS2 REMITADDRESS3 REMITADDRESS4 REMITCONTACT HOMEPAGE BANKNUM DUNSNUM TAXEXEMPTCODE TAXEXEMPTNUM

MAXIMO Tables Length Nulls Table
15.2 8 20 20 20 20 20 20 8 20 20 20 36 36 36 36 50 124 16 16 1 20 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES

Type
DECIMAL UPPER ALN ALN ALN ALN ALN ALN UPPER UPPER ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN

Column Name
CO13 LOCATION REGISTRATION1 REGISTRATION2 REGISTRATION3 APCONTROLACC APSUSPENSEACC RBNIACC PAYVENDOR BANKACCOUNT REGISTRATION4 REGISTRATION5 REMITADDRESS1 REMITADDRESS2 REMITADDRESS3 REMITADDRESS4 REMITCONTACT HOMEPAGE BANKNUM DUNSNUM TAXEXEMPTCODE TAXEXEMPTNUM

149

Chapter 3

MAX_PR_INTERFACE Table Column Name Type

MAXIMO Tables Length Nulls Table
1 1 Y Y COMPANIES COMPANIES

Column Name
ECOMMERCEENABLED DISABLED

ECOMMERCEENABLED ALN DISABLED ALN

POSITION

ALN

24

Y

COMPCONTACT POSITION

ITMDESCRIPTION ITEMLONGDESC STOCKTYPE LOTTYPE CAPITALIZED ROTATING ISSUEUNIT ROWSTAMP MEMO USERDATA1 USERDATA2 USERDATA3 USERDATA4 USERDATA5 USERDATA6 USERDATA7 USERDATA8

ALN ALN ALN UPPER YORN YORN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN

80 2000 8 5 1 1 8 40 50 1 1 1 1 1 1 1 1

Y Y Y Y Y Y Y

ITEM

DESCRIPTION

ITEM ITEM ITEM ITEM INVENTORY

STOCKTYPE LOTTYPE CAPITALIZED ROTATING ISSUEUNIT

Y Y Y Y Y Y Y Y Y

PRSTATUS

MEMO

150

Using the Integration Module

MAX_PR_INTERFACE Table Column Name
USERDATA9 USERDATA10 TOTALLINES

MAXIMO Tables Length Nulls Table
1 1 4 Y Y Y

Type
ALN ALN INTEGER

Column Name

BATCHID BATCHLINEID UTRANSTYPE SOURCEID SOURCESYSID OWNERSYSID EXTERNALREFID APISITE

ALN INTEGER ALN ALN ALN ALN ALN ALN

25 4 25 25 10 10 10 256

Y Y Y Y Y Y Y Y PR PR PR PR SOURCEID SOURCESYSID OWNERSYSID EXTERNALREFID

IMPORTSTATUS IMPORTTIMESTAMP IMPORTMESSAGE

ALN

25

Y Y Y

DATETIME 10 ALN 2000

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.
MAX_PO_INTERFACE Table Column Name
PONUM PODESCRIPTION PURCHASEAGENT ORDERDATE REQUIREDDATE FOLLOWUPDATE POTYPE ORIGINALPONUM STATUS STATUSDATE VENDOR CONTACT FREIGHTTERMS PAYMENTTERMS SHIPVIA CUSTOMERNUM FOB

MAXIMO Tables Table
PO PO PO PO PO PO PO PO PO PO PO PO PO PO PO PO PO

Type
UPPER ALN ALN

Length Nulls
8 80 50 N Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y

Column Name
PONUM DESCRIPTION PURCHASEAGENT ORDERDATE REQUIREDDATE FOLLOWUPDATE POTYPE ORIGINALPONUM STATUS STATUSDATE VENDOR CONTACT FREIGHTTERMS PAYMENTTERMS SHIPVIA CUSTOMERNUM FOB

DATETIME 10 DATETIME 10 DATE UPPER UPPER UPPER 4 6 8 6

DATETIME 10 UPPER ALN ALN ALN ALN ALN UPPER 8 50 50 20 20 16 20

152

Using the Integration Module

MAX_PO_INTERFACE Table Column Name
SHIPTO SHIPTOATTN BILLTO BILLTOATTN TOTALCOST CHANGEBY CHANGEDATE PRIORITY HISTORYFLAG PO1 PO2 PO3 PO4 PO5 PO6 PO7 PO8 PO9 PO10 CURRENCYCODE EXCHANGERATE EXCHANGEDATE

MAXIMO Tables Table
PO PO PO PO PO PO PO PO PO PO PO PO PO PO PO PO PO PO PO PO PO PO

Type
UPPER ALN UPPER ALN DECIMAL UPPER

Length Nulls
8 50 8 50 10 18 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y

Column Name
SHIPTO SHIPTOATTN BILLTO BILLTOATTN TOTALCOST CHANGEBY CHANGEDATE PRIORITY HISTORYFLAG PO1 PO2 PO3 PO4 PO5 PO6 PO7 PO8 PO9 PO10 CURRENCYCODE EXCHANGERATE EXCHANGEDATE

DATETIME 10 INTEGER YORN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN UPPER DECIMAL DATE 4 1 1 1 1 1 1 1 1 1 1 1 8 12 4

153

Chapter 3 MAX_PO_INTERFACE Table Column Name BUYAHEAD TOTALTAX1 TOTALTAX2 TOTALTAX3 INCLUSIVE1 INCLUSIVE2 INCLUSIVE3 INTERNAL TOTALTAX4 TOTALTAX5 INCLUSIVE4 INCLUSIVE5 STARTDATE ENDDATE PAYONRECEIPT WFID WFACTIVE BUYERCOMPANY ITEMNUM STORELOC MODELNUM CATALOGCODE MAXIMO Tables Table PO PO PO PO PO PO PO PO PO PO PO PO PO PO PO PO PO PO POLINE POLINE POLINE POLINE Type YORN DECIMAL DECIMAL DECIMAL YORN YORN YORN YORN DECIMAL DECIMAL YORN YORN DATE DATE ALN FLOAT ALN ALN UPPER UPPER ALN ALN Length Nulls 1 10 10 10 1 1 1 1 10 10 1 1 4 4 1 126 1 8 8 8 8 12 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Column Name BUYAHEAD TOTALTAX1 TOTALTAX2 TOTALTAX3 INCLUSIVE1 INCLUSIVE2 INCLUSIVE3 INTERNAL TOTALTAX4 TOTALTAX5 INCLUSIVE4 INCLUSIVE5 STARTDATE ENDDATE PAYONRECEIPT WFID WFACTIVE BUYERCOMPANY ITEMNUM STORELOC MODELNUM CATALOGCODE 154 .

Using the Integration Module MAX_PO_INTERFACE Table Column Name ORDERQTY ORDERUNIT UNITCOST CONVERSION RECEIVEDQTY RECEIVEDUNITCOST RECEIVEDTOTALCOST REJECTEDQTY VENDELIVERYDATE SUPERVISOR TAXED ENTERDATE ENTERBY DESCRIPTION PL1 PL2 PL3 PL4 PL5 WONUM REQUESTEDBY REQDELIVERYDATE MAXIMO Tables Table POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE Type DECIMAL ALN DECIMAL DECIMAL DECIMAL DECIMAL DECIMAL DECIMAL DATE UPPER YORN Length Nulls 15 8 10 15 15 10 10 15 4 8 1 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Column Name ORDERQTY ORDERUNIT UNITCOST CONVERSION RECEIVEDQTY RECEIVEDUNITCOST RECEIVEDTOTALCOST REJECTEDQTY VENDELIVERYDATE SUPERVISOR TAXED ENTERDATE ENTERBY DESCRIPTION PL1 PL2 PL3 PL4 PL5 WONUM REQUESTEDBY REQDELIVERYDATE DATETIME 10 UPPER ALN ALN ALN ALN ALN ALN UPPER UPPER DATE 18 50 1 1 1 1 1 10 18 4 155 .

Chapter 3 MAX_PO_INTERFACE Table Column Name ISSUE POLINENUM WPOPERATION PLIN1 PLIN2 PLIN3 PLIN4 PLIN5 EQNUM CHARGESTORE GLDEBITACCT GLCREDITACCT LINECOST TAX1CODE TAX1 TAX2CODE TAX2 TAX3CODE TAX3 SCHARGECODE RECEIPTREQD MANUFACTURER MAXIMO Tables Table POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE Type YORN INTEGER INTEGER ALN ALN ALN ALN ALN UPPER YORN ALN ALN DECIMAL UPPER DECIMAL UPPER DECIMAL UPPER DECIMAL UPPER YORN UPPER Length Nulls 1 4 4 1 1 1 1 1 8 1 20 20 10 8 10 8 10 8 10 8 1 8 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Column Name ISSUE POLINENUM WPOPERATION PLIN1 PLIN2 PLIN3 PLIN4 PLIN5 EQNUM CHARGESTORE GLDEBITACCT GLCREDITACCT LINECOST TAX1CODE TAX1 TAX2CODE TAX2 TAX3CODE TAX3 SCHARGECODE RECEIPTREQD MANUFACTURER 156 .

2 10 8 4 1 50 36 36 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Column Name SERVICE TAX4CODE TAX4 TAX5CODE TAX5 CATEGORY REMARK LOCATION LOADEDCOST PRORATESERVICE AGREEMENTPONUM AGREEMENTPOTYPE RECEIPTSCOMPLETE INSPECTIONREQUIRED PRORATECOST POLINEID PRNUM PRLINENUM INSPECTIONREQUIRED ALN PRORATECOST POLINEID PRNUM PRLINENUM COMPANYTYPE NAME ADDRESS1 ADDRESS2 DECIMAL DECIMAL ALN INTEGER ALN ALN ALN ALN COMPANIES TYPE COMPANIES NAME COMPANIES ADDRESS1 COMPANIES ADDRESS2 157 .Using the Integration Module MAX_PO_INTERFACE Table Column Name SERVICE TAX4CODE TAX4 TAX5CODE TAX5 CATEGORY REMARK LOCATION LOADEDCOST PRORATESERVICE AGREEMENTPONUM AGREEMENTPOTYPE RECEIPTSCOMPLETE MAXIMO Tables Table POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE PR PRLINE Type ALN UPPER DECIMAL UPPER DECIMAL UPPER ALN UPPER DECIMAL ALN ALN ALN ALN Length Nulls 1 8 10 8 10 4 50 8 10 1 8 6 1 1 10.

Chapter 3 MAX_PO_INTERFACE Table Column Name ADDRESS3 ADDRESS4 PHONE FAX CO1 CO2 CO3 CO4 CO5 CO6 CO7 CO8 CO9 CO10 CO11 CO12 CO13 COMPANYLOC REGISTRATION1 REGISTRATION2 REGISTRATION3 APCONTROLACC MAXIMO Tables Table Column Name Type ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN UPPER ALN ALN ALN ALN Length Nulls 36 36 20 20 1 1 1 1 1 1 1 1 1 1 1 1 1 8 20 20 20 20 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y COMPANIES ADDRESS3 COMPANIES ADDRESS4 COMPANIES PHONE COMPANIES FAX COMPANIES CO1 COMPANIES CO2 COMPANIES CO3 COMPANIES CO4 COMPANIES CO5 COMPANIES CO6 COMPANIES CO7 COMPANIES CO8 COMPANIES CO9 COMPANIES CO10 COMPANIES CO11 COMPANIES CO12 COMPANIES CO13 COMPANIES LOCATION COMPANIES REGISTRATION1 COMPANIES REGISTRATION2 COMPANIES REGISTRATION3 COMPANIES APCONTROLACC 158 .

Using the Integration Module MAX_PO_INTERFACE Table Column Name APSUSPENSEACC RBNIACC PAYVENDOR BANKACCOUNT REGISTRATION4 REGISTRATION5 POLONGDESC POLINELONGDESC USERDATA1 USERDATA2 USERDATA3 USERDATA4 USERDATA5 USERDATA6 USERDATA7 USERDATA8 USERDATA9 USERDATA10 BATCHID MAXIMO Tables Table Column Name Type ALN ALN UPPER UPPER ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN Length Nulls 20 20 8 20 20 20 2000 2000 1 1 1 1 1 1 1 1 1 1 25 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y COMPANIES APSUSPENSEACC COMPANIES RBNIACC COMPANIES PAYVENDOR COMPANIES BANKACCOUNT COMPANIES REGISTRATION4 COMPANIES REGISTRATION5 159 .

Chapter 3 MAX_PO_INTERFACE Table Column Name BATCHLINEID UTRANSTYPE SOURCEID APISEQ APISITE APISYNC IMPORTSTATUS IMPORTTIMESTAMP IMPORTMESSAGE MAXIMO Tables Table Column Name Type INTEGER ALN ALN INTEGER ALN INTEGER ALN Length Nulls 4 25 25 4 256 4 40 Y Y Y Y Y Y Y Y Y PO POLINE SOURCEID APISEQ POLINE APISYNC DATETIME 10 ALN 2000 160 .

They are there to separate information coming from different tables or to group sets of data.Using the Integration Module MAX_POX_INTERFACE Table The MAX_POX_INTERFACE table receives purchase order update data from Oracle Financials. MAX_POX_INTERFACE Table Column Name PONUM STATUS STATUSDATE CHANGEBY CHANGEDATE PO1 PO2 PO3 PO4 PO5 PO6 PO7 PO8 PO9 PO10 MEMO POTYPE MAXIMO Tables Length 8 6 Type UPPER UPPER Nulls Table N Y Y N Y Y Y Y Y Y Y Y Y Y Y Y Y PO PO PO PO PO PO PO PO PO PO PO PO PO PO PO POSTATUS PO Column Name PONUM STATUS STATUSDATE CHANGEBY CHANGEDATE PO1 PO2 PO3 PO4 PO5 PO6 PO7 PO8 PO9 PO10 MEMO POTYPE DATETIME 10 UPPER 18 DATETIME 10 ALN ALN ALN ALN ALN AMOUNT 10 10 10 10 10 10 DATETIME 10 DECIMAL INTEGER YORN ALN ALN 15 4 1 25 6 161 . Data is sent to the following MAXIMO tables. Empty rows in the table are not physical rows in the database.

Chapter 3 MAX_POX_INTERFACE Table Column Name ORIGINALPONUM USERDATA1 USERDATA2 USERDATA3 USERDATA4 USERDATA5 USERDATA6 USERDATA7 USERDATA8 USERDATA9 USERDATA10 ROWSTAMP BATCHID BATCHLINEID UTRANSTYPE SOURCEID APISEQ APISITE IMPORTSTATUS MAXIMO Tables Length 8 1 1 1 1 1 1 1 1 1 1 40 25 4 25 25 4 256 25 Type ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN INTEGER ALN ALN INTEGER ALN ALN Nulls Table Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y PO POLINE PO Column Name ORIGINALPONUM SOURCEID APISEQ IMPORTTIMESTAMP DATETIME 10 IMPORTMESSAGE ALN 2000 162 .

Empty rows in the table are not physical rows in the database. This interface tables sends data to two MAXIMO tables: MATRECTRANS and SERVRECTRANS. MAX_RCV_INTERFACE Table Column Name ITEMNUM TOSTORELOC TRANSDATE ACTUALDATE QUANTITY RECEIVEDUNIT ISSUETYPE UNITCOST ACTUALCOST PONUM INVOICENUM REJECTCODE REJECTQTY REJECTCOST CONVERSION MATRECTRANS Table Length 30 8 Type UPPER UPPER Nulls Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Column Name ITEMNUM TOSTORELOC TRANSDATE ACTUALDATE QUANTITY RECEIVEDUNIT ISSUETYPE UNITCOST ACTUALCOST PONUM INVOICENUM REJECTCODE REJECTQTY DATETIME 10 DATETIME 10 DECIMAL ALN UPPER AMOUNT AMOUNT UPPER UPPER UPPER DECIMAL DECIMAL DECIMAL 15 8 8 10 10 8 8 6 15 15 15 CONVERSION 163 .Using the Integration Module MAX_RCV_INTERFACE Table The MAX_RCV_INTERFACE table receives receipt data from Oracle Financials. The following table shows the mapping for the MAX_RCV_INTERFACE and MATRECTRANS tables. They are there to separate information coming from different tables or to group sets of data.

Chapter 3 MAX_RCV_INTERFACE Table Column Name WONUM EQNUM SERIALNUM ENTERBY IT1 IT2 IT3 IT4 IT5 OUTSIDE WPOPERATION ISSUETO PACKINGSLIPNUM POLINENUM ISSUE REQUESTEDBY TOTALCURBAL OLDAVGCOST ITIN1 ITIN2 ITIN3 TOBIN MATRECTRANS Table Length 10 8 15 18 10 10 10 15 10 1 4 8 20 4 1 20 15 10 10 10 10 8 Type UPPER UPPER UPPER UPPER ALN ALN ALN AMOUNT ALN YORN INTEGER UPPER ALN INTEGER YORN ALN AMOUNT AMOUNT ALN ALN ALN ALN Nulls Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Column Name WONUM EQNUM ENTERBY IT1 IT2 IT3 IT4 IT5 WPOPERATION WPOPERATION ISSUETO PACKINGSLIPNUM POLINENUM ISSUE REQUESTEDBY ITIN1 ITIN2 ITIN3 TOBIN 164 .

Using the Integration Module MAX_RCV_INTERFACE Table Column Name GLDEBITACCT GLCREDITACCT LINECOST LINECOST2 FINANCIALPERIOD CURRENCYCODE CURRENCYCODE2 EXCHANGERATE EXCHANGERATE2 CURRENCYUNITCOST MANUFACTURER MODELNUM CURRENCYLINECOST LOCATION DESCRIPTION REMARK FROMSTORELOC FROMBIN QTYHELD FROMLOT TOLOT LOADEDCOST MATRECTRANS Table Length 20 20 10 10 6 8 8 14 14 10 8 8 10 8 80 50 8 8 15 8 8 10 Type ALN ALN AMOUNT AMOUNT ALN UPPER UPPER DECIMAL DECIMAL DECIMAL UPPER ALN DECIMAL UPPER ALN ALN UPPER ALN DECIMAL ALN ALN DECIMAL Nulls Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Column Name GLDEBITACCT GLCREDITACCT LINECOST LINECOST2 FINANCIALPERIOD CURRENCYCODE EXCHANGERATE EXCHANGERATE2 CURRENCYUNITCOST MANUFACTURER MODELNUM CURRENCYLINECOST LOCATION DESCRIPTION REMARK FROMSTORELOC FROMBIN QTYHELD FROMLOT TOLOT LOADEDCOST 165 .

Chapter 3 MAX_RCV_INTERFACE Table Column Name TAX1CODE TAX1 TAX2CODE TAX2 TAX3CODE TAX3 TAX4CODE TAX4 TAX5CODE TAX5 PRORATED PRORATECOST STATUS STATUSDATE STATUSCHANGEBY CURBAL INVOICEDQTY CLAIMNUM APPROVED APPROVEDATE APPROVEBY MRNUM MATRECTRANS Table Length 8 10 8 10 8 10 8 10 8 10 1 10 8 Type ALN DECIMAL ALN DECIMAL ALN DECIMAL ALN DECIMAL ALN DECIMAL ALN DECIMAL ALN Nulls Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Column Name TAX1CODE TAX1 TAX2CODE TAX2 TAX3CODE TAX3 TAX4CODE TAX4 TAX5CODE TAX5 PRORATED PRORATECOST STATUS STATUSDATE STATUSCHANGEBY CURBAL DATETIME 10 ALN DECIMAL DECIMAL UPPER YORN 18 15 15 8 1 DATETIME 10 UPPER ALN 18 8 MRNUM 166 .

Using the Integration Module MAX_RCV_INTERFACE Table Column Name MRLINENUM MATRECTRANSID SERVRECTRANSID SOURCESYSID QTYREQUESTED OWNERSYSID EXTERNALREFID IT6 IT7 IT8 IT9 IT10 ITIN4 ITIN5 ITIN6 ITIN7 APISEQ SENDERSYSID RECID ROLLUP IBUPD LONGDESC MATRECTRANS Table Length 4 10 4 10 15 10 10 10 10 10 10 10 10 10 10 10 4 50 1 1 1 2000 Type INTEGER NUMBER INTEGER ALN DECIMAL ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN INTEGER ALN ALN ALN YORN ALN Nulls Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Column Name MRLINENUM MATRECTRANSID SOURCESYSID QTYREQUESTED OWNERSYSID EXTERNALREFID IT6 IT7 IT8 IT9 IT10 ITIN4 ITIN5 ITIN6 ITIN7 APISEQ SENDERSYSID 167 .

Chapter 3 MAX_RCV_INTERFACE Table Column Name ROWSTAMP USERDATA1 USERDATA2 USERDATA3 USERDATA4 USERDATA5 USERDATA6 USERDATA7 USERDATA8 USERDATA9 USERDATA10 BATCHID BATCHLINEID UTRANSTYPE SOURCEID APISITE IMPORTSTATUS IMPORTTIMESTAMP IMPORTMESSAGE MATRECTRANS Table Length 40 1 1 1 1 1 1 1 1 1 1 25 4 25 25 256 25 Type ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN INTEGER ALN ALN ALN ALN Nulls N Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Column Name SOURCEID DATETIME 10 ALN 2000 168 .

Empty rows in the table are not physical rows in the database. MAX_RCV_INTERFACE Table Column Name ITEMNUM TOSTORELOC TRANSDATE ACTUALDATE QUANTITY RECEIVEDUNIT ISSUETYPE UNITCOST ACTUALCOST PONUM INVOICENUM REJECTCODE REJECTQTY REJECTCOST CONVERSION WONUM EQNUM SERIALNUM SERVRECTRANS Table Length 30 8 Type UPPER UPPER Nulls Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Column Name DATETIME 10 DATETIME 10 DECIMAL ALN UPPER AMOUNT AMOUNT UPPER UPPER UPPER DECIMAL DECIMAL DECIMAL UPPER UPPER UPPER 15 8 8 10 10 8 8 6 15 15 15 10 8 15 TRANSDATE ENTERDATE QUANTITY UNITCOST PONUM INVOICENUM REJECTQTY REJECTCOST WONUM EQNUM 169 . They are there to separate information coming from different tables or to group sets of data.Using the Integration Module The following table shows the mapping for the MAX_RCV_INTERFACE and SERVRECTRANS tables.

Chapter 3 MAX_RCV_INTERFACE Table Column Name ENTERBY IT1 IT2 IT3 IT4 IT5 OUTSIDE WPOPERATION ISSUETO PACKINGSLIPNUM POLINENUM ISSUE REQUESTEDBY TOTALCURBAL OLDAVGCOST ITIN1 ITIN2 ITIN3 TOBIN GLDEBITACCT GLCREDITACCT LINECOST SERVRECTRANS Table Length 18 10 10 10 15 10 1 4 8 20 4 1 20 15 10 10 10 10 8 20 20 10 Type UPPER ALN ALN ALN AMOUNT ALN YORN INTEGER UPPER ALN INTEGER YORN ALN AMOUNT AMOUNT ALN ALN ALN ALN ALN ALN AMOUNT Nulls Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Column Name ENTERBY SS1 OUTSIDE WPOPERATION POLINENUM SSPL1 SSPL2 SSPL3 GLDEBITACCT GLCREDITACCT LINECOST 170 .

Using the Integration Module MAX_RCV_INTERFACE Table Column Name LINECOST2 FINANCIALPERIOD CURRENCYCODE CURRENCYCODE2 EXCHANGERATE EXCHANGERATE2 CURRENCYUNITCOST MANUFACTURER MODELNUM CURRENCYLINECOST LOCATION DESCRIPTION REMARK FROMSTORELOC FROMBIN QTYHELD FROMLOT TOLOT LOADEDCOST TAX1CODE TAX1 TAX2CODE SERVRECTRANS Table Length 10 6 8 8 14 14 10 8 8 10 8 80 50 8 8 15 8 8 10 8 10 8 Type AMOUNT ALN UPPER UPPER DECIMAL DECIMAL DECIMAL UPPER ALN DECIMAL UPPER ALN ALN UPPER ALN DECIMAL ALN ALN DECIMAL ALN DECIMAL ALN Nulls Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Column Name LINECOST2 FINANCIALPERIOD CURRENCYCODE EXCHANGERATE EXCHANGERATE2 CURRENCYUNITCOST CURRENCYLINECOST LOCATION DESCRIPTION REMARK 171 .

Chapter 3 MAX_RCV_INTERFACE Table Column Name TAX2 TAX3CODE TAX3 TAX4CODE TAX4 TAX5CODE TAX5 PRORATED PRORATECOST STATUS STATUSDATE STATUSCHANGEBY CURBAL INVOICEDQTY CLAIMNUM APPROVED APPROVEDATE APPROVEBY MRNUM MRLINENUM MATRECTRANSID SERVRECTRANSID SERVRECTRANS Table Length 10 8 10 8 10 8 10 1 10 8 Type DECIMAL ALN DECIMAL ALN DECIMAL ALN DECIMAL ALN DECIMAL ALN Nulls Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Column Name DATETIME 10 ALN DECIMAL DECIMAL UPPER YORN 18 15 15 8 1 CLAIMNUM APPROVED APPROVEDATE APPROVEBY MRNUM MRLINENUM DATETIME 10 UPPER ALN INTEGER NUMBER INTEGER 18 8 4 10 4 SERVRECTRANSID 172 .

Using the Integration Module MAX_RCV_INTERFACE Table Column Name SOURCESYSID QTYREQUESTED OWNERSYSID EXTERNALREFID IT6 IT7 IT8 IT9 IT10 ITIN4 ITIN5 ITIN6 ITIN7 APISEQ SENDERSYSID RECID ROLLUP IBUPD LONGDESC ROWSTAMP USERDATA1 USERDATA2 SERVRECTRANS Table Length 10 15 10 10 10 10 10 10 10 10 10 10 10 4 50 1 1 1 2000 40 1 1 Type ALN DECIMAL ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN INTEGER ALN ALN ALN YORN ALN ALN ALN ALN Nulls Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N Y Y Column Name SOURCESYSID OWNERSYSID EXTERNALREFID APISEQ SENDERSYSID ROLLUP 173 .

Chapter 3 MAX_RCV_INTERFACE Table Column Name USERDATA3 USERDATA4 USERDATA5 USERDATA6 USERDATA7 USERDATA8 USERDATA9 USERDATA10 BATCHID BATCHLINEID UTRANSTYPE SOURCEID APISITE IMPORTSTATUS IMPORTTIMESTAMP IMPORTMESSAGE SERVRECTRANS Table Length 1 1 1 1 1 1 1 1 25 4 25 25 256 25 Type ALN ALN ALN ALN ALN ALN ALN ALN ALN INTEGER ALN ALN ALN ALN Nulls Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Column Name SOURCEID DATETIME 10 ALN 2000 174 .

Data is sent from the following MAXIMO tables.Using the Integration Module MOUT_PO_INTERFACE Table The MOUT_PO_INTERFACE table sends purchase order data from MAXIMO to Oracle Financials. The mappings displayed are the defaults. they either separate information that comes from different tables or they group different sets of data. NOTE: Empty rows in the table are not physical rows in the database. MOUT_PO_INTERFACE Table Column Name PONUM PODESCRIPTION PURCHASEAGENT ORDERDATE REQUIREDDATE FOLLOWUPDATE POTYPE ORIGINALPONUM STATUS STATUSDATE VENDOR CONTACT FREIGHTTERMS PAYMENTTERMS SHIPVIA MAXIMO Tables Length Nulls Table 8 50 50 N Y Y Y Y Y Y Y Y Y Y Y Y Y Y PO PO PO PO PO PO PO PO PO PO PO PO PO PO PO Type UPPER ALN ALN Column Name PONUM DESCRIPTION PURCHASEAGENT ORDERDATE REQUIREDDATE FOLLOWUPDATE POTYPE ORIGINALPONUM STATUS STATUSDATE VENDOR CONTACT FREIGHTTERMS PAYMENTTERMS SHIPVIA DATETIME 10 DATETIME 10 DATE UPPER UPPER UPPER 4 6 8 6 DATETIME 10 UPPER ALN ALN ALN ALN 8 50 50 20 20 175 . and do not necessarily reflect your values. Your MAXIMO system catalogue determines your values.

Chapter 3 MOUT_PO_INTERFACE Table Column Name CUSTOMERNUM FOB SHIPTO SHIPTOATTN BILLTO BILLTOATTN TOTALCOST CHANGEBY CHANGEDATE PRIORITY HISTORYFLAG PO1 PO2 PO3 PO4 PO5 PO6 PO7 PO8 PO9 PO10 RECEIPTS MAXIMO Tables Length Nulls Table 16 20 8 50 8 50 10 18 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y PO PO PO PO PO PO PO PO PO PO PO PO PO PO PO PO PO PO PO PO PO PO Type ALN UPPER UPPER ALN UPPER ALN DECIMAL UPPER Column Name CUSTOMERNUM FOB SHIPTO SHIPTOATTN BILLTO BILLTOATTN TOTALCOST CHANGEBY CHANGEDATE PRIORITY HISTORYFLAG PO1 PO2 PO3 PO4 PO5 PO6 PO7 PO8 PO9 PO10 RECEIPTS DATETIME 10 INTEGER YORN ALN ALN ALN ALN ALN AMOUNT 4 1 10 10 10 10 10 10 DATETIME 10 DECIMAL INTEGER YORN ALN 15 4 1 20 176 .

Using the Integration Module MOUT_PO_INTERFACE Table Column Name CURRENCYCODE CURRENCYCODE2 EXCHANGERATE EXCHANGERATE2 EXCHANGEDATE BUYAHEAD TOTALTAX1 TOTALTAX2 TOTALTAX3 INCLUSIVE1 INCLUSIVE2 INCLUSIVE3 INTERNAL TOTALTAX4 TOTALTAX5 INCLUSIVE4 INCLUSIVE5 STARTDATE ENDDATE PAYONRECEIPT WFID MAXIMO Tables Length Nulls Table 8 8 14 14 4 1 10 10 10 1 1 1 1 10 10 1 1 4 4 1 126 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y PO MAXVAR PO PO PO PO PO PO PO PO PO PO PO PO PO PO PO PO PO PO PO Type UPPER UPPER DECIMAL DECIMAL DATE YORN DECIMAL DECIMAL DECIMAL YORN YORN YORN YORN DECIMAL DECIMAL YORN YORN DATE DATE ALN FLOAT Column Name CURRENCYCODE VARVALUE(BASCURREN CY2) EXCHANGERATE EXCHANGERATE2 EXCHANGEDATE BUYAHEAD TOTALTAX1 TOTALTAX2 TOTALTAX3 INCLUSIVE1 INCLUSIVE2 INCLUSIVE3 INTERNAL TOTALTAX4 TOTALTAX5 INCLUSIVE4 INCLUSIVE5 STARTDATE ENDDATE PAYONRECEIPT WFID 177 .

Chapter 3 MOUT_PO_INTERFACE Table Column Name WFACTIVE BUYERCOMPANY MNETSENT ECOMERROR ECOMSTATUSDATE SOURCESYSID OWNERSYSID EXTERNALREFID APISEQ SENDERSYSID MEMO ITEMNUM STORELOC MODELNUM CATALOGCODE ORDERQTY ORDERUNIT UNITCOST CONVERSION RECEIVEDQTY RECEIVEDUNITCOST MAXIMO Tables Length Nulls Table 1 8 12 254 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y PO PO PO PO PO PO PO PO POLINE PO POSTATUS POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE Type ALN ALN ALN ALN Column Name WFACTIVE BUYERCOMPANY MNETSENT ECOMERROR ECOMSTATUSDATE SOURCESYSID OWNERSYSID EXTERNALREFID APISEQ SENDERSYSID MEMO ITEMNUM STORELOC MODELNUM CATALOGCODE ORDERQTY ORDERUNIT UNITCOST CONVERSION RECEIVEDQTY RECEIVEDUNITCOST RECEIVEDTOTALCOST DATETIME 10 ALN ALN ALN INTEGER ALN ALN UPPER UPPER ALN ALN DECIMAL ALN DECIMAL DECIMAL DECIMAL DECIMAL 10 10 10 4 50 50 30 8 8 30 15 8 10 15 15 10 10 RECEIVEDTOTALCOST DECIMAL 178 .

Using the Integration Module MOUT_PO_INTERFACE Table Column Name REJECTEDQTY VENDELIVERYDATE TAXED ENTERDATE ENTERBY DESCRIPTION PL1 PL2 PL3 PL4 PL5 WONUM REQUESTEDBY REQDELIVERYDATE ISSUE POLINENUM WPOPERATION PLIN1 PLIN2 PLIN3 PLIN4 PLIN5 MAXIMO Tables Length Nulls Table 15 4 1 4 18 80 10 10 10 15 10 10 18 4 1 4 4 10 10 10 4 15 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE Type DECIMAL DATE ALN DATE ALN ALN ALN ALN ALN DECIMAL ALN ALN UPPER DATE YORN INTEGER INTEGER ALN ALN ALN DATE DECIMAL Column Name REJECTEDQTY VENDELIVERYDATE TAXED ENTERDATE ENTERBY DESCRIPTION PL1 PL2 PL3 PL4 PL5 WONUM REQUESTEDBY REQDELIVERYDATE ISSUE POLINENUM WPOPERATION PLIN1 PLIN2 PLIN3 PLIN4 PLIN5 179 .

Chapter 3 MOUT_PO_INTERFACE Table Column Name PCARDNUM PCARDTYPE PCARDEXPDATE MAXIMO Tables Length Nulls Table 30 20 7 4 10 10 10 10 10 10 10 10 10 8 1 20 20 10 10 8 10 8 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE Type ALN ALN ALN Column Name PCARDNUM PCARDTYPE PCARDEXPDATE PCARDVERIFICATION PL6 PL7 PL8 PL9 PL10 PLIN6 PLIN7 PLIN8 PLIN9 EQNUM CHARGESTORE GLDEBITACCT GLCREDITACCT LINECOST LINECOST TAX1CODE TAX1 TAX2CODE PCARDVERIFICATION ALN PL6 PL7 PL8 PL9 PL10 PLIN6 PLIN7 PLIN8 PLIN9 EQNUM CHARGESTORE GLDEBITACCT GLCREDITACCT LINECOST LINECOST2 TAX1CODE TAX1 TAX2CODE ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN UPPER ALN ALN DECIMAL DECIMAL UPPER DECIMAL UPPER 180 .

Using the Integration Module MOUT_PO_INTERFACE Table Column Name TAX2 TAX3CODE TAX3 SCHARGECODE RECEIPTREQD MANUFACTURER SERVICE TAX4CODE TAX4 TAX5CODE TAX5 SUPERVISOR CATEGORY REMARK LOCATION LOADEDCOST PRORATESERVICE AGREEMENTPONUM AGREEMENTPOTYPE RECEIPTSCOMPLETE MAXIMO Tables Length Nulls Table 10 8 10 8 1 8 1 8 10 8 10 8 4 50 8 10 1 8 6 1 1 10 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE POLINE Type DECIMAL UPPER DECIMAL UPPER YORN ALN UPPER UPPER DECIMAL UPPER DECIMAL ALN UPPER ALN UPPER DECIMAL ALN ALN ALN ALN Column Name TAX2 TAX3CODE TAX3 SCHARGECODE RECEIPTREQD MANUFACTURER SERVICE TAX4CODE TAX4 TAX5CODE TAX5 SUPERVISOR CATEGORY REMARK LOCATION LOADEDCOST PRORATESERVICE AGREEMENTPONUM AGREEMENTPOTYPE RECEIPTSCOMPLETE INSPECTIONREQUIRED PRORATECOST INSPECTIONREQUIRED ALN PRORATECOST DECIMAL 181 .

2 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y POLINE PR PRLINE POLINE POLINE COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES Type DECIMAL ALN INTEGER ALN INTEGER ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN DECIMAL DATE ALN DECIMAL Column Name POLINEID PRNUM PRLINENUM MRNUM MRLINENUM TYPE NAME NAME ADDRESS1 ADDRESS2 ADDRESS3 ADDRESS4 PHONE COMPCONTACT POSITION COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES FAX CO1 CO2 CO3 CO4 CO5 CO6 CO7 182 .Chapter 3 MOUT_PO_INTERFACE Table Column Name POLINEID PRNUM PRLINENUM MRNUM MRLINENUM COMPANYTYPE MFGNAME NAME ADDRESS1 ADDRESS2 ADDRESS3 ADDRESS4 PHONE POSITION FAX CO1 CO2 CO3 CO4 CO5 CO6 CO7 MAXIMO Tables Length Nulls Table 10 8 4 8 4 1 50 50 36 36 36 36 20 24 20 10 10 10 10 10 10 10.

Using the Integration Module MOUT_PO_INTERFACE Table Column Name CO8 CO9 CO10 CO11 CO12 CO13 COMPANYLOC REGISTRATION1 REGISTRATION2 REGISTRATION3 APCONTROLACC APSUSPENSEACC RBNIACC PAYVENDOR BANKACCOUNT REGISTRATION4 REGISTRATION5 ROWSTAMP ITEMDESCRIPTION ITEMLONGDESC STOCKTYPE LOTTYPE MAXIMO Tables Length Nulls Table 4 4 1 10 10 15 8 20 20 20 20 20 20 8 20 20 20 40 80 2000 8 5 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y ITEM ITEM STOCKTYPE LOTTYPE ITEM DESCRIPTION COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES Type DATE INTEGER ALN ALN DATE DECIMAL ALN ALN UPPER ALN ALN ALN ALN ALN ALN UPPER UPPER ALN ALN ALN ALN ALN Column Name CO8 CO9 CO10 CO11 CO12 CO13 LOCATION REGISTRATION1 REGISTRATION2 REGISTRATION3 APCONTROLACC APSUSPENSEACC RBNIACC PAYVENDOR BANKACCOUNT REGISTRATION4 REGISTRATION5 183 .

Chapter 3 MOUT_PO_INTERFACE Table Column Name CAPITALIZED ISSUEUNIT POLONGDESC POLINELONGDESC USERDATA1 USERDATA2 USERDATA3 USERDATA4 USERDATA5 USERDATA6 USERDATA7 USERDATA8 USERDATA9 USERDATA10 MKTPLCITEM VENDORPACKCODE MAXIMO Tables Length Nulls Table 1 8 2000 2000 1 1 1 1 1 1 1 1 1 1 1 12 12 12 4 25 10 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y POLINE POLINE POLINE POLINE MKTPLCITEM VENDORPACKCODE VENDORPACKQUANTIT Y VENDORWAREHOUSE ITEM INVENTORY Type ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN YORN ALN Column Name CAPITALIZED ISSUEUNIT VENDORPACKQUANTI TY ALN VENDORWAREHOUSE ALN TOTALLINES BATCHID BATCHLINEID INTEGER ALN INTEGER 184 .

Using the Integration Module MOUT_PO_INTERFACE Table Column Name UTRANSTYPE SOURCEID APISITE IMPORTSTATUS IMPORTTIMESTAMP IMPORTMESSAGE MAXIMO Tables Length Nulls Table 25 25 256 25 4 2000 Y Y Y Y Y Y PO SOURCEID Type ALN ALN ALN ALN DATE ALN Column Name 185 .

MOUT_RCV_INTERFACE Table Column Name ITEMNUM TOSTORELOC TRANSDATE ACTUALDATE QUANTITY RECEIVEDUNIT ISSUETYPE UNITCOST ACTUALCOST PONUM INVOICENUM REJECTCODE REJECTQTY MATRECTRANS Table Length Nulls Column Name 30 8 Y Y Y Y Y Y Y Y Y Y Y Y Y ITEMNUM TOSTORELOC TRANSDATE ACTUALDATE QUANTITY RECEIVEDUNIT ISSUETYPE UNITCOST ACTUALCOST PONUM INVOICENUM REJECTCODE REJECTQTY Type UPPER UPPER DATETIME 10 DATETIME 10 DECIMAL ALN UPPER AMOUNT AMOUNT UPPER UPPER UPPER DECIMAL 15 8 8 10 10 8 8 6 15 186 . and do not necessarily reflect your values. The mappings displayed are the defaults. they either separate information that comes from different tables or they group different sets of data. Your MAXIMO system catalogue determines your values. The following table shows the mapping for the MOUT_RCV_INTERFACE and MATRECTRANS tables. Data is transferred to the external financial application. NOTE: Empty rows in the table are not physical rows in the database.Chapter 3 MOUT_RCV_INTERFACE Table MAXIMO sends data to the MOUT_RCV_INTERFACE table from two tables: MATRECTRANS and SERVRECTRANS.

Using the Integration Module MOUT_RCV_INTERFACE Table Column Name REJECTCOST CONVERSION WONUM EQNUM ENTERBY IT1 IT2 IT3 IT4 IT5 OUTSIDE WPOPERATION ISSUETO PACKINGSLIPNUM POLINENUM ISSUE REQUESTEDBY TOTALCURBAL OLDAVGCOST ITIN1 ITIN2 ITIN3 MATRECTRANS Table Length Nulls Column Name 15 15 10 8 18 10 10 10 15 10 1 4 8 20 4 1 20 15 10 10 10 1 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y CONVERSION WONUM EQNUM ENTERBY IT1 IT2 IT3 IT4 IT5 OUTSIDE WPOPERATION ISSUETO PACKINGSLIPNUM POLINENUM ISSUE REQUESTEDBY TOTALCURBAL OLDAVGCOST ITIN1 ITIN2 ITIN3 Type DECIMAL DECIMAL UPPER UPPER UPPER ALN ALN ALN DECIMAL ALN YORN INTEGER UPPER ALN INTEGER YORN ALN AMOUNT AMOUNT ALN ALN ALN 187 .

Chapter 3 MOUT_RCV_INTERFACE Table Column Name TOBIN LOTNUM GLDEBITACCT GLCREDITACCT LINECOST LINECOST2 FINANCIALPERIOD CURRENCYCODE CURRENCYCODE2 EXCHANGERATE EXCHANGERATE2 CURRENCYUNITCOST MANUFACTURER MODELNUM CURRENCYLINECOST LOCATION DESCRIPTION REMARK FROMSTORELOC FROMBIN QTYHELD CLAIMNUM MATRECTRANS Table Length Nulls Column Name 8 8 20 20 10 10 6 8 8 14 14 10 8 8 10 8 80 50 8 8 15 8 Y Y Y Y N N Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y TOBIN LOTNUM GLDEBITACCT GLCREDITACCT LINECOST LINECOST2 FINANCIALPERIOD CURRENCYCODE MAXVAR EXCHANGERATE EXCHANGERATE2 CURRENCYUNITCOST MANUFACTURER MODELNUM CURRENCYLINECOST LOCATION DESCRIPTION REMARK FROMSTORELOC FROMBIN QTYHELD Type ALN UPPER ALN ALN AMOUNT AMOUNT ALN UPPER UPPER DECIMAL DECIMAL DECIMAL UPPER ALN DECIMAL UPPER ALN ALN UPPER ALN DECIMAL UPPER 188 .

Using the Integration Module MOUT_RCV_INTERFACE Table Column Name APPROVED APPROVEDATE APPROVEBY LONGDESC ROWSTAMP FROMLOT TOLOT LOADEDCOST TAX1CODE TAX1 TAX2CODE TAX2 TAX3CODE TAX3 TAX4CODE TAX4 TAX5CODE TAX5 PRORATED PRORATECOST STATUS STATUSDATE MATRECTRANS Table Length Nulls Column Name 1 Y Y Y Y N Y Y N Y Y Y Y Y Y Y Y Y Y N Y Y Y FROMLOT TOLOT LOADEDCOST TAX1CODE TAX1 TAX2CODE TAX2 TAX3CODE TAX3 TAX4CODE TAX4 TAX5CODE TAX5 PRORATED PRORATECOST STATUS STATUSDATE Type YORN DATETIME 10 UPPER ALN ALN ALN ALN AMOUNT ALN AMOUNT ALN AMOUNT ALN AMOUNT ALN AMOUNT ALN AMOUNT ALN AMOUNT ALN 18 2000 40 8 8 10 8 10 8 10 8 10 8 10 8 10 1 10 8 DATETIME 10 189 .

Chapter 3 MOUT_RCV_INTERFACE Table Column Name STATUSCHANGEBY CURBAL INVOICEDQTY MRNUM MRLINENUM MATRECTRANSID SERVRECTRANSID SOURCESYSID QTYREQUESTED OWNERSYSID EXTERNALREFID IT6 IT7 IT8 IT9 IT10 ITIN4 ITIN5 ITIN6 ITIN7 APISEQ SENDERSYSID MATRECTRANS Table Length Nulls Column Name 18 15 15 8 4 10 4 10 15 10 10 10 10 10 10 10 10 10 10 10 4 50 Y N Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y SOURCESYSID QTYREQUESTED OWNERSYSID EXTERNALREFID IT6 IT7 IT8 IT9 IT10 ITIN4 ITIN5 ITIN6 ITIN7 APISEQ SENDERSYSID STATUSCHANGEBY CURBAL FUTURE MRNUM MRLINENUM MATRECTRANSID Type ALN AMOUNT AMOUNT ALN INTEGER NUMBER INTEGER ALN DECIMAL ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN INTEGER ALN 190 .

Using the Integration Module MOUT_RCV_INTERFACE Table Column Name RECID ROLLUP USERDATA1 USERDATA2 USERDATA3 USERDATA4 USERDATA5 USERDATA6 USERDATA7 USERDATA8 USERDATA9 USERDATA10 BATCHID BATCHLINEID UTRANSTYPE SOURCEID APISITE IMPORTSTATUS IMPORTTIMESTAMP IMPORTMESSAGE MATRECTRANS Table Length Nulls Column Name 1 1 1 1 1 1 1 1 1 1 1 1 25 4 25 25 256 25 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y SOURCEID Type ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN INTEGER ALN ALN ALN ALN DATETIME 10 ALN 2000 191 .

MOUT_RCV_INTERFACE Table Column Name ITEMNUM TOSTORELOC TRANSDATE ACTUALDATE QUANTITY RECEIVEDUNIT ISSUETYPE UNITCOST ACTUALCOST PONUM INVOICENUM REJECTCODE REJECTQTY REJECTCOST CONVERSION WONUM SERVRECTRANS Table Length 30 8 Type UPPER UPPER Nulls Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Column Name DATETIME 10 DATETIME 10 DECIMAL ALN UPPER AMOUNT AMOUNT UPPER UPPER UPPER DECIMAL DECIMAL DECIMAL UPPER 15 8 8 10 10 8 8 6 15 15 15 10 TRANSDATE ENTERDATE QUANTITY UNITCOST PONUM INVOICENUM REJECTQTY REJECTCOST WONUM 192 . The mappings displayed are the defaults. and do not necessarily reflect your values. Your MAXIMO system catalogue determines your values. they either separate information that comes from different tables or they group different sets of data.Chapter 3 The following table shows the mapping for MOUT_RCV_INTERFACE and SERVRECTRANS. NOTE: Empty rows in the table are not physical rows in the database.

Using the Integration Module MOUT_RCV_INTERFACE Table Column Name EQNUM ENTERBY IT1 IT2 IT3 IT4 IT5 OUTSIDE WPOPERATION ISSUETO PACKINGSLIPNUM POLINENUM ISSUE REQUESTEDBY TOTALCURBAL OLDAVGCOST ITIN1 ITIN2 ITIN3 TOBIN LOTNUM GLDEBITACCT SERVRECTRANS Table Length 8 18 10 10 10 15 10 1 4 8 20 4 1 20 15 10 10 10 1 8 8 20 Type UPPER UPPER ALN ALN ALN DECIMAL ALN YORN INTEGER UPPER ALN INTEGER YORN ALN AMOUNT AMOUNT ALN ALN ALN ALN UPPER ALN Nulls Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Column Name EQNUM ENTERBY SS1 WPOPERATION WPOPERATION POLINENUM SSPL1 SSPL2 SSPL3 GLDEBITACCT 193 .

Chapter 3 MOUT_RCV_INTERFACE Table Column Name GLCREDITACCT LINECOST LINECOST2 FINANCIALPERIOD CURRENCYCODE CURRENCYCODE2 EXCHANGERATE EXCHANGERATE2 CURRENCYUNITCOST MANUFACTURER MODELNUM CURRENCYLINECOST LOCATION DESCRIPTION REMARK FROMSTORELOC FROMBIN QTYHELD CLAIMNUM APPROVED APPROVEDATE APPROVEBY SERVRECTRANS Table Length 20 10 10 6 8 8 14 14 10 8 8 10 8 80 50 8 8 15 8 1 Type ALN AMOUNT AMOUNT ALN UPPER UPPER DECIMAL DECIMAL DECIMAL UPPER ALN DECIMAL UPPER ALN ALN UPPER ALN DECIMAL UPPER YORN Nulls Y N N Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Column Name GLCREDITACCT LINECOST LINECOST2 FINANCIALPERIOD CURRENCYCODE MAXVAR EXCHANGERATE EXCHANGERATE2 CURRENCYUNITCOST CURRENCYLINECOST LOCATION DESCRIPTION REMARK CLAIMNUM APPROVED APPROVEDATE APPROVEBY DATETIME 10 UPPER 18 194 .

Using the Integration Module MOUT_RCV_INTERFACE Table Column Name LONGDESC ROWSTAMP FROMLOT TOLOT LOADEDCOST TAX1CODE TAX1 TAX2CODE TAX2 TAX3CODE TAX3 TAX4CODE TAX4 TAX5CODE TAX5 PRORATED PRORATECOST STATUS STATUSDATE STATUSCHANGEBY CURBAL INVOICEDQTY SERVRECTRANS Table Length 2000 40 8 8 10 8 10 8 10 8 10 8 10 8 10 1 10 8 Type ALN ALN ALN ALN AMOUNT ALN AMOUNT ALN AMOUNT ALN AMOUNT ALN AMOUNT ALN AMOUNT ALN AMOUNT ALN Nulls Y N Y Y N Y Y Y Y Y Y Y Y Y Y N Y Y Y Y N Y Column Name DATETIME 10 ALN AMOUNT AMOUNT 18 15 15 195 .

Chapter 3 MOUT_RCV_INTERFACE Table Column Name MRNUM MRLINENUM MATRECTRANSID SERVRECTRANSID SOURCESYSID QTYREQUESTED OWNERSYSID EXTERNALREFID IT6 IT7 IT8 IT9 IT10 ITIN4 ITIN5 ITIN6 ITIN7 APISEQ SENDERSYSID RECID ROLLUP USERDATA1 SERVRECTRANS Table Length 8 4 10 4 10 15 10 10 10 10 10 10 10 10 10 10 10 4 50 1 1 1 Type ALN INTEGER NUMBER INTEGER ALN DECIMAL ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN INTEGER ALN ALN ALN ALN Nulls Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Column Name MRNUM MRLINENUM SERVRECTRANSID SOURCESYSID OWNERSYSID EXTERNALREFID APISEQ SENDERSYSID ROLLUP 196 .

Using the Integration Module MOUT_RCV_INTERFACE Table Column Name USERDATA2 USERDATA3 USERDATA4 USERDATA5 USERDATA6 USERDATA7 USERDATA8 USERDATA9 USERDATA10 BATCHID BATCHLINEID UTRANSTYPE SOURCEID APISITE IMPORTSTATUS IMPORTTIMESTAMP IMPORTMESSAGE SERVRECTRANS Table Length 1 1 1 1 1 1 1 1 1 25 4 25 25 256 25 Type ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN INTEGER ALN ALN ALN ALN Nulls Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Column Name SOURCEID DATETIME 10 ALN 2000 197 .

The values displayed in the following tables are examples.Chapter 3 Item Interface Tables This section provides the mapping for the interface tables that the APIs use to transfer item data between MAXIMO and Oracle Financials. and do not necessarily reflect your actual values. MAX_ITM_INTERFACE Table Column Name ITEMNUM DESCRIPTION ROTATING STOCKTYPE LOTTYPE CAPITALIZED MSDSNUM OUTSIDE MAXIMO Tables Length Nulls Table 8 50 1 8 5 1 10 1 N Y Y Y Y Y Y Y ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM Type UPPER ALN YORN ALN UPPER YORN ALN YORN Column Name ITEMNUM DESCRIPTION ROTATING STOCKTYPE LOTTYPE CAPITALIZED MSDSNUM OUTSIDE 198 . 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. It also receives item data from the following MAXIMO tables and transfers it to Oracle Financials. MAX_ITM_INTERFACE The MAX_ITM_INTERFACE table receives item data from Oracle Financials and sends it to the following MAXIMO tables. Empty rows in the table are not physical rows in the database. Your MAXIMO system catalogue determines your values. They are there to separate information coming from different tables or to group sets of data.

Using the Integration Module MAX_ITM_INTERFACE Table Column Name IN1 IN2 IN3 IN4 IN5 IN6 IN7 IN8 IN9 IN10 IN11 IN12 IN13 IN14 IN15 IN16 IN17 IN18 IN19 IN20 IN21 IN22 MAXIMO Tables Length Nulls Table 10 10 10 10 10 10 10 10 10 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM Type ALN ALN ALN ALN ALN ALN ALN ALN AMOUNT Column Name IN1 IN2 IN3 IN4 IN5 IN6 IN7 IN8 IN9 IN10 IN11 IN12 IN13 IN14 IN15 IN16 IN17 IN18 IN19 IN20 IN21 IN22 DATETIME 10 DECIMAL DECIMAL ALN INTEGER YORN ALN AMOUNT ALN ALN ALN ALN 15.2 10 4 1 10 10.2 15.2 10 10 10 10 DATETIME 10 199 .

Chapter 3 MAX_ITM_INTERFACE Table Column Name IN23 IN24 IN25 IN26 IN27 TAX1CODE TAX2CODE TAX3CODE TAX4CODE TAX5CODE SPAREPARTAUTOADD HAZARDID CLASSSTRUCTUREID INSPECTIONREQUIRED LDKEY LOCATION BINNUM MINLEVEL MAXLEVEL CATEGORY ORDERUNIT ISSUEUNIT MAXIMO Tables Length Nulls Table 10.2 10 10 10 10 8 8 8 8 8 1 8 8 1 4 8 8 15 15 4 8 8 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM INVENTORY INVENTORY INVENTORY INVENTORY INVENTORY INVENTORY INVENTORY Type DECIMAL ALN ALN ALN ALN UPPER UPPER UPPER UPPER UPPER ALN ALN ALN ALN INTEGER UPPER ALN DECIMAL DECIMAL UPPER ALN ALN Column Name IN23 IN24 IN25 IN26 IN27 TAX1CODE TAX2CODE TAX3CODE TAX4CODE TAX5CODE SPAREPARTAUTOADD HAZARDID CLASSSTRUCTUREID INSPECTIONREQUIRED LDKEY LOCATION BINNUM MINLEVEL MAXLEVEL CATEGORY ORDERUNIT ISSUEUNIT 200 .

Using the Integration Module MAX_ITM_INTERFACE Table Column Name CONVERSION QUANTITY LOTNUM CURBAL PHYSCNT PHYSCNTDATE IB1 IB2 IB3 IB4 IB5 RECONCILED ORDERQTY STDCOST AVGCOST LASTCOST COSTCURRENCYCODE MAXIMO Tables Length Nulls Table 15 15 8 15 15 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y INVENTORY INVTRANS INVBALANCES INVTRANS INVBALANCES INVBALANCES INVBALANCES INVBALANCES INVBALANCES INVBALANCES INVBALANCES INVBALANCES INVENTORY INVENTORY INVENTORY INVENTORY EXCHANGE EXCHANGE EXCHANGE Y Y Y INVENTORY INVENTORY INVENTORY Type DECIMAL DECIMAL UPPER DECIMAL DECIMAL Column Name CONVERSION QUANTITY LOTNUM CURBAL PHYSCNT PHYSCNTDATE IB1 IB2 IB3 IB4 IB5 RECONCILED ORDERQTY STDCOST AVGCOST LASTCOST CURRENCYCODE CURRENCYCODE EXCHANGERATE LASTISSUEDATE ISSUEYTD ISSUE1YRAGO DATETIME 10 ALN ALN ALN ALN ALN YORN DECIMAL AMOUNT AMOUNT AMOUNT ALN 1 1 1 1 1 1 15 10 10 10 8 8 12.5 COSTCURRENCYCODE2 ALN EXCHANGERATE2 LASTISSUEDATE ISSUEYTD ISSUE1YRAGO DECIMAL DATETIME 10 DECIMAL DECIMAL 15 15 201 .

2 10 10 10 10 10 20 20 20 20 VENDOR UPPER 8 Y INVVENDOR VENDOR 202 .Chapter 3 MAX_ITM_INTERFACE Table Column Name ISSUE2YRAGO ISSUE3YRAGO ABCTYPE CCF SSTOCK DELIVERYTIME IL1 IL2 IL3 IL4 IL5 IL6 IL7 IL8 IL9 IL10 GLACCOUNT CONTROLACC SHRINKAGEACC INVCOSTADJACC MAXIMO Tables Length Nulls Table 15 15 1 4 15 4 10 10 10 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y INVENTORY INVENTORY INVENTORY INVENTORY INVENTORY INVENTORY INVENTORY INVENTORY INVENTORY INVENTORY INVENTORY INVENTORY INVENTORY INVENTORY INVENTORY INVENTORY INVENTORY INVENTORY INVENTORY INVENTORY Type DECIMAL DECIMAL UPPER INTEGER DECIMAL INTEGER ALN ALN ALN Column Name ISSUE2YRAGO ISSUE3YRAGO ABCTYPE CCF SSTOCK DELIVERYTIME IL1 IL2 IL3 IL4 IL5 IL6 IL7 IL8 IL9 IL10 GLACCOUNT CONTROLACC SHRINKAGEACC INVCOSTADJACC DATETIME 10 DECIMAL ALN ALN ALN ALN ALN ALN ALN ALN ALN 15.

2 10 DATETIME 10 INTEGER DECIMAL 4 10 DATETIME 10 ALN 124 COMPANYTYPE NAME ADDRESS1 ADDRESS2 ADDRESS3 ADDRESS4 ALN ALN ALN ALN ALN ALN 1 50 36 36 36 36 Y Y Y Y Y Y COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES TYPE NAME ADDRESS1 ADDRESS2 ADDRESS3 ADDRESS4 203 .Using the Integration Module MAX_ITM_INTERFACE Table Column Name MANUFACTURER MODELNUM CATALOGCODE IV1 IV2 IV3 IVCO1 IVCO2 IVCO3 BIDPRICE BIDDATE PROMDELIVERYTIME VENDORLASTCOST LASTDATE CATALOGWEBPAGE MAXIMO Tables Length Nulls Table 8 8 12 10 10 1 10 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y INVVENDOR INVVENDOR INVVENDOR INVVENDOR INVVENDOR INVVENDOR INVVENDOR INVVENDOR INVVENDOR INVVENDOR INVVENDOR INVVENDOR INVVENDOR INVVENDOR INVVENDOR Type UPPER ALN ALN ALN ALN ALN ALN Column Name MANUFACTURER MODELNUM CATALOGCODE IV1 IV2 IV3 IVCO1 IVCO2 IVCO3 BIDPRICE BIDDATE PROMDELIVERYTIME LASTCOST LASTDATE CATALOGWEBPAGE DATETIME 10 DECIMAL DECIMAL 15.

2 204 .Chapter 3 MAX_ITM_INTERFACE Table Column Name CONTACT POSITION PHONE FAX FOB FREIGHTTERMS SHIPVIA PAYMENTTERMS CUSTOMERNUM CO1 CO2 CO3 CO4 CO5 CO6 CO7 CO8 CO9 CO10 CO11 CO12 CO13 MAXIMO Tables Length Nulls Table 50 24 20 20 20 50 20 20 16 10 10 10 10 10 10 10.2 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y COMPANIES Type ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN AMOUNT Column Name CONTACT COMPCONTACT POSITION COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES PHONE FAX FOB FREIGHTTERMS SHIPVIA PAYMENTTERMS CUSTOMERNUM CO1 CO2 CO3 CO4 CO5 CO6 CO7 CO8 CO9 CO10 CO11 CO12 CO13 DATETIME 10 INTERGER YORN ALN 4 1 10 DATETIME 10 DECIMAL 15.

2 10 38 1 CHANGEBY CHANGEDATE UPPER 18 Y Y COMPANIES COMPANIES CHANGEBY CHANGEDATE DATETIME 10 205 .2 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES LOCATIONS LOCATIONS LOCATIONS LOCATIONS LOCATIONS LOCATIONS LOCATIONS LOCATIONS LOCATIONS LOCATIONS LOCATIONS LOCATIONS LOCATIONS LOCATIONS Type ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN DECIMAL Column Name CO14 CO15 CO16 CO17 CO18 LO2 LO3 LO4 LO5 LO6 LO7 LO8 LO9 LO10 LO11 LO12 LO13 LO14 LO15 DATETIME 10 DECIMAL DECIMAL ALN DECIMAL ALN 15.Using the Integration Module MAX_ITM_INTERFACE Table Column Name CO14 CO15 CO16 CO17 CO18 LO2 LO3 LO4 LO5 LO6 LO7 LO8 LO9 LO10 LO11 LO12 LO13 LO14 LO15 MAXIMO Tables Length Nulls Table 10 10 10 10 10 10 10 10 10 10 10 10 10.2 15.

Chapter 3 MAX_ITM_INTERFACE Table Column Name INCLUSIVE1 INCLUSIVE2 INCLUSIVE3 INCLUSIVE4 INCLUSIVE5 CURRENCYCODE COMPANYLOC REGISTRATION1 REGISTRATION2 REGISTRATION3 REGISTRATION4 REGISTRATION5 APCONTROLACC APSUSPENSEACC RBNIACC PAYVENDOR BANKACCOUNT DISABLED REMITCONTACT REMITADDRESS1 REMITADDRESS2 REMITADDRESS3 MAXIMO Tables Length Nulls Table 1 1 1 1 1 8 8 20 20 20 20 20 20 20 20 8 20 1 50 36 36 36 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES Type YORN YORN YORN YORN YORN UPPER UPPER ALN ALN ALN ALN ALN ALN ALN ALN UPPER UPPER YORN ALN ALN ALN ALN Column Name INCLUSIVE1 INCLUSIVE2 INCLUSIVE3 INCLUSIVE4 INCLUSIVE5 CURRENCYCODE LOCATION REGISTRATION1 REGISTRATION2 REGISTRATION3 REGISTRATION4 REGISTRATION5 APCONTROLACC APSUSPENSEACC RBNIACC PAYVENDOR BANKACCOUNT DISABLED REMITCONTACT REMITADDRESS1 REMITADDRESS2 REMITADDRESS3 206 .

Using the Integration Module MAX_ITM_INTERFACE Table Column Name REMITADDRESS4 MAXIMO Tables Length Nulls Table 36 Y COMPANIES Type ALN Column Name REMITADDRESS4 PAYONRECEIPT HOMEPAGE BANKNUM DUNSNUM TAXEXEMPTCODE TAXEXEMPTNUM ALN ALN ALN ALN ALN ALN 1 124 16 16 1 20 1 20 20 20 1 1 1 1 50 1 50 20 20 20 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES LOCATIONS LOCATIONS LOCATIONS LOCATIONS LOCATIONS LOCATIONS LOCATIONS COMPANIES INVVENDOR LOCATIONS LOCATIONS LOCATIONS LOCATIONS PAYONRECEIPT HOMEPAGE BANKNUM DUNSNUM TAXEXEMPTCODE TAXEXEMPTNUM ECOMMERCEENABLED OLDCONTROLACC OLDSHRINKAGEACC OLDINVCOSTAJDACC GISPARAM1 GISPARAM2 GISPARAM3 DISABLED NAME ISDEFAULT DESCRIPTION PURCHVARACC INVOICEVARACC CURVARACC ECOMMERCEENABLED ALN OLDCONTROLACC OLDSHRINKAGEACC OLDINVCOSTAJDACC GISPARAM1 GISPARAM2 GISPARAM3 LOC_DISABLED MFGNAME ISDEFAULT LODESC PURCHVARACC INVOICEVARACC CURVARACC ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN 207 .

Chapter 3 MAX_ITM_INTERFACE Table Column Name RECEIPTVARACC LONGDESC USERDATA1 USERDATA2 USERDATA3 USERDATA4 USERDATA5 USERDATA6 USERDATA7 USERDATA8 USERDATA9 USERDATA10 MAXIMO Tables Length Nulls Table 20 2000 1 1 1 1 1 1 1 1 1 1 Y Y Y Y Y Y Y Y Y Y Y Y LOCATIONS Type ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN Column Name RECEIPTVARACC BATCHID BATCHLINEID UTRANSTYPE ALN INTEGER ALN 25 4 25 Y Y Y ITEM_SOURCESYSID ITEM_OWNERSYSID ALN ALN 10 10 10 10 10 Y Y Y Y Y ITEM ITEM ITEM INVENTORY INVENTORY SOURCESYSID OWNERSYSID EXTERNALREFID SOURCESYSID OWNERSYSID ITEM_EXTERNALREFID ALN INV_SOURCESYSID INV_OWNERSYSID ALN ALN 208 .

Using the Integration Module MAX_ITM_INTERFACE Table Column Name INV_EXTERNALREFID BAL_SOURCESYSID BAL_OWNERSYSID BAL_EXTERNALREFID VND_SOURCESYSID VND_OWNERSYSID VND_EXTERNALREFID COMP_SOURCESYSID COMP_OWNERSYSID MAXIMO Tables Length Nulls Table 10 10 10 10 10 10 10 10 10 10 10 10 10 Y Y Y Y Y Y Y Y Y Y Y Y Y INVENTORY INVBALANCES INVBALANCES INVBALANCES INVVENDOR INVVENDOR INVVENDOR COMPANIES COMPANIES COMPANIES LOCATIONS LOCATIONS LOCATIONS Type ALN ALN ALN ALN ALN ALN ALN ALN ALN Column Name EXTERNALREFID SOURCESYSID OWNERSYSID EXTERNALREFID SOURCESYSID OWNERSYSID EXTERNALREFID SOURCESYSID OWNERSYSID EXTERNALREFID SOURCESYSID OWNERSYSID EXTERNALREFID COMP_EXTERNALREFID ALN LOC_SOURCESYSID LOC_OWNERSYSID LOC_EXTERNALREFID ALN ALN ALN SOURCEID APISEQ SENDERSYSID APISITE ALN INTEGER ALN ALN 25 4 50 256 Y Y Y Y SOURCE SOURCE ITEM SOURCE SOURCEID APISEQ SENDERSYSID APISITE IMPORTSTATUS IMPORTTIMESTAMP IMPORTMESSAGE ALN 40 Y Y Y DATETIME 10 ALN 2000 209 .

Chapter 3 210 .

2 15.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.2 1 1 20 20 N N N Y Y N N N N Y Y Y Y Y Y Y INVRESERVE INVRESERVE INVRESERVE INVRESERVE INVRESERVE INVRESERVE INVRESERVE INVRESERVE INVRESERVE INVRESERVE INVRESERVE INVRESERVE INVRESERVE INVRESERVE INVRESERVE INVRESERVE Type UPPER UPPER UPPER UPPER INTEGER DECIMAL DECIMAL YORN YORN ALN ALN Column Name REQUESTNUM ITEMNUM LOCATION WONUM WPOPERATION ACTUALQTY RESERVEDQTY INITFLAG DIRECTREQ GLACCOUNT REQUESTEDBY REQUESTEDDATE REQUIREDDATE PONUM POLINENUM DELLOCATION DATETIME 10 DATETIME 10 UPPER INTEGER UPPER 8 4 8 211 . they either separate information that comes from different tables or they group different sets of data. NOTE: Empty rows in the table are not physical rows in the database. MOUT_RSV_INTERFACE Table Column Name REQUESTNUM ITEMNUM LOCATION WONUM WPOPERATION ACTUALQTY RESERVEDQTY INITFLAG DIRECTREQ GLACCOUNT REQUESTEDBY REQUESTEDDATE REQUIREDDATE PONUM POLINENUM DELLOCATION MAXIMO Tables Length Nulls Table 8 8 8 10 4 15.

2 4 8 4 10 10 10 8 4 50 10 10 10 10 10 10 10 212 .Chapter 3 MOUT_RSV_INTERFACE Table Column Name DESCRIPTION IR1 IR2 IR3 IR4 IR5 POLINEID MRNUM MRLINENUM SOURCESYSID OWNERSYSID EXTERNALREFID ISSUETO APISEQ SENDERSYSID IN1 IN2 IN3 IN4 IN5 IN6 IN7 MAXIMO Tables Length Nulls Table 50 10 10 10 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y INVRESERVE INVRESERVE ITEM ITEM ITEM ITEM ITEM ITEM ITEM APISEQ SENDERSYSID IN1 IN2 IN3 IN4 IN5 IN6 IN7 INVRESERVE INVRESERVE INVRESERVE INVRESERVE INVRESERVE INVRESERVE INVRESERVE INVRESERVE INVRESERVE INVRESERVE INVRESERVE INVRESERVE Type ALN ALN ALN ALN Column Name DESCRIPTION IR1 IR2 IR3 IR4 IR5 POLINEID MRNUM MRLINENUM SOURCESYSID OWNERSYSID EXTERNALREFID DATETIME 10 AMOUNT INTEGER ALN INTEGER ALN ALN ALN ALN INTEGER ALN ALN ALN ALN ALN ALN ALN ALN 15.

Using the Integration Module MOUT_RSV_INTERFACE Table Column Name IN8 IN9 IN10 IN11 IN12 IN13 IN14 IN15 IN16 IN17 IN18 IN19 IN20 IN21 IN22 IN23 VENDOR MANUFACTURER MODELNUM CATALOGCODE CATEGORY ORDERUNIT MAXIMO Tables Length Nulls Table 10 10.2 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N Y ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM INVENTORY INVENTORY INVENTORY INVENTORY INVENTORY INVENTORY Type ALN AMOUNT Column Name IN8 IN9 IN10 IN11 IN12 IN13 IN14 IN15 IN16 IN17 IN18 IN19 IN20 IN21 IN22 IN23 VENDOR MANUFACTURER MODELNUM CATALOGCODE CATEGORY ORDERUNIT DATETIME 10 ALN ALN ALN ALN ALN ALN AMOUNT ALN ALN ALN ALN ALN ALN UPPER UPPER ALN ALN UPPER ALN 3 1 25 3 1 10 10.2 10 10 10 1 1 1 8 8 8 12 4 8 213 .

2 10.2 10 Y N N N Y INVENTORY INVENTORY INVENTORY INVENTORY INVENTORY Type ALN DECIMAL AMOUNT AMOUNT AMOUNT Column Name ISSUEUNIT CONVERSION STDCOST AVGCOST LASTCOST PARENT STATUS STATUSDATE WORKTYPE LEADCRAFT WODESC EQNUM WOLOCATION JPNUM FAILDATE CHANGEBY CHANGEDATE PMNUM HISTORYFLAG CONTRACT WOPRIORITY UPPER UPPER 10 8 Y N N Y Y Y Y Y Y Y Y Y Y N Y Y WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER MASTERWONUM STATUS STATUSDATE WORKTYPE LEADCRAFT DESCRIPTION EQNUM LOCATION JPNUM FAILDATE CHANGEBY CHANGEDATE PMNUM HISTORYFLAG CONTRACT WOPRIORITY DATETIME 10 UPPER UPPER ALN UPPER UPPER UPPER 5 8 50 8 8 10 DATETIME 10 UPPER 18 DATETIME 10 UPPER YORN UPPER INTEGER 8 1 8 4 214 .Chapter 3 MOUT_RSV_INTERFACE Table Column Name ISSUEUNIT CONVERSION STDCOST AVGCOST LASTCOST MAXIMO Tables Length Nulls Table 8 15.2 10.

2 10 10 10 10 10.2 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER Type ALN AMOUNT Column Name WOPM6 WOPM7 TARGCOMPDATE TARGSTARTDATE WOEQ1 WOEQ2 WOEQ3 WOEQ4 WOEQ5 WOEQ6 WOEQ7 WOEQ8 WOEQ9 WOEQ10 WOEQ11 WOEQ12 WO1 WO2 WO3 WO4 WO5 WO6 DATETIME 10 DATETIME 10 ALN ALN ALN ALN AMOUNT 10 10 10 10 10.2 10 10 10 10 10 10 215 .2 DATETIME 10 AMOUNT ALN ALN ALN ALN AMOUNT ALN ALN ALN ALN ALN ALN 15.Using the Integration Module MOUT_RSV_INTERFACE Table Column Name WOPM6 WOPM7 TARGCOMPDATE TARGSTARTDATE WOEQ1 WOEQ2 WOEQ3 WOEQ4 WOEQ5 WOEQ6 WOEQ7 WOEQ8 WOEQ9 WOEQ10 WOEQ11 WOEQ12 WO1 WO2 WO3 WO4 WO5 WO6 MAXIMO Tables Length Nulls Table 10 15.

2 216 .2 10 10 10 10.Chapter 3 MOUT_RSV_INTERFACE Table Column Name WO7 WO8 WO9 WO10 REPORTEDBY REPORTDATE PHONE PROBLEMCODE CALENDAR INTERRUPTABLE ACTSTART ACTFINISH SCHEDSTART SCHEDFINISH CREWID SUPERVISOR WOEQ13 WOEQ14 WOPM1 WOPM2 WOPM3 WOPM4 MAXIMO Tables Length Nulls Table 10 10 10 10 18 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER Type ALN ALN ALN ALN ALN Column Name WO7 WO8 WO9 WO10 REPORTEDBY REPORTDATE PHONE PROBLEMCODE CALENDAR INTERRUPTABLE ACTSTART ACTFINISH SCHEDSTART SCHEDFINISH CREWID SUPERVISOR WOEQ13 WOEQ14 WOPM1 WOPM2 WOPM3 WOPM4 DATETIME 10 ALN UPPER UPPER YORN 15 8 8 1 DATETIME 10 DATETIME 10 DATETIME 10 DATETIME 10 ALN UPPER 8 8 DATETIME 10 AMOUNT ALN ALN ALN AMOUNT 15.

2 Y Y Y Y Y Y Y Y Y Y Y Y Y N Y Y Y Y Y Y Y Y WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER Type ALN ALN ALN ALN AMOUNT Column Name WOPM5 WOJP1 WOJP2 WOJP3 WOJP4 WOJP5 WOL1 WOL2 WOL3 WOL4 RESPONDBY EQLOCPRIORITY CALCPRIORITY CHARGESTORE FAILURECODE WOLO1 WOLO2 WOLO3 WOLO4 WOLO5 WOLO6 WOLO7 DATETIME 10 ALN ALN AMOUNT 10 10 10.Using the Integration Module MOUT_RSV_INTERFACE Table Column Name WOPM5 WOJP1 WOJP2 WOJP3 WOJP4 WOJP5 WOL1 WOL2 WOL3 WOL4 RESPONDBY EQLOCPRIORITY CALCPRIORITY CHARGESTORE FAILURECODE WOLO1 WOLO2 WOLO3 WOLO4 WOLO5 WOLO6 WOLO7 MAXIMO Tables Length Nulls Table 10 10 10 10 10.2 DATETIME 10 217 .2 DATETIME 10 DATETIME 10 INTEGER INTEGER YORN UPPER ALN ALN ALN ALN ALN AMOUNT 4 4 1 8 10 10 10 10 10 10.

Chapter 3 MOUT_RSV_INTERFACE Table Column Name WOLO8 WOLO9 WOLO10 DISABLED CURRENCYCODE CURRENCYCODE2 ROWSTAMP MAXIMO Tables Length Nulls Table 15.2 10 4 1 8 8 40 Y Y Y Y Y Y Y WORKORDER WORKORDER WORKORDER WORKORDER CURRENCY CURRENCY Type AMOUNT ALN INTEGER YORN UPPER UPPER ALN Column Name WOLO8 WOLO9 WOLO10 DISABLED CURRENCYCODE CURRENCYCODE USERDATA1 USERDATA2 USERDATA3 USERDATA4 USERDATA5 USERDATA6 USERDATA7 USERDATA8 USERDATA9 USERDATA10 ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN 1 1 1 1 1 1 1 1 1 1 Y Y Y Y Y Y Y Y Y Y BATCHID BATCHLINEID ALN INTEGER 25 4 Y Y 218 .

Using the Integration Module MOUT_RSV_INTERFACE Table Column Name UTRANSTYPE MAXIMO Tables Length Nulls Table 25 Y Type ALN Column Name SOURCEID ALN 25 Y INVRESERVE SOURCEID APISITE ALN 256 Y IMPORTSTATUS ALN 40 Y Y Y IMPORTTIMESTAMP DATETIME 10 IMPORTMESSAGE ALN 2000 219 .

they either separate information that comes from different tables or they group different sets of data. MOUT_RSV_INTERFACE Table Column Name REQUESTNUM ITEMNUM LOCATION WONUM WPOPERATION ACTUALQTY RESERVEDQTY INITFLAG DIRECTREQ GLACCOUNT REQUESTEDBY REQUESTEDDATE REQUIREDDATE PONUM POLINENUM MAXIMO Tables Length Nulls Table 8 8 8 10 4 15. NOTE: Empty rows in the table are not physical rows in the database.Chapter 3 Inventory Confirmation Tables MAX_ICF_INTERFACE Table The MAX_ICF_INTERFACE table receives inventory confirmation data from Oracle Financials and sends it to the following MAXIMO tables.2 1 1 20 20 N N N Y Y N N N N Y Y Y Y Y Y INVRESERVE INVRESERVE INVRESERVE INVRESERVE INVRESERVE INVRESERVE INVRESERVE INVRESERVE INVRESERVE INVRESERVE INVRESERVE INVRESERVE INVRESERVE INVRESERVE INVRESERVE Type UPPER UPPER UPPER UPPER INTEGER DECIMAL DECIMAL YORN YORN ALN ALN Column Name REQUESTNUM ITEMNUM LOCATION WONUM WPOPERATION ACTUALQTY RESERVEDQTY INITFLAG DIRECTREQ GLACCOUNT REQUESTEDBY REQUESTEDDATE REQUIREDDATE PONUM POLINENUM DATETIME 10 DATETIME 10 UPPER INTEGER 8 4 220 .2 15.

2 4 8 4 10 10 10 8 4 50 10 10 10 10 10 10 221 .Using the Integration Module MOUT_RSV_INTERFACE Table Column Name DELLOCATION DESCRIPTION IR1 IR2 IR3 IR4 IR5 POLINEID MRNUM MRLINENUM SOURCESYSID OWNERSYSID EXTERNALREFID ISSUETO APISEQ SENDERSYSID IN1 IN2 IN3 IN4 IN5 IN6 MAXIMO Tables Length Nulls Table 8 50 10 10 10 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y INVRESERVE INVRESERVE ITEM ITEM ITEM ITEM ITEM ITEM APISEQ SENDERSYSID IN1 IN2 IN3 IN4 IN5 IN6 INVRESERVE INVRESERVE INVRESERVE INVRESERVE INVRESERVE INVRESERVE INVRESERVE INVRESERVE INVRESERVE INVRESERVE INVRESERVE INVRESERVE INVRESERVE Type UPPER ALN ALN ALN ALN Column Name DELLOCATION DESCRIPTION IR1 IR2 IR3 IR4 IR5 POLINEID MRNUM MRLINENUM SOURCESYSID OWNERSYSID EXTERNALREFID DATETIME 10 AMOUNT INTEGER ALN INTEGER ALN ALN ALN ALN INTEGER ALN ALN ALN ALN ALN ALN ALN 15.

Chapter 3 MOUT_RSV_INTERFACE Table Column Name IN7 IN8 IN9 IN10 IN11 IN12 IN13 IN14 IN15 IN16 IN17 IN18 IN19 IN20 IN21 IN22 IN23 VENDOR MANUFACTURER MODELNUM CATALOGCODE CATEGORY MAXIMO Tables Length Nulls Table 10 10 10.2 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM ITEM INVENTORY INVENTORY INVENTORY INVENTORY INVENTORY Type ALN ALN AMOUNT Column Name IN7 IN8 IN9 IN10 IN11 IN12 IN13 IN14 IN15 IN16 IN17 IN18 IN19 IN20 IN21 IN22 IN23 VENDOR MANUFACTURER MODELNUM CATALOGCODE CATEGORY DATETIME 10 ALN ALN ALN ALN ALN ALN AMOUNT ALN ALN ALN ALN ALN ALN UPPER UPPER ALN ALN UPPER 3 1 25 3 1 10 10.2 10 10 10 1 1 1 8 8 8 12 4 222 .

2 10 Y Y N N N Y INVENTORY INVENTORY INVENTORY INVENTORY INVENTORY INVENTORY Type ALN ALN DECIMAL AMOUNT AMOUNT AMOUNT Column Name ORDERUNIT ISSUEUNIT CONVERSION STDCOST AVGCOST LASTCOST PARENT STATUS STATUSDATE WORKTYPE LEADCRAFT WODESC EQNUM WOLOCATION JPNUM FAILDATE CHANGEBY CHANGEDATE PMNUM HISTORYFLAG CONTRACT UPPER UPPER 10 8 Y N N Y Y Y Y Y Y Y Y Y Y N Y WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER MASTERWONUM STATUS STATUSDATE WORKTYPE LEADCRAFT DESCRIPTION EQNUM LOCATION JPNUM FAILDATE CHANGEBY CHANGEDATE PMNUM HISTORYFLAG CONTRACT DATETIME 10 UPPER UPPER ALN UPPER UPPER UPPER 5 8 50 8 8 10 DATETIME 10 UPPER 18 DATETIME 10 UPPER YORN UPPER 8 1 8 223 .Using the Integration Module MOUT_RSV_INTERFACE Table Column Name ORDERUNIT ISSUEUNIT CONVERSION STDCOST AVGCOST LASTCOST MAXIMO Tables Length Nulls Table 8 8 15.2 10.2 10.

2 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER Type INTEGER ALN AMOUNT Column Name WOPRIORITY WOPM6 WOPM7 TARGCOMPDATE TARGSTARTDATE WOEQ1 WOEQ2 WOEQ3 WOEQ4 WOEQ5 WOEQ6 WOEQ7 WOEQ8 WOEQ9 WOEQ10 WOEQ11 WOEQ12 WO1 WO2 WO3 WO4 WO5 DATETIME 10 DATETIME 10 ALN ALN ALN ALN AMOUNT 10 10 10 10 10.Chapter 3 MOUT_RSV_INTERFACE Table Column Name WOPRIORITY WOPM6 WOPM7 TARGCOMPDATE TARGSTARTDATE WOEQ1 WOEQ2 WOEQ3 WOEQ4 WOEQ5 WOEQ6 WOEQ7 WOEQ8 WOEQ9 WOEQ10 WOEQ11 WOEQ12 WO1 WO2 WO3 WO4 WO5 MAXIMO Tables Length Nulls Table 4 10 15.2 10 10 10 10 10.2 DATETIME 10 AMOUNT ALN ALN ALN ALN AMOUNT ALN ALN ALN ALN ALN 15.2 10 10 10 10 10 224 .

Using the Integration Module MOUT_RSV_INTERFACE Table Column Name WO6 WO7 WO8 WO9 WO10 REPORTEDBY REPORTDATE PHONE PROBLEMCODE CALENDAR INTERRUPTABLE ACTSTART ACTFINISH SCHEDSTART SCHEDFINISH CREWID SUPERVISOR WOEQ13 WOEQ14 WOPM1 WOPM2 WOPM3 MAXIMO Tables Length Nulls Table 10 10 10 10 10 18 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER Type ALN ALN ALN ALN ALN ALN Column Name WO6 WO7 WO8 WO9 WO10 REPORTEDBY REPORTDATE PHONE PROBLEMCODE CALENDAR INTERRUPTABLE ACTSTART ACTFINISH SCHEDSTART SCHEDFINISH CREWID SUPERVISOR WOEQ13 WOEQ14 WOPM1 WOPM2 WOPM3 DATETIME 10 ALN UPPER UPPER YORN 15 8 8 1 DATETIME 10 DATETIME 10 DATETIME 10 DATETIME 10 ALN UPPER 8 8 DATETIME 10 AMOUNT ALN ALN ALN 15.2 10 10 10 225 .

2 226 .Chapter 3 MOUT_RSV_INTERFACE Table Column Name WOPM4 WOPM5 WOJP1 WOJP2 WOJP3 WOJP4 WOJP5 WOL1 WOL2 WOL3 WOL4 RESPONDBY EQLOCPRIORITY CALCPRIORITY CHARGESTORE FAILURECODE WOLO1 WOLO2 WOLO3 WOLO4 WOLO5 WOLO6 MAXIMO Tables Length Nulls Table 10.2 10 10 10 10 10.2 DATETIME 10 DATETIME 10 INTEGER INTEGER YORN UPPER ALN ALN ALN ALN ALN AMOUNT 4 4 1 8 10 10 10 10 10 10.2 Y Y Y Y Y Y Y Y Y Y Y Y Y Y N Y Y Y Y Y Y Y WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER Type AMOUNT ALN ALN ALN ALN AMOUNT Column Name WOPM4 WOPM5 WOJP1 WOJP2 WOJP3 WOJP4 WOJP5 WOL1 WOL2 WOL3 WOL4 RESPONDBY EQLOCPRIORITY CALCPRIORITY CHARGESTORE FAILURECODE WOLO1 WOLO2 WOLO3 WOLO4 WOLO5 WOLO6 DATETIME 10 ALN ALN AMOUNT 10 10 10.

2 10 4 1 8 8 40 USERDATA1 USERDATA2 USERDATA3 USERDATA4 USERDATA5 USERDATA6 USERDATA7 USERDATA8 USERDATA9 USERDATA10 ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN 1 1 1 1 1 1 1 1 1 1 Y Y Y Y Y Y Y Y Y Y BATCHID BATCHLINEID ALN INTEGER 25 4 Y Y 227 .Using the Integration Module MOUT_RSV_INTERFACE Table Column Name WOLO7 WOLO8 WOLO9 WOLO10 DISABLED CURRENCYCODE CURRENCYCODE2 ROWSTAMP MAXIMO Tables Length Nulls Table Y Y Y Y Y Y Y Y WORKORDER WORKORDER WORKORDER WORKORDER WORKORDER CURRENCY CURRENCY Type Column Name WOLO7 WOLO8 WOLO9 WOLO10 DISABLED CURRENCYCODE CURRENCYCODE DATETIME 10 AMOUNT ALN INTEGER YORN UPPER UPPER ALN 15.

Chapter 3 MOUT_RSV_INTERFACE Table Column Name Type MAXIMO Tables Length Nulls Table Column Name UTRANSTYPE ALN 25 Y SOURCEID ALN 25 Y INVRESERVE SOURCEID APISITE ALN 256 Y IMPORTSTATUS ALN 40 Y Y Y IMPORTTIMESTAMP DATETIME 10 IMPORTMESSAGE ALN 2000 228 .

2 15. MAX_ISU_INTERFACE Table Column Name ITEMNUM STORELOC TRANSDATE ACTUALDATE QUANTITY CURBAL PHYSCNT UNITCOST ACTUALCOST PONUM CONVERSION WONUM EQNUM ENTERBY IT1 MAXIMO Tables Length Nulls Table 30 8 Y Y N N N N N N N Y N Y Y N Y MATUSETRANS MATUSETRANS MATUSETRANS MATUSETRANS MATUSETRANS MATUSETRANS MATUSETRANS MATUSETRANS MATUSETRANS MATUSETRANS MATUSETRANS MATUSETRANS MATUSETRANS MATUSETRANS MATUSETRANS Type UPPER UPPER Column Name ITEMNUM STORELOC TRANSDATE ACTUALDATE QUANTITY CURBAL PHYSCNT UNITCOST ACTUALCOST PONUM CONVERSION WONUM EQNUM ENTERBY IT1 DATETIME 10 DATETIME 10 DECIMAL DECIMAL DECIMAL AMOUNT AMOUNT UPPER DECIMAL UPPER UPPER UPPER ALN 15.2 10.2 8 15.Using the Integration Module Issues Data Tables MAX_ISU_INTERFACE Table The MAX_ISU_INTERFACE table receives item issues data from Oracle Financials and sends it to the following MAXIMO tables. NOTE: Empty rows in the table are not physical rows in the database.2 10.2 10 8 18 10 229 . they either separate information that comes from different tables or they group different sets of data.2 15.

2 10 15.2 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N Y Y N MATUSETRANS MATUSETRANS MATUSETRANS MATUSETRANS MATUSETRANS MATUSETRANS MATUSETRANS MATUSETRANS MATUSETRANS MATUSETRANS MATUSETRANS MATUSETRANS MATUSETRANS MATUSETRANS MATUSETRANS MATUSETRANS MATUSETRANS MATUSETRANS MATUSETRANS MATUSETRANS MATUSETRANS MATUSETRANS Type ALN ALN DECIMAL ALN DECIMAL DECIMAL ALN YORN INTEGER UPPER ALN INTEGER YORN ALN ALN ALN ALN UPPER UPPER ALN ALN AMOUNT Column Name IT2 IT3 IT4 IT5 METERREADING METERREADING2 MEMO OUTSIDE WPOPERATION ISSUETO PACKINGSLIPNUM POLINENUM ROLLUP ITIN1 ITIN2 ITIN3 BINNUM LOTNUM ISSUETYPE GLDEBITACCT GLCREDITACCT LINECOST 230 .2 254 1 4 8 20 4 1 10 10 10 8 8 8 20 20 10.2 15.Chapter 3 MAX_ISU_INTERFACE Table Column Name IT2 IT3 IT4 IT5 METERREADING METERREADING2 MEMO OUTSIDE WPOPERATION ISSUETO PACKINGSLIPNUM POLINENUM ROLLUP ITIN1 ITIN2 ITIN3 BINNUM LOTNUM ISSUETYPE GLDEBITACCT GLCREDITACCT LINECOST MAXIMO Tables Length Nulls Table 10 10 15.

7 1 8 8 1 1 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y MATUSETRANS MATUSETRANS MATUSETRANS MATUSETRANS MATUSETRANS MATUSETRANS MATUSETRANS MATUSETRANS MATUSETRANS MATUSETRANS MATUSETRANS MATUSETRANS INVRESERVE INVRESERVE INVRESERVE Type AMOUNT ALN UPPER UPPER Column Name LINECOST2 FINANCIALPERIOD CURRENCYCODE CURRENCYCODE2 CURRENCYUNITCOST ROTEQNUM CURRENCYLINECOST LOCATION DESCRIPTION EXCHANGERATE EXCHANGERATE2 SPAREPARTADDED UPPER DELLOCATION DIRECTREQ CURRENCYUNITCOST DECIMAL ROTEQNUM UPPER CURRENCYLINECOST DECIMAL LOCATION DESCRIPTION EXCHANGERATE EXCHANGERATE2 SPAREPARTADDED REQUESTNUM DELLOCATION DIRECTREQ IBUPD UPPER ALN DECIMAL DECIMAL ALN UPPER UPPER YORN YORN MRNUM MRLINENUM MATUSETRANSID MATRECTRANSID IT6 ALN INTEGER INTEGER INTEGER ALN 8 4 4 4 10 Y Y Y Y Y MRNUM MRLINENUM MATUSETRANSID MATRECTRANSID IT6 231 .Using the Integration Module MAX_ISU_INTERFACE Table Column Name LINECOST2 FINANCIALPERIOD CURRENCYCODE CURRENCYCODE2 MAXIMO Tables Length Nulls Table 10.2 8 80 14.7 14.2 8 10.2 6 8 8 10.

Chapter 3 MAX_ISU_INTERFACE Table Column Name IT7 IT8 IT9 IT10 IT11 IT12 ITIN4 ITIN5 ITIN6 ITIN7 SOURCESYSID OWNERSYSID EXTERNALREFID APISEQ SENDERSYSID ISSUEID QTYREQUESTED QTYRETURNED MAXIMO Tables Length Nulls Table 10 10 10 10 10 10 10 10 10 10 10 10 10 4 50 4 15.2 15.2 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y QTYREQUESTED LABTRANS INVRESERVE Type ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN INTEGER ALN INTEGER DECIMAL DECIMAL Column Name IT7 IT8 IT9 IT10 IT11 IT12 ITIN4 ITIN5 ITIN6 ITIN7 SOURCESYSID OWNERSYSID EXTERNALREFID APISEQ ALN ROWSTAMP ALN 40 Y USERDATA1 ALN 1 Y 232 .

Using the Integration Module MAX_ISU_INTERFACE Table Column Name USERDATA2 USERDATA3 USERDATA4 USERDATA5 USERDATA6 USERDATA7 USERDATA8 USERDATA9 USERDATA10 MAXIMO Tables Length Nulls Table 1 1 1 1 1 1 1 1 1 Y Y Y Y Y Y Y Y Y Type ALN ALN ALN ALN ALN ALN ALN ALN ALN Column Name BATCHID BATCHLINEID ALN INTEGER 25 4 Y Y UTRANSTYPE ALN 25 Y SOURCEID ALN 25 Y LABTRANS SOURCEID APISITE ALN 256 Y IMPORTSTATUS IMPORTTIMESTAMP IMPORTMESSAGE ALN 25 Y Y Y DATETIME 10 ALN 2000 233 .

Chapter 3 234 .

and do not necessarily reflect your actual values. MAX_COM_INTERFACE Table Column Name COMPANY TYPE NAME ADDRESS1 ADDRESS2 ADDRESS3 ADDRESS4 CONTACT POSITION PHONE FAX MAXIMO Tables Length Nulls Table 8 1 50 36 36 36 36 50 24 20 20 N Y Y Y Y Y Y Y Y Y Y COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES Type UPPER ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN Column Name COMPANY TYPE NAME ADDRESS1 ADDRESS2 ADDRESS3 ADDRESS4 CONTACT COMPCONTACT POSITION COMPANIES COMPANIES PHONE FAX 235 .Using the Integration Module Vendor Interface Tables This section provides the mapping for the interface tables that the APIs use to transfer vendor data between MAXIMO and Oracle Financials. Empty rows in the table are not physical rows in the database. The values displayed in the following tables are examples. Your MAXIMO system catalogue determines your values. MAX_COM_INTERFACE The MAX_COM_INTERFACE table receives vendor data from Oracle Financials and sends it to the following MAXIMO tables. They are there to separate information coming from different tables or to group sets of data.

Chapter 3 MAX_COM_INTERFACE Table Column Name FOB FREIGHTTERMS SHIPVIA PAYMENTTERMS CUSTOMERNUM CO1 CO2 CO3 CO4 CO5 CO6 CO7 CO8 CO9 CO10 CO11 CO12 CO13 CHANGEBY CHANGEDATE INCLUSIVE1 INCLUSIVE2 MAXIMO Tables Length Nulls Table 20 50 20 20 16 10 10 10 10 10 10 10.2 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES Type ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN DECIMAL Column Name FOB FREIGHTTERMS SHIPVIA PAYMENTTERMS CUSTOMERNUM CO1 CO2 CO3 CO4 CO5 CO6 CO7 CO8 CO9 CO10 CO11 CO12 CO13 CHANGEBY CHANGEDATE INCLUSIVE1 INCLUSIVE2 DATETIME 10 INTEGER ALN ALN ALN ALN UPPER 4 1 10 10 15 18 DATETIME 10 YORN YORN 1 1 236 .

Using the Integration Module MAX_COM_INTERFACE Table Column Name INCLUSIVE3 INCLUSIVE4 INCLUSIVE5 TAX1CODE TAX2CODE TAX3CODE TAX4CODE TAX5CODE CURRENCYCODE LOCATION REGISTRATION1 REGISTRATION2 REGISTRATION3 REGISTRATION4 REGISTRATION5 APCONTROLACC APSUSPENSEACC RBNIACC PAYVENDOR BANKACCOUNT DISABLED LDKEY MAXIMO Tables Length Nulls Table 1 1 1 8 8 8 8 8 8 8 20 20 20 20 20 20 20 20 8 20 1 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES Type YORN YORN YORN UPPER UPPER UPPER UPPER UPPER UPPER UPPER ALN ALN ALN ALN ALN ALN ALN ALN UPPER UPPER YORN INTEGER Column Name INCLUSIVE3 INCLUSIVE4 INCLUSIVE5 TAX1CODE TAX2CODE TAX3CODE TAX4CODE TAX5CODE CURRENCYCODE LOCATION REGISTRATION1 REGISTRATION2 REGISTRATION3 REGISTRATION4 REGISTRATION5 APCONTROLACC APSUSPENSEACC RBNIACC PAYVENDOR BANKACCOUNT DISABLED LDKEY 237 .

Chapter 3 MAX_COM_INTERFACE Table Column Name REMITADDRESS1 REMITADDRESS2 REMITADDRESS3 REMITADDRESS4 REMITCONTACT PAYONRECEIPT HOMEPAGE BANKNUM DUNSNUM TAXEXEMPTCODE TAXEXEMPTNUM MAXIMO Tables Length Nulls Table 36 36 36 36 50 1 124 16 16 1 20 1 50 8 10 10 10 10 10 10 10 10 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES Type ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN Column Name REMITADDRESS1 REMITADDRESS2 REMITADDRESS3 REMITADDRESS4 REMITCONTACT PAYONRECEIPT HOMEPAGE BANKNUM DUNSNUM TAXEXEMPTCODE TAXEXEMPTNUM ECOMMERCEENABLED ECOMMERCEENABLED ALN MNETUSERID MNETCOMPANYID CO14 CO15 CO16 CO17 CO18 SOURCESYSID OWNERSYSID EXTERNALREFID ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN COMPCONTACT MNETUSERID COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES MNETCOMPANYID CO14 CO15 CO16 CO17 CO18 SOURCESYSID OWNERSYSID EXTERNALREFID 238 .

2 4 30 Y Y Y Y Y Y Y Y Y Y Y Y COMPCONTACT VOICEPHONE COMPCONTACT FAXPHONE COMPCONTACT EMAIL COMPCONTACT HOMEPHONE COMPCONTACT PAGEPHONE COMPCONTACT CNT1 COMPCONTACT CNT2 COMPCONTACT CNT3 COMPCONTACT CNT4 COMPCONTACT CNT5 PROCUREMENTCARDNU COMPCONTACT M PROCCARDEXPAIREDAT COMPCONTACT E PROCUREMENTCARDN UM ALN PROCCARDEXPAIREDA TE DATETIME 4 LONGDESC ALN 2000 Y PRIMARYCONTACT PRIMARYREMIT ALN ALN 1 1 Y Y USERDATA1 USERDATA2 ALN ALN 1 1 Y Y 239 .Using the Integration Module MAX_COM_INTERFACE Table Column Name Type MAXIMO Tables Length Nulls Table Column Name VOICEPHONE FAXPHONE EMAIL HOMEPHONE PAGEPHONE CNT1 CNT2 CNT3 CNT4 CNT5 ALN ALN ALN ALN ALN ALN ALN ALN DECIMAL INTEGER 20 20 60 20 30 1 1 1 15.

Chapter 3 MAX_COM_INTERFACE Table Column Name USERDATA3 USERDATA4 USERDATA5 USERDATA6 USERDATA7 USERDATA8 USERDATA9 USERDATA10 BATCHID BATCHLINEID MAXIMO Tables Length Nulls Table 1 1 1 1 1 1 1 1 25 4 Y Y Y Y Y Y Y Y Y Y Type ALN ALN ALN ALN ALN ALN ALN ALN ALN INTEGER Column Name UTRANSTYPE SOURCEID APISEQ APISITE ALN ALN INTEGER ALN 25 25 4 256 Y Y Y Y SOURCE SOURCE SOURCE SOURCEID APISEQ APISITE SENDERSYSID ALN 50 Y COMPANIES SENDERSYSID VENDORSENDSASN VENDORSENDSINV ECOMINTERFACE MNETECOMNUM1 ALN ALN ALN ALN 1 1 30 30 Y Y Y Y COMPANIES COMPANIES COMPANIES COMPANIES VENDORSENDSASN VENDORSENDSINV ECOMINTERFACE MNETECOMNUM1 240 .

Using the Integration Module MAX_COM_INTERFACE Table Column Name MNETECOMNUM2 MNETECOMNUM3 MNETECOMNUM4 MAXIMO Tables Length Nulls Table 1 1 1 1 1 1 12 1 Y Y Y Y Y Y Y Y COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES Type ALN ALN ALN Column Name MNETECOMNUM2 MNETECOMNUM3 MNETECOMNUM4 VENDORSENDSSTATUS AUTOAPPROVEINV AUTOSENDPOCANCEL AUTOSENDPOCANCEL AUTORECEIVEONASN VENDORSENDSSTATUS ALN AUTOAPPROVEINV ALN AUTOSENDPOCANCEL ALN DEFAULTWAREHOUSE ALN AUTORECEIVEONASN ALN IMPORTSTATUS IMPORTTIMESTAMP IMPORTMESSAGE ALN 40 Y Y Y DATETIME 10 ALN 2000 241 .

Empty rows in the table are not physical rows in the database. and do not necessarily reflect your values. Data is transferred to Oracle Financials.Chapter 3 Accounts Payable Interface Tables This section provides the mapping for the interface tables that the APIs use to transfer accounts payable data between MAXIMO and Oracle Financials. The values displayed in the following tables are examples. MOUT_AP_INTERFACE MOUT_AP_INTERFACE receives invoice data from the following MAXIMO tables. Your MAXIMO system catalogue determines your values. They are there to separate information coming from different tables or to group sets of data. MOUT_AP_INTERFACE Table Column Name INVOICENUM INVOICEDESC PONUM VENDOR CONTACT PAYMENTTERMS CHECKCODE CHECKNUM CURRENCYCODE EXCHANGERATE EXCHANGEDATE DOCUMENTTYPE MAXIMO Tables Length Nulls Table 8 50 8 8 50 20 8 8 8 12 10 8 N Y Y N Y Y Y Y Y N N N INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE Type UPPER ALN UPPER UPPER ALN ALN UPPER UPPER UPPER DECIMAL DATE UPPER Column Name INVOICENUM DESCRIPTION PONUM VENDOR CONTACT PAYMENTTERMS CHECKCODE CHECKNUM CURRENCYCODE EXCHANGERATE EXCHANGEDATE DOCUMENTTYPE 242 .

Using the Integration Module MOUT_AP_INTERFACE Table Column Name ORIGINVOICENUM STATUS STATUSDATE APPROVALNUM INVOICEDATE DISCOUNTDATE DUEDATE PAID PAIDDATE ENTERDATE ENTERBY CHANGEDATE CHANGEBY HISTORYFLAG TOTALTAX1 TAX1GL TOTALTAX2 TAX2GL TOTALTAX3 TAX3GL TOTALTAX4 TAX4GL MAXIMO Tables Length Nulls Table 8 7 Y N N Y N Y Y Y Y Y N Y Y Y N Y N Y N Y N Y INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE Type UPPER UPPER Column Name ORIGINVOICENUM STATUS STATUSDATE APPROVALNUM INVOICEDATE DISCOUNTDATE DUEDATE PAID PAIDDATE ENTERDATE ENTERBY CHANGEDATE CHANGEBY HISTORYFLAG TOTALTAX1 TAX1GL TOTALTAX2 TAX2GL TOTALTAX3 TAX3GL TOTALTAX4 TAX4GL DATETIME 10 ALN 8 DATETIME 10 DATETIME 10 DATETIME 10 DECIMAL 10 DATETIME 10 DATETIME 10 UPPER 18 DATETIME 10 ALN ALN DECIMAL ALN DECIMAL ALN DECIMAL ALN DECIMAL ALN 18 1 12 20 12 20 12 20 12 20 243 .

Chapter 3 MOUT_AP_INTERFACE Table Column Name INCLUSIVE1 INCLUSIVE2 INCLUSIVE3 DISCOUNT TOTALCOST INVOICE1 INVOICE2 INVOICE3 INVOICE4 INVOICE5 TOTALTAX5 TAX5GL INCLUSIVE4 INCLUSIVE5 MAXIMO Tables Length Nulls Table 1 1 1 10 10 1 1 1 1 1 12 20 1 1 12 10 20 20 4 12 N N N Y Y Y Y Y Y Y N Y N N Y Y Y Y Y N INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE Type YORN YORN YORN DECIMAL DECIMAL ALN ALN ALN ALN ALN DECIMAL ALN YORN YORN Column Name INCLUSIVE1 INCLUSIVE2 INCLUSIVE3 DISCOUNT TOTALCOST INVOICE1 INVOICE2 INVOICE3 INVOICE4 INVOICE5 TOTALTAX5 TAX5GL INCLUSIVE4 INCLUSIVE5 VENDORINVOICENUM BASETOTALCOST APSUSPENSEACCT APCONTROLACCT FINANCIALPERIOD EXCHANGERATE2 VENDORINVOICENUM ALN BASETOTALCOST APSUSPENSEACCT APCONTROLACCT FINANCIALPERIOD EXCHANGERATE2 NUMBER ALN ALN ALN DECIMAL BANKACCOUNT ALN 20 Y COMPANIES BANKACCOUNT 244 .

Using the Integration Module MOUT_AP_INTERFACE Table Column Name BANKNUM INVOICE6 INVOICE7 INVOICE8 INVOICE9 INVOICE10 SOURCESYSID OWNERSYSID EXTERNALREFID WFID WFACTIVE SYSCODE MAXIMO Tables Length Nulls Table 16 10 10 10 10 10 10 10 10 4 1 4 Y Y Y Y Y Y Y Y Y Y Y Y COMPANIES INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE Type ALN ALN ALN ALN ALN ALN ALN ALN ALN INTEGER YORN INTEGER Column Name BANKNUM INVOICE6 INVOICE7 INVOICE8 INVOICE9 INVOICE10 SOURCESYSID OWNERSYSID EXTERNALREFID WFID WFACTIVE APISEQ SENDERSYSID INVOICELINENUM POLINENUM ITEMNUM DESCRIPTION SCHARGECODE INVOICEQTY INVOICEUNIT INTEGER ALN INTEGER INTEGER UPPER ALN UPPER DECIMAL ALN 4 50 4 4 8 50 8 10 8 Y Y Y Y Y Y Y Y Y INVOICE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE SENDERSYSID INVOICELINENUM POLINENUM ITEMNUM DESCRIPTION SCHARGECODE INVOICEQTY INVOICEUNIT 245 .

Chapter 3 MOUT_AP_INTERFACE Table Column Name INOVOICEUNITCOST INVOICELINECOST CONVERSION RECEIPTREQD TAX1CODE TAX1 TAX2CODE TAX2 TAX3CODE TAX3 INVOICELIN1 INVOICELIN2 INVOICELIN3 INVOICELIN4 INVOICELIN5 TAX4CODE TAX4 TAX5CODE TAX5 SERVICE LOADEDCOST PRORATED MAXIMO Tables Length Nulls Table 15 15 15 1 8 10 8 10 8 10 1 1 1 1 1 8 10 8 10 1 10 1 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE Type DECIMAL DECIMAL DECIMAL YORN UPPER DECIMAL UPPER DECIMAL UPPER DECIMAL ALN ALN ALN ALN ALN UPPER DECIMAL UPPER DECIMAL YORN DECIMAL ALN Column Name UNITCOST LINECOST CONVERSION RECEIPTREQD TAX1CODE TAX1 TAX2CODE TAX2 TAX3CODE TAX3 INVOICELIN1 INVOICELIN2 INVOICELIN3 INVOICELIN4 INVOICELIN5 TAX4CODE TAX4 TAX5CODE TAX5 SERVICE LOADEDCOST PRORATED 246 .

Using the Integration Module MOUT_AP_INTERFACE Table Column Name PRORATECOST PRORATESERVICE AGREEMENTPONUM AGREEMENTPOTYPE LINECOST2 INVOICELIN6 INVOICELIN7 INVOICELIN8 INVOICELIN9 CURRENCYCODE2 GLDEBITACCT GLCREDITACCT WONUM WPOPERATION EQNUM PERCENTAGE MEMO COSTLINENUM LINECOST CHARGESTORE ICT1 MAXIMO Tables Length Nulls Table 12 1 8 6 12 10 10 10 10 8 20 20 10 4 8 5 25 4 15 1 1 Y Y Y Y Y Y Y Y Y Y N Y Y Y Y Y Y Y Y Y Y INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE MAXVAR INVOICECOST INVOICECOST INVOICECOST INVOICECOST INVOICECOST INVOICECOST INVOICECOST INVOICECOST INVOICECOST INVOICECOST INVOICECOST Type DECIMAL ALN ALN ALN DECIMAL ALN ALN ALN ALN UPPER ALN ALN UPPER INTEGER UPPER DECIMAL ALN INTEGER DECIMAL YORN ALN Column Name PRORATECOST PRORATESERVICE AGREEMENTPONUM AGREEMENTPOTYPE LINECOST2 INVOICELIN6 INVOICELIN7 INVOICELIN8 INVOICELIN9 VARVALUE(BASCURRE NCY2) GLDEBITACCT GLCREDITACCT WONUM WPOPERATION EQNUM PERCENTAGE MEMO COSTLINENUM LINECOST CHARGESTORE ICT1 247 .

Chapter 3 MOUT_AP_INTERFACE Table Column Name ICT2 ICT3 QUANTITY LOCATION COMPANYTYPE NAME ADDRESS1 ADDRESS2 ADDRESS3 ADDRESS4 POSITION PHONE FAX FOB FREIGHTTERMS SHIPVIA CUSTOMERNUM CO1 CO2 CO3 CO4 CO5 MAXIMO Tables Length Nulls Table 1 1 10 8 1 50 36 36 36 36 24 20 20 20 50 20 16 10 10 10 10 10 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y INVOICECOST INVOICECOST INVOICECOST INVOICECOST COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES Type ALN ALN DECIMAL UPPER ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN Column Name ICT2 ICT3 QUANTITY LOCATION TYPE NAME ADDRESS1 ADDRESS2 ADDRESS3 COMPCONTACT ADDRESS4 COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES POSITION PHONE FAX FOB FREIGHTTERMS SHIPVIA CUSTOMERNUM CO1 CO2 CO3 CO4 CO5 248 .

2 8 20 20 20 20 20 20 20 20 8 1 240 1 124 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N Y Y Y COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES Type ALN AMOUNT DATTIME INTEGER ALN ALN DATTIME DECIMAL UPPER ALN ALN ALN ALN ALN ALN ALN ALN UPPER ALN ALN ALN ALN Column Name CO6 CO7 CO8 CO9 CO10 CO11 CO12 CO13 LOCATION REGISTRATION1 REGISTRATION2 REGISTRATION3 REGISTRATION4 REGISTRATION5 APCONTROLACC APSUSPENSEACC RBNIACC PAYVENDOR DISABLED REMITCONTACT PAYONRECEIPT HOMEPAGE 249 .Using the Integration Module MOUT_AP_INTERFACE Table Column Name CO6 CO7 CO8 CO9 CO10 CO11 CO12 CO13 COMPANYLOC REGISTRATION1 REGISTRATION2 REGISTRATION3 REGISTRATION4 REGISTRATION5 APCONTROLACC APSUSPENSEACC RBNIACC PAYVENDOR DISABLED REMITCONTACT PAYONRECEIPT HOMEPAGE MAXIMO Tables Length Nulls Table 10 10.2 10 4 1 10 10 15.

Chapter 3 MOUT_AP_INTERFACE Table Column Name DUNSNUM TAXEXEMPTCODE TAXEXEMPTNUM MAXIMO Tables Length Nulls Table 16 1 20 1 1 46 46 25 8 12 Y Y Y Y Y Y Y Y Y Y COMPANIES COMPANIES COMPANIES COMPANIES POLINE POLINE POLINE POLINE POLINE Type ALN ALN ALN Column Name DUNSNUM TAXEXEMPTCODE TAXEXEMPTNUM ECOMMERCEENABLED ISSUE MANUFACTURER MFGNAME MODELNUM STORELOC ECOMMERCEENABLED ALN ISSUE MANUFACTURER MFGNAME MODELNUM STORELOC PRICEVAR ALN ALN ALN ALN ALN DECIMAL INVOICETRANS LINECOST APLONGDESC APLINELONGDESC ALN ALN 2000 2000 Y Y USERDATA1 USERDATA2 USERDATA3 USERDATA4 USERDATA5 USERDATA6 USERDATA7 USERDATA8 ALN ALN ALN ALN ALN ALN ALN ALN 1 1 1 1 1 1 1 1 Y Y Y Y Y Y Y Y 250 .

Using the Integration Module MOUT_AP_INTERFACE Table Column Name USERDATA9 USERDATA10 TOTALLINES BATCHID BATCHLINEID UTRANSTYPE SOURCEID APISITE EINVOICE IMPORTSTATUS IMPORTTIMESTAMP IMPORTMESSAGE MAXIMO Tables Length Nulls Table 1 1 4 25 4 25 25 256 1 40 Y Y Y Y Y Y Y Y Y Y Y Y INVOICE EINVOICE INVOICE SOURCEID Type ALN ALN INTEGER ALN INTEGER ALN ALN ALN ALN ALN Column Name DATETIME 10 ALN 2000 251 .

MAX_AP_INTERFACE Table Column Name INVOICENUM INVOICEDESC PONUM VENDOR CONTACT PAYMENTTERMS CHECKCODE CHECKNUM CURRENCYCODE EXCHANGEDATE EXCHANGERATE DOCUMENTTYPE ORIGINVOICENUM STATUS STATUSDATE APPROVALNUM INVOICEDATE MAXIMO Tables Length Nulls Table 8 50 8 8 50 20 8 8 8 4 12 8 8 7 N Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE Type UPPER ALN UPPER UPPER ALN ALN UPPER UPPER UPPER DATE DECIMAL UPPER UPPER UPPER Column Name APCONTROLACCT APPROVALNUM APSUSPENSEACCT BASETOTALCOST CHANGEBY CHANGEDATE CHECKCODE CHECKNUM CONTACT EXCHANGEDATE EXCHANGERATE DOCUMENTTYPE DISCOUNTDATE DOCUMENTTYPE DUEDATE ENTERBY ENTERDATE DATETIME 10 ALN 8 DATETIME 10 252 . They are there to separate information coming from different tables or to group sets of data. Data is sent to the following MAXIMO tables.Chapter 3 MAX_AP_INTERFACE MAX_AP_INTERFACE receives invoice data from Oracle Financials. Empty rows in the table are not physical rows in the database.

Using the Integration Module MAX_AP_INTERFACE Table Column Name DISCOUNTDATE DUEDATE PAID PAIDDATE ENTERBY ENTERDATE CHANGEBY CHANGEDATE HISTORYFLAG TOTALTAX1 TOTALTAX2 TOTALTAX3 TOTALTAX4 TOTALTAX5 TAX1 TAX1CODE TAX1GL TAX2 TAX2CODE TAX2GL TAX3 TAX3CODE MAXIMO Tables Length Nulls Table Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICELINE INVOICELINE INVOICE INVOICELINE INVOICELINE INVOICE INVOICELINE INVOICELINE Type Column Name DISCOUNTDATE DUEDATE FINANCIALPERIOD EXCHANGERATE2 ENTERBY ENTERDATE CHANGEBY CHANGEDATE INCLUSIVE4 INCLUSIVE5 INVOICE2 INVOICE4 INVOICEDATE TAX4GL TAX1 TAX1CODE INVOICE1 TAX2 TAX2CODE INVOICE3 TAX3 TAX3CODE DATETIME 10 DATETIME 10 DECIMAL 10 DATETIME 10 ALN 18 DATETIME 10 ALN 18 DATETIME 10 ALN DECIMAL DECIMAL DECIMAL DECIMAL DECIMAL DECIMAL UPPER ALN DECIMAL UPPER ALN DECIMAL UPPER 1 10 10 10 10 10 10 8 20 10 8 20 10 8 253 .

Chapter 3 MAX_AP_INTERFACE Table Column Name TAX3GL TAX4 TAX4CODE TAX4GL TAX5 TAX5CODE TAX5GL INCLUSIVE1 INCLUSIVE2 INCLUSIVE3 DISCOUNT TOTALCOST INVOICE1 INVOICE2 INVOICE3 INVOICE4 INVOICE5 INCLUSIVE4 INCLUSIVE5 MAXIMO Tables Length Nulls Table 20 10 8 20 10 8 20 1 1 1 10 10 1 1 1 1 1 1 1 12 10 20 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y INVOICE INVOICELINE INVOICELINE INVOICE INVOICELINE INVOICELINE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE Type ALN DECIMAL UPPER ALN DECIMAL UPPER ALN YORN YORN YORN DECIMAL DECIMAL ALN ALN ALN ALN ALN YORN YORN Column Name INVOICE5 TAX4 TAX4CODE INVOICENUM TAX5 TAX5CODE TAX5GL ORIGINVOICENUM PAID PAIDDATE DISCOUNT PONUM STATUS STATUSDATE TAX1GL TAX2GL TAX3GL TOTALCOST TOTALTAX1 TOTALTAX2 TOTALTAX3 TOTALTAX4 VENDORINVOICENUM ALN BASETOTALCOST APSUSPENSEACCT DECIMAL ALN 254 .

Using the Integration Module MAX_AP_INTERFACE Table Column Name APCONTROLACCT MAXIMO Tables Length Nulls Table 20 Y INVOICE Type ALN Column Name APCONTROLACCT FINANCIALPERIOD EXCHANGERATE2 ALN DECIMAL 4 12 Y N INVOICE INVOICE VENDOR EXCHANGERATE2 BANKACCOUNT BANKNUM INVOICE6 INVOICE7 INVOICE8 INVOICE9 INVOICE10 SOURCESYSID OWNERSYSID EXTERNALREFID WFID WFACTIVE SYSCODE APISEQ SENDERSYSID INVOICELINENUM POLINENUM ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN INTEGER YORN INTEGER INTEGER ALN INTEGER INTEGER 20 16 10 10 10 10 10 10 10 10 4 1 4 4 50 4 4 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE BANKACCOUNT BANKNUM INVOICE6 INVOICE7 INVOICE8 INVOICE9 INVOICE10 SOURCESYSID OWNERSYSID EXTERNALREFID WFID WFACTIVE SYSCODE INVOICECOST APISEQ INVOICE INVOICELINE INVOICELINE SENDERSYSID INVOICELINENUM POLINENUM 255 .

Chapter 3 MAX_AP_INTERFACE Table Column Name ITEMNUM DESCRIPTION SCHARGECODE INVOICEQTY INVOICEUNIT INVOICEUNITCOST INVOICELINECOST CONVERSION RECEIPTREQD INVOICELIN1 INVOICELIN2 INVOICELIN3 INVOICELIN4 INVOICELIN5 SERVICE LOADEDCOST PRORATECOST PRORATED PRORATESERVICE AGREEMENTPONUM AGREEMENTPOTYPE LINECOST2 MAXIMO Tables Length Nulls Table 8 50 8 10 8 15 15 15 1 1 1 1 1 1 1 10 10 1 1 8 6 12 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE INVOICELINE Type UPPER ALN UPPER DECIMAL ALN DECIMAL DECIMAL DECIMAL YORN ALN ALN ALN ALN ALN YORN DECIMAL DECIMAL ALN ALN ALN ALN DECIMAL Column Name ITEMNUM DESCRIPTION SCHARGECODE INVOICEQTY INVOICEUNIT UNITCOST LINECOST CONVERSION RECEIPTREQD INVOICELIN1 INVOICELIN2 INVOICELIN3 INVOICELIN4 INVOICELIN5 SERVICE LOADEDCOST PRORATECOST PRORATED PRORATESERVICE AGREEMENTPONUM AGREEMENTPOTYPE LINECOST2 256 .

Using the Integration Module MAX_AP_INTERFACE Table Column Name CURRENCYCODE2 INVOICELIN6 INVOICELIN7 INVOICELIN8 INVOICELIN9 GLCREDITACCT GLDEBITACCT WONUM WPOPERATION EQNUM LINECOST PERCENTAGE MEMO COSTLINENUM CHARGESTORE ICT1 ICT2 ICT3 QUANTITY LOCATION COMPANYTYPE MAXIMO Tables Length Nulls Table 8 10 10 10 10 20 20 10 4 8 10 5 25 4 1 10 10 10 10 8 1 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y MAXVAR INVOICELINE INVOICELINE INVOICELINE INVOICELINE Type UPPER ALN ALN ALN ALN ALN ALN UPPER INTEGER UPPER DECIMAL DECIMAL ALN INTEGER YORN ALN ALN ALN DECIMAL UPPER ALN Column Name VARVALUE(BASCURREN CY2) INVOICELIN6 INVOICELIN7 INVOICELIN8 INVOICELIN9 INVOICECOST GLCREDITACCT INVOICECOST GLDEBITACCT INVOICECOST WONUM INVOICECOST WPOPERATION INVOICECOST EQNUM INVOICECOST LINECOST INVOICECOST PERCENTAGE INVOICECOST MEMO INVOICECOST COSTLINENUM INVOICECOST CHARGESTORE INVOICECOST ICT1 INVOICECOST ICT2 INVOICECOST ICT3 INVOICECOST QUANTITY INVOICECOST LOCATION COMPANIES TYPE 257 .

Chapter 3 MAX_AP_INTERFACE Table Column Name NAME ADDRESS1 ADDRESS2 ADDRESS3 ADDRESS4 POSITION PHONE FAX FOB FREIGHTTERMS SHIPVIA CUSTOMERNUM CO1 CO10 CO11 CO12 CO13 CO2 CO3 CO4 CO5 CO6 MAXIMO Tables Length Nulls Table 50 36 36 36 36 24 20 20 20 50 20 16 10 1 10 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES Type ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN YORN ALN Column Name NAME ADDRESS1 ADDRESS2 ADDRESS3 ADDRESS4 POSITION PHONE FAX FOB FREIGHTTERMS SHIPVIA CUSTOMERNUM CO1 CO10 CO11 CO12 CO13 CO2 CO3 CO4 CO5 CO6 DATETIME 10 DECIMAL ALN ALN ALN ALN ALN 15.2 10 10 10 10 10 258 .

Using the Integration Module MAX_AP_INTERFACE Table Column Name CO7 CO8 CO9 COMPANYLOC REGISTRATION1 REGISTRATION2 REGISTRATION3 REGISTRATION4 REGISTRATION5 APCONTROLACC APSUSPENSEACC RBNIACC PAYVENDOR DISABLED REMITCONTACT PAYONRECEIPT HOMEPAGE DUNSNUM TAXEXEMPTCODE TAXEXEMPTNUM MAXIMO Tables Length Nulls Table 10.2 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES COMPANIES POLINE Type AMOUNT Column Name CO7 CO8 CO9 LOCATION REGISTRATION1 REGISTRATION2 REGISTRATION3 REGISTRATION4 REGISTRATION5 APCONTROLACC APSUSPENSEACC RBNIACC PAYVENDOR DISABLED REMITCONTACT PAYONRECEIPT HOMEPAGE DUNSNUM TAXEXEMPTCODE TAXEXEMPTNUM ECOMMERCEENABLED ISSUE DATETIME 10 INTEGER UPPER ALN ALN ALN ALN ALN ALN ALN ALN UPPER YORN ALN ALN ALN ALN ALN ALN 4 8 20 20 20 20 20 20 20 20 8 1 50 1 124 16 1 20 1 1 ECOMMERCEENABLED ALN ISSUE YORN 259 .

Chapter 3 MAX_AP_INTERFACE Table Column Name MANUFACTURER MFGNAME MODELNUM STORELOC PRICEVAR APLONGDESC APLINELONGDESC USERDATA1 USERDATA2 USERDATA3 USERDATA4 USERDATA5 USERDATA6 USERDATA7 USERDATA8 USERDATA9 USERDATA10 MAXIMO Tables Length Nulls Table 8 8 8 8 8 2000 2000 1 1 1 1 1 1 1 1 1 1 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y POLINE COMPANIES POLINE POLINE Type ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN Column Name MANUFACTURER NAME MODELNUM STORELOC INVOICETRAN S LINECOST TOTALLINES INTEGER 4 Y BATCHID ALN 25 Y 260 .

Using the Integration Module MAX_AP_INTERFACE Table Column Name BATCHLINEID UTRANSTYPE SOURCEID MAXIMO Tables Length Nulls Table 4 25 25 Y Y Y INVOICECOST SOURCEID Type INTEGER ALN ALN Column Name APISITE EINVOICE IMPORTMESSAGE IMPORTSTATUS IMPORTTIMESTAMP ALN ALN ALN ALN 256 1 2000 40 Y Y Y Y Y INVOICE EINVOICE DATETIME 10 261 .

MOUT_GL_INTERFACE Table Column Name GLDEBITACCT GLCREDITACCT FINANCIALPERIOD INVTRANS Table Length Nulls 20 20 4 Y Y Y Type ALN ALN ALN Column Name GLDEBITACCT GLCREDITACCT FINANCIALPERIOD TRANSDATE ENTERDATE TRANSTYPE DATETIME DATETIME UPPER 10 10 16 N Y Y TRANSDATE TRANSDATE TRANSTYPE 262 . The following table shows the mapping for the MOUT_GL_INTERFACE and INVTRANS tables. LABTRANS.Chapter 3 General Ledger Interface Tables This section provides the mapping for the interface tables that are used when transferring general ledger data between MAXIMO and Oracle Financials. Additional data comes from the INVOICELINE and INVOICECOST tables. Data is sent to Oracle Financials. MATRECTRANS. They are there to separate information coming from different tables or to group sets of data. The values displayed in the following tables are examples. MATUSETRANS. SERVRECTRANS. and do not necessarily reflect your actual values. MOUT_GL_INTERFACE Table The MOUT_GL_INTERFACE table can receive journal entry data from seven MAXIMO tables: INVTRANS. Empty rows in the table are not physical rows in the database. Your values are determined by your MAXIMO system catalogue. INVOICETRANS or TOOLTRANS.

Using the Integration Module MOUT_GL_INTERFACE Table Column Name Type Length Nulls INVTRANS Table Column Name DESCRIPTION ITEMNUM STORELOC BINNUM QUANTITY FROMSTORELOC ALN UPPER UPPER ALN DECIMAL UPPER 254 8 8 8 15 8 Y Y Y Y Y Y ITEMNUM STORELOC BINNUM QUANTITY UNITCOST LINECOST AMOUNT DECIMAL 10 10 Y N NEWCOST LINECOST PONUM POLINENUM UPPER INTEGER 8 4 Y Y INVOICENUM INVOICELINENUM COSTLINENUM UPPER INTEGER INTEGER 8 4 4 Y Y Y WONUM WPOPERATION EQNUM LOCATION UPPER INTEGER UPPER UPPER 10 4 8 8 Y Y Y Y 263 .

Chapter 3 MOUT_GL_INTERFACE Table Column Name Type Length Nulls INVTRANS Table Column Name CLAIMNUM UPPER 8 Y CURRENCYCODE CURRENCYUNITCOST CURRENCYLINECOST EXCHANGERATE UPPER DECIMAL DECIMAL DECIMAL 8 10 10 10 Y Y Y Y JE1 JE2 JE3 JE4 JE5 JE6 JE7 JE8 ALN ALN ALN ALN ALN ALN ALN ALN 254 254 254 254 254 254 254 254 Y Y Y Y Y Y Y Y LABORCODE CRAFT REGULARHRS OTHRS UPPER UPPER DURATION DURATION 8 8 8 8 Y Y Y Y 264 .

Using the Integration Module MOUT_GL_INTERFACE Table Column Name TOOLNUM INVTRANS Table Length Nulls 8 Y Type UPPER Column Name VENDOR UPPER 8 Y ENTERBY MEMO UPPER ALN 18 254 N Y ENTERBY MEMO FROMLOT TOLOT LOADEDCOST TAX1CODE TAX1 TAX2CODE TAX2 TAX3CODE TAX3 TAX4CODE TAX4 TAX5CODE TAX5 PRORATED PRORATECOST LOTNUM 265 .

Chapter 3 MOUT_GL_INTERFACE Table Column Name STATUS STATUSDATE STATUSCHANGEBY INVTRANS Table Length Nulls Column Name Type GENAPPRSERVRECEIPT PAYMENTRANSDATE AGREEMENTPONUM AGREEMENTPOTYPE PRORATESERVICE CURRENCYCODE2 EXCHANGERATE2 LINECOST2 EXCHANGERATE2 LINECOST2 FINCNTRLID BUDGETID BUDGETLINEID PROJECTID TASKID BUDGETTYPE PROJECTTYPE TASKTYPE ALN ALN ALN ALN ALN ALN ALN ALN 8 25 25 25 25 30 30 30 Y Y Y Y Y Y Y Y 266 .

Using the Integration Module MOUT_GL_INTERFACE Table Column Name BUDGETREF BUDGETLINEREF PROJECTREF TASKREF ISCHARGEABLE FC01 FC02 FC03 FC04 FC05 FC06 FC07 FC08 FC09 FC10 FC11 FC12 FC13 FC14 FC15 PROJDATA1 PROJDATA2 INVTRANS Table Length Nulls 50 50 50 50 Y Y Y Y Type ALN ALN ALN ALN Column Name 267 .

Chapter 3 MOUT_GL_INTERFACE Table Column Name PROJDATA3 PROJDATA4 PROJDATA5 PROJDATA6 PROJDATA7 PROJDATA8 PROJDATA9 PROJDATA10 PROJDATA11 PROJDATA12 PROJDATA13 PROJDATA14 PROJDATA15 INVTRANS Table Length Nulls Column Name Type ROWSTAMP USERDATA1 USERDATA2 USERDATA3 USERDATA4 USERDATA5 ALN ALN ALN ALN ALN 1 1 1 1 1 Y Y Y Y Y 268 .

Using the Integration Module MOUT_GL_INTERFACE Table Column Name USERDATA6 USERDATA7 USERDATA8 USERDATA9 USERDATA10 INVTRANS Table Length Nulls 1 1 1 1 1 Y Y Y Y Y Type ALN ALN ALN ALN ALN Column Name BATCHID BATCHLINEID ALN INTEGER 25 4 Y Y UTRANSTYPE ALN 25 Y SOURCEID APISEQ APISITE ALN INTEGER 25 4 Y Y SOURCEID APISEQ SENDERSYSID SOURCESYSID OWNERSYSID EXTERNALREFID ISSUEID INVTRANSID SENDERSYSID SOURCESYSID OWNERSYSID EXTERNALREFID INVTRANSID 269 .

Chapter 3 MOUT_GL_INTERFACE Table Column Name IMPORTSTATUS IMPORTTIMESTAMP IMPORTMESSAGE INVTRANS Table Length Nulls 40 10 2000 Y Y Y Type ALN DATETIME ALN Column Name 270 .

They are there to separate information coming from different tables or to group sets of data. MOUT_GL_INTERFACE Table Column Name GLDEBITACCT GLCREDITACCT FINANCIALPERIOD MATUSETRANS Table Length Nulls 20 20 4 Y Y Y Type ALN ALN ALN Column Name GLDEBITACCT GLCREDITACCT FINANCIALPERIOD TRANSDATE ENTERDATE TRANSTYPE DATETIME DATETIME UPPER 10 10 16 N Y Y TRANSDATE ACTUALDATE ISSUETYPE DESCRIPTION ITEMNUM STORELOC BINNUM QUANTITY FROMSTORELOC ALN UPPER UPPER ALN DECIMAL UPPER 254 8 8 8 15 8 Y Y Y Y Y Y DESCRIPTION ITEMNUM STORELOC BINNUM QUANTITY UNITCOST LINECOST AMOUNT DECIMAL 10 10 Y N UNITCOST/ACTUALCOST LINECOST 271 .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.

Chapter 3 MOUT_GL_INTERFACE Table Column Name PONUM POLINENUM MATUSETRANS Table Length Nulls 8 4 Y Y Type UPPER INTEGER Column Name PONUM POLINENUM INVOICENUM INVOICELINENUM COSTLINENUM UPPER INTEGER INTEGER 8 4 4 Y Y Y WONUM WPOPERATION EQNUM LOCATION UPPER INTEGER UPPER UPPER 10 4 8 8 Y Y Y Y WONUM WPOPERATION EQNUM LOCATION CLAIMNUM UPPER 8 Y CURRENCYCODE CURRENCYUNITCOST CURRENCYLINECOST EXCHANGERATE UPPER DECIMAL DECIMAL DECIMAL 8 10 10 10 Y Y Y Y CURRENCYCODE CURRENCYUNITCOST CURRENCYLINECOST EXCHANGERATE JE1 JE2 JE3 ALN ALN ALN 254 254 254 Y Y Y IT1 IT2 IT3 272 .

Using the Integration Module MOUT_GL_INTERFACE Table Column Name JE4 JE5 JE6 JE7 JE8 MATUSETRANS Table Length Nulls 254 254 254 254 254 Y Y Y Y Y Type ALN ALN ALN ALN ALN Column Name IT4 IT5 ITIN1 ITIN2 ITIN3 LABORCODE CRAFT REGULARHRS OTHRS UPPER UPPER DURATION DURATION 8 8 8 8 Y Y Y Y TOOLNUM UPPER 8 Y VENDOR UPPER 8 Y ENTERBY MEMO UPPER ALN 18 254 N Y ENTERBY MEMO FROMLOT TOLOT LOADEDCOST TAX1CODE LOTNUM 273 .

Chapter 3 MOUT_GL_INTERFACE Table Column Name TAX1 TAX2CODE TAX2 TAX3CODE TAX3 TAX4CODE TAX4 TAX5CODE TAX5 PRORATED PRORATECOST STATUS STATUSDATE STATUSCHANGEBY MATUSETRANS Table Length Nulls Column Name Type GENAPPRSERVRECEIPT PAYMENTRANSDATE AGREEMENTPONUM AGREEMENTPOTYPE PRORATESERVICE CURRENCYCODE2 274 .

Using the Integration Module MOUT_GL_INTERFACE Table Column Name EXCHANGERATE2 LINECOST2 MATUSETRANS Table Length Nulls Column Name EXCHANGERATE2 LINECOST2 Type FINCNTRLID BUDGETID BUDGETLINEID PROJECTID TASKID BUDGETTYPE PROJECTTYPE TASKTYPE BUDGETREF BUDGETLINEREF PROJECTREF TASKREF ISCHARGEABLE FC01 FC02 FC03 FC04 FC05 FC06 ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN 8 25 25 25 25 30 30 30 50 50 50 50 Y Y Y Y Y Y Y Y Y Y Y Y 275 .

Chapter 3 MOUT_GL_INTERFACE Table Column Name FC07 FC08 FC09 FC10 FC11 FC12 FC13 FC14 FC15 PROJDATA1 PROJDATA2 PROJDATA3 PROJDATA4 PROJDATA5 PROJDATA6 PROJDATA7 PROJDATA8 PROJDATA9 PROJDATA10 PROJDATA11 PROJDATA12 PROJDATA13 MATUSETRANS Table Length Nulls Column Name Type 276 .

Using the Integration Module MOUT_GL_INTERFACE Table Column Name PROJDATA14 PROJDATA15 MATUSETRANS Table Length Nulls Column Name Type ROWSTAMP USERDATA1 USERDATA2 USERDATA3 USERDATA4 USERDATA5 USERDATA6 USERDATA7 USERDATA8 USERDATA9 USERDATA10 ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN 1 1 1 1 1 1 1 1 1 1 Y Y Y Y Y Y Y Y Y Y BATCHID BATCHLINEID ALN INTEGER 25 4 Y Y UTRANSTYPE ALN 25 Y 277 .

Chapter 3 MOUT_GL_INTERFACE Table Column Name SOURCEID APISEQ APISITE MATUSETRANS Table Length Nulls 25 4 Y Y Type ALN INTEGER Column Name SOURCEID APISEQ SENDERSYSID SOURCESYSID OWNERSYSID EXTERNALREFID ISSUEID INVTRANSID SENDERSYSID SOURCESYSID OWNERSYSID EXTERNALREFID ISSUEID IMPORTSTATUS IMPORTTIMESTAMP IMPORTMESSAGE ALN DATETIME ALN 40 10 2000 Y Y Y 278 .

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.Using the Integration Module The following table shows the mapping for the MOUT_GL_INTERFACE and MATRECTRANS tables. MOUT_GL_INTERFACE Table Column Name GLDEBITACCT GLCREDITACCT FINANCIALPERIOD MATRECTRANS Table Length Nulls 20 20 4 Y Y Y Type ALN ALN ALN Column Name GLDEBITACCT GLCREDITACCT FINANCIALPERIOD TRANSDATE ENTERDATE TRANSTYPE DATETIME 10 DATETIME 10 UPPER 16 N Y Y TRANSDATE ACTUALDATE ISSUETYPE DESCRIPTION ITEMNUM STORELOC BINNUM QUANTITY FROMSTORELOC ALN UPPER UPPER ALN DECIMAL UPPER 254 8 8 8 15 8 Y Y Y Y Y Y DESCRIPTION ITEMNUM TOSTORELOC TOBIN QUANTITY FROMSTORELOC UNITCOST LINECOST AMOUNT DECIMAL 10 10 Y N UNITCOST/ACTUALCOST LINECOST 279 .

Chapter 3 MOUT_GL_INTERFACE Table Column Name PONUM POLINENUM MATRECTRANS Table Length Nulls 8 4 Y Y Type UPPER INTEGER Column Name PONUM POLINENUM INVOICENUM INVOICELINENUM COSTLINENUM UPPER INTEGER INTEGER 8 4 4 Y Y Y INVOICENUM WONUM WPOPERATION EQNUM LOCATION UPPER INTEGER UPPER UPPER 10 4 8 8 Y Y Y Y WONUM WPOPERATION EQNUM LOCATION CLAIMNUM UPPER 8 Y CURRENCYCODE CURRENCYUNITCOST CURRENCYLINECOST EXCHANGERATE UPPER DECIMAL DECIMAL DECIMAL 8 10 10 10 Y Y Y Y CURRENCYCODE CURRENCYUNITCOST CURRENCYLINECOST EXCHANGERATE JE1 JE2 JE3 ALN ALN ALN 254 254 254 Y Y Y IT1 IT2 IT3 280 .

Using the Integration Module MOUT_GL_INTERFACE Table Column Name JE4 JE5 JE6 JE7 JE8 MATRECTRANS Table Length Nulls 254 254 254 254 254 Y Y Y Y Y Type ALN ALN ALN ALN ALN Column Name IT4 IT5 ITIN1 ITIN2 ITIN3 LABORCODE CRAFT REGULARHRS OTHRS UPPER UPPER 8 8 Y Y Y Y DURATION 8 DURATION 8 TOOLNUM UPPER 8 Y VENDOR UPPER 8 Y ENTERBY MEMO UPPER ALN 18 254 N Y ENTERBY REMARK FROMLOT TOLOT LOADEDCOST TAX1CODE FROMLOT TOLOT LOADEDCOST TAX1CODE 281 .

Chapter 3 MOUT_GL_INTERFACE Table Column Name TAX1 TAX2CODE TAX2 TAX3CODE TAX3 TAX4CODE TAX4 TAX5CODE TAX5 PRORATED PRORATECOST STATUS STATUSDATE STATUSCHANGEBY MATRECTRANS Table Length Nulls Column Name TAX1 TAX2CODE TAX2 TAX3CODE TAX3 TAX4CODE TAX4 TAX5CODE TAX5 PRORATED PRORATECOST STATUS STATUSDATE STATUSCHANGEBY Type GENAPPRSERVRECEIPT PAYMENTRANSDATE AGREEMENTPONUM AGREEMENTPOTYPE PRORATESERVICE CURRENCYCODE2 282 .

Using the Integration Module MOUT_GL_INTERFACE Table Column Name EXCHANGERATE2 LINECOST2 MATRECTRANS Table Length Nulls Column Name EXCHANGERATE2 LINECOST2 Type FINCNTRLID BUDGETID BUDGETLINEID PROJECTID TASKID BUDGETTYPE PROJECTTYPE TASKTYPE BUDGETREF BUDGETLINEREF PROJECTREF TASKREF ISCHARGEABLE FC01 FC02 FC03 FC04 FC05 FC06 ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN 8 25 25 25 25 30 30 30 50 50 50 50 Y Y Y Y Y Y Y Y Y Y Y Y 283 .

Chapter 3 MOUT_GL_INTERFACE Table Column Name FC07 FC08 FC09 FC10 FC11 FC12 FC13 FC14 FC15 PROJDATA1 PROJDATA2 PROJDATA3 PROJDATA4 PROJDATA5 PROJDATA6 PROJDATA7 PROJDATA8 PROJDATA9 PROJDATA10 PROJDATA11 PROJDATA12 PROJDATA13 MATRECTRANS Table Length Nulls Column Name Type 284 .

Using the Integration Module MOUT_GL_INTERFACE Table Column Name PROJDATA14 PROJDATA15 MATRECTRANS Table Length Nulls Column Name Type ROWSTAMP USERDATA1 USERDATA2 USERDATA3 USERDATA4 USERDATA5 USERDATA6 USERDATA7 USERDATA8 USERDATA9 USERDATA10 ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN 1 1 1 1 1 1 1 1 1 1 Y Y Y Y Y Y Y Y Y Y BATCHID BATCHLINEID ALN INTEGER 25 4 Y Y UTRANSTYPE ALN 25 Y 285 .

Chapter 3 MOUT_GL_INTERFACE Table Column Name SOURCEID APISEQ APISITE MATRECTRANS Table Length Nulls 25 4 Y Y Type ALN INTEGER Column Name SOURCEID APISEQ SENDERSYSID SOURCESYSID OWNERSYSID EXTERNALREFID ISSUEID INVTRANSID SENDERSYSID SOURCESYSID OWNERSYSID EXTERNALREFID IMPORTSTATUS IMPORTTIMESTAMP IMPORTMESSAGE ALN 40 Y Y Y DATETIME 10 ALN 2000 286 .

They are there to separate information coming from different tables or to group sets of data.Using the Integration Module The following table shows the mapping for the MOUT_GL_INTERFACE and SERVRECTRANS tables. MOUT_GL_INTERFACE Table Column Name GLDEBITACCT GLCREDITACCT FINANCIALPERIOD SERVRECTRANS Table Length 20 20 4 Type ALN ALN ALN Nulls Y Y Y Column Name GLDEBITACCT GLCREDITACCT FINANCIALPERIOD TRANSDATE ENTERDATE TRANSTYPE DATETIME 10 DATETIME 10 UPPER 16 N Y Y TRANSDATE ENTERDATE DESCRIPTION ITEMNUM STORELOC BINNUM QUANTITY FROMSTORELOC ALN UPPER UPPER ALN DECIMAL UPPER 254 8 8 8 15 8 Y Y Y Y Y Y DESCRIPTION QUANTITY UNITCOST LINECOST AMOUNT DECIMAL 10 10 Y N UNITCOST LINECOST 287 . Empty rows in the table are not physical rows in the database.

Chapter 3 MOUT_GL_INTERFACE Table Column Name PONUM POLINENUM SERVRECTRANS Table Length 8 4 Type UPPER INTEGER Nulls Y Y Column Name PONUM POLINENUM INVOICENUM INVOICELINENUM COSTLINENUM UPPER INTEGER INTEGER 8 4 4 Y Y Y INVOICENUM WONUM WPOPERATION EQNUM LOCATION UPPER INTEGER UPPER UPPER 10 4 8 8 Y Y Y Y WONUM WPOPERATION EQNUM LOCATION CLAIMNUM UPPER 8 Y CLAIMNUM CURRENCYCODE CURRENCYUNITCOST CURRENCYLINECOST EXCHANGERATE UPPER DECIMAL DECIMAL DECIMAL 8 10 10 10 Y Y Y Y CURRENCYCODE CURRENCYUNITCOST CURRENCYLINECOST EXCHANGERATE JE1 JE2 JE3 ALN ALN ALN 254 254 254 Y Y Y SS1 SS2 SS3 288 .

Using the Integration Module MOUT_GL_INTERFACE Table Column Name JE4 JE5 JE6 JE7 JE8 SERVRECTRANS Table Length 254 254 254 254 254 Type ALN ALN ALN ALN ALN Nulls Y Y Y Y Y Column Name SS4 SS5 SSPL1 SSPL2 SSPL3 LABORCODE CRAFT REGULARHRS OTHRS UPPER UPPER 8 8 Y Y Y Y DURATION 8 DURATION 8 TOOLNUM UPPER 8 Y VENDOR UPPER 8 Y ENTERBY MEMO UPPER ALN 18 254 N Y ENTERBY REMARK FROMLOT TOLOT LOADEDCOST TAX1CODE LOADEDCOST TAX1CODE 289 .

Chapter 3 MOUT_GL_INTERFACE Table Column Name TAX1 TAX2CODE TAX2 TAX3CODE TAX3 TAX4CODE TAX4 TAX5CODE TAX5 PRORATED PRORATECOST STATUS STATUSDATE STATUSCHANGEBY SERVRECTRANS Table Length Nulls Column Name TAX1 TAX2CODE TAX2 TAX3CODE TAX3 TAX4CODE TAX4 TAX5CODE TAX5 PRORATED PRORATECOST Type GENAPPRSERVRECEIPT PAYMENTRANSDATE AGREEMENTPONUM AGREEMENTPOTYPE PRORATESERVICE CURRENCYCODE2 290 .

Using the Integration Module MOUT_GL_INTERFACE Table Column Name EXCHANGERATE2 LINECOST2 SERVRECTRANS Table Length Nulls Column Name EXCHANGERATE2 LINECOST2 Type FINCNTRLID BUDGETID BUDGETLINEID PROJECTID TASKID BUDGETTYPE PROJECTTYPE TASKTYPE BUDGETREF BUDGETLINEREF PROJECTREF TASKREF ISCHARGEABLE FC01 FC02 FC03 FC04 FC05 FC06 ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN 8 25 25 25 25 30 30 30 50 50 50 50 Y Y Y Y Y Y Y Y Y Y Y Y 291 .

Chapter 3 MOUT_GL_INTERFACE Table Column Name FC07 FC08 FC09 FC10 FC11 FC12 FC13 FC14 FC15 PROJDATA1 PROJDATA2 PROJDATA3 PROJDATA4 PROJDATA5 PROJDATA6 PROJDATA7 PROJDATA8 PROJDATA9 PROJDATA10 PROJDATA11 PROJDATA12 PROJDATA13 SERVRECTRANS Table Length Nulls Column Name Type 292 .

Using the Integration Module MOUT_GL_INTERFACE Table Column Name PROJDATA14 PROJDATA15 SERVRECTRANS Table Length Nulls Column Name Type ROWSTAMP USERDATA1 USERDATA2 USERDATA3 USERDATA4 USERDATA5 USERDATA6 USERDATA7 USERDATA8 USERDATA9 USERDATA10 ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN 1 1 1 1 1 1 1 1 1 1 Y Y Y Y Y Y Y Y Y Y BATCHID BATCHLINEID ALN INTEGER 25 4 Y Y UTRANSTYPE ALN 25 Y 293 .

Chapter 3 MOUT_GL_INTERFACE Table Column Name SOURCEID APISEQ APISITE SERVRECTRANS Table Length 25 4 Type ALN INTEGER Nulls Y Y Column Name SOURCEID APISEQ SENDERSYSID SOURCESYSID OWNERSYSID EXTERNALREFID ISSUEID INVTRANSID SENDERSYSID SOURCESYSID OWNERSYSID EXTERNALREFID IMPORTSTATUS IMPORTTIMESTAMP IMPORTMESSAGE ALN 40 Y Y Y DATETIME 10 ALN 2000 294 .

MOUT_GL_INTERFACE Table Column Name GLDEBITACCT GLCREDITACCT FINANCIALPERIOD LABTRANS Table Length Nulls 20 20 4 Y Y Y Type ALN ALN ALN Column Name GLDEBITACCT GLCREDITACCT FINANCIALPERIOD TRANSDATE ENTERDATE TRANSTYPE DATETIME DATETIME UPPER 10 10 16 N Y Y TRANSDATE ENTERDATE TRANSTYPE DESCRIPTION ITEMNUM STORELOC BINNUM QUANTITY FROMSTORELOC ALN UPPER UPPER ALN DECIMAL UPPER 254 8 8 8 15 8 Y Y Y Y Y Y UNITCOST LINECOST AMOUNT DECIMAL 10 10 Y N PAYRATE*OTSCALE LINECOST 295 . 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.Using the Integration Module The following table shows the mapping for the MOUT_GL_INTERFACE and LABTRANS tables.

Chapter 3 MOUT_GL_INTERFACE Table Column Name PONUM POLINENUM LABTRANS Table Length Nulls 8 4 Y Y Type UPPER INTEGER Column Name PONUM POLINENUM INVOICENUM INVOICELINENUM COSTLINENUM UPPER INTEGER INTEGER 8 4 4 Y Y Y WONUM WPOPERATION EQNUM LOCATION UPPER INTEGER UPPER UPPER 10 4 8 8 Y Y Y Y WONUM WPOPERATION EQNUM LOCATION CLAIMNUM UPPER 8 Y CURRENCYCODE CURRENCYUNITCOST CURRENCYLINECOST EXCHANGERATE UPPER DECIMAL DECIMAL DECIMAL 8 10 10 10 Y Y Y Y JE1 JE2 JE3 ALN ALN ALN 254 254 254 Y Y Y LT1 LT2 LT3 296 .

Using the Integration Module MOUT_GL_INTERFACE Table Column Name JE4 JE5 JE6 JE7 JE8 LABTRANS Table Length Nulls 254 254 254 254 254 Y Y Y Y Y Type ALN ALN ALN ALN ALN Column Name LT4 LT5 LTL1 LTL2 LTL3 LABORCODE CRAFT REGULARHRS OTHRS UPPER UPPER DURATION DURATION 8 8 8 8 Y Y Y Y LABORCODE CRAFT REGULARHRS OTHRS TOOLNUM UPPER 8 Y VENDOR UPPER 8 Y ENTERBY MEMO UPPER ALN 18 254 N Y ENTERBY MEMO FROMLOT TOLOT LOADEDCOST TAX1CODE 297 .

Chapter 3 MOUT_GL_INTERFACE Table Column Name TAX1 TAX2CODE TAX2 TAX3CODE TAX3 TAX4CODE TAX4 TAX5CODE TAX5 PRORATED PRORATECOST STATUS STATUSDATE STATUSCHANGEBY LABTRANS Table Length Nulls Column Name Type GENAPPRSERVRECEIPT PAYMENTRANSDATE AGREEMENTPONUM AGREEMENTPOTYPE PRORATESERVICE GENAPPRSERVRECEIPT PAYMENTTRANSDATE CURRENCYCODE2 298 .

Using the Integration Module MOUT_GL_INTERFACE Table Column Name EXCHANGERATE2 LINECOST2 LABTRANS Table Length Nulls Column Name EXCHANGERATE2 LINECOST2 Type FINCNTRLID BUDGETID BUDGETLINEID PROJECTID TASKID BUDGETTYPE PROJECTTYPE TASKTYPE BUDGETREF BUDGETLINEREF PROJECTREF TASKREF ISCHARGEABLE FC01 FC02 FC03 FC04 FC05 FC06 ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN 8 25 25 25 25 30 30 30 50 50 50 50 Y Y Y Y Y Y Y Y Y Y Y Y 299 .

Chapter 3 MOUT_GL_INTERFACE Table Column Name FC07 FC08 FC09 FC10 FC11 FC12 FC13 FC14 FC15 PROJDATA1 PROJDATA2 PROJDATA3 PROJDATA4 PROJDATA5 PROJDATA6 PROJDATA7 PROJDATA8 PROJDATA9 PROJDATA10 PROJDATA11 PROJDATA12 PROJDATA13 LABTRANS Table Length Nulls Column Name Type 300 .

Using the Integration Module MOUT_GL_INTERFACE Table Column Name PROJDATA14 PROJDATA15 LABTRANS Table Length Nulls Column Name Type ROWSTAMP USERDATA1 USERDATA2 USERDATA3 USERDATA4 USERDATA5 USERDATA6 USERDATA7 USERDATA8 USERDATA9 USERDATA10 ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN 1 1 1 1 1 1 1 1 1 1 Y Y Y Y Y Y Y Y Y Y BATCHID BATCHLINEID ALN INTEGER 25 4 Y Y UTRANSTYPE ALN 25 Y 301 .

Chapter 3 MOUT_GL_INTERFACE Table Column Name SOURCEID APISEQ APISITE LABTRANS Table Length Nulls 25 4 Y Y Type ALN INTEGER Column Name SOURCEID APISEQ SENDERSYSID SOURCESYSID OWNERSYSID EXTERNALREFID ISSUEID INVTRANSID SENDERSYSID SOURCESYSID OWNERSYSID EXTERNALREFID IMPORTSTATUS IMPORTTIMESTAMP IMPORTMESSAGE ALN DATETIME ALN 40 10 2000 Y Y Y 302 .

They are there to separate information coming from different tables or to group sets of data. Empty rows in the table are not physical rows in the database.Using the Integration Module The following table shows the mapping for MOUT_GL_INTERFACE and the INVOICETRANS. INVOICELINE and INVOICECOST tables. MOUT_GL_INTERFACE Table Column Name GLDEBITACCT GLCREDITACCT FINANCIALPERIOD INVOICETRANS / INVOICELINE / INVOICECOST Tables Length Nulls 20 20 4 Y Y Y Type ALN ALN ALN Column Name GLDEBITACCT GLCREDITACCT FINANCIALPERIOD TRANSDATE ENTERDATE TRANSTYPE DATETIME 10 DATETIME 10 UPPER 16 N Y Y TRANSDATE TRANSDATE TRANSTYPE DESCRIPTION ITEMNUM STORELOC BINNUM QUANTITY FROMSTORELOC ALN UPPER UPPER ALN DECIMAL UPPER 254 8 8 8 15 8 Y Y Y Y Y Y UNITCOST LINECOST AMOUNT DECIMAL 10 10 Y N LINECOST 303 .

PONUM LINE.WONUM COST.Chapter 3 MOUT_GL_INTERFACE Table Column Name PONUM POLINENUM INVOICETRANS / INVOICELINE / INVOICECOST Tables Length Nulls 8 4 Y Y Type UPPER INTEGER Column Name LINE.POLINENUM INVOICENUM INVOICELINENUM COSTLINENUM UPPER INTEGER INTEGER 8 4 4 Y Y Y INVOICENUM INVOICELINENUM COSTLINENUM WONUM WPOPERATION EQNUM LOCATION UPPER INTEGER UPPER UPPER 10 4 8 8 Y Y Y Y COST.WPOPERATION COST.LOCATION CLAIMNUM UPPER 8 Y CURRENCYCODE CURRENCYUNITCOST CURRENCYLINECOST EXCHANGERATE UPPER DECIMAL DECIMAL DECIMAL 8 10 10 10 Y Y Y Y CURRENCYCODE CURRENCYLINECOST EXCHANGERATE JE1 JE2 ALN ALN 254 254 Y Y 304 .EQNUM COST.

Using the Integration Module MOUT_GL_INTERFACE Table Column Name JE3 JE4 JE5 JE6 JE7 JE8 INVOICETRANS / INVOICELINE / INVOICECOST Tables Length Nulls 254 254 254 254 254 254 Y Y Y Y Y Y Type ALN ALN ALN ALN ALN ALN Column Name LABORCODE CRAFT REGULARHRS OTHRS UPPER UPPER 8 8 Y Y Y Y DURATION 8 DURATION 8 TOOLNUM UPPER 8 Y VENDOR UPPER 8 Y VENDOR ENTERBY MEMO UPPER ALN 18 254 N Y ENTERBY FROMLOT TOLOT 305 .

Chapter 3 MOUT_GL_INTERFACE Table Column Name LOADEDCOST TAX1CODE TAX1 TAX2CODE TAX2 TAX3CODE TAX3 TAX4CODE TAX4 TAX5CODE TAX5 PRORATED PRORATECOST STATUS STATUSDATE STATUSCHANGEBY INVOICETRANS / INVOICELINE / INVOICECOST Tables Length Nulls Column Name Type GENAPPRSERVRECEIPT PAYMENTRANSDATE AGREEMENTPONUM AGREEMENTPOTYPE AGREEMENTPONUM AGREEMENTPOTYPE 306 .

Using the Integration Module MOUT_GL_INTERFACE Table Column Name PRORATESERVICE INVOICETRANS / INVOICELINE / INVOICECOST Tables Length Nulls Column Name PRORATESERVICE Type CURRENCYCODE2 EXCHANGERATE2 LINECOST2 EXCHANGERATE2 LINECOST2 FINCNTRLID BUDGETID BUDGETLINEID PROJECTID TASKID BUDGETTYPE PROJECTTYPE TASKTYPE BUDGETREF BUDGETLINEREF PROJECTREF TASKREF ISCHARGEABLE FC01 FC02 ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN 8 25 25 25 25 30 30 30 50 50 50 50 Y Y Y Y Y Y Y Y Y Y Y Y 307 .

Chapter 3 MOUT_GL_INTERFACE Table Column Name FC03 FC04 FC05 FC06 FC07 FC08 FC09 FC10 FC11 FC12 FC13 FC14 FC15 PROJDATA1 PROJDATA2 PROJDATA3 PROJDATA4 PROJDATA5 PROJDATA6 PROJDATA7 PROJDATA8 INVOICETRANS / INVOICELINE / INVOICECOST Tables Length Nulls Column Name Type 308 .

Using the Integration Module MOUT_GL_INTERFACE Table Column Name PROJDATA9 PROJDATA10 PROJDATA11 PROJDATA12 PROJDATA13 PROJDATA14 PROJDATA15 INVOICETRANS / INVOICELINE / INVOICECOST Tables Length Nulls Column Name Type ROWSTAMP USERDATA1 USERDATA2 USERDATA3 USERDATA4 USERDATA5 USERDATA6 USERDATA7 USERDATA8 USERDATA9 USERDATA10 ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN 1 1 1 1 1 1 1 1 1 1 Y Y Y Y Y Y Y Y Y Y 309 .

Chapter 3 MOUT_GL_INTERFACE Table Column Name Type Length Nulls INVOICETRANS / INVOICELINE / INVOICECOST Tables Column Name BATCHID BATCHLINEID ALN INTEGER 25 4 Y Y UTRANSTYPE ALN 25 Y SOURCEID APISEQ APISITE ALN INTEGER 25 4 Y Y SOURCEID APISEQ SENDERSYSID SOURCESYSID OWNERSYSID EXTERNALREFID ISSUEID INVTRANSID SENDERSYSID SOURCESYSID OWNERSYSID EXTERNALREFID IMPORTSTATUS IMPORTTIMESTAMP IMPORTMESSAGE ALN 40 Y Y Y DATETIME 10 ALN 2000 310 .

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.Using the Integration Module The following table shows the mapping for MOUT_GL_INTERFACE and TOOLTRANS. MOUT_GL_INTERFACE Table Column Name GLDEBITACCT GLCREDITACCT FINANCIALPERIOD TOOLTRANS Table Length 20 20 4 Type ALN ALN ALN Nulls Y Y Y Column Name GLDEBITACCT GLCREDITACCT FINANCIALPERIOD TRANSDATE ENTERDATE TRANSTYPE DATETIME DATETIME UPPER 10 10 16 N Y Y TRANSDATE ENTERDATE DESCRIPTION ITEMNUM STORELOC BINNUM QUANTITY FROMSTORELOC ALN UPPER UPPER ALN DECIMAL UPPER 254 8 8 8 15 8 Y Y Y Y Y Y TOOLQTY UNITCOST LINECOST AMOUNT DECIMAL 10 10 Y N TOOLRATE LINECOST 311 .

Chapter 3 MOUT_GL_INTERFACE Table Column Name PONUM POLINENUM TOOLTRANS Table Length 8 4 Type UPPER INTEGER Nulls Y Y Column Name INVOICENUM INVOICELINENUM COSTLINENUM UPPER INTEGER INTEGER 8 4 4 Y Y Y WONUM WPOPERATION EQNUM LOCATION UPPER INTEGER UPPER UPPER 10 4 8 8 Y Y Y Y WONUM WPOPERATION EQNUM LOCATION CLAIMNUM UPPER 8 Y CURRENCYCODE CURRENCYUNITCOST CURRENCYLINECOST EXCHANGERATE UPPER DECIMAL DECIMAL DECIMAL 8 10 10 10 Y Y Y Y JE1 JE2 JE3 ALN ALN ALN 254 254 254 Y Y Y TT1 TT2 TT3 312 .

Using the Integration Module MOUT_GL_INTERFACE Table Column Name JE4 JE5 JE6 JE7 JE8 TOOLTRANS Table Length 254 254 254 254 254 Type ALN ALN ALN ALN ALN Nulls Y Y Y Y Y Column Name TT4 TT5 LABORCODE CRAFT REGULARHRS OTHRS UPPER UPPER DURATION DURATION 8 8 8 8 Y Y Y Y TOOLHRS TOOLNUM UPPER 8 Y TOOLNUM VENDOR UPPER 8 Y ENTERBY MEMO UPPER ALN 18 254 N Y ENTERBY FROMLOT TOLOT LOADEDCOST TAX1CODE 313 .

Chapter 3 MOUT_GL_INTERFACE Table Column Name TAX1 TAX2CODE TAX2 TAX3CODE TAX3 TAX4CODE TAX4 TAX5CODE TAX5 PRORATED PRORATECOST STATUS STATUSDATE STATUSCHANGEBY TOOLTRANS Table Length Nulls Column Name Type GENAPPRSERVRECEIPT PAYMENTRANSDATE AGREEMENTPONUM AGREEMENTPOTYPE PRORATESERVICE CURRENCYCODE2 314 .

Using the Integration Module MOUT_GL_INTERFACE Table Column Name EXCHANGERATE2 LINECOST2 TOOLTRANS Table Length Nulls Column Name EXCHANGERATE2 LINECOST2 Type FINCNTRLID BUDGETID BUDGETLINEID PROJECTID TASKID BUDGETTYPE PROJECTTYPE TASKTYPE BUDGETREF BUDGETLINEREF PROJECTREF TASKREF ISCHARGEABLE FC01 FC02 FC03 FC04 FC05 FC06 ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN 8 25 25 25 25 30 30 30 50 50 50 50 Y Y Y Y Y Y Y Y Y Y Y Y 315 .

Chapter 3 MOUT_GL_INTERFACE Table Column Name FC07 FC08 FC09 FC10 FC11 FC12 FC13 FC14 FC15 PROJDATA1 PROJDATA2 PROJDATA3 PROJDATA4 PROJDATA5 PROJDATA6 PROJDATA7 PROJDATA8 PROJDATA9 PROJDATA10 PROJDATA11 PROJDATA12 PROJDATA13 TOOLTRANS Table Length Nulls Column Name Type 316 .

Using the Integration Module MOUT_GL_INTERFACE Table Column Name PROJDATA14 PROJDATA15 TOOLTRANS Table Length Nulls Column Name Type ROWSTAMP USERDATA1 USERDATA2 USERDATA3 USERDATA4 USERDATA5 USERDATA6 USERDATA7 USERDATA8 USERDATA9 USERDATA10 ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN 1 1 1 1 1 1 1 1 1 1 Y Y Y Y Y Y Y Y Y Y BATCHID BATCHLINEID ALN INTEGER 25 4 Y Y UTRANSTYPE ALN 25 Y SOURCEID ALN 25 Y SOURCEID 317 .

Chapter 3 MOUT_GL_INTERFACE Table Column Name APISEQ APISITE TOOLTRANS Table Length 4 Type INTEGER Nulls Y Column Name APISEQ SENDERSYSID SOURCESYSID OWNERSYSID EXTERNALREFID ISSUEID INVTRANSID SENDERSYSID SOURCESYSID OWNERSYSID EXTERNALREFID IMPORTSTATUS IMPORTTIMESTAMP IMPORTMESSAGE ALN DATETIME ALN 40 10 2000 Y Y Y 318 .

MAX_COA_INTERFACE Table Column Name GLACCOUNT GLCOMP01 COMPTEXT01 GLCOMP02 COMPTEXT02 GLCOMP03 COMPTEXT03 GLCOMP04 COMPTEXT04 GLCOMP05 COMPTEXT05 GLCOMP06 COMPTEXT06 GLCOMP07 COMPTEXT07 GLCOMP08 COMPTEXT08 MAXIMO Tables Length Nulls Table 20 4 30 3 30 3 30 20 30 20 30 20 30 20 30 20 30 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y CHARTOFACCOUNTS CHARTOFACCOUNTS GLCOMPONENTS CHARTOFACCOUNTS GLCOMPONENTS CHARTOFACCOUNTS GLCOMPONENTS CHARTOFACCOUNTS GLCOMPONENTS CHARTOFACCOUNTS GLCOMPONENTS CHARTOFACCOUNTS GLCOMPONENTS CHARTOFACCOUNTS GLCOMPONENTS CHARTOFACCOUNTS GLCOMPONENTS Type ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN Column Name GLACCOUNT GLCOMP01 COMPTEXT GLCOMP02 COMPTEXT GLCOMP03 COMPTEXT GLCOMP04 COMPTEXT GLCOMP05 COMPTEXT GLCOMP06 COMPTEXT GLCOMP07 COMPTEXT GLCOMP08 COMPTEXT 319 . Empty rows in the table are not physical rows in the database.Using the Integration Module MAX_COA_INTERFACE Table MAX_COA_INTERFACE receives chart of accounts data from Oracle Financials. They are there to separate information coming from different tables or to group sets of data. Data is sent to the following MAXIMO tables.

Chapter 3 MAX_COA_INTERFACE Table Column Name GLCOMP09 COMPTEXT09 GLCOMP10 COMPTEXT10 GLCOMP11 COMPTEXT11 GLCOMP12 COMPTEXT12 GLCOMP13 COMPTEXT13 GLCOMP14 COMPTEXT14 GLCOMP15 COMPTEXT15 GLCOMP16 COMPTEXT16 GLCOMP17 COMPTEXT17 GLCOMP18 COMPTEXT18 GLCOMP19 COMPTEXT19 MAXIMO Tables Length Nulls Table 20 30 20 30 20 30 20 30 20 30 20 30 20 30 20 30 20 30 20 30 20 30 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y CHARTOFACCOUNTS GLCOMPONENTS CHARTOFACCOUNTS GLCOMPONENTS CHARTOFACCOUNTS GLCOMPONENTS CHARTOFACCOUNTS GLCOMPONENTS CHARTOFACCOUNTS GLCOMPONENTS CHARTOFACCOUNTS GLCOMPONENTS CHARTOFACCOUNTS GLCOMPONENTS CHARTOFACCOUNTS GLCOMPONENTS CHARTOFACCOUNTS GLCOMPONENTS CHARTOFACCOUNTS GLCOMPONENTS CHARTOFACCOUNTS GLCOMPONENTS Type ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN Column Name GLCOMP09 COMPTEXT GLCOMP10 COMPTEXT GLCOMP11 COMPTEXT GLCOMP12 COMPTEXT GLCOMP13 COMPTEXT GLCOMP14 COMPTEXT GLCOMP15 COMPTEXT GLCOMP16 COMPTEXT GLCOMP17 COMPTEXT GLCOMP18 COMPTEXT GLCOMP19 COMPTEXT 320 .

2 4 1 1 1 1 1 1 1 1 1 1 1 1 1 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y CHARTOFACCOUNTS GLCOMPONENTS CHARTOFACCOUNTS CHARTOFACCOUNTS CHARTOFACCOUNTS CHARTOFACCOUNTS CHARTOFACCOUNTS CHARTOFACCOUNTS CHARTOFACCOUNTS CHARTOFACCOUNTS CHARTOFACCOUNTS CHARTOFACCOUNTS CHARTOFACCOUNTS CHARTOFACCOUNTS CHARTOFACCOUNTS CHARTOFACCOUNTS CHARTOFACCOUNTS CHARTOFACCOUNTS CHARTOFACCOUNTS CHARTOFACCOUNTS CHARTOFACCOUNTS CHARTOFACCOUNTS Type ALN ALN ALN ALN ALN ALN ALN DECIMAL INTEGER YORN YORN YORN YORN YORN YORN YORN YORN YORN YORN YORN YORN YORN Column Name GLCOMP20 COMPTEXT ACCOUNTNAME GLACCTYPE CH1 CH2 CH3 CH4 CH5 DISABLED DISABLED DISABLED DISABLED DISABLED DISABLED DISABLED DISABLED DISABLED DISABLED DISABLED DISABLED DISABLED 321 .Using the Integration Module MAX_COA_INTERFACE Table Column Name GLCOMP20 COMPTEXT20 ACCOUNTNAME GLACCTYPE CH1 CH2 CH3 CH4 CH5 DISABLED DISABLED01 DISABLED02 DISABLED03 DISABLED04 DISABLED05 DISABLED06 DISABLED07 DISABLED08 DISABLED09 DISABLED10 DISABLED11 DISABLED12 MAXIMO Tables Length Nulls Table 20 30 50 3 10 10 10 15.

Chapter 3 MAX_COA_INTERFACE Table Column Name DISABLED13 DISABLED14 DISABLED15 DISABLED16 DISABLED17 DISABLED18 DISABLED19 DISABLED20 SOURCESYSID OWNERSYSID EXTERNALREFID MAXIMO Tables Length Nulls Table 1 1 1 1 1 1 1 1 10 10 10 Y Y Y Y Y Y Y Y Y Y Y CHARTOFACCOUNTS CHARTOFACCOUNTS CHARTOFACCOUNTS CHARTOFACCOUNTS CHARTOFACCOUNTS CHARTOFACCOUNTS CHARTOFACCOUNTS CHARTOFACCOUNTS CHARTOFACCOUNTS CHARTOFACCOUNTS CHARTOFACCOUNTS Type YORN YORN YORN YORN YORN YORN YORN YORN ALN ALN ALN Column Name DISABLED DISABLED DISABLED DISABLED DISABLED DISABLED DISABLED DISABLED SOURCESYSID OWNERSYSID EXTERNALREFID USERDATA1 USERDATA2 USERDATA3 USERDATA4 USERDATA5 USERDATA6 USERDATA7 USERDATA8 USERDATA9 ALN ALN ALN ALN ALN ALN ALN ALN ALN 1 1 1 1 1 1 1 1 1 Y Y Y Y Y Y Y Y Y 322 .

Data is sent to the following MAXIMO tables. MAX_COAX_INTERFACE Table Column Name GLCOMP01 GLCOMP02 MAXIMO Tables Length Nulls Table 3 4 Y Y GLCOMPONENTS GLCOMPONENTS Type ALN ALN Column Name COMPVALUE COMPVALUE 323 . They are there to separate information coming from different tables or to group sets of data.Using the Integration Module MAX_COA_INTERFACE Table Column Name USERDATA10 MAXIMO Tables Length Nulls Table 1 Y Type ALN Column Name UTRANSTYPE ALN 25 Y SOURCEID APISEQ APISITE SENDERSYSID ALN INTEGER ALN ALN 25 4 256 50 Y Y Y Y CHARTOFACCOUNTS CHARTOFACCOUNTS SOURCEID APISEQ CHARTOFACCOUNTS SENDERSYSID IMPORTSTATUS ALN 40 Y Y Y IMPORTTIMESTAMP DATETIME 10 IMPORTMESSAGE ALN 2000 MAX_COAX_INTERFACE Table MAX_COAX_INTERFACE receives GL component data from Oracle Financials. Empty rows in the table are not physical rows in the database.

Chapter 3 MAX_COAX_INTERFACE Table Column Name GLCOMP03 GLCOMP04 GLCOMP05 GLCOMP06 GLCOMP07 GLCOMP08 GLCOMP09 GLCOMP10 GLCOMP11 GLCOMP12 GLCOMP13 GLCOMP14 GLCOMP15 GLCOMP16 GLCOMP17 GLCOMP18 GLCOMP19 GLCOMP20 COMPTEXT01 COMPTEXT02 COMPTEXT03 COMPTEXT04 MAXIMO Tables Length Nulls Table 3 3 10 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 30 30 30 30 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS Type ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN Column Name COMPVALUE COMPVALUE COMPVALUE COMPVALUE COMPVALUE COMPVALUE COMPVALUE COMPVALUE COMPVALUE COMPVALUE COMPVALUE COMPVALUE COMPVALUE COMPVALUE COMPVALUE COMPVALUE COMPVALUE COMPVALUE COMPTEXT COMPTEXT COMPTEXT COMPTEXT 324 .

Using the Integration Module MAX_COAX_INTERFACE Table Column Name COMPTEXT05 COMPTEXT06 COMPTEXT07 COMPTEXT08 COMPTEXT09 COMPTEXT10 COMPTEXT11 COMPTEXT12 COMPTEXT13 COMPTEXT14 COMPTEXT15 COMPTEXT16 COMPTEXT17 COMPTEXT18 COMPTEXT19 COMPTEXT20 DISABLED01 DISABLED02 DISABLED03 DISABLED04 DISABLED05 DISABLED06 MAXIMO Tables Length Nulls Table 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 1 1 1 1 1 1 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS Type ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN Column Name COMPTEXT COMPTEXT COMPTEXT COMPTEXT COMPTEXT COMPTEXT COMPTEXT COMPTEXT COMPTEXT COMPTEXT COMPTEXT COMPTEXT COMPTEXT COMPTEXT COMPTEXT COMPTEXT DISABLED DISABLED DISABLED DISABLED DISABLED DISABLED 325 .

Chapter 3 MAX_COAX_INTERFACE Table Column Name DISABLED07 DISABLED08 DISABLED09 DISABLED10 DISABLED11 DISABLED12 DISABLED13 DISABLED14 DISABLED15 DISABLED16 DISABLED17 DISABLED18 DISABLED19 DISABLED20 SOURCESYSID OWNERSYSID EXTERNALREFID MAXIMO Tables Length Nulls Table 1 1 1 1 1 1 1 1 1 1 1 1 1 1 10 10 10 Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS GLCOMPONENTS CHARTOFACCOUNTS CHARTOFACCOUNTS CHARTOFACCOUNTS Type ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN Column Name DISABLED DISABLED DISABLED DISABLED DISABLED DISABLED DISABLED DISABLED DISABLED DISABLED DISABLED DISABLED DISABLED DISABLED SOURCESYSID OWNERSYSID EXTERNALREFID USERDATA1 USERDATA2 USERDATA3 USERDATA4 ALN ALN ALN ALN 1 1 1 1 Y Y Y Y 326 .

Using the Integration Module MAX_COAX_INTERFACE Table Column Name USERDATA5 USERDATA6 USERDATA7 USERDATA8 USERDATA9 USERDATA10 MAXIMO Tables Length Nulls Table 1 1 1 1 1 1 Y Y Y Y Y Y Type ALN ALN ALN ALN ALN ALN Column Name UTRANSTYPE ALN 25 Y SOURCEID APISEQ APISITE SENDERSYSID ALN INTEGER ALN ALN 25 4 256 50 Y Y Y Y CHARTOFACCOUNTS CHARTOFACCOUNTS SOURCEID APISEQ GLCOMPONENTS SENDERSYSID IMPORTSTATUS ALN 40 Y Y Y IMPORTTIMESTAMP DATETIME 10 IMPORTMESSAGE ALN 2000 327 .

MAXIMO MAX_COA_ INTERFACE GLACCOUNT GLCOMP01 GLCOMP02 GLCOMP03 GLCOMP04 GLCOMP05 GLCOMP06 GLCOMP07 GLCOMP08 GLCOMP09 GLCOMP10 GLCOMP11 GLCOMP12 GLCOMP13 GLCOMP14 GLCOMP15 Oracle Financials Table.SEGMENT10 GL_CODE_COMBINATIONS.SEGMENT14 GL_CODE_COMBINATIONS.SEGMENT13 GL_CODE_COMBINATIONS.SEGMENT1 GL_CODE_COMBINATIONS.SEGMENT3 GL_CODE_COMBINATIONS.SEGMENT11 GL_CODE_COMBINATIONS.Column GL_CODE_COMBINATIONS.Chapter 3 General Ledger Code Combinations from Oracle Financials This section provides the cross mapping for the interface tables that are used when transferring valid general ledger (GL) account data between MAXIMO and Oracle Financials applications.20 GL_CODE_COMBINATIONS.SEGMENT12 GL_CODE_COMBINATIONS..SEGMENT15 API variable gl_segment1.SEGMENT7 GL_CODE_COMBINATIONS.SEGMENT9 GL_CODE_COMBINATIONS.SEGMENT6 GL_CODE_COMBINATIONS.SEGMENT1.SEGMENT2 GL_CODE_COMBINATIONS.SEGMENT5 GL_CODE_COMBINATIONS..SEGMENT8 GL_CODE_COMBINATIONS.SEGMENT4 GL_CODE_COMBINATIONS.gl_segment20 gl_segment1 gl_segment2 gl_segment3 gl_segment4 gl_segment5 gl_segment6 gl_segment7 gl_segment8 gl_segment9 gl_segment10 gl_segment11 gl_segment12 gl_segment13 gl_segment14 gl_segment15 328 . Note that variable length code combinations are not supported in MAXIMO. Data is transferred from several Oracle Financials general ledger tables to the MAXIMO MAX_COA_INTERFACE table.

DESCRIPTION FND_FLEX_VALUES.SEGMENT16 GL_CODE_COMBINATIONS.DESCRIPTION FND_FLEX_VALUES.Column GL_CODE_COMBINATIONS.DESCRIPTION FND_FLEX_VALUES.DESCRIPTION FND_FLEX_VALUES.DESCRIPTION FND_FLEX_VALUES.Using the Integration Module MAXIMO MAX_COA_ INTERFACE GLCOMP16 GLCOMP17 GLCOMP18 GLCOMP19 GLCOMP20 COMPTEXT01 COMPTEXT02 COMPTEXT03 COMPTEXT04 COMPTEXT05 COMPTEXT06 COMPTEXT07 COMPTEXT08 COMPTEXT09 COMPTEXT10 COMPTEXT11 COMPTEXT12 COMPTEXT13 COMPTEXT14 COMPTEXT15 COMPTEXT16 COMPTEXT17 COMPTEXT18 COMPTEXT19 COMPTEXT20 ACCOUNTNAME Oracle Financials Table.DESCRIPTION FND_FLEX_VALUES.DESCRIPTION FND_FLEX_VALUES.SEGMENT18 GL_CODE_COMBINATIONS.DESCRIPTION GL_CODE_COMBINATIONS.SEGMENT17 GL_CODE_COMBINATIONS.SEGMENT19 GL_CODE_COMBINATIONS.DESCRIPTION FND_FLEX_VALUES.DESCRIPTION FND_FLEX_VALUES.DESCRIPTION FND_FLEX_VALUES.DESCRIPTION FND_FLEX_VALUES.DESCRIPTION FND_FLEX_VALUES.DESCRIPTION FND_FLEX_VALUES.DESCRIPTION FND_FLEX_VALUES.SEGMENT20 FND_FLEX_VALUES.DESCRIPTION FND_FLEX_VALUES.DESCRIPTION FND_FLEX_VALUES.DESCRIPTION FND_FLEX_VALUES.DESCRIPTION FND_FLEX_VALUES.DESCRIPTION FND_FLEX_VALUES.DESCRIPTION API variable gl_segment16 gl_segment17 gl_segment18 gl_segment19 gl_segment20 gl_segment_name1 gl_segment_name2 gl_segment_name3 gl_segment_name4 gl_segment_name5 gl_segment_name6 gl_segment_name7 gl_segment_name8 gl_segment_name9 gl_segment_name10 gl_segment_name11 gl_segment_name12 gl_segment_name13 gl_segment_name14 gl_segment_name15 gl_segment_name16 gl_segment_name17 gl_segment_name18 gl_segment_name19 gl_segment_name20 gl_desc 329 .

concatenate first 15 characters of each COMPTEXT) GL_CODE_COMBINATIONS.ACCOUNT_TYPE API variable gl_account_type GL_CODE_COMBINATIONS.ENABLED_FLAG vdisabled 330 .Chapter 3 MAXIMO MAX_COA_ INTERFACE GLACCTYPE CH1 CH2 CH3 CH4 CH5 DISABLED USERDATA1 USERDATA2 USERDATA3 USERDATA4 USERDATA5 USERDATA6 USERDATA7 USERDATA8 USERDATA9 USERDATA10 UTRANSTYPE Oracle Financials Table.Column (or if null.

flex_value FND_FLEX_VALUE.flex_value FND_FLEX_VALUE. If the API disables a component within MAXIMO.flex_value FND_FLEX_VALUE.flex_value FND_FLEX_VALUE. This interface will send components to MAXIMO when a component is added or when the component has a change in its description or enabled flag.flex_value FND_FLEX_VALUE.flex_value API variable flex_value flex_value flex_value flex_value flex_value flex_value flex_value flex_value flex_value flex_value flex_value flex_value flex_value flex_value flex_value 331 .Using the Integration Module General Ledger Components from Oracle Financials This section provides the cross mapping for the interface tables that are used when transferring general ledger (GL) component data from Oracle Financials to MAXIMO. it will search and disable any chart of account that contains that component.flex_value FND_FLEX_VALUE.flex_value FND_FLEX_VALUE. The data is populated into the appropriate columns based on the component’s segment number within Oracle Financials. Only one component is interface per transaction.flex_value FND_FLEX_VALUE. Data is transferred from several Oracle Financials general ledger tables to the MAXIMO MAX_COAX_INTERFACE table.flex_value FND_FLEX_VALUE.flex_value FND_FLEX_VALUE.flex_value FND_FLEX_VALUE.flex_value FND_FLEX_VALUE.Column FND_FLEX_VALUE.flex_value FND_FLEX_VALUE.flex_value FND_FLEX_VALUE. MAXIMO MAX_COAX_INTERFACE GLCOMP01 GLCOMP02 GLCOMP03 GLCOMP04 GLCOMP05 GLCOMP06 GLCOMP07 GLCOMP08 GLCOMP09 GLCOMP10 GLCOMP11 GLCOMP12 GLCOMP13 GLCOMP14 GLCOMP15 Oracle Financials Table.

DESCRIPTION FND_FLEX_VALUES.flex_value FND_FLEX_VALUE.DESCRIPTION FND_FLEX_VALUES.DESCRIPTION FND_FLEX_VALUES.DESCRIPTION FND_FLEX_VALUES.DESCRIPTION FND_FLEX_VALUES.Column FND_FLEX_VALUE.DESCRIPTION FND_FLEX_VALUES.ENABLED_FLAG FND_FLEX_VALUES.DESCRIPTION FND_FLEX_VALUES.DESCRIPTION FND_FLEX_VALUES.DESCRIPTION FND_FLEX_VALUES.DESCRIPTION FND_FLEX_VALUES.flex_value FND_FLEX_VALUE.ENABLED_FLAG API variable flex_value flex_value flex_value flex_value flex_value description description description description description description description description description description description description description description description description description description description description enabled_flag (Y/N reversed) enabled_flag (Y/N reversed) enabled_flag (Y/N reversed) 332 .DESCRIPTION FND_FLEX_VALUES.DESCRIPTION FND_FLEX_VALUES.flex_value FND_FLEX_VALUE.flex_value FND_FLEX_VALUES.Chapter 3 MAXIMO MAX_COAX_INTERFACE GLCOMP16 GLCOMP17 GLCOMP18 GLCOMP19 GLCOMP20 COMPTEXT01 COMPTEXT02 COMPTEXT03 COMPTEXT04 COMPTEXT05 COMPTEXT06 COMPTEXT07 COMPTEXT08 COMPTEXT09 COMPTEXT10 COMPTEXT11 COMPTEXT12 COMPTEXT13 COMPTEXT14 COMPTEXT15 COMPTEXT16 COMPTEXT17 COMPTEXT18 COMPTEXT19 COMPTEXT20 DISABLED01 DISABLED02 DISABLED03 Oracle Financials Table.DESCRIPTION FND_FLEX_VALUES.DESCRIPTION FND_FLEX_VALUES.DESCRIPTION FND_FLEX_VALUES.DESCRIPTION FND_FLEX_VALUES.ENABLED_FLAG FND_FLEX_VALUES.DESCRIPTION FND_FLEX_VALUES.DESCRIPTION FND_FLEX_VALUES.flex_value FND_FLEX_VALUE.DESCRIPTION FND_FLEX_VALUES.DESCRIPTION FND_FLEX_VALUES.

ENABLED_FLAG FND_FLEX_VALUES.ENABLED_FLAG FND_FLEX_VALUES.ENABLED_FLAG FND_FLEX_VALUES.ENABLED_FLAG FND_FLEX_VALUES.ENABLED_FLAG FND_FLEX_VALUES.ENABLED_FLAG FND_FLEX_VALUES.ENABLED_FLAG FND_FLEX_VALUES.ENABLED_FLAG FND_FLEX_VALUES.ENABLED_FLAG FND_FLEX_VALUES.Using the Integration Module MAXIMO MAX_COAX_INTERFACE DISABLED03 DISABLED04 DISABLED05 DISABLED06 DISABLED07 DISABLED08 DISABLED09 DISABLED010 DISABLED011 DISABLED012 DISABLED013 DISABLED014 DISABLED015 DISABLED016 DISABLED017 DISABLED018 DISABLED019 DISABLED020 USERDATA1 USERDATA2 USERDATA3 USERDATA4 USERDATA5 USERDATA6 USERDATA7 USERDATA8 Oracle Financials Table.ENABLED_FLAG FND_FLEX_VALUES.ENABLED_FLAG FND_FLEX_VALUES.ENABLED_FLAG FND_FLEX_VALUES.ENABLED_FLAG FND_FLEX_VALUES.ENABLED_FLAG FND_FLEX_VALUES.ENABLED_FLAG FND_FLEX_VALUES.ENABLED_FLAG API variable enabled_flag (Y/N reversed) enabled_flag (Y/N reversed) enabled_flag (Y/N reversed) enabled_flag (Y/N reversed) enabled_flag (Y/N reversed) enabled_flag (Y/N reversed) enabled_flag (Y/N reversed) enabled_flag (Y/N reversed) enabled_flag (Y/N reversed) enabled_flag (Y/N reversed) enabled_flag (Y/N reversed) enabled_flag (Y/N reversed) enabled_flag (Y/N reversed) enabled_flag (Y/N reversed) enabled_flag (Y/N reversed) enabled_flag (Y/N reversed) enabled_flag (Y/N reversed) enabled_flag (Y/N reversed) 333 .Column FND_FLEX_VALUES.ENABLED_FLAG FND_FLEX_VALUES.ENABLED_FLAG FND_FLEX_VALUES.

Chapter 3 MAXIMO MAX_COAX_INTERFACE USERDATA9 USERDATA10 UTRANSTYPE Oracle Financials Table.Column API variable 334 .

Using the Integration Module Invoices from Oracle Financials This section provides the cross mapping for the interface tables that are used when transferring invoice data between MAXIMO and Oracle Financials applications.CREATION_DATE AP_INVOICES.INVOICE_CURRENCY_CODE AP_INVOICE_DISTRIBUTIONS.DESCRIPTION PO_HEADERS.INVOICE_NUM AP_INVOICES.SEGMENT1 PO_VENDORS. MAXIMO MAX_AP_INTERFACE INVOICENUM INVOICEDESC PONUM VENDOR CONTACT PAYMENTTERMS CHECKCODE CHECKNUM CURRENCYCODE EXCHANGERATE EXCHANGEDATE DOCUMENTTYPE ORIGINVOICENUM STATUS STATUSDATE APPROVALNUM INVOICEDATE DISCOUNTDATE DUEDATE Oracle Financials Table.NAME AP_INVOICES. Data is transferred from several Oracle Financials accounts payables and purchasing tables to the MAXIMO MAX_AP_INTERFACE table.EXCHANGE_DATE AP_INVOICES.INVOICE_TYPE_LOOKUP_CODE UPPER(invc_curcode) invc_d_xchg_rate invc_d_xchg_date invc_doc_type 'APPR' invc_change_date invc_date AP_INVOICE_DISTRIBUTIONS.EXCHANGE_RATE AP_INVOICE_DISTRIBUTIONS.Column AP_INVOICES.SEGMENT1 API variable UPPER(invc_no) invc_desc UPPER(invc_po_no) UPPER(invc_vnd_no)||''||UPPER(invc_vndsite_code) invc_terms AP_TERMS.INVOICE_DATE 335 .

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

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

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

Using the Integration Module MAXIMO MAX_AP_INTERFACE QUANTITY LOCATION COMPANYTYPE NAME ADDRESS1 ADDRESS2 ADDRESS3 ADDRESS4 POSITION PHONE FAX FOB FREIGHTTERMS SHIPVIA CUSTOMERNUM CO1 CO2 CO3 CO4 CO5 CO6 CO7 CO8 CO9 CO10 CO11 CO12 CO13 Oracle Financials Table.QUANTITY_INVOICED API variable invc_d_qty 339 .Column AP_INVOICE_DISTRIBUTIONS.

Chapter 3 MAXIMO MAX_AP_INTERFACE Table.0) 340 .Column Oracle Financials API variable COMPANYLOC REGISTRATION1 REGISTRATION2 REGISTRATION3 REGISTRATION4 REGISTRATION5 APCONTROLACC APSUSPENSEACC RBNIACC PAYVENDOR BANKACCOUNT REMITCONTACT PAYONRECEIPT HOMEPAGE BANKNUM DUNSNUM TAXEXEMPTCODE TAXEXEMPTNUM ECOMMERCEENABLED ISSUE MANUFACTURER MFGNAME MODELNUM STORELOC FINANCIALPERIOD AP_INVOICE_DISTRIBUTIONS.BASE_INVOICE_PRICE_VARIA NCE DISABLED invc_fp NVL(invc_d_bvar.PERIOD_NAME PRICEVAR AP_INVOICE_DISTRIBUTIONS.

Column API variable 341 .Using the Integration Module MAXIMO MAX_AP_INTERFACE USERDATA1 USERDATA2 USERDATA3 USERDATA4 USERDATA5 USERDATA6 USERDATA7 USERDATA8 USERDATA9 USERDATA10 UTRANSTYPE Oracle Financials Table.

) MAXIMO MAX_ITM_INTERFACE Table.SEGMENT1 MTL_SYSTEM_ITEMS.LOT_CONTROL_CODE FA_CATEGORIES.HAZARD_CLASS Oracle Financials API variable UPPER(mtl_segment1) mtl_desc sNo mtl_itm_type mtl_lot_code mtl_cap_asset_f mtl_hazard_class sNo 342 .CAPITALIZE_FLAG PO_HAZARD_CLASSES.Column ITEMNUM DESCRIPTION ROTATING STOCKTYPE LOTTYPE CAPITALIZED MSDSNUM OUTSIDE IN1 IN2 IN3 IN4 IN5 IN6 IN7 IN8 IN9 IN10 MTL_SYSTEM_ITEMS. Data is transferred from several Oracle Financials inventory tables to the MAXIMO MAX_ITM_INTERFACE table. (Note that the MAXIMO item interface table is also used to transfer data into the MAXIMO Inventory.Chapter 3 Items from Oracle Financials This section provides the cross mapping for the interface tables that are used when transferring item data between MAXIMO and Oracle Financials applications.DESCRIPTION MTL_SYSTEM_ITEMS. The SOURCEID indicates the direction of data and must be present in order to avoid recursive updates or endless loops.ITEM_TYPE MTL_SYSTEM_ITEMS.

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

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

30 GL_CODE_COMBINATIONS..Using the Integration Module MAXIMO MAX_ITM_INTERFACE Table.ORGANIZATION_CODE MTL_SYSTEM_ITEMS.SEGMENT1.Column IL2 IL3 IL4 IL5 IL6 IL7 IL8 IL9 IL10 GLACCOUNT CONTROLACC SHRINKAGEACC INVCOSTADJACC COSTCENTER VENDOR MANUFACTURER MODELNUM CATALOGCODE IV1 IV2 IV3 IVCO1 IVCO2 IVCO3 BIDPRICE BIDDATE PROMDELIVERYTIME VENDORLASTCOST Oracle Financials API variable mtl_sourceorg_code mtl_sourceinv_code ORG_ORGANIZATION_DEFINITIONS..SEGMENT1.30 GL_CODE_COMBINATIONS.SOURCE_SUBINVENTORY GL_CODE_COMBINATIONS.30 mtl_item_gl mtl_shrink_gl mtl_avgvar_gl 345 .SEGMENT1..

Chapter 3 MAXIMO MAX_ITM_INTERFACE Table.Column LASTDATE CATALOGWEBPAGE COMPANYTYPE NAME ADDRESS1 ADDRESS2 ADDRESS3 ADDRESS4 CONTACT POSITION PHONE FAX FOB FREIGHTTERMS SHIPVIA PAYMENTTERMS CUSTOMERNUM CO1 CO2 CO3 CO4 CO5 CO6 CO7 CO8 CO9 CO10 CO11 Oracle Financials API variable 346 .

Using the Integration Module MAXIMO MAX_ITM_INTERFACE Table.LAST_UPDATE_DATE 347 .Column CO12 CO13 CHANGEBY CHANGEDATE INCLUSIVE1 INCLUSIVE2 INCLUSIVE3 INCLUSIVE4 INCLUSIVE5 CURRENCYCODE COMPANYLOC REGISTRATION1 REGISTRATION2 REGISTRATION3 REGISTRATION4 REGISTRATION5 APCONTROLACC APSUSPENSEACC RBNIACC PAYVENDOR BANKACCOUNT REMITCONTACT PAYONRECEIPT HOMEPAGE BANKNUM DUNSNUM TAXEXEMPTCODE TAXEXEMPTNUM Oracle Financials API variable mtl_change_by mtl_change_date FND_USER.USER_NAME MTL_SYSTEM_ITEMS.

Column ECOMMERCEENABLED DISABLED MFGNAME LODESC PUTCHVARACC INVOICEVARACC CURVARACC RECEIPTVARACC USERDATA1 USERDATA2 USERDATA3 USERDATA4 USERDATA5 USERDATA6 USERDATA7 USERDATA8 USERDATA9 USERDATA10 UTRANSTYPE Oracle Financials API variable 348 .Chapter 3 MAXIMO MAX_ITM_INTERFACE Table.

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

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

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

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

Oracle Financials MAXIMO MTL_MATERIAL_TRANSACTION MAX_ITM_INTERFACE Column Name INVENTORY_ITEM_ID Column Name ITEMNUM Type UPPER Length COMMENTS 40 Mapped to UPPER(MTL_SYSTEM_ITEMS.Using the Integration Module Balances from Oracle Financials This section provides the cross mapping for the interface tables that are used when transferring Balance data between Oracle Financials and MAXIMO.SEGM ENT1) of the item (MTL_MATERIAL_TRANSACTIONS.N VENTORY_ITEM_ID of the ORGANIZATION_ID in Oracle Financial). Data is transferred from Oracle Financials’ MTL_MATERIAL_TRANSACTION to the MAXIMO MAX_ITM_INTERFACE table.ASSET_CATE GORY_ID of the item (MTL_MATERIAL_TRANSACTIONS. 353 .N VENTORY ITEM ID) is ‘YES’.CAPITALIZE_FLAG of MTL_SYSTEM_ITEMS. DESCRIPTION ROTATING STOCKTYPE LOTTYPE CAPITALIZED ALN YORN ALN UPPER YORN 240 1 30 5 1 ‘Y’ if FA_CATEGORIES.

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

UN_NUMBER_ ID of the item (MTL_MATERIAL_TRANSACTIONS.UN_NUMBER correspondent to MTL_SYSTEM_ITEMS.Using the Integration Module Oracle Financials MAXIMO IN13 ALN 25 VENTORY_ITEM_ID) Mapped to PO_UN_NUMBERS.INTERNAL_OR DER_FLAG of the item (MTL MATERIAL TRANSACTIONS.N IN22 ALN 1 355 .PURCHASING _ITEM_FLAG of the item (MTL_MATERIAL_TRANSACTIONS.O RGANIZATION_ID’s1 ORGANIZATION_ID IN14 ALN 3 IN15 IN16 IN17 IN18 IN19 IN20 IN21 YORN ALN AMOUNT ALN ALN ALN ALN 1 10 10 10 10 10 10 Mapped to MTL_SYSTEM_ITEMS.N VENTORY_ITEM_ID) Mapped to MTL_PARAMETERS.ORGANIZATION _CODE correspondent to the MASTER_ORGANIZATION_ID of MTL_MATERIAL_TRANSACTIONS.N VENTORY_ITEM_ID) Mapped to MTL_SYSTEM_ITEMS.

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

otherwise.MIN_MINMAX_ QUANTITY of the item (MTL_MATERIAL_TRANSACTIONS.LO CATOR_ID is not null.UNIT_OF_ISS UE of the item (MTL MATERIAL TRANSACTIONS. mapped to SUBINVENTORY_CODE concatenated by LOCATOR_ID with a delimiter provided by OFCTL control variable SUBLOCDEL Mapped to MTL_SYSTEM_ITEMS.N MINLEVEL DECIMAL 15 MAXLEVEL DECIMAL 15 CATEGORY UPPER 4 ORDERUNIT ALN 25 ISSUEUNIT ALN 25 357 . set to ‘NS’ Mapped to MTL_SYSTEM_ITEMS.MAX_MINMAX _QUANTITY of the item (MTL_MATERIAL_TRANSACTIONS.N VENTORY_ITEM_ID) Mapped to MTL_SYSTEM_ITEMS.Using the Integration Module Oracle Financials LOCATOR_ID MAXIMO BINNUM ALN 10 If MTL_MATERIAL_TRANSACTIONS.N VENTORY_ITEM_ID) is ‘Y’ or NULL.N VENTORY_ITEM_ID) ‘STK’ if MTL_SYSTEM_ITEMS.PRIMARY_UNI T_OF_MEASURE of the item (MTL_MATERIAL_TRANSACTIONS.STOCK_ENAB LED_FLAG of the item (MTL_MATERIAL_TRANSACTIONS.N VENTORY_ITEM_ID) Mapped to MTL_SYSTEM_ITEMS.

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

4 Mapped to MTL_SYSTEM_ITEMS.SOURCE_TYP E of the item (MTL_MATERIAL_TRANSACTIONS.LIST_PRICE_P ER_UNIT of the item (MTL_MATERIAL_TRANSACTIONS.ORGANIZATION _CODE correspondent to MTL SYSTEM ITEMS.N VENTORY_ITEM_ID) Mapped to MTL_PARAMETERS.N VENTORY_ITEM_ID) COSTCURRENCYCODE COSTCURRENCYCODE2 EXCHANGERATE2 LASTISSUEDATE ISSUEYTD ISSUE1YRAGO ISSUE2YRAGO ISSUE3YRAGO ABCTYPE CCF SSTOCK DELIVERYTIME IL1 UPPER UPPER DECIMAL DATETIME DECIMAL DECIMAL DECIMAL DECIMAL UPPER INTEGER DECIMAL INTEGER ALN 15 15 14 10 15 15 15 15 1 4 15 4 22 Mapped to MTL_SYSTEM_ITEMS.ITEM_COST for the item in the organization.SOURCE OR IL2 ALN 10 359 .Using the Integration Module Oracle Financials MAXIMO LASTCOST AMOUNT 10 CST_ITEM_COSTS.

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

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

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

‘API’) correspondent to MTL_MATERIAL_TRANSACTIONS.Using the Integration Module Oracle Financials MAXIMO CO9 CO10 CO11 CO12 CO13 INTEGER YORN ALN ALN ALN UPPER 4 1 10 25 25 18 NVL(FND_USER.LA ST_UPDATED_BY SYSDATE LAST_UPDATED_BY CHANGEBY CHANGEDATE INCLUSIVE1 INCLUSIVE2 INCLUSIVE3 INCLUSIVE4 INCLUSIVE5 CURRENCYCODE COMPANYLOC REGISTRATION1 REGISTRATION2 REGISTRATION3 REGISTRATION4 REGISTRATION5 APCONTROLACC APSUSPENSEACC DATETIME 10 YORN YORN YORN YORN YORN UPPER UPPER ALN ALN ALN ALN ALN ALN ALN 1 1 1 1 1 15 8 20 20 20 20 20 36 36 363 .USER_NAME.

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

NEXTVAL DATETIME 10 ALN 2000 365 .Using the Integration Module Oracle Financials MAXIMO USERDATA4 USERDATA5 USERDATA6 USERDATA7 USERDATA8 USERDATA9 USERDATA10 BATCHID BATCHLINEID UTRANSTYPE SOURCEID APISEQ APISITE IMPORTSTATUS IMPORTTIMESTAMP IMPORTMESSAGE ALN ALN ALN ALN ALN ALN ALN ALN INTEGER ALN ALN INTEGER ALN ALN 1 1 1 1 1 1 1 25 4 25 25 4 256 25 'XSB' 'I' Sequence APISEG.

REQUESTN UM. or 'WO:'|| MOUT_RSV_INTERFACE. Data is transferred from the MAXIMO MOUT_RSV_INTERFACE table to Oracle Financials’ MTL_RESERVATIONS_INTERFACE table.APISEQ apiseq. MTL_TXN_SOURCE_TYPES.nextval from Dual.TRANSA CTION_SOURCE_TYPE_ID whose TRANSACTION_SOURCE_TYPE_NA ME is ‘Inventory’ MOUT_RSV_INTERFACE MTL_RESERVATIONS_INTERFACE RESERVATION_INTERFACE_ Number ID RESERVATION_BATCH_ID Number DEMAND_SOURCE_TYPE_ID Number WONUM DEMAND_SOURCE_NAME Varchar2 40 REQUESTNUM DEMAND_SOURCE_LINE_ID Number SUPPLY_SOURCE_TYPE_ID Number 366 .WONUM MOUT_RSV_INTERFACE. MAXIMO Column Name Oracle Financials Column Name Type Length COMMENTS IntRec.TRANSA CTION_SOURCE_TYPE_ID whose TRANSACTION_SOURCE_TYPE_NA ME is ‘Inventory’ ‘MISC’ || MOUT_RSV_INTERFACE.REQUESTN UM MTL_TXN_SOURCE_TYPES.Chapter 3 Reservations from MAXIMO This section provides the cross mapping for the interface tables that are used when transferring Reservation data between MAXIMO and Oracle Financials applications.

DEMAND_SOURCE_NAME Mapped to BINNUM form the ITEM/LOCATION.ORGANIZATION _ID whose ORGANIZATION_CODE is MOUT_RSV_INTERFACE. Mapped to BINNUM form the ITEM/LOCATION. 3-del. 1 (1-Active 2 -Inactive 3-Error) 2 (1-yes 2 –no) 1 (1-ins. 2-upd. 4-xfr) 3 (3-background) 1 (1-yes.LOCATION WPOPERATION ACTUALQTY RESERVEDQTY RESERVATION_QUANTITY Number PRIMARY_RESERVATION_Q Number UANTITY MOUT_RSV_INTERFACE.Using the Integration Module MAXIMO Oracle Financials SUPPLY_SOURCE_NAME SUBINVENTORY_CODE LOCATOR_ID ROW_STATUS_CODE LOCK_FLAG RESERVATION_ACTION_CO DE TRANSACTION_MODE VALIDATION_FLAG PARTIAL_QUANTITIES_ALLO WED LAST_UPDATE_DATE Varchar2 Varchar2 Number Number Number Number Number Number Number MTL_RESERVATIONS_INTERFACE . 2-no) Date SYSDATE ITEMNUM LOCATION INVENTORY_ITEM_ID ORGANIZATION_ID Number Number MTL_PARAMETERS. 2-no) 1 (1-yes. RESERVEDQTY 367 .

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

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

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

Using the Integration Module MAXIMO WOPRIORITY WOPM6 WOPMM7 TARGCOMPDATE TARGSTARTDATE WOEQ1 WOEQ2 WOEQ3 WOEQ4 WOEQ5 WOEQ6 WOEQ7 WOEQ8 WOEQ9 WOEQ10 WOEQ11 WOEQ12 WO1 WO2 WO3 WO4 WO5 WO6 WO7 WO8 Oracle Financials 371 .

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

Using the Integration Module MAXIMO WOJP4 WOJP5 WOL1 WOL2 WOL3 WOL4 RESPONDBY EQLOCPRIORITY CALCPRIORITY CHARGESTORE FAILURECODE WOLO1 WOLO2 WOLO3 WOLO4 WOLO5 WOLO6 WOLO7 WOLO8 WOLO9 WOLO10 DISABLED CURRENCYCODE ROWSTAMP Oracle Financials 373 .

Chapter 3 MAXIMO USERDATA1 USERDATA2 USERDATA3 USERDATA4 USERDATA5 USERDATA6 USERDATA7 USERDATA8 USERDATA9 USERDATA10 BATCHID BATCHLINEID UTRANSTYPE SOURCEID APISEQ APISITE APISYNC IMPORTSTATUS IMPORTTIMESTAMP IMPORTMESSAGE Oracle Financials 374 .

FIRST NAME||MIDDLE NAME||LAST po_change_date UPPER(po_vnd_no)||''||UPPER(po_vndsite_no) po_vndctc_no 375 .Column PO_HEADERS.ATTRIBUTE12 PO_HEADERS.Using the Integration Module Purchase Orders from Oracle Financials This section provides the cross mapping for the interface tables that are used when transferring purchase order data between MAXIMO and Oracle Financials applications.SEGMENT1 (PO NUM) (CONCATENATED WITH RELEASE NUMBER.SEGMENT1||||PO_VENDOR_SITES. Note that the purchase order data is transferred to MAXIMO for completeness of the purchase requisition-purchase order-receipt-invoice cycle in MAXIMO.FIRM_DATE API variable UPPER(po_no) rd_at15 rd_at12 NVL(po_comments. Data is transferred from Oracle Financials purchasing tables to the MAXIMO MAX_PO_INTERFACE table.LAST_UPDATE_DATE PO_VENDORS. FOR RELEASE POs) PO_REQ_DISTRIBUTIONS. No modification of the purchase order is supported. 'Purchase Order from Oracle FInancials') po_buyer po_order_date PO_HEADERS.FULL_NAME PO_HEADERS.ATTRIBUTE15 PO_REQ_DISTRIBUTIONS.VENDOR_SITE_CODE PO VENDOR CONTACTS.TYPE_LOOKUP_CODE po_type PO_HEADERS. MAXIMO MAX_PO_INTERFACE PONUM PRNUM PRLINENUM PODESCRIPTION PURCHASEAGENT ORDERDATE REQUIREDDATE FOLLOWUPDATE POTYPE ORIGINALPONUM STATUS STATUSDATE VENDOR CONTACT Oracle Financials Table.COMMENTS PER_PEOPLE_F.

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

UNIT_MEAS_LOOKUP_CODE PO_LINES.Using the Integration Module MAXIMO MAX_PO_INTERFACE TOTALTAX1 TOTALTAX2 TOTALTAX3 INCLUSIVE1 INCLUSIVE2 INCLUSIVE3 INTERNAL TOTALTAX4 TOTALTAX5 INCLUSIVE4 INCLUSIVE5 STARTDATE ENDDATE PAYONRECEIPT WFID WFACTIVE BAYERCOMPANY ITEMNUM STORELOC MODELNUM CATALOGCODE ORDERQTY ORDERUNIT UNITCOST CONVERSION RECEIVEDQTY RECEIVEDUNITCOST RECEIVEDTOTALCOST Oracle Financials Table.ATTRIBUTE14.UPPER(pl_itm_no)) rd_at13 pl_vnd_itm_no pd_ordqty pl_uom pl_unit_price 377 .MTL_SYSTEM_ITEMS.Column API variable PO_REQ_DISTRIBUTIONS.VENDOR_PRODUCT_NUM PO_DISTRIBUTIONS. SEGMENT1 PO_REQ_DISTRIBUTIONS.QUANTITY_ORDERED PO_LINES.UNIT_PRICE NVL(rd_at14.ATTRIBUTE13 PO_LINES.

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

Column API variable ps_tax_name ps_tax_amt GLCREDITACCT LINECOST TAX1CODE PO_LINE_LOCATIONS.TAX_NAME TAX1 PO_LINE_LOCATIONS.ESTIMATED_TAX_AMOUNT TAX2CODE TAX2 TAX3CODE TAX3 SCHARGECODE RECEIPTREQD MANUFACTURER SERVICE TAX4CODE TAX4 TAX5CODE TAX5 SUPERVISOR CATEGORY REMARK LOCATION LOADEDCOST PRORATESERVICE AGREEMENTPONUM AGREEMENTPOTYPE RECEIPTSCOMPLETE INSPECTIONREQUIRED PRORATECOST POLINEID COMPANYTYPE 379 .Using the Integration Module MAXIMO MAX_PO_INTERFACE Oracle Financials Table.

Column API variable 380 .Chapter 3 MAXIMO MAX_PO_INTERFACE NAME ADDRESS1 ADDRESS2 ADDRESS3 ADDRESS4 PHONE FAX CO1 CO2 CO3 CO4 CO5 CO6 CO7 CO8 CO9 CO10 CO11 CO12 CO13 COMPANYLOC REGISTRATION1 REGISTRATION2 REGISTRATION3 APCONTROLACC APSUSPENSEACC RBNIACC PAYVENDOR BANKACCOUNT Oracle Financials Table.

Using the Integration Module MAXIMO MAX_PO_INTERFACE REGISTRATION4 REGISTRATION5 POLONGDESC POLINELONGDESC USERDATA1 USERDATA2 USERDATA3 USERDATA4 USERDATA5 USERDATA6 USERDATA7 USERDATA8 USERDATA9 USERDATA10 UTRANSTYPE APISYNC Oracle Financials Table.'LINE' rd_at11 381 .ATTRIBUTE11 'HEADER'.Column API variable PO_REQ_DISTRIBUTIONS.

SHIPMENT_UNIT_PRICE.PO_UNIT_PRICE RCV_SHIPMENT_LINES. UPPER(rcv_itm_no)) rcv_req_at13 rcv_change_date rcv_enter_date rcv_quantity rcv_uom rcv_po_unitcost NVL(shp_unit_cost. MAXIMO Oracle Financials API variable NVL(rcv_req_at14.UOM_CONVERSION_RATE NVL(shp_uom_rate. rcv_po_unitcost) UPPER(rcv_po_no) rcv_rma_ref MAX_RCV_INTERFACE Table.ATTRIBUTE13 RCV_TRANSACTIONS.SEGMENT1 RCV_TRANSACTIONS.ATTRIBUTE14. MTL_SYSTEM_ITEMS.LAST_UPDATE_DATE RCV_TRANSACTIONS.SEGMENT1 PO_REQ_DISTRIBUTIONS.RMA_REFERENCE RCV_SHIPMENT_LINES. Data is transferred from several Oracle Financials purchasing tables to the MAXIMO MAX_RCV_INTERFACE table.1) FND_USER.RCV_TRANSA CTIONS.USER_NAME rcv_change_by 382 .Column ITEMNUM TOSTORELOC TRANSDATE ACTUALDATE QUANTITY RECEIVEDUNIT ISSUETYPE UNITCOST ACTUALCOST PONUM INVOICENUM REJECTCODE REJECTQTY REJECTCOST CONVERSION WONUM EQNUM ENTERBY PO_REQ_DISTRIBUTIONS.Chapter 3 Receipts from Oracle Financials This section provides the cross mapping for the interface tables that are used when transferring receipt data between MAXIMO and Oracle Financials applications.PO_UNIT_PRICE PO_HEADERS.TRANSACTION_DATE RCV_TRANSACTIONS.QUANTITY RCV_TRANSACTIONS.UNIT_OF_MEASURE RCV_TRANSACTIONS.

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

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

Using the Integration Module MAXIMO Oracle Financials API variable MAX_RCV_INTERFACE Table.ATTRIBUTE11 rcv_req_at11 385 .Column TAX3 TAX4CODE TAX4 TAX5CODE TAX5 PRORATED PRORATEDCOST STATUS STATUSDATE STATUSCHANGEBY VENDORINVOICENUM CURBAL CLAIMNUM APPROVED APPROVEDATE APPROVEBY USERDATA1 USERDATA2 USERDATA3 USERDATA4 USERDATA5 USERDATA6 USERDATA7 USERDATA8 USERDATA9 USERDATA10 UTRANSTYPE APISYNC PO_REQ_DISTRIBUTIONS.

ZIP ||PO_VENDOR_SITES.ADDRESS_LINE2 PO_VENDOR_SITES. (Note that the MAXIMO interface table is also used to transfer data from the MAXIMO Companies table.STATE ||PO_VENDOR_SITES.COUNTRY PO_VENDOR_CONTACTS.Chapter 3 Vendors from Oracle Financials This section provides the cross mapping for the interface tables that are used when transferring vendor data between MAXIMO and Oracle Financials applications.PROVINCE ||PO_VENDOR_SITES.LAST_NAME PO_VENDOR_CONTACTS.TITLE API variable UPPER(vnd_segment1) ||'-'||UPPER(vnd_site) vnd_type vnd_name vnd_addr1 vnd_addr2 vnd_addr3 vnd_city ||' '||vnd_state ||' '||vnd_province ||' '||vnd_zip ||' '||vnd_country vnd_ctc_fname| |' '||vnd_ctc_mname ||' '||vnd_ctc_lname vnd_ctc_title CONTACT POSITION PHONE FAX 386 .Column PO_VENDORS.ADDRESS_LINE3 PO_VENDOR_SITES. Data is transferred from several Oracle Financials vendor tables to the MAXIMO MAX_COM_INTERFACE table.MIDDLE_NAME ||PO_VENDOR_CONTACTS.VENDOR_TYPE_LOOKUP_CODE PO_VENDORS.FIRST_NAME ||PO_VENDOR_CONTACTS.VENDOR_NAME PO_VENDOR_SITES.) MAXIMO MAX_COM_INTERFACE COMPANY TYPE NAME ADDRESS1 ADDRESS2 ADDRESS3 ADDRESS4 Oracle Financials Table.SEGMENT1 ||'-'||PO_VENDOR_SITES. The SOURCEID indicates the direction of data and must be present in order to aviod recursive updates or endless loops.ADDRESS_LINE1 PO_VENDOR_SITES.CITY ||PO_VENDOR_SITES.VENDOR_SITE_CODE PO_VENDORS.

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

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

Using the Integration Module MAXIMO MAX_COM_INTERFACE ECOMMERCEENABLED VOICEPHONE FAXPHONE EMAIL HOMEPHONE PAGERPHONE CNT1 CNT2 CNT3 CNT4 CNT5 PROCUREMENTCARDNUM PROCARDEXPIREDATE USERDATA1 USERDATA2 USERDATA3 USERDATA4 USERDATA5 USERDATA6 USERDATA7 USERDATA8 USERDATA9 USERDATA10 UTRANSTYPE Oracle Financials Table.Column API variable 389 .

TRANSDATE) OFCTL:GLCURNCYTYPE EXCHANGERATE 390 .'USD') TRANSDATE APISEQ 'A' OFCTL:JE??? 'MAXIMO1' NVL(ENTERDATE.TRANSDATE) NVL(CURRENCYCODE. Oracle Financials GL_INTERFACE STATUS SET_OF_BOOKS_ID ACCOUNTING_DATE CURRENCY_CODE DATE_CREATED CREATED_BY ACTUAL_FLAG USER_JE_CATEGORY_NAME USER_JE_SOURCE_NAME CURRENCY_CONVERSION_DATE ENCUMBRANCE_TYPE_ID BUDGET_VERSION_ID USER_CURRENCY_CONVERSION_TYPE CURRENCY_CONVERSION_RATE SEGMENT1 SEGMENT2 SEGMENT3 SEGMENT4 SEGMENT5 SEGMENT6 MAXIMO MOUT_GL_INTERFACE 'NEW' OFCTL:GLSOBID NVL(ENTERDATE. Data is transferred from the MAXIMO MOUT_GL_INTERFACE table to Oracle Financials’ GL_INTERFACE table.Chapter 3 Journal Transactions from MAXIMO This section provides the cross mapping for the interface tables that are used when transferring journal entry data between MAXIMO and Oracle Financials applications.

Using the Integration Module Oracle Financials 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 ENTERED_CR MAXIMO MOUT_GL_INTERFACE LINECOST for GLDEBITACCT if LINECOST is +ve LINECOST for GLCREDITACCT if LINECOST is -ve LINECOST for GLCREDITACCT if LINECOST is +ve LINECOST for GLDEBITACCT if LINECOST is -ve 391 .

Chapter 3 Oracle Financials GL_INTERFACE ACCOUNTED_DR ACCOUNTED_CR TRANSACTION_DATE REFERENCE1 REFERENCE2 REFERENCE3 REFERENCE4 REFERENCE5 REFERENCE6 REFERENCE7 REFERENCE8 REFERENCE9 REFERENCE10 REFERENCE11 REFERENCE12 REFERENCE13 REFERENCE14 REFERENCE15 REFERENCE16 REFERENCE17 REFERENCE18 REFERENCE19 REFERENCE20 REFERENCE21 REFERENCE22 REFERENCE23 MAXIMO MOUT_GL_INTERFACE CURRENCYLINECOST for GLDEBITACCT if LINECOST is +ve CURRENCYLINECOST for GLCREDITACCT if LINECOST is -ve CURRENCYLINECOST for GLCREDITACCT if LINECOST is +ve CURRENCYLINECOST for GLDEBITACCT if LINECOST is -ve BATCHID APISEQ DESCRIPTION WONUM WPOPERATION EQNUM 392 .

.i.Using the Integration Module Oracle Financials GL_INTERFACE REFERENCE24 REFERENCE25 REFERENCE26 REFERENCE27 REFERENCE28 REFERENCE29 REFERENCE30 JE_BATCH_ID PERIOD_NAME JE_HEADER_ID JE_LINE_NUM CHART_OF_ACCOUNTS_ID FUNCTIONAL_CURRENCY_CODE CODE_COMBINATION_ID 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 MAXIMO MOUT_GL_INTERFACE LOCATION PONUM JE1 JE2 JE3 JE4 JE5 OFCTL:GLCOAID OFCTL:GLCURNCY GLDEBITACCT/GLCREDITACCT . one row for Debit and one row for Credit 393 .e.

Chapter 3 Oracle Financials 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 MAXIMO MOUT_GL_INTERFACE 394 .

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

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

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

Chapter 3

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

MAXIMO

398

Using the Integration Module

Oracle Financials
SOURCE_SUBINVENTORY EXPENSE_ACCOUNT ENCUMBRANCE_ACCOUNT RESTRICT_SUBINVENTORIES_CODE UNIT_WEIGHT WEIGHT_UOM_CODE VOLUME_UOM_CODE UNIT_VOLUME RESTRICT_LOCATORS_CODE LOCATION_CONTROL_CODE SHRINKAGE_RATE ACCEPTABLE_EARLY_DAYS PLANNING_TIME_FENCE_CODE DEMAND_TIME_FENCE_CODE LEAD_TIME_LOT_SIZE STD_LOT_SIZE CUM_MANUFACTURING_LEAD_TIME OVERRUN_PERCENTAGE MRP_CALCULATE_ATP_FLAG ACCEPTABLE_RATE_INCREASE ACCEPTABLE_RATE_DECREASE CUMULATIVE_TOTAL_LEAD_TIME PLANNING_TIME_FENCE_DAYS DEMAND_TIME_FENCE_DAYS END_ASSEMBLY_PEGGING_FLAG REPETITIVE_PLANNING_FLAG PLANNING_EXCEPTION_SET BOM_ITEM_TYPE PICK_COMPONENTS_FLAG REPLENISH_TO_ORDER_FLAG

MAXIMO

'2'

'2' '1'

399

Chapter 3

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

MAXIMO

400

Using the Integration Module

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

MAXIMO

401

Chapter 3

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

MAXIMO

TAX1CODE

STOCKTYPE

402

Using the Integration Module

Oracle Financials
PROCESS_FLAG ORGANIZATION_CODE ITEM_NUMBER COPY_ITEM_NUMBER TEMPLATE_ID TEMPLATE_NAME COPY_ORGANIZATION_ID COPY_ORGANIZATION_CODE ATO_FORECAST_CONTROL TRANSACTION_TYPE MATERIAL_COST MATERIAL_SUB_ELEM MATERIAL_OH_RATE MATERIAL_OH_SUB_ELEM MATERIAL_SUB_ELEM_ID MATERIAL_OH_SUB_ELEM_ID

MAXIMO
'1' If OFCTL.GENSTORE or LOCATION is null then OFCTL.ITMORG Else LOCATION

'CREATE'

403

Chapter 3

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

MOUT_PO_INTERFACE PO_HEADERS_INTERFACE_CAI_ALL
Column Name REQUESTEDBY POTYPE Column Name po_header_id agent_id type_lookup_code Type Length COMMENTS Null Employee ID for the PO.REQUESTEDBY if not null and GENUSR = N, else Employee ID for ‘MAXIMO1’ If PO.POTYPE = STD, then value is ‘STANDARD’ If PO.POTYPE = BLK or REL, then value is ‘BLANKET’ SYSDATE User ID for the PO.ENTERBY if not null and GENUSR = N, else User ID for ‘MAXIMO1’ If PO.POTYPE is REL, then the PO.ORIGINALPONUM is used to populate this column ‘N’ NUMBER 15 NUMBER ALN 25

ENTERBY PONUM

last_update_date last_updated_by segment1 summary_flag

DATE NUMBER 15 ALN ALN 20 1

404

Using the Integration Module

MAXIMO

Oracle Financials
enabled_flag segment2 segment3 segment4 segment5 start_date_active end_date_active last_update_login creation_date created_by vendor_id vendor_site_id vendor_contact_id ship_to_location_id bill_to_location_id terms_id ship_via_lookup_code fob_lookup_code freight_terms_lookup_code status_lookup_code currency_code rate_type ALN ALN ALN ALN ALN DATE DATE NUMBER DATE NUMBER NUMBER 1 20 20 20 20 ‘Y’ Null Null Null Null Null Null Null Last_updated_by Vendor Id associated to PO.VENDOR (pos 1 to delimiter ‘-‘) Vendor Site Id associated to PO.VENDOR (pos after delimiter ‘-‘ to the end) Null Ship to Id associated to PO.SHIPTO Bill to Id associated to PO.BillTO Terms Id associated to PO.PAYMENTTERMS, If null, uses value from OFCTL/PAYTERMSID

15 15 15

ORDERDATE VENDOR VENDOR

NUMBER 15 NUMBER NUMBER NUMBER NUMBER ALN ALN ALN ALN ALN ALN 15 15 15 15 25 25 25 25 15 25

SHIPTO BILLTO PAYMENTTERMS SHIPVIA FOB FREIGHTTERMS CURRENCYCODE

‘APPROVED’ Value from OFCTL/GLCURNCYTYPE

405

Chapter 3

MAXIMO
EXCHANGEDATE EXCHANGERATE

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

TOTALCOST

STATUSDATE

PODESCRIPTION

406

Using the Integration Module MAXIMO Oracle Financials rfq_close_date quote_type_lookup_code quotation_class_code quote_warning_delay_unit quote_warning_delay quote_vendor_quote_number acceptance_required_flag acceptance_due_date closed_date user_hold_flag approval_required_flag cancel_flag firm_status_lookup_code frozen_flag attribute_category attribute1 attribute2 attribute3 attribute4 attribute5 attribute6 attribute7 attribute8 attribute9 DATE ALN ALN ALN NUMBER ALN ALN DATE DATE ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN 25 25 25 15 25 1 Null Null Null Null Null Null ‘N’ Null Null Null Null ‘N’ ‘N’ ‘N’ ‘Default’ Segment1 Null Null Null Null Null Null Null Null 1 1 1 30 1 30 150 150 150 150 150 150 150 150 150 407 .

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

ENTERBY if not null and GENUSR = N.Using the Integration Module MAXIMO MOUT_PO_INTERFACE Column Name Oracle Financials PO_LINES_INTERFACE_CAI_ALL Column Name po_line_id last_update_date Type NUMBER DATE NUMBER NUMBER NUMBER 15 15 15 Length COMMENTS 15 Null Sysdate User ID for the PO. else User ID for ‘MAXIMO1’ Null If Service uses value in OFCTL/PRSERVLINETYPE For non-Services uses value in OFCTL/POLINETYPE Null Last_updated_by Item ID associated to ITEMNUM Null For service uses value from OFCTL/SERVCATID or retrieves id based on PLIN1 For non-service uses value from OFCTL/ITEMCATID or retrieves id based on PLIN1 240 ENTERBY last_updated_by po_header_id line_type_id POLINENUM ORDERDATE ITEMNUM line_num last_update_login creation_date created_by item_id item_revision category_id NUMBER NUMBER DATE NUMBER NUMBER ALN NUMBER 15 15 3 15 DESCRIPTION item_description ALN 409 .

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

Using the Integration Module MAXIMO Oracle Financials cancelled_by cancel_date cancel_reason firm_status_lookup_code vendor_product_num contract_num taxable_flag tax_name type_1099 capital_expense_flag negotiated_by_preparer_flag attribute_category attribute1 NUMBER DATE ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN 240 30 25 25 1 15 10 1 1 30 150 150 150 150 150 150 150 150 150 150 Null Null Null Null Null Null Null Null 15 Null Null Null Null Null Null ‘N’ Null Null ‘N’ ‘N’ Null Segment1 from Header record POLINENUM attribute2 attribute3 attribute4 attribute5 attribute6 attribute7 attribute8 attribute9 attribute10 411 .

Chapter 3 MAXIMO Oracle Financials attribute11 attribute12 attribute13 attribute14 attribute15 reference_num min_release_amount price_type_lookup_code closed_code price_break_lookup_code ussgl_transaction_code government_context request_id program_application_id program_id program_update_date closed_date closed_reason closed_by transaction_reason_code delete_after_process transaction_id transaction_type ALN ALN ALN ALN ALN ALN NUMBER ALN ALN ALN ALN ALN NUMBER NUMBER NUMBER DATE DATE ALN NUMBER ALN ALN NUMBER ALN 240 25 1 20 25 25 25 30 30 150 150 150 150 150 25 Null Null Null Null Null Null Null Null ‘OPEN’ Null Null Null Null Null Null Null Null Null Null Null ‘N’ Either ‘CREATE’ or ‘UPDATE’ based on po already sent to Oracle APISYNC 412 .

Using the Integration Module MAXIMO Oracle Financials status_code org_id ALN NUMBER 25 Null Operating unit – from either OFCTL/OPERUNITID or entered in extra column (PO1-PO10) on PO form 413 .

REQUESTEDBY if not null and GENUSR = N. else Employee ID for ‘MAXIMO1’ SYSDATE 0 25 1 Null ‘Y’ 0 Null 1 ‘N’ Length COMMENTS For a new release. uses APISEQ For updates.Chapter 3 NOTE: This table is populated only when the POTYPE = ‘REL’ (processing a MAXIMO Release PO). MAXIMO MOUT_PO_INTERFACE Column Name APISEQ Oracle Financials PO_RELEASES_INTERFACE_CAI_ALL Column Name Po_release_id last_update_date last_updated_by po_header_id Type NUMBER DATE NUMBER NUMBER NUMBER NUMBER Employee ID for the PO. else User ID for ‘MAXIMO1’ Retrieved from Oracle using ORIGINALPONUM ENTERBY 15 APISEQ REQUESTEDBY release_num agent_id release_date ORDERDATE create_date revision_num revised_date approved_flag STATUSDATE approved_date print_count printed_date cancel_flag DATE DATE NUMBER ALN ALN DATE NUMBER DATE ALN 414 . retrieves release from Oracle base table SYSDATE User ID for the PO.ENTERBY if not null and GENUSR = N.

Using the Integration Module MAXIMO MOUT_PO_INTERFACE Oracle Financials PO_RELEASES_INTERFACE_CAI_ALL cancelled_by cancel_date cancel_reason attribute1 attribute2 attribute3 attribute4 attribute5 attribute6 attribute7 attribute8 attribute9 attribute10 attribute11 attribute12 attribute13 attribute14 attribute15 attribute_category last_update_login creation_date created_by hold_by NUMBER DATE ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN NUMBER DATE NUMBER NUMBER 240 150 150 150 150 150 150 150 150 150 150 150 150 150 150 150 30 Null Null Null Segment1 from Header Line_Num from Line Null Null Null Null Null Null Null Null Null Null Null Null Concatenate PONUM||POLINENUM Null Null Null Null Null 415 .

Chapter 3 MAXIMO MOUT_PO_INTERFACE Oracle Financials PO_RELEASES_INTERFACE_CAI_ALL hold_date hold_reason hold_flag firm_status_lookup_code firm_date acceptance_due_date acceptance_required_flag authorization_status ussgl_transaction_code government_context request_id program_application_id program_id program_update_date closed_code frozen_flag release_type note_to_vendor delete_after_process DATE ALN ALN ALN DATE DATE ALN ALN ALN ALN NUMBER NUMBER NUMBER DATE ALN ALN ALN ALN ALN NUMBER ALN ALN 20 25 Either ‘CREATE’ or ‘UPDATE’ based on po already sent to Oracle Null 25 1 25 240 1 1 25 30 30 240 1 25 Null Null Null Null Null Null Null ‘APPROVED’ Null Null Null Null Null Null ‘OPEN’ Null ‘BLANKET’ Null Null APISYNC transaction_id transaction_type status_code 416 .

Using the Integration Module MAXIMO MOUT_PO_INTERFACE Oracle Financials PO_RELEASES_INTERFACE_CAI_ALL org_id NUMBER Operating unit – from either OFCTL/OPERUNITID or entered in extra column (PO1-PO10) on PO form 417 .

Chapter 3 MAXIMO MOUT_PO_INTERFACE Column Name ENTERBY Oracle Financials PO_SHIPMENTS_INTERFACE_CAI_ALL Column Name line_location_id last_updated_by last_update_date po_header_id po_line_id last_update_login Type NUMBER NUMBER DATE NUMBER NUMBER NUMBER DATE NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER ALN NUMBER NUMBER ALN DATE DATE 25 15 15 25 From the release record when created Ship to Id associated to PO. used REQUIREDDATE Null 0 0 0 0 15 Last_updated_by 15 15 15 Length COMMENTS 15 15 Null User ID for the PO.ENTERBY if not null and GENUSR = N. else User ID for ‘MAXIMO1’ SYSDATE Null Null Null ORDERDATE ORDERQTY ORDERQTY creation_date created_by quantity quantity_received quantity_accepted quantity_rejected quantity_billed quantity_cancelled ORDERUNIT SHIPTO REQDELIVERYDATE unit_meas_lookup_code po_release_id ship_to_location_id ship_via_lookup_code need_by_date promised_date 418 .SHIPTO Null If Null.

Using the Integration Module MAXIMO MOUT_PO_INTERFACE UNITCOST Oracle Financials PO_SHIPMENTS_INTERFACE_CAI_ALL last_accept_date price_override encumbered_date encumbered_flag unencumbered_quantity fob_lookup_code freight_terms_lookup_code taxable_flag DATE NUMBER DATE ALN NUMBER ALN ALN ALN ALN NUMBER NUMBER NUMBER DATE DATE NUMBER ALN NUMBER NUMBER ALN DATE ALN NUMBER DATE 1 15 ‘N’ Null Null 15 1 15 25 25 25 1 15 15 15 15 Null Null Null Null Null Null Null Null Null ‘Y’ 1 Null Null ‘N’ Null Null Null If TAX1CODE is not null then set to Y Else set to N TAX1CODE tax_name from_header_id from_line_id from_line_location_id start_date end_date lead_time lead_time_unit price_discount terms_id approved_flag STATUSDATE approved_date cancel_flag cancelled_by cancel_date 419 .

Chapter 3 MAXIMO MOUT_PO_INTERFACE Oracle Financials PO_SHIPMENTS_INTERFACE_CAI_ALL cancel_reason firm_status_lookup_code firm_date attribute_category attribute1 attribute2 ALN ALN DATE ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN 240 25 30 150 150 150 150 150 150 150 150 150 150 150 150 150 150 150 25 1 1 1 Null ‘N’ Null Null Segment1 from Header Line_Num from Line Null Null Null Null Null Null Null Null Null Null Null Null Null Null ‘N’ POLINENUM attribute3 attribute4 attribute5 attribute6 attribute7 attribute8 attribute9 attribute10 attribute11 attribute12 attribute13 attribute14 attribute15 unit_of_measure_class encumber_now inspection_required_flag RECEIPTREQD receipt_required_flag 420 .

if storeloc is null.Using the Integration Module MAXIMO MOUT_PO_INTERFACE Oracle Financials PO_SHIPMENTS_INTERFACE_CAI_ALL qty_rcv_tolerance qty_rcv_exception_code enforce_ship_to_location_co allow_substitute_receipts_f days_early_receipt_allowed days_late_receipt_allowed receipt_days_exception_code invoice_close_tolerance receive_close_tolerance NUMBER ALN ALN ALN NUMBER NUMBER ALN NUMBER NUMBER NUMBER NUMBER NUMBER ALN ALN NUMBER NUMBER NUMBER DATE ALN ALN NUMBER ALN ALN 30 30 1 240 25 25 Null Null ‘OPEN’ Null Null Null Null Null Null Null ‘N’ Null 25 25 25 1 Null Null Null Null Null Null Null Null Null Uses ID for Storeloc. uses org id associated to the shipto STORELOC POLINENUM ship_to_organization_id shipment_num source_shipment_id shipment_type closed_code request_id program_application_id program_id program_update_date ussgl_transaction_code government_context receiving_routing_id accrue_on_receipt_flag closed_reason 421 .

Chapter 3 MAXIMO MOUT_PO_INTERFACE Oracle Financials PO_SHIPMENTS_INTERFACE_CAI_ALL closed_date closed_by delete_after_process DATE NUMBER ALN NUMBER ALN ALN NUMBER 20 25 Either ‘CREATE’ or ‘UPDATE’ based on PO already sent to Oracle Null Operating unit – from either OFCTL/OPERUNITID or entered in extra column (PO1-PO10) on PO form 1 Null Null ‘N’ APISYNC transaction_id transaction_type status_code org_id 422 .

else User ID for ‘MAXIMO1’ Null Null Null Value from OFCTL/GLSOBID Uses ID associated to debit account Null ENTERBY last_updated_by po_header_id po_line_id line_location_id set_of_books_id GLDEBITACCT ORDERQTY ORDERDATE code_combination_id quantity_ordered last_update_login creation_date created_by po_release_id quantity_delivered quantity_billed quantity_cancelled req_header_reference_num req_line_reference_num req_distribution_id ORDERQTY SHIPTO Deliver_to_location_id 423 .Using the Integration Module MAXIMO MOUT_PO_INTERFACE Column Name Oracle Financials PO_DISTRIB_INTERFACE_CAI_ALL Column Name po_distribution_id last_update_date Type NUMBER DATE NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER DATE NUMBER NUMBER NUMBER NUMBER NUMBER ALN ALN NUMBER NUMBER 25 25 15 15 15 15 Last_updated_by From the Release record when created 0 0 Null Null Null Ship to Id associated to PO.SHIPTO Length COMMENTS 15 15 15 15 15 15 15 15 Null SYSDATE User ID for the PO.ENTERBY if not null and GENUSR = N.

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

Using the Integration Module MAXIMO Oracle Financials attribute6 attribute7 Attribute8 Attribute9 attribute10 attribute11 attribute12 attribute13 attribute14 attribute15 wip_entity_id wip_operation_seq_num wip_resource_seq_num wip_repetitive_schedule_id wip_line_id bom_resource_id budget_account_id ALN ALN ALN ALN ALN ALN ALN ALN ALN ALN NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER ALN ALN ALN ALN NUMBER 1 30 30 30 150 150 150 150 150 150 150 150 150 150 Null Null Null Null Null Null Null Null Null Null Null Null Null Null Null Null Null Uses ID associated to credit account Uses ID associated to debit account ‘N’ Null Null Null GLCREDITACCT GLDEBITACCT accrual_account_id variance_account_id prevent_encumberence_flag ussgl_transaction_code government_context destination_context POLINENUM distribution_num 425 .

if storeloc is null.Chapter 3 MAXIMO Oracle Financials source_distribution_id request_id program_application_id program_id program_update_date project_id task_id expenditure_type project_accounting_context expenditure_organization_id gl_closed_date accrue_on_receipt_flag expenditure_item_date NUMBER NUMBER NUMBER NUMBER DATE NUMBER NUMBER ALN ALN NUMBER DATE ALN DATE NUMBER ALN NUMBER ALN ALN NUMBER 20 25 Either ‘CREATE’ or ‘UPDATE’ based on po already sent to Oracle Null Operating unit – from either OFCTL/OPERUNITID or entered in extra column (PO1-PO10) on PO form 1 1 30 30 Null Null Null Null Null Null Null Null Null Null Null ‘N’ Null Uses ID for Storeloc. uses org id associated to the shipto ‘N’ STORELOC Destination_organization_id delete_after_process APISYNC Transaction_id Transaction_type status_code org_id 426 .

PO_LINES_Interface.interface_head er_id Null Null 'ORIGINAL' 'DEFAULT' clnt_info which is operating unit If PO. MAXIMO Oracle Financials MOUT_PO_INTERFACE PO_HEADERS_INTERFACE Column Name Column Name interface_header_id batch_id interface_source_code process_code action group_code org_id document_type_code Type NUMBER NUMBER VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 NUMBER VARCHAR2 25 25 25 25 25 Length COMMENTS Obtained from Oracle sequence PO_HEADERS_INTERFACE_S in Oracle Financial PO module PO_HEADERS_INTERFACE.POTYPE = STD. Data is transferred from the MAXIMO MOUT_PO_INTERFACE table to the Oracle Financials PO_HEADERS_Interface. then value is ‘STANDARD’ POTYPE 427 . NOTE: The Standard Purchasing Documents Open Interface is available for Oracle versions 11. PO_RELEASES_Interface_CAI_ALL and PO_DISTRIBUTIONS_Interface tables.3 and later.Using the Integration Module Purchase Orders from MAXIMO to the Oracle Standard Purchasing Documents Open Interface Tables This section provides the cross mapping for the interface tables that are used when transferring PO data between MAXIMO and Oracle Standard Purchasing Documents Open Interface tables.5.

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

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

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

else User ID for ‘MAXIMO’ Null Null Null Null Null Null Null Null Null Null Null Null 25 1 30 25 15 25 431 .Using the Integration Module MAXIMO ENTERBY Oracle Financials last_updated_by last_update_login request_id program_application_id program_id program_update_date reference_num load_sourcing_rules_flag vendor_num from_RFQ_num wf_group_id pcard_id pay_on_code NUMBER NUMBER NUMBER NUMBER NUMBER DATE VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 NUMBER NUMBER VARCHAR2 User ID for the PO.ENTERBY if not null and GENUSR = N.

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

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

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

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

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

line_num PO_Lines_Interface.ENTERBY if not null and GENUSR = N.creation_date User ID for the PO.Using the Integration Module MAXIMO Oracle Financials shipment_attribute2 shipment_attribute3 shipment_attribute4 shipment_attribute15 last_update_date VARCHAR2 150 VARCHAR2 150 VARCHAR2 150 VARCHAR2 150 DATE NUMBER NUMBER DATE NUMBER NUMBER NUMBER NUMBER DATE DATE VARCHAR2 30 VARCHAR2 150 VARCHAR2 150 VARCHAR2 150 PO_Lines_Interface.ENTERBY if not null and GENUSR = N. shipment_num Null Null SYSDATE User ID for the PO. else User ID for ‘MAXIMO’ Null Null Null Null Null Null Null Null Null ENTERBY last_updated_by last_update_login creation_date ENTERBY created_by request_id program_application_id program_id program_update_date organization_id item_attribute_category item_attribute1 item_attribute2 item_attribute15 437 . else User ID for ‘MAXIMO’ Null PO_Headers_Interface.

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

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

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

'PROJPO') is ‘Yes’ and if PO.wonum is not null then populate this field else it is Null. Null If ('OFCTL'. Null If ('OFCTL'.wonum is not null then populate this field else it is Null.'PROJPO') is ‘Yes’ and if PO. If ('OFCTL'.wonum is not null then populate this field else it is Null.Using the Integration Module MAXIMO Oracle Financials wip_line_id bom_resource_code bom_resource_id ussgl_transaction_code government_context project Project_id Task Task_id expenditure expenditure_type project_accounting_context expenditure_organization expenditure_organization_id project_releated_flag expenditure_item_date NUMBER VARCHAR2 NUMBER VARCHAR2 VARCHAR2 VARCHAR2 NUMBER VARCHAR2 NUMBER VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 NUMBER VARCHAR2 DATE 1 60 30 30 60 20 30 30 25 10 Null Null Null Null Null Null If ('OFCTL'.'PROJPO') is ‘Yes’ and if PO.wonum is not null then populate this field else it is Null.'PROJPO') is ‘Yes’ and if PO.wonum is not null then populate this field else it is Null. Null If ('OFCTL'. Null If ('OFCTL'.'PROJPO') is ‘Yes’ and if PO.'PROJPO') is ‘Yes’ and if PO.wonum is not null then populate this 441 .

document_num PO_Lines_interface.creation_date Last_updated_by ENTERBY last_updated_by last_update_login creation_date created_by 442 .Chapter 3 MAXIMO Oracle Financials field else it is Null. attribute_category attribute1 Attribute2 Attribute3 Attribute4 Attribute15 last_update_date VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 VARCHAR2 DATE NUMBER NUMBR DATE NUMBER 30 150 150 150 150 150 Null PO_Headers_interface. else User ID for ‘MAXIMO’ Null PO_Headers_interface.ENTERBY if not null and GENUSR = N.shipment_num PO_Distributions_interface.line_num PO_Lines_interface.distribution_nu m Null SYSDATE User ID for the PO.

Data is transferred from the MAXIMO MAX_RCV_INTERFACE table to Oracle Financials’ RCV_HEADERS_INTERFACE and RCV_TRANSACTIONS_INTERFACE tables.GROU 443 . MAX_RCV_INTERFACE RCV_HEADERS_INTERFACE RCV_TRANSACTIONS_INTERFACE Column Name Column Name HEADER_INTERFACE_ID GROUP_ID VENDOR_ID PROCESSING_STATUS_CODE RECEIPT_SOURCE_CODE TRANSACTION_TYPE LAST_UPDATE_DATE VALIDATION_FLAG HEADER_INTERFACE_ID GROUP_ID Table Type Names H Number H H H H H H H T T Number Number Varchar2 Varchar2 Varchar2 Date Varchar2 Number Number Length COMMENTS Obtained from Oracle sequence RCV_HEADERS_INTERFACE_S in Oracle Financial PO module Obtained from Oracle sequence RCV_INTERFACE_GROUPS_S in Oracle Financial PO module PO_VENDORS.VENDOR_ID of the vendor of the PO1 ‘PENDING’ ‘VENDOR’ ‘NEW’ SYSDATE ‘Y’ Same as RCV_HEADERS_INTERFACE. HEADER_INTERFACE_ID Same as RCV HEADERS INTERFACE.Using the Integration Module Receipt Transfer from MAXIMO to Oracle Financials This section provides the cross mapping for the interface tables that are used when transferring Receipt data between MAXIMO and Oracle Financials.

VENDO R_ID PO. SYSDATE) in Oracle Financial MTL_SYSTEM_ITEMS.Chapter 3 MAX_RCV_INTERFACE RCV_HEADERS_INTERFACE RCV_TRANSACTIONS_INTERFACE Column Name Column Name Table Type Names T T T T T T T T T T T T T T T T Number date Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Number Varchar2 Varchar2 Varchar2 Number Length COMMENTS P_ID Obtained from Oracle sequence RCV_TRANSACTIONS_INTERFACE_ S in Oracle Financial PO module SYSDATE ‘RECEIVE’ ‘PENDING’ ‘BATCH’ ‘PENDING’ ‘DELIVER’ ‘VENDOR’ ‘PO’ ‘Y’ ‘MAXIMO1 RECEIPT’ Same as RCV_HEADERS_INTERFACE.REQUREDDATE. DELIVER_TO_LOCATION_CODE NVL(PO.INVENTORY_I TEM_ID in Oracle Financial4 INTERFACE_TRANSACTION_ID LAST_UPDATE_DATE TRANSACTION_TYPE PROCESSING_STATUS_CODE PROCESSING_MODE_CODE TRANSACTION_STATUS_CODE AUTO_TRANSACT_CODE RECEIPT_SOURCE_CODE SOURCE_DOCUMENT_CODE VALIDATION_FLAG COMMENTS VENDOR_ID DELIVER_TO_LOCATION_CODE SHIP_TO_LOCATION_CODE EXPECTED_RECEIPT_DATE ITEMNUM ITEM_ID 444 .SHIPTO in MAXIMO1 Same as RCV_TRANSACTIONS_INTERFACE.

PO_HEADER_ID Column Name SHIP_TO_ORGANIZATION_CODE TRANSACTION_DATE CREATION_DATE CREATION_DATE QUANTITY UNIT_OF_MEASURE Table Type Length COMMENTS Names H Varchar2 T Date H T T T DATE DATE Number Varchar2 445 .LAST_ PO_HEADER_ID SHIPMENT_NUM H H Number Varchar2 PO_HEADERS.USER_ID for ENTERBY or ‘MAXIMO1’2 Same as RCV_HEADERS_INTERFACE.Using the Integration Module MAX_RCV_INTERFACE RCV_HEADERS_INTERFACE RCV_TRANSACTIONS_INTERFACE Column Name TOSTORELOC TRANSDATE ACTUALDATE QUANTITY RECEIVEDUNIT ISSUETYPE UNITCOST ACTUALCOST PONUM INVOICENUM REJECTCODE REJECTQTY REJECTCOST CONVERSION WONUM EQNUM ENTERBY EMPLOYEE_ID LAST_UPDATED_BY CREATED_BY H H H Number Number Number PER_ALL_PEOPLE_F.PERSON_ID for ENTERBY or ‘MAXIMO1’2 FND_USER.

LAST_ UPDATE_BY2 LAST_UPDATED_BY CREATED_BY LAST_UPDATE_LOGIN IT1 IT2 IT3 IT4 IT5 OUTSIDE WPOPERATION ISSUETO PACKINGSLIPNUM POLINENUM ISSUE REQUESTEDBY TOTALCURBAL OLDAVGCOST SHIPMENT_NUM H Varchar2 446 .Chapter 3 MAX_RCV_INTERFACE RCV_HEADERS_INTERFACE RCV_TRANSACTIONS_INTERFACE Column Name Column Name Table Type Names T T T Number Number Number Length COMMENTS UPDATE_BY2 Same as RCV_HEADERS_INTERFACE.LAST_ UPDATE_BY2 Same as RCV_HEADERS_INTERFACE.LAST_ UPDATE_BY2 Same as RCV_HEADERS_INTERFACE.

Using the Integration Module MAX_RCV_INTERFACE RCV_HEADERS_INTERFACE RCV_TRANSACTIONS_INTERFACE Column Name ITIN1 ITIN2 ITIN3 TOBIN LOTNUM GLCREDITACCT GLDEBITACCT LINECOST LINECOST2 FINANCIALPERIOD CURRENCYCODE CURRENCYCODE2 EXCHANGERATE EXCHANGERATE2 CURRENCYUNITCOST MANUFACTURER MODELNUM CURRENCYLINECOST LOCATION DESCRIPTION SUBINVENTORY LOCATOR_ID T T Varchar2 Varchar2 Column Name Table Type Names Length COMMENTS ITEM_DESCRIPTION T Varchar2 447 .

Chapter 3 MAX_RCV_INTERFACE RCV_HEADERS_INTERFACE RCV_TRANSACTIONS_INTERFACE Column Name REMARK FROMSTORELOC FROMBIN QTYHELD CLAIMNUM APPROVED APPROVEDATE APPROVEBY LONGDESC USERDATA1 USERDATA2 USERDATA3 USERDATA4 USERDATA5 USERDATA6 USERDATA7 USERDATA8 USERDATA9 USERDATA10 BATCHID BATCHLINEID UTRANSTYPE Column Name Table Type Names Length COMMENTS 448 .

Using the Integration Module MAX_RCV_INTERFACE RCV_HEADERS_INTERFACE RCV_TRANSACTIONS_INTERFACE Column Name SOURCEID APISEQ APISYNC IMPORTSTATUS IMPORTTIMESTAMP IMPORTMESSAGE Key to Tables H S RCV_HEADERS_INTERFACE RCV_TRANSACTIONS_INTERFACE Column Name Table Type Names Length COMMENTS 449 .

ISSUE = 'N' or Null Then 'INVENTORY' 450 . Oracle Financials PO_REQUISITIONS_INTERFACE TRANSACTION_ID PROCESS_FLAG REQUEST_ID PROGRAM_ID PROGRAM_APPLICATION_ID PROGRAM_UPDATE_DATE LAST_UPDATED_BY LAST_UPDATE_DATE LAST_UPDATE_LOGIN CREATION_DATE CREATED_BY INTERFACE_SOURCE_CODE INTERFACE_SOURCE_LINE_ID SOURCE_TYPE_CODE REQUISITION_HEADER_ID REQUISITION_LINE_ID REQ_DISTRIBUTION_ID REQUISITION_TYPE DESTINATION_TYPE_CODE MAXIMO MOUT_PR_INTERFACE ENTERBY ID SYSDATE ISSUEDATE MAXIMO1 ID 'MAXIMO1' APISEQ If PR.INTERNAL = 'N' or Null Then 'VENDOR' If PR. Data is transferred from the MAXIMO MOUT_PR_INTERFACE table to Oracle Financials’ PO_REQUISITIONS_INTERFACE table.Chapter 3 Purchase Requisition from MAXIMO This section provides the cross mapping for the interface tables that are used when transferring purchase requisition data between MAXIMO and Oracle Financials.INTERNAL = 'Y' Then 'INVENTORY' If PRLINE.

Using the Integration Module Oracle Financials PO_REQUISITIONS_INTERFACE ITEM_DESCRIPTION QUANTITY UNIT_PRICE AUTHORIZATION_STATUS BATCH_ID GROUP_CODE DELETE_ENABLED_FLAG UPDATE_ENABLED_FLAG APPROVER_ID APPROVER_NAME APPROVAL_PATH_ID NOTE_TO_APPROVER PREPARER_ID AUTOSOURCE_FLAG REQ_NUMBER_SEGMENT1 REQ_NUMBER_SEGMENT2 REQ_NUMBER_SEGMENT3 REQ_NUMBER_SEGMENT4 REQ_NUMBER_SEGMENT5 HEADER_DESCRIPTION HEADER_ATTRIBUTE_CATEGORY HEADER_ATTRIBUTE1 HEADER_ATTRIBUTE2 HEADER_ATTRIBUTE3 HEADER_ATTRIBUTE4 HEADER_ATTRIBUTE5 HEADER_ATTRIBUTE6 MAXIMO MOUT_PR_INTERFACE If PRLINE.ISSUE = 'Y' Then 'EXPENSE' PRLDESCRIPTION ORDERQTY UNITCOST 'APPROVED' PRNUM 'APPROVED MAXIMO1 REQUISITION' PRNUM optional DESCRIPTION PR1 PR2 PR3 PR4 PR5 451 .

Chapter 3 Oracle Financials PO_REQUISITIONS_INTERFACE HEADER_ATTRIBUTE7 HEADER_ATTRIBUTE8 HEADER_ATTRIBUTE9 HEADER_ATTRIBUTE10 HEADER_ATTRIBUTE11 HEADER_ATTRIBUTE12 HEADER_ATTRIBUTE13 HEADER_ATTRIBUTE14 URGENT_FLAG HEADER_ATTRIBUTE15 RFQ_REQUIRED_FLAG JUSTIFICATION NOTE_TO_BUYER NOTE_TO_RECEIVER ITEM_ID ITEM_SEGMENT1 ITEM_SEGMENT2 ITEM_SEGMENT3 ITEM_SEGMENT4 ITEM_SEGMENT5 ITEM_SEGMENT6 ITEM_SEGMENT7 ITEM_SEGMENT8 ITEM_SEGMENT9 ITEM_SEGMENT10 ITEM_SEGMENT11 ITEM_SEGMENT12 ITEM_SEGMENT13 MAXIMO MOUT_PR_INTERFACE PR6 PR7 PR8 PR9 ITEMNUM optional 452 .

Using the Integration Module Oracle Financials PO_REQUISITIONS_INTERFACE ITEM_SEGMENT14 ITEM_SEGMENT15 ITEM_SEGMENT16 ITEM_SEGMENT17 ITEM_SEGMENT18 ITEM_SEGMENT19 ITEM_SEGMENT20 ITEM_REVISION CHARGE_ACCOUNT_ID 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 MAXIMO MOUT_PR_INTERFACE GLDEBITACCT 453 .

Chapter 3 Oracle Financials PO_REQUISITIONS_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 CATEGORY_SEGMENT2 CATEGORY_SEGMENT3 CATEGORY_SEGMENT4 CATEGORY_SEGMENT5 CATEGORY_SEGMENT6 CATEGORY_SEGMENT7 CATEGORY_SEGMENT8 CATEGORY_SEGMENT9 CATEGORY_SEGMENT10 CATEGORY_SEGMENT11 CATEGORY_SEGMENT12 CATEGORY_SEGMENT13 CATEGORY_SEGMENT14 CATEGORY_SEGMENT15 CATEGORY_SEGMENT16 MAXIMO MOUT_PR_INTERFACE IN19 (Parsed) IN19 (Parsed) IN19 (Parsed) IN19 (Parsed) IN19 (Parsed) IN19 (Parsed) IN19 (Parsed) IN19 (Parsed) IN19 (Parsed) IN19 (Parsed) IN19 (Parsed) IN19 (Parsed) IN19 (Parsed) IN19 (Parsed) IN19 (Parsed) IN19 (Parsed) 454 .

Null for all others. PRNUM VENDOR if PR.PRSERVLINETYPE for service lines.Using the Integration Module Oracle Financials PO_REQUISITIONS_INTERFACE CATEGORY_SEGMENT17 CATEGORY_SEGMENT18 CATEGORY_SEGMENT19 CATEGORY_SEGMENT20 UNIT_OF_MEASURE UOM_CODE LINE_TYPE_ID LINE_TYPE UN_NUMBER_ID UN_NUMBER HAZARD_CLASS_ID HAZARD_CLASS MUST_USE_SUGG_VENDOR_FLAG REFERENCE_NUM 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 SOURCE_SUBINVENTORY DESTINATION_ORGANIZATION_ID DESTINATION_ORGANIZATION_CODE MAXIMO MOUT_PR_INTERFACE IN19 (Parsed) IN19 (Parsed) IN19 (Parsed) IN19 (Parsed) ORDERUNIT OFCTL.INTERNAL = 'Y' BILLTO 455 .

Chapter 3 Oracle Financials PO_REQUISITIONS_INTERFACE DESTINATION_SUBINVENTORY DELIVER_TO_LOCATION_ID DELIVER_TO_LOCATION_CODE DELIVER_TO_REQUESTOR_ID DELIVER_TO_REQUESTOR_NAME SUGGESTED_BUYER_ID SUGGESTED_BUYER_NAME SUGGESTED_VENDOR_NAME SUGGESTED_VENDOR_ID SUGGESTED_VENDOR_SITE SUGGESTED_VENDOR_SITE_ID SUGGESTED_VENDOR_CONTACT SUGGESTED_VENDOR_CONTACT_ID SUGGESTED_VENDOR_PHONE SUGGESTED_VENDOR_ITEM_NUM LINE_ATTRIBUTE_CATEGORY LINE_ATTRIBUTE1 LINE_ATTRIBUTE2 LINE_ATTRIBUTE3 LINE_ATTRIBUTE4 LINE_ATTRIBUTE5 LINE_ATTRIBUTE6 LINE_ATTRIBUTE7 LINE_ATTRIBUTE8 LINE_ATTRIBUTE9 LINE_ATTRIBUTE10 LINE_ATTRIBUTE11 LINE_ATTRIBUTE12 MAXIMO MOUT_PR_INTERFACE SHIPTO SHIPTOATTN NAME CO1 CONTACT PHONE MODELNUM RL1 RL2 RL3 RL4 RL5 RLIN1 RLIN2 RLIN3 RLIN4 RLIN5 456 .

nvl(requiredate.sysdate)) 457 .Using the Integration Module Oracle Financials PO_REQUISITIONS_INTERFACE LINE_ATTRIBUTE13 LINE_ATTRIBUTE14 LINE_ATTRIBUTE15 NEED_BY_DATE 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 MAXIMO MOUT_PR_INTERFACE nvl(REQDELIVERYDATE.

Chapter 3 Oracle Financials PO_REQUISITIONS_INTERFACE DISTRIBUTION_ATTRIBUTE3 DISTRIBUTION_ATTRIBUTE4 DISTRIBUTION_ATTRIBUTE5 DISTRIBUTION_ATTRIBUTE6 DISTRIBUTION_ATTRIBUTE7 DISTRIBUTION_ATTRIBUTE8 DISTRIBUTION_ATTRIBUTE9 DISTRIBUTION_ATTRIBUTE10 DISTRIBUTION_ATTRIBUTE11 DISTRIBUTION_ATTRIBUTE12 DISTRIBUTION_ATTRIBUTE13 DISTRIBUTION_ATTRIBUTE14 DISTRIBUTION_ATTRIBUTE15 PREPARER_NAME BOM_RESOURCE_ID ACCRUAL_ACCOUNT_ID VARIANCE_ACCOUNT_ID BUDGET_ACCOUNT_ID USSGL_TRANSACTION_CODE GOVERNMENT_CONTEXT CURRENCY_CODE CURRENCY_UNIT_PRICE RATE RATE_DATE RATE_TYPE PREVENT_ENCUMBRANCE_FLAG AUTOSOURCE_DOC_HEADER_ID AUTOSOURCE_DOC_LINE_NUM MAXIMO MOUT_PR_INTERFACE APISYNC PRLINENUM STORELOC ITEMNUM PRNUM 'MAXIMO1.' CURRENCYCODE API calculated value EXCHANGERATE EXCHANGEDATE OFCTL:GLCURNCYTYPE 458 .

Using the Integration Module Oracle Financials PO_REQUISITIONS_INTERFACE PROJECT_ACCOUNTING_CONTEXT EXPENDITURE_ORGANIZATION_ID PROJECT_ID TASK_ID EXPENDITURE_ITEM_DATE DOCUMENT_TYPE_CODE ORG_ID * MAXIMO MOUT_PR_INTERFACE From PR window or from ofctl/operunitid or null if single org *Oracle Version 10.6 and later only 459 .

GLSOBID 'MAXIMO1' 460 .Chapter 3 Invoices from MAXIMO This section provides the cross mapping for the interface tables that are used when transferring invoice data between MAXIMO and Oracle Financials applications. Oracle Financials AP_EXPENSE_REPORT_HEADERS REPORT_HEADER_ID EMPLOYEE_ID WEEK_END_DATE CREATION_DATE CREATED_BY LAST_UPDATE_DATE LAST_UPDATED_BY VOUCHNO TOTAL VENDOR_ID VENDOR_SITE_ID EXPENSE_CHECK_ADDRESS_FLAG REFERENCE_1 REFERENCE_2 INVOICE_NUM EXPENSE_REPORT_ID ACCTS_PAY_CODE_COMBINATION_ID SET_OF_BOOKS_ID SOURCE MAXIMO MOUT_AP_INTERFACE API calculated value CHANGEDATE SYSDATE MAXIMO1 ID TRANSDATE ENTERBY ID '0' TOTALCOST VENDOR (Parsed) VENDOR (Parsed) INVOICENUM APCONTROLACCT OFCTL. Data is transferred from the MAXIMO MOUT_AP_INTERFACE table to Oracle Financials’ AP_EXPENSE_REPORT_HEADER and AP_EXPENSE_REPORT_LINE tables.

GLCURNCY.Using the Integration Module Oracle Financials AP_EXPENSE_REPORT_HEADERS PURGEABLE_FLAG ACCOUNTING_DATE MAXIMUM_AMOUNT_TO_APPLY ADVANCE_INVOICE_TO_APPLY APPLY_ADVANCES_DEFAULT EMPLOYEE_CCID DESCRIPTION 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 DEFAULT_EXCHANGE_RATE_TYPE MAXIMO MOUT_AP_INTERFACE INVOICEDATE INVOICEDESC OFCTL.GLCURNCYTYPE 461 . CURRENCYCODE OFCTL.

INVOICENUM.Chapter 3 Oracle Financials AP_EXPENSE_REPORT_HEADERS DEFAULT_EXCHANGE_RATE DEFAULT_EXCHANGE_DATE LAST_UPDATE_LOGIN VOUCHER_NUM USSGL_TRANSACTION_CODE USSGL_TRX_CODE_CONTEXT DOC_CATEGORY_CODE MAXIMO MOUT_AP_INTERFACE EXCHANGERATE EXCHANGEDATE Oracle Financials AP_EXPENSE_REPORT_LINES REPORT_HEADER_ID LAST_UPDATE_DATE LAST_UPDATED_BY CODE_COMBINATION_ID ITEM_DESCRIPTION SET_OF_BOOKS_ID AMOUNT ATTRIBUTE_CATEGORY ATTRIBUTE1 ATTRIBUTE2 ATTRIBUTE3 ATTRIBUTE4 ATTRIBUTE5 ATTRIBUTE6 MAXIMO MOUT_AP_INTERFACE API calculated value CHANGEDATE ENTERBY ID APSUSPENSEACCT 'Approved MAXIMO1 Invoice: '||InvoiceRec.GLSOBID LINECOST 462 . OFCTL.

GLCURNCYTYPE EXCHANGERATE CHANGEDATE OFCTL.APLINETYPE SYSDATE MAXIMO1 ID 463 .Using the Integration Module Oracle Financials AP_EXPENSE_REPORT_LINES ATTRIBUTE7 ATTRIBUTE8 ATTRIBUTE9 ATTRIBUTE10 ATTRIBUTE11 ATTRIBUTE12 ATTRIBUTE13 ATTRIBUTE14 ATTRIBUTE15 CURRENCY_CODE EXCHANGE_RATE_TYPE EXCHANGE_RATE EXCHANGE_DATE VAT_CODE LINE_TYPE_LOOKUP_CODE LAST_UPDATE_LOGIN CREATION_DATE CREATED_BY 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 MAXIMO MOUT_AP_INTERFACE CURRENCYCODE OFCTL.

Chapter 3 Oracle Financials AP_EXPENSE_REPORT_LINES DISTRIBUTION_LINE_NUMBER REFERENCE_1 REFERENCE_2 MAXIMO MOUT_AP_INTERFACE 464 .

You use this script to recompile the API triggers and procedures and you must run it if any of your database changes affected the APIs. When you use the Database Configuration application in the MAXIMO Setup module. If so. Configuring the Database The interface tables contain columns that match the MAXIMO database table columns.CHAPTER 4 SYSTEM MAINTENANCE This chapter provides both system maintenance instructions and troubleshooting information. you might reconfigure the tables and invalidate the database triggers. To find out whether your database changes affected the APIs. If that file references any tables that you just reconfigured. see Installation of Packages. For complete instructions on running the script and testing the results. Procedures. you must run the script. The troubleshooting section lists error messages that you might see in the interface tables and provides information on how to correct the related errors. you might see a dialog box telling you to run the AFTCONFO.OUT.SQL script. and Triggers (including the section 465 . you should look at the output file SHOWINT. If the file does not reference any tables that you reconfigured. The system maintenance instructions include procedures and tasks that your system administrator or database administrator should routinely perform at your site to help keep your system running smoothly. you do not have to run the script.

the integration API calls the user exit procedure and passes the data to that exit procedure. Customizing the Integration APIS MRO Software provides user exit procedures with the integration APIs so that you can customize the APIs. If you need to modify MAXIMO data so that your financial application can use it. or it might get additional data and write it to an extra table. Before it writes the data to the interface table. 466 . When the user exit procedure is complete. For example. the API first copies data from the MAXIMO tables or from the financial application. the integration API inserts the data into the appropriate interface table.g. User exit procedures are templates for custom procedures that you can add that allow you to manipulate data being sent to an interface table. WARNING: Do not customize the standard integration APIs provided by MRO Software except by using the user exit procedures provided for that purpose. a user exit procedure might rearrange data in a new format required by the financial application. you can customize the user exit procedures we provide so that they contain your procedures. This manual is available in the APIDOCS directory. when you approve a purchase requisition).Chapter 4 Checking for Errors) in the Installation manual.. When you perform a task that activates an integration API (e. The user exit procedure then manipulates the data as specified by the user.

you first create a column in your extra table called APISEQ. Using UTRANSTYPE Values with User Exit Procedures You can use a UTRANSTYPE value in your user exit procedure to cancel entire data transactions or to cancel the transfer of some data in a transaction.PSP—PL/SQL packages . WARNING: You should modify only .SQL—Scripts that run as part of the installation. For more information about the UTRANSTYPE column. To add an extra table to a user exit procedure. Using Extra Tables in User Exits You can create an extra table in a user exit that is directly associated with the corresponding interface table. You must have the APISEQ column in your extra table to capture additional data from one of the standard integration APIs and to associate the extra table with the interface table.USP—Files containing user stored procedures.PKG and . To cancel the transfer of data. Using UTRANSTYPE values allows you to control the exchange of data in a transaction. see “MAXIMO Interface Tables” on page 125.USP files. You can use the extra table to maintain more data than the integration API sends to the interface table. including user exit procedures . assign the value ABORT to UTRANSTYPE in your custom procedure. you can identify each by its filename extension: .System Maintenance There are six file types in the integration module. 467 .SP—Files containing stored procedures . You can use this method to cancel the transfer of data to MAXIMO from Oracle Financials or from MAXIMO to Oracle Financials. This column is the same as the APISEQ column in the corresponding interface table.TRG—Files containing triggers .

MRO Software has designed the MAXIMO integration APIs to provide your batch processes with batch coding information. the batch numbers remain unique. In that case. the accounts payable and general ledger (journal transactions) APIs might share a batch numbering scheme. For more information on the MAXIMO extra table features. Using Batch Routines You can use custom batch routines to process outbound MAXIMO data. Every MAXIMO integration API has a corresponding batch name that you can enter in the tables. Use these tables to define your batch processes.Chapter 4 Any time the integration API calls the user exit procedure and writes MAXIMO data to the custom procedure. The first thing you must do before you can run batch processes is to define those processes for the integration APIs. You can either manually run a batch process or use a scheduler program to run the batch process for you. This table identifies global batch processes that many APIs may share. You can define most of the global parameters in the MAXBATCH table. when accounts payable transactions are posted from the accounts payable system to the general ledger. the installation script creates two batch-related tables called MAXBATCH and APIBATCH. You must also define the values or parameters that each process will use. During the integration module installation.SQL script to purge MAXIMO interface tables. Therefore when your custom procedure writes data to the extra table. it also writes the APISEQ value. If you would like your extra tables to be purged automatically when you use the CLEANUP. add _EXT_INT to the end of the table names. see “Purging the Interface Tables” on page 474. refer to the MAXIMO System Administrator’s Guide. 468 . For more information about purging tables. For example. it also must write the APISEQ value to that table.

System Maintenance MAXBATCH Table Columns Name BTCHNAME BTCHDESC BTCHNUM BTCHMIN BTCHMAX BTCHSTEP BTCHLINENUM BTCHLINEMIN BTCHLINEMAX BTCHLINESTEP BTCHNUMPREFIX BTCHNUMPOSTFIX Type UPPER ALN INT INT INT INT INT INT INT INT ALN ALN Null N Y N N N N N N N N Y Y Description Batch name (required) Batch description (optional) Current batch number (required) Batch number minimum (required) Batch number maximum (required) Batch number increment value (required) Current batch line number (required) Batch line number minimum (required) Batch line number maximum (required) Batch line number increment value (required) Batch number prefix (optional) Batch number suffix (optional) 469 .

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

APIBATCH Table Columns Name APINAME BTCHNAME XBTCHNUMPREFIX XBTCHNUMPOSTFIX Type UPPER UPPER ALN ALN Null N N Y Y Description API name (required) Batch name (required) Batch number prefix (optional) Batch number suffix (optional) Parameter APINAME BTCHNAME XBTCHNUMPREFIX XBTCHNUMPOSTFIX Description Common name of the API. Value to add to the front of the batch number.System Maintenance BTCHNUMPOSTFIX Value to add to the end of the batch number. Overrides the value from the batch record. Value to add to the end of the batch number. Overrides the value from the batch record. The APIBATCH table associates the integration APIs with a batch process from the MAXBATCH table above. 471 . Name of the batch routine.

it returns a Null value and continues the usual processing. store. Before it writes the data to the interface tables. Batch number prefixes and suffixes you enter here override those listed in the MAXBATCH table. 472 . 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.Chapter 4 The APIBATCH table must contain the integration API common name and the batch name. If it does not find the correct integration API name and batch name. GetBatch verifies that the APIBATCH table contains the same integration API name and batch name. The Batch Routine Process Any time there is a data transfer from MAXIMO to Oracle Financials. the integration API calls the batch routine GetBatch. If it does fine the correct integration API name and batch name. the integration API first copies data from the MAXIMO tables. Common API names: • • • • • • APOUT – Invoice/accounts payable interface JEOUT – Journal transaction (all sources) interface PROUT – Purchase requisition interface ITMOUT – All item (item. you can have multiple integration APIs that use the same batch routine. vendor. However. GetBatch has the integration API common name associated with it. it continues to the MAXBATCH table. You can only define the integration API common name once in APIBATCH.

you must define the parameters for each batch routine you want to use. You can use the same batch routine for many integration APIs. you must set parameters for the maximum allowable batch number and batch line number for your application. If you do not want the batch number or batch line number to automatically reset to the minimum numbers. you may want to create a MAXBATCH table interface that updates the batch number and batch line number to ensure the use of unique batch numbers and batch line numbers. Use SQL tools to define those parameters. whenever a batch routine exceeds the maximum batch number you specified in MAXBATCH. it adds the batch number to the BATCHID column and the batch line number to the BATCHLINEID column of the interface table. 473 .System Maintenance After the GetBatch continues to the MAXBATCH table. If you want to use batch routines to transfer data from MAXIMO. it executes the batch routine. When the batch routine is complete. you must track the number of batch routines that have been processed and reset the numbers before they automatically recycle. The same is true for the batch line number. In MAXBATCH. the batch number automatically recycles to the specified minimum batch number. If you use a complex batch routine that is controlled by a central system. When the integration API writes data to the interface table. Maintaining the Batch Files MRO Software provides with the integration module MAXBATCH and APIBATCH tables that do not contain predefined data. Then. 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.

SQLTalk. For more information about the interface tables. The following tables are the ones you should purge: • • • • • • • • • • • • • • • • • • MAX_AP_INTERFACE MAX_COAX_INTERFACE MAX_COA_INTERFACE MAX_COM_INTERFACE MAX_ICF_INTERFACE MAX_ISU_INTERFACE MAX_ITM_INTERFACE MAX_LPY_INTERFACE MAX_LS_INTERFACE MAX_POX_INTERFACE MAX_PO_INTERFACE MAX_PRX_INTERFACE MAX_PR_INTERFACE MAX_RCV_INTERFACE MAX_SRV_INTERFACE MAX_WOX_INTERFACE MOUT_AP_INTERFACE MOUT_GL_INTERFACE 474 .Chapter 4 Maintaining the Interface Tables This section provides information about how to purge and to maintain the interface tables. Purging the Interface Tables All data that has been inserted in the interface tables remains in the tables until you purge them. You should use SQL*Plus. All new data is appended to the existing data in the tables to provide an audit trail of activity. You should purge the interface tables periodically to prevent them from getting too large. see “MAXIMO Interface Tables” on page 125. or Quest to query the interface tables or to update their contents.

SQL. 475 .System Maintenance • • • • MOUT_PO_INTERFACE MOUT_PR_INTERFACE MOUT_RSV_INTERFACE MOUT_WO_INTERFACE You can purge all MAXIMO interface tables at one time by running the SQL*Plus script called CLEANUP. For a description of the MAXIMO interface log table. You may wish to create a batch routine that selectively removes data from the interface tables on a regular schedule. Use the error status columns to identify transactions that were not completed successfully. You should use SQL*Plus or Quest to run these reports. see “Using Extra Tables in User Exits” on page 467. This script purges the tables listed above and also purges extra tables that have names ending in _EXT_INT. see “MAXIMO Interface Log” on page 477. For information about naming extra tables. Running Reports You can periodically run reports on the MAXIMO interface log table to check for error statuses in the log.

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

System Maintenance For more information on coordinating column length and type. see Chapter 3. 477 . To see more information about an error in one of the interface tables. see “Reconfiguring MAXIMO Table Columns” on page 18. If your transactions occur in real-time rather than by batch mode. verify that all interface table columns are correctly mapped between the two applications—column type and length must be compatible. Checking Status Columns and Debugging Errors Using MAXIMO Interface Flow for more error information. continue to step 5. map them now.” 4. MAXIMO Interface Log The MAXIMO interface log table. If you have correctly mapped the interface table columns. For more information on mapping. records the status of all transactions that occur between MAXIMO and your external application. check the interface log table for the full text of the error and the error history. The interface log contains detailed information about the transactions. For more information about mapping columns. Verify that the user objects (triggers and procedures) are still valid. If you have not mapped the interface table columns. “Using the Integration Module. 5. You can also see the following two sections. called MAX_INTERFACE_LOG. see “Reconfiguring MAXIMO Table Columns” on page 18.

• IMPORTTIMESTAMP shows the date and time the transaction completed or failed. To produce an output file that contains information on your transactions. you must enable the MAXIMO interface flow so that it “captures” the transaction information. IMPORTMESSAGE shows a general message. • Debugging Errors Using MAXIMO Interface Flow If there is a database rollback. MAXIMO does not write relevant information to the interface log. If you need more information than is provided by MAX_INTERFACE_LOG and the status columns in the interface tables. you can produce a detailed set of API transaction information by using the MAXIMO interface flow. All interface tables contain the following three status columns: • IMPORTSTATUS shows the status of the transaction. Check IMPORTMESSAGE for error messages. Check IMPORTMESSAGE for error messages.Chapter 4 Checking Status Columns Each interface table has three status columns to contain information on the status of a transaction. If a transaction failed. The status columns indicate whether or not a transaction was successfully completed. you can refer to the status columns for the time of the failure and for a general error message about the failure. This means that you should repeat the error transaction with the 478 . ERROR—errors were detected during the transaction and the data transfer did not occur. DONE—the transaction was successful. WARNING—the data was transferred but there was a problem during the transfer.

Use SQL*Plus to issue this command: SQL>start C:\MAXIMO\INTERFAC\SETEXVAR (maximo1 –remove this whole line after determining if ‘maximo’ stays in the path above) 5. You should disable the interface flow after you produce the information you need. errors from MAXIMO to the APIs are not propagated. SHOWFLOW. Exit MAXIMO then restart MAXIMO.FLOWON 2. 1.System Maintenance interface flow turned on. Whenever the interface flow in enabled.SHOWFLOW (maximo1 –remove this whole line after determining if ‘maximo’ stays in the command above) 6. The script SHOWFLOW. Redo the error transaction.SQL in the INTERFAC directory produces an output file that contains the data from the MAX_INTERFACE_FLOW table. WARNING: Do not leave the MAXIMO interface flow enabled.OUT that the SHOWFLOW script wrote to the LOG directory. issue this command: SQL>start &MAXIMODIR. Enable the MAXIMO interface flow by connecting to SQL*Plus as the MAXIMO user and issuing this command: SQL>EXEC MAXAPISET. 479 . 3. View the output file. This output file contains the detailed information on the error transaction. 4. 7. Then.

FLOWOFF Error Messages This section describes some of the error messages that you might see when you use the APIs. Transferring Purchase Requisition Changes into MAXIMO For each error shown below. PO cannot be created for PR: PRNumber with status: PRStatus The PR does not have a status of APPR (approved). Connect as the MAXIMO user. Issue the following command: SQL>EXEC MAXAPISET. it must be APPR or PRINT to be Canceled or Closed. PR is CurrentPRStatus. The PR must be approved before a PO can be created. an invalid status change was given to MAX_PRX_INTERFACE: PR is CurrentPRStatus. 480 . PR is CurrentPRStatus. complete the following steps in SQL*Plus: 1. it must be APPR or PRINT to be unapproved. 2. Errors are grouped according to their associated integration APIs. it must be waiting approval to be approved. Transferring Purchase Orders into MAXIMO Invalid PrNum: PRNumber The PR number does not exist in MAXIMO.Chapter 4 To disable the MAXIMO interface flow.

The value was replaced with default 'OTHER'. The value in the Ship Via field does not exist in SHIPVIA value list. The PR does not have a status of APPR (approved). PO cannot be created for PR: PRNumber with status: PRStatus. 481 . Transferring Receipts into MAXIMO Invalid GLDEBITACCT: DebitAcct PrLine: PRLineNumber. The PR must be approved before a PO can be created. Warning 101 Found Shipvia: ShipVia Replaced with: 'OTHER'. it must be APPR or PRINT to be Canceled or Closed. it must be APPR or PRINT to be unapproved. An invalid GL account was given for the GLDEBITACCT field.System Maintenance Transferring Purchase Order Changes into MAXIMO For each error shown below. Enter a valid GL account. it must be waiting approval to be approved. PO is CurrentPOStatus. an invalid status change was given to MAX_POX_INTERFACE: PO is CurrentPOStatus. The PR number does not exist in MAXIMO. Invalid PrNum: PRNumber. PO is CurrentPOStatus.

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

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

Determine the value of APISEQ for the row in error. In the MAX_AP_INTERFACE table. (this ensures that you only update the one row in error) Commit. 484 . (if you are changing the vendor identifier insert the column updates here) Where APISEQ = value for the row in error. the IMPORTMESSAGE status column shows the vendor identifier of the disqualified vendor. The invoice row is not inserted into the MAXIMO tables. Action: There are two ways to resolve this error. the update to the table causes the API triggers to import the row into MAXIMO. After you run this script. You can use the Companies application in MAXIMO to qualify the vendor or you can change the identifier of the vendor listed in the MAX_AP_INTERFACE table to a vendor that is qualified in MAXIMO. the error is caught and the IMPORTSTATUS column of the MAX_AP_INTERFACE is updated with the value ERROR. After you take either of these steps. you will update the MAX_AP_INTERFACE table to send the invoice row to MAXIMO: Update MAX_AP_INTERFACE Set IMPORTSTATUS= NULL.Chapter 4 Error: Disqualified Vendor When an invoice row is sent to MAXIMO that contains a vendor that has been updated as DISABLED in the COMPANIES table. Verify the update was successful by checking the IMPORTSTATUS column of the interface table.

Invalid BillTo BillTo must have a valid organization in Oracle Financials. • ErrorNumber is the Oracle error number. • ErrorMessage is the Oracle error message.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. Enter a valid GL account. If GENUSR is Y. Specify a valid organization defined in Oracle Financials. You might see one of the following error messages when transferring data from MAXIMO to Oracle Financials. If GENUSR is set to N. 485 . Invalid Debit/Credit GL Code Combinations The GL account value failed Oracle Financials validation. the user ID being passed may be invalid or not authorized for the function being performed in Oracle Financials. Enter a valid user ID. set up the MAXIMO ID in Oracle Financials to have access to the function being performed. Invalid enter by user The user ID value failed Oracle Financials validation.

Chapter 4 Invalid vendor or Invalid vendor header The component in the MAXIMO vendor key that makes up the vendor ID failed Oracle Financials validation. Invalid vendor site The component in the MAXIMO vendor key that makes up the vendor site ID failed Oracle Financials validation. Enter a valid vendor. 486 . Enter a valid vendor.

Notes 487 .

MPD0741-max411orafn11i-02-ENG-09/2002 .

Sign up to vote on this title
UsefulNot useful