Readme document for the SAP ERP 6.0 Adapter fix pack 7.1.0.3 Date: June 29, 2010 (C) Copyright International Business Machines Corporation 2009. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. ==================================================================================== Table of contents ==================================================================================== 1. Introduction 2. Content 3. New feature 4. Pre-installation instructions 5. Installation instructions 6. Post-installation instructions 7. Enabling the new feature 8. Resolved issues 9. Notices ==================================================================================== 1. Introduction ==================================================================================== This readme document provides information about fix pack 3 for IBM(R) Maximo(R) Enterprise Adapter 7.1 for SAP ERP 6.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.5 or later fix pack - IBM Maximo Enterprise Adapter 7.1 for SAP ERP 6.0 - Back up your database. This fix pack is cumulative and contains fixes required for the Maximo Enterprise Adapter for SAP upgrade from 6 to 7. If you are upgrading from version 6 to version 7, apply this fix pack before you upgrade Maximo Asset Management 6 to version 7. ==================================================================================== 2. Content ==================================================================================== The following item is included: SAPERP60Fixpack7103.zip -------------------------------------- This zip package contains fix pack 3 for Maximo Enterprise Adapter 7.1 for SAP ERP 6.0. ==================================================================================== 3. New feature ==================================================================================== With this fix pack, you can now choose to use batch reports or the INFREC and CREMAS IDOC methods to synchronize your SAP purchase info record data and vendor master data to Maximo Asset Management. The advantage of using the IDOC methods is that you can synchronize this data in real time. Maximo Enterprise Adapter for SAP ERP 6.0 now has these additional IDOC methods to meet the business need of the adapter clients. The new feature becomes effective only after you configure the SAP application server and SAP NetWeaver Process Integration. Because of the new feature, this fix pack introduces two new SAP ABAP structures. For information about these structures, see the related technotes at www.ibm.com/support. ==================================================================================== 4. Pre-installation instructions ==================================================================================== Before you install this fix pack, you must complete the following steps: 1) Determine the current software version: a) Sign in to Maximo Asset Management. b) From the navigation bar, click Help. c) From the drop-down list, select System Information. If the system displays the following result, the software is current and you do not need to install this fix pack: SAP ERP 6.0 Adapter 7.1.0.3 Build 20091201-0631 DB Build V7100-04 2) Process any transactions in the inbound and outbound queues. For more information, see “Processing transactions in queues." 3) Disable the SAP ERP 6.0 external system in Maximo Asset Management: a) From the Integration module of Maximo Asset Management, 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. 4) Stop the Maximo application servers and services. 5) Stop the Actuate servers and services. 6) Back up the entire maximo_root folder. 7) Back up the Maximo database. Processing transactions in queues Before you install this fix pack, you must process all transactions in the inbound and outbound queues. After you install the fix pack, you cannot process any outstanding transactions. Complete the following procedures: Processing transactions in WebLogic Server queues To process transactions in the inbound and outbound queues on Oracle WebLogic Server, you must ensure that no messages remain in the following queue servers: - mxintcqinserver - mxintsqinserver - mxintsqoutserver Procedure: 1) Sign in to the WebLogic Server Administration Console. For example: http://:/console 2) On the WebLogic Server home page, navigate to mydomain > Services > JMS > Servers > mxintcqinserver. 3) On the Monitoring tab of the mxintcqinserver page, click the Monitor Active JMS Servers link. On the Active JMS Servers page, the Messages column for the mxintcqinserver queue server displays the number of unprocessed messages in that queue. 4) Wait until the queue contains zero messages. If some messages remain in the queue, check the error folder. This error folder is in the global directory location that you defined in the Integration Administration Setup window of the External Systems application. 5) If error messages exist, correct the corresponding transactions and place them in the retry folder. 6) Repeat the preceding steps for the mxintsqinserver and mxintsqoutserver queue servers. Processing transactions in WebSphere Application Server queues To process transactions in the inbound and outbound queues on IBM WebSphere(R) Application Server, you must ensure that no messages remain in the following queue destinations: - cqinbd - sqinbd - sqoutbd Procedure: 1) Sign in to the WebSphere Application Server console. For example, http://localhost:9060/ibm/console. 2) Navigate to Service Integration > Buses > meajmsbus > Destinations. 3) Click queue destination cqinbd. 4) On the Configuration tab, select Queue Points under Message Points. 5) Select the identifier for the queue. The Current Message Depth field on the Runtime tab shows the number of messages in the queue. 6) If the number of messages in the queue is zero, go to step 11. 7) To see the messages with their Transaction IDs, click the Messages link under Additional Properties. 8) Click Refresh until the queue contains zero messages. 9) If some messages remain in the queue, check the error folder. This error folder is in the global directory location that you defined in the Integration Administration Setup window of the External Systems application. 10) If error messages exist, correct the corresponding transactions and place them in the retry folder. 11) Repeat the preceding steps for the sqinbd and sqoutbd queues. ==================================================================================== 5. Installation instructions ==================================================================================== Installing the fix pack 1) Download the SAPERP60Fixpack7103.zip file, into a temporary directory on the administrative system. For example, C:\temp 2) Go to the directory where your solutionInstallerGUI.bat file is located (for example, home dir\SMP\bin). 3) Double-click the solutionInstallerGUI.bat file in your drive folder. The IBM Tivoli(R) Base Services window opens. 4) Select a language for your installation and click OK. 5) From the Process Solution Installer Introduction panel, click Next. 6) From the Choose PSI Package panel, click Choose, navigate to the SAPERP60Fixpack7103.zip file (for example, C:\temp\SAPERP60Fixpack7103.zip), select it, click Open and 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, or, if the package is intended as an upgrade. The system is also checked to ensure the base package has already been installed. 7) From the Package Validation Results panel, review and verify the information displayed, and click Next. 8) If you installed your adapter on WebLogic Server or you have not used the Middleware installer, skip to step 12. 9) From the Middleware Login Information panel, 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, the 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. Select the Defer Maximo Application Redeployment and clear 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. Click Next to advance. 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) Rebuild and redeploy the maximo.ear file. ==================================================================================== 6. Post-installation instructions ==================================================================================== Importing ABAP updates that are in the SAP-Side subdirectories You can import the ABAP updates that are in the SAP-Side subdirectories while you install the fix pack. You must import them before you send transactions between Maximo Asset Management and SAP ERP 6.0. Procedure: 1) Review the files that are in the SAP-Side subdirectories to determine whether they affect any customizations in SAP ERP 6.0. 2) If the updates affect your customizations, merge the changes in the patched file or ABAP program with your customizations. 3) If you are applying more than one fix pack, repeat step 1 for each fix pack that you are applying. The transport files have consecutive numbers. If you are applying more than one fix pack, upload the transport files in sequence, starting with the earliest fix pack that you are applying. 4) For each Maximo Enterprise Adapter for SAP fix pack that you install, import the corresponding files to your SAP system. If the updates do not affect your customizations, you can use the transport file that corresponds to the fix pack that you are applying. It loads the entire group of updated files into your system. 5) If you customize any files in the fix pack, merge the fixes in the patched version of each modified file with your customized version of the file. 6) If a file is in more than one fix pack, import the latest patched version of the file. Importing updates that are in the SAP-Side\xi-repository directory You can import the transport file updates that are in the SAP-Side\xi-repository directory while you install the fix pack. Import them before you send transactions between Maximo Asset Management and SAP ERP 6.0. Procedure: 1) Review the files that are in the SAP-Side\xi-repository directory to determine whether they affect any customizations that you implemented in your SAP ERP 6.0 system. 2) If you customized any objects in the transport files, merge the changes in the XI objects with your customizations. 3) If you are installing more than one fix pack, repeat step 1 for each fix pack that you are installing. 4) If you are installing more than one fix pack, upload the transport files in sequence, starting with the earliest fix pack that you are installing. 5) Import the files that are in the SAP-Side\xi-repository directory sequentially, starting with the earliest fix pack that you are installing. 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. ==================================================================================== 7. Enabling the new feature ==================================================================================== Enabling the new feature on the SAP application server To enable the real time synchronization of SAP purchase info record and vendor master data to Maximo Asset Management, you must configure the SAP application server. The configuration includes procedures such as adding the INFREC and CREMAS message types, and setting filtering and partner profiles for these message types. INFREC is the message type for SAP purchase info record data. CREMAS is the message type for SAP vendor master data. Complete the following procedures: Adding the new message types in the model view You must add the INFREC and CREMAS message types in the model view. SAP will use these new message types to synchronize purchase and vendor transactions to Maximo Asset Management in real time. Procedure: 1) In the Change Distribution Model window, click Add message type. 2) Select your application server for ERP as the sender. 3) Select your integration server for Process Integration as the receiver. 4) Select the INFREC message type and click the Choose icon. 5) Repeat Steps 1-4 for the CREMAS message type. Setting filtering for the new message types 1) In the Change Distribution Model window, expand the tree structure under the INFREC message type. 2) Double-click No filter set. 3) In the Change Filter window, click the Create filter group. 4) Expand Data filtering to display the list of fields that you can use to filter messages for this message type. 5) Double-click a filter group, and then specify the values in the Edit List of Values window. 6) Specify the filter values and save your changes. 7 Repeat Steps 1-6 for the CREMAS message type. Configuring partner profiles for the new message types 1) In the Display IMG tree structure, expand the Structure tree structure to Maintain Partner Profile Manually: Cross-Application Components > Predefined ALE Business Processes > Logistics > Logistics > External Systems > External Transportation Planning Systems > Maintain ALE Partner Profiles 2) Click the clock icon next to Maintain Partner Profile Manually and expand Partner Type LS. 3) Under Partner Type LS, select the Exchange Infrastructure Integration Server IDoc Adapter. 4) Under the Outbound parameters section, click the Create Outbound Parameter icon. 5) Define the following outbound parameters for each new message type of the model view: Outbound Options tab parameter Value Receiver port Your receiver port number Output Mode Transfer Idoc immed. option 6) Select INFREC01 as the basic type for the INFREC message type. 7) Repeat Step 6 for the CREMAS message type and select CREMAS04 as the basic type. 8) Save the parameters. 9) If it is necessary for your integration to change the default to specify different receivers, you can do so on the Post Processing Permitted Agent tab. Activating change pointers 1) In the Display IMG tree structure, expand the Structure tree structure to Activate Change Pointers Generally: SAP Netweaver > Application Server > IDoc Interface / Application Link Enabling (ALE) > Modeling and Implementing Business Processes > Master Data Distribution > Replication of Modified Data > Activate Change Pointers - Generally 2) Select Activate Change Pointers - Generally. 3) Select the Change pointers activated - generally check box. 4) Click Save. 5) In the previous Display IMG window, select Activate Change Pointers for Message Types. 6) In the Change View “Activate Change pointers for Message Type”: Overview window, select the active check boxes for the INFREC and CREMAS message types. 7) Click Save. Defining variants for replication of modified master data You must define variants to run the RBDMICOD program, the standard SAP report that creates IDocs from change pointers, to distribute the INFREC and CREMAS message types. Procedure: 1) In the Display IMG tree structure, expand the Structure tree structure to Define Variants: SAP Netweaver > Application Server > IDoc Interface / Application Link Enabling (ALE) > Modeling and Implementing Business Processes > Master Data Distribution > Replication of Modified Data > Create IDocs from Change Pointers > Define Variants 2) Select Define Variants. 3) In the Program field of the ABAP Editor: Initial Screen window, select RBDMIDOC. 4) In the Subobjects section, select Variants. The window changes to show the variant subobjects. 5) Click Create. 6) In the ABAP: Variants - Initial window, type the variant name INFREC and CREMAS. 7) Click Create. 8) In the Message type field, type INFREC and CREMAS and click Attributes. 9) Add a variant description and save the changes. 10) Click Save. 11) Run the RBDMIDOC report every five minutes. Configuring ZBC_FILTER for purchase info record and vendor master objects 1) In the Maintain Table Views: Initial window, set the transaction code to SM30. 2) In the Table/View field, type the ZBC_Filters table name and click Enter. The transport file creates the table using default values and shows all processes inbound into SAP. 3) In the Data Browser window for the table that you typed, click Execute. 4) In the Change View window, edit table fields by selecting the check box in farthest left column for a row in the table, and then clicking the pencil icon. 5) Set the receiver to have the same name as the definition of the Maximo Business System in the SAP Exchange Infrastructure System Landscape Directory and ZBC_Destination. 6) Configure the ZBC_FILTERS table for following new objects: ZBC_FILTERS object Description INFORECORD Purchase Info Record CREMASTER Vendor Master 7) Apply at least one filter for the company code. 8) Save the changes. Enabling the new feature in SAP NetWeaver Process Integration To enable the real time synchronization of SAP purchase info record and vendor master data to Maximo Asset Management, you must configure SAP NetWeaver Process Integration to distribute purchase info record and vendor master data from SAP to Maximo. Procedure: 1) Define the interface determinations for distribution of purchase info record and vendor master data from SAP to Maximo: a) In the Configuration: Integration Builder window, click the Objects tab and expand Interface Determination. b) Double-click the interface determination. c) Change to edit view by clicking the pencil icon. d) Configure the following values for each interface determination object: Interface determination Sender interface Receiver interface Purchase info record INFREC.INFREC01 SAP_IDOC_INFREC_TOSAP Vendor master data CREMAS.CREMAS04 SAP_IDOC_CREMAS_TOSAP e) Click Save. 2) On the Change Lists tab, activate your changes by right-clicking Standard Change List and selecting Activate. 3) In the Activate change list window, activate the objects. 4) Click Close. ==================================================================================== 8. Resolved issues ==================================================================================== The following issues were resolved in this fix pack release: ISSUE: 08-23407 APPLICATION: Maximo Enterprise Adapter for SAP ERP 6.0 DESCRIPTION: The vendor enterprise service (MXVENDOR_FRSAP05) must be modified to add IDOC option to integrate SAP vendor to Maximo Asset Management in real time. ISSUE: 09-12370 APPLICATION: Maximo Enterprise Adapter for SAP ERP 6.0 DESCRIPTION: When you post an unevaluated transfer, the system does not send any invoice balance for the receiving storeroom. REPLACED FILES: SAP-Side\function groups\ZBC_S2M\Z_BC_BAPI_MATMOVE_GET_DETAIL ISSUE: 09-15061 APPLICATION: Maximo Enterprise Adapter for SAP ERP 6.0 DESCRIPTION: The vendor enterprise service (MXVENDOR_FRSAP05) must be modified to add IDOC option to integrate SAP vendor to Maximo in real time. REPLACED FILES: SAP-Side\function groups\ZBC_S2M\Z_BC_BAPI_VENDOR_GET_DETAIL SAP-Side\function groups\ZBC_S2M\Z_BC_BAPI_MESSAGEFILTER SAP-Side\dictionary\ZBC_S2M_CONTACTADR SAP-Side\classes\ZII_SAP_IDOC_CREMAS_TOSAP~SAP_IDOC_CREMAS_TOSAP SAP-Side\dictionary\bc_structures_outbound.xls SAP-Side\dictionary\bc_domains_internal.xls ISSUE: 09-15148 APPLICATION: Maximo Enterprise Adapter for SAP ERP 6.0 DESCRIPTION: The INVVendor enterprise service (MXINVVENDOR_FRSAP05) must be modified to add IDOC option to integrate SAP purchase info record to Maximo in real time. REPLACED FILES: SAP-Side\function groups\ZBC_S2M\Z_BC_BAPI_INFOREC_GET_DETAIL SAP-Side\function groups\ZBC_S2M\Z_BC_BAPI_MESSAGEFILTER SAP-Side\classes\ZII_SAP_IDOC_INFREC_TOSAP~SAP_IDOC_INFREC_TOSAP SAP-Side\dictionary\bc_structures_outbound.xls SAP-Side\dictionary\bc_domains_internal.xls ISSUE: 09-16370 APPLICATION: Maximo Enterprise Adapter for SAP ERP 6.0 DESCRIPTION: After you create a goods issue return in SAP including cancellation and material document, the Maximo reservation number is not deleted. REPLACED FILES: applications\maximo\businessobjects\classes\psdi\iface\sap2005\IssueInExt ISSUE: 09-18319 APPLICATION: Maximo Enterprise Adapter for SAP ERP 6.0 DESCRIPTION: If you create internal orders in SAP, the settlement rule is filled with 0% instead of 100%. REPLACED FILES: SAP-Side\function groups\ZBC_M2S\Z_BC_CREATE_WORKORDER_BAPI ISSUE: 09-18320 APPLICATION: Maximo Enterprise Adapter for SAP ERP 6.0 DESCRIPTION: The purchase order updates from Maximo to SAP, lines against items, and the Maximo storeroom are not processed correctly. REPLACED FILES: SAP-Side\function groups\ZBC_S2M\Z_BC_UPDATE_PURCHORDER_BAPI ISSUE: 09-18744 APPLICATION: Maximo Enterprise Adapter for SAP ERP 6.0 DESCRIPTION: When you send a new vendor from SAP to Maximo using IDOC method, an error is generated in SAP NetWeaver Process Integration. ISSUE: 09-19070 APPLICATION: Maximo Enterprise Adapter for SAP ERP 6.0 DESCRIPTION: When you create a purchase requisition using standard services with Z_BC_CREATE_PURCHASEREQ_N_BAPI function module, an error occurs. REPLACED FILES: SAP-Side\function groups\ZBC_M2S\Z_BC_CREATE_PURCHASEREQ_N_BAPI The following issues were resolved for Maximo Enterprise Adapter v7.1.0.2 for SAP 6.0 ISSUE: 09-10571 APPLICATION: Maximo Enterprise Adapter for SAP ERP 6.0 DESCRIPTION: When the flag is set for goods-receipt-based invoice verification on the POLine, and multiple Goods Receipts are used, every reversal coming from MXES requires a reference link to the original receipt. REPLACED FILES: SAP-Side\function groups\ZBC_M2S\Z_BC_CREATE_GRECEIPTS_BAPI SAP-Side\xi-repository\msgMap_M2S_RECEIPT SAP-Side\xi-repository\DT_SAP_RECEIPT ISSUE: 09-10781 APPLICATION: Maximo Enterprise Adapter for SAP ERP 6.0 DESCRIPTION: If Maximo Enterprise Adapter for SAP is enabled, and a new PO is created and approved with the standard service type, an error occurs when you try to save the PO. REPLACED FILES: applications\maximo\businessobjects\classes\psdi\iface\sap2005\ReceiptOutExt.class The following issues were resolved for Maximo Enterprise Adapter v7.1.0.1 for SAP 6.0: ISSUE: 08-21959 APPLICATION: Maximo Enterprise Adapter for SAP ERP 6.0 DESCRIPTION: Create Reservation against WBS elements fails when using BAPI processing REPLACED FILES: SAP-Side\function groups\ZBC_M2S\Z_BC_CREATE_RESERVATION_BAPI ===================================================================================== 9. 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 not 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.