Readme document for the Oracle R12 Adapter fix pack 7.1.0.3 Date: December 15, 2010 (C) Copyright International Business Machines Corporation 2010. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. ======================================================================== Contents ======================================================================== 1. Introduction 2. Contents 3. Pre-installation instructions 4. Installation instructions 5. Post-installation instructions 6. Resolved issues 7. Notices ======================================================================== 1. Introduction ======================================================================== This readme document provides information about fix pack 3 for IBM(R) Maximo(R) Enterprise Adapter 7.1 for Oracle E-Business Suite 12.0. This readme document describes the contents of this fix pack, provides installation instructions, and a list of the fixed issues in this release and the previous releases. Prerequisites - Make sure that you have installed all products in the order listed: - IBM Maximo Asset Management 7.1 - IBM Maximo Base Services 7.1.1.8 fix pack - Oracle E-Business Suite R12.0 or R12.1 - IBM Maximo Enterprise Adapter 7.1 (for Oracle Applications R12) - Back up your database. If upgrading from version 6 to 7, apply this update before you upgrade your Maximo database and your adapter. ======================================================================== 2. Contents ======================================================================== The following items are included: oracle_erp_fixpack7103.zip -------------------------------------- This zip package fix pack 3 for Maximo Enterprise Adapter 7.1 for Oracle Applications R12. ======================================================================== 3. Pre-installation instructions ======================================================================== Before you install fix pack 3 for Maximo Enterprise Adapter 7.1 for Oracle Applications R12, you must complete the following steps: 1) Determine the current software version: a) Sign in to Maximo. b) From the Maximo navigation bar, click "Help". c) From the Help list, select "System Information". Maximo displays the current Maximo Enterprise Adapter for Oracle Applications R12 software version, in the following format: Oracle Adapter 7.1.0.3 Build 20101130-1632 DB Build V7100-20 If this value matches your adapter version, the software is current. Do not install Maximo Enterprise Adapter 7.1 for Oracle Applications R12 fix pack 3. 2) Process any transactions in the inbound and outbound queues. For more information, see "Processing transactions in the inbound and outbound queues." 3) Process any transactions in the Maximo and Oracle Applications interface tables. For more information, see "Processing transactions in the Maximo interface tables" and "Processing transactions in the Oracle Applications open interface tables." 4) Disable the Oracle Applications external system in Maximo: a) From the Maximo Integration module, select the "External Systems" application. b) Select the external system that you want to disable. c) On the System tab, clear the "Enabled" check box. 5) Stop the Maximo application servers and services. 6) Stop the Actuate servers and services. 7) Back up the entire folder. NOTE Make sure you back up the ORACLEAPIS folder, specially the files found in /ORACLEAPIS/apiuser. 8) Back up the Maximo database. ------------------------------------------------------------------------ Processing transactions in the inbound and outbound queues ------------------------------------------------------------------------ You can use the Message Reprossessing application to process the queues. Procedure: 1)Sign in to Maximo. Go To > Integration > Message Reprocessing. 2)Select each message with errors and click on the Details icon. Correct the message Save it or click on the Process button. Only messages classified with the status of HOLD can be corrected. If you click Save, you will need to change the status of the message to Retry by clicking the icon on the toolbar. 3)Click "Refresh" until the queue is empty. ------------------------------------------------------------------------ Processing transactions in the Maximo interface tables ------------------------------------------------------------------------ 1) Connect to the MAXORA schema in the Oracle Applications database. 2) To check for unprocessed transactions in the inbound queue table, complete the following steps: a) Enter the following SQL statement: select * from MXIN_INTER_TRANS; b) If the SQL statement does not return any records, no unprocessed transactions exist. If the SQL statement returns any records, wait for the Maximo server to process the transactions. 3) To check for unprocessed transactions in the outbound queue table, complete the following steps: a) Enter the following SQL statement: select distinct iface_name from MXOUT_INTER_TRANS; b) If the SQL statement returns records, use the following table to determine the interface table that corresponds to each interface (iface_name) returned by the SQL statement. Interface Interface table MXGLCOMP_IFACE MXGLCOMP_TOOA12 MXCOA_IFACE MXCOA_TOOA12 MXLABOR_IFACE MXLABOR_TOOA12 MXCRAFT_IFACE MXCRAFT_TOOA12 MXITEM_IFACE MXITEM_TOOA12 MXVENDOR_IFACE MXVENDOR_TOOA12 MXPR_IFACE MXPR_TOA12 MXPO_IFACE MXPO_TOOA12 MXPC_IFACE MXPC_TOOA12 MXGLTXN_IFACE MXGLTXN_TOOA12 MXINVBAL_IFACE MXINVBAL_TOOA12 MXPROJ_IFACE MXPROJ_TOOA12 MXINVENTORY_IFACE MXINVENTORY_TOOA12 MXPROJTXN_IFACE MXPROJTXN_TOOA12 MXINVISSUE_IFACE MXINVISSUE_TOOA12 MXINVOICE_IFACE MXINVOICE_TOOA12 MXRCVROTITM_IFACE MXRCVROTITM_TOOA12 MXINVOICE_IFACE MXINVOICE_TOOA12 MXRECEIPT_IFACE MXRECEIPT_TOOA12 MXINVRES_IFACE MXINVRES_TOOA12 c) For each interface table that corresponds to an interface name returned by the SQL statement in step 3a, enter the following SQL statement: select * from interfacetablename where oa_ifacestatus <> ’DONE’; This statement returns any unprocessed transactions. d) Correct the unprocessed transactions. 4) Back up the interface tables to retain them for historical purposes. Depending on the current fix pack level, the patch process might drop the interface tables. ------------------------------------------------------------------------ Processing transactions in the Oracle Applications open interface tables ------------------------------------------------------------------------ 1) In Oracle E-Business Suite, run the concurrent reports for each integration point that you use. 2) For PO and PC updates and cancellations within PO_UPDATE_IFACE PO_CANCEL_IFACE, run the corresponding concurrent reports to clear the unprocessed transactions. 3) Check the exception reports and correct any errors. 4) Rerun the concurrent reports until no errors exist. ======================================================================== 4. Installation instructions ======================================================================== Installing the fix pack 1) Download the oracle_erp_fixpack7103.zip file into a temporary directory on the administrative system. For example, C:\temp 2) Using Windows(R) Explorer, go to the directory where your solution InstallerGUI.bat file is located (for example, home dir\SMP\bin). 3)Double-click the solutionInstallerGUI.bat file in your drive folder. 4)From the Process Solution Installer Introduction window, click "Next". 5)From the Choose PSI Package panel, click "Choose", navigate to the oracle_erp_fixpack7103.zip file (for example, C:\temp\oracle_erp_fixpack7103.zip ) and select the file. 6) Click "Open", and then click "Next". Once a package has been selected and opened, the process solution installer performs a series of validation checks to verify that the package you selected is valid. The system is checked to ensure that the package has not already been deployed. 7) From the Package Validation Results panel, review and verify the information displayed, and click "Next". 8) Enter the Userid and password for Maximo Database, and click "Next". 9) If you are using Middleware, enter the credentials for which you are being prompted, and click "Next". The contents of this panel are constructed dynamically, and depend on the type of package that you are installing. Once you have entered the requested user IDs and passwords, he process solution installation wizard validates the credentials by connecting to the middleware servers using the supplied credentials. 10) After the credentials have been verified, a package options panel is displayed and details the deployment options that the package supports. Clear the Defer Maximo Application Redeployment and the Defer the Upgrade of the Maximo Database check boxes, and click "Next". The process solution installer performs a system check to ensure that all system requirements necessary for the package to be installed are present. 11) From the Pre-Install Summary panel, review and verify the information displayed, and click "Next". The process solution installer begins the installation process. You can view the progress on the screen. When the installation is complete, the Package Successfully Deployed panel opens. If the installation fails, a message displays the step that failed. Do not proceed to the next step until you have resolved the error and the package has been installed successfully. 12) From the Package Successfully Deployed panel, click "Next". 13) From the Install Another Package panel, leave the Install Another Package check box cleared and click "Done" to exit the wizard. 14) If you did not install Middleware and are using WebLogic, you need to redploy the maximo.ear file. ======================================================================== 5. Post-installation instructions ======================================================================== After installing the pack, you must redo the customization changes in ORACLEAPIS\apisuser\oprx.usp and opaact.usp. ------------------------------------------------------------------------ Recreating all the interface tables and configuring the database ------------------------------------------------------------------------ 1) Start the Maximo application servers and services. 2) Start the Actuate servers and services. 3) Go to the External Systems application in Maximo. 4) Select the OA12 External System. 5) From the Select Action menu, select Create Interface Tables. 6) Select the check box on the left of the interface table listing to recreate this interface table. 7) Click Create. ------------------------------------------------------------------------ Configuring installation-dependent parameters in the setofvar.sql script ------------------------------------------------------------------------ 1) In the \ORACLEAPIS\install directory, open the setofvar.sql script. 2) Configure the following parameters: Parameter: hostStrOF = 'service name for Oracle database' Description: Enter the Oracle database service name configured in tnsnames.ora. Parameter: MaximoUserName = 'MAXORA' Description: User name created for the Oracle E-Business Suite integration schema. Parameter: MaximoPass = 'MAXORA user password' Description: Password for MAXORA. Parameter: ORAAPPLSYSUSERNAME = 'APPS' Description: Owner for the Oracle E-Business Suite database. Parameter: ORAAPPLSYSPASS = 'APPS' Description: Password for the Oracle E-Business Suite owner. Parameter: RootApis = '\ORACLEAPIS' Description: The install directory for the Oracle E-Business Suite adapter. It contains the following subdirectories: - apiuser - install - interface - log ------------------------------------------------------------------------ Installing store procedures ------------------------------------------------------------------------ 1) In SQL*PLUS(R), connect to the Oracle Applications database as user MAXORA. 2) To list and set the install parameters defined in the setofvar.sql script, enter the following command: SQL> start \ORACLEAPIS\install\setofvar The defined install parameters are displayed. 3) Enter the following command: SQL> start &InstallDir.install 4) Press Enter. The generated file is in the following location: \ORACLEAPIS\log\install.out 5) Open the install.out file and check for errors. The following table describes the errors that you might find: Error type: File not found Error text and action: Search for text similar to “unable to open file \\ORACLEAPIS\...”. If you find this text, verify that the setofvar.sql script has the correct folder settings. Error type: Statement not accepted Error text and action: Search for “unknown command” text by the system. If you find this text, check that the version of SQL*PLUS for Microsoft(R) Windows is the same or later than 3.1.3.5.4. Error type: Oracle error Error text and action: Search for “ORA –” text. If you find this text, contact your Oracle database administrator. Error type: Compile error Error text and action: Search for “PLS –” text. If you find this text, search for “with compilation error.” 6) Fix any problems that you find and rerun the install.sql file without errors. ------------------------------------------------------------------------ Enabling the external system ------------------------------------------------------------------------ 1) In the External Systems application, select the external system that you want to enable. 2) On the System tab, select the Enabled check box. ======================================================================== 6. Resolved issues ======================================================================== ------------------------------------------------------------------------ The following issues were resolved in this fix pack release ------------------------------------------------------------------------ There are no customer-reported issues that required fixing in this release. However, this fixpack provides support for Oracle E-Business Suite R12.1 ------------------------------------------------------------------------ The following issues were resolved for Maximo Enterprise Adapter v7.1.0.2 for Oracle Applications R12 ------------------------------------------------------------------------ --- ISSUE: 09-10308 Application: Maximo Enterprise Adapter for Oracle Applications Description: If you generate purchase orders with distributed PO lines in Oracle E-Business Suite and receive the associated items in Maximo, the Maximo Receiving application does not extract the distribution line numbers from the PO line numbers. --- ISSUE: 09-10807 Application: Maximo Enterprise Adapter for Oracle Applications Description: The End date field for contract and blanket expiration is not sent from Oracle E-Business Suite to Maximo Asset Management. --- ISSUE: 09-11492 Application: Maximo Enterprise Adapter for Oracle Applications Description: If two Maximo invoices have the same vendor invoice number, the first one in canceled status and the second one in open status, and you send a payment transaction for the open status invoice, Maximo tries to update the canceled invoice to PAID status and an error occurs. --- ISSUE: 09-11637 Application: Maximo Enterprise Adapter for Oracle Applications Description: In Oracle E-Business Suite, if you transfer item quantities from one bin to another, the bin balance is not updated correctly in Maximo. --- ISSUE: 09-11743 Applications: Maximo Enterprise Adapter for Oracle Applications Description: If you create a blanket contract and an associated release PO in Oracle E-Business Suite, replicate and receive the PO in Maximo, the data is not received into the MXRECEIPT_IFACE interface table. --- ISSUE: 09-11960 Application: Maximo Enterprise Adapter for Oracle Applications Description: If you send a PR from Maximo to Oracle E-Business Suite, and the PR is filled in with a foreign currency, the adapter leaves the UNIT_PRICE field blank and Oracle E-Business Suite cannot import the PR. --- ISSUE: 09-12178 Application: Maximo Enterprise Adapter for Oracle Applications Description: The work order cost is not updated with the variance amount. --- ISSUE: 09-12304 Application: Maximo Enterprise Adapter for Oracle Applications Description: A fully receipted PO in Oracle E-Business Suite is set to closed status. When the PO is revised, the revision process sends the closed status to Maximo before it sends the PO changes. As a result, an error transaction occurs and the PO is no longer in synchronation. --- ISSUE: 09-12682 Application: Maximo Enterprise Adapter for Oracle Applications Description: In the inbound process the hyphen delimiter of the GL accounts are not transformed into the period delimiter that is the configured format in Maximo. --- ISSUE: 09-13416 Application: Maximo Enterprise Adapter for Oracle Applications Description: If you update the name and or the lastname of a contact in Oracle E-Business Suite, this update is not correctly transfered to Maximo. --- ISSUE: 09-14104 Application: Maximo Enterprise Adapter for Oracle Applications Description: If you use star date and end date instead of using diabled flags for GL components, the flag values are not correctly sent to Maximo when you start the sync process. --- ISSUE: 09-14198 Application: Maximo Enterprise Adapter for Oracle Applications Description: If you use a synonim that is not also defined in the contract status list for one of the main statuses in the PO list, Oracle E-Business Suite 11i validates the synonim as a PO status for Outbound POs and generates a nullpointer error. --- ISSUE: 09-15262 Application: Maximo Enterprise Adapter for Oracle Applications Description: If you create a Purchase Requesition using as a Supplier a site that is assing to multiple Operating Units and one of this Units creates a Purchase Order from this Purchase Requesition, the following error occurs in Oracle E-Business Suite: "Supplier Site not valid." --- ISSUE: 08-21436 Application: Maximo Enterprise Adapter for Oracle Applications Description: If you send a PO from Oracle E-Business Suite to Maximo Asset Management, receive the PO items in Maximo, and return it to Oracle E-Business Suite, the PO line on the Oracle side is not found. --- ------------------------------------------------------------------------ The following issues were resolved for Maximo Enterprise Adapter v7.1.0.1 for Oracle Applications R12: ------------------------------------------------------------------------ --- ISSUE: 08-20792 Application: Maximo Enterprise Adapter for Oracle Applications Description: When you cancel a blanket PO in in Oracle E-Business Suite 11i, the contracts inbound displays an error. --- ======================================================================== 7. Notices ======================================================================== This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan, Ltd. 1623-14, Shimotsuruma, Yamato-shi Kanagawa 242-8502 Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation 2Z4A/101 11400 Burnet Road Austin, TX 78758 U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. If you are viewing this information softcopy, the photographs and color illustrations may appear. Trademarks IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at “Copyright and trademark information” at www.ibm.com/legal/copytrade.shtml. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.