Professional Documents
Culture Documents
NRX Asset Hub 4.6.15 - Release Notes
NRX Asset Hub 4.6.15 - Release Notes
NRX Asset Hub 4.6.15 - Release Notes
15 Release Notes
NRX Global Corp. 150 York Steet 14th Floor Toronto, Ontario Canada M5H 3S5
Telephone : 416.368.4567 Fax Toll Free : 416.368.9844 : 877.603.4679
Copyright
Copyright 2009 NRX Global Corp. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of NRX Global Corp. The information contained herein may be changed without prior notice. Some software products marketed by NRX Global Corp. and its distributors contain proprietary software components of other software vendors. Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and SQL Server are registered trademarks of Microsoft Corporation. ORACLE is a registered trademark of ORACLE Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology.
www.nrx.com
NRX, VIP, and Asset Hub are trade marks or registered trade marks of NRX Global Corp. HP-UX is a registered trademark of Hewlett-Packard Company. JAVA is a registered trademark of Sun Microsystems, Inc. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, SAP Enterprise Portal and SAP Web Application Server are trademarks or registered trademarks of SAP AG in Germany and in several other countries. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves information purposes only. National product specifications may vary.
Typographic Conventions
Type Style Example Text Represents Words or characters that appear on the screen. These include field names, screen titles, and pushbuttons, as well as menu names, paths, and options. Cross-references to other documentation Example text Emphasized words or phrases in body text, titles of graphics, and tables Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE. Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, source code, as well as names of installation, upgrade, and database tools. Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries. Keys on the keyboard, for example, function keys (such as F2) or the Strg key.
Icons
Icon Meaning Caution Example Note Recommendation Syntax
EXAMPLE TEXT
Example text
Example text
<Example text>
EXAMPLE TEXT
Table of Contents
1 History of New Features ................................................................................. 6
1.1 Corrections and Enhancements in Asset Hub 4.6.14....................................................6 1.2 Corrections and Enhancements in Asset Hub 4.6.13....................................................6 1.3 Corrections and Enhancements in Asset Hub 4.6.12....................................................6 1.4 Corrections and Enhancements in Asset Hub 4.6.11....................................................6 1.5 Corrections and Enhancements in Asset Hub 4.6.10....................................................7 1.6 Corrections and Enhancements in Asset Hub 4.6.9......................................................7 1.7 Corrections and Enhancements in Asset Hub 4.6.8......................................................7 1.8 Corrections and Enhancements in Asset Hub 4.6.7......................................................7 1.9 Corrections and Enhancements in Asset Hub 4.6.6......................................................8 1.10 Corrections and Enhancements in Asset Hub 4.6.5......................................................8 1.11 Corrections and Enhancements in Asset Hub 4.6.4......................................................8 1.12 Corrections and Enhancements in Asset Hub 4.6.3......................................................9 1.13 Corrections and Enhancements in Asset Hub 4.6.2......................................................9 1.14 New Features in Asset Hub 4.6.1.....................................................................................9 1.15 New Features in Asset Hub 4.6......................................................................................10 1.16 New Features in Asset Hub 4.5.2...................................................................................10 1.17 New Features in Asset Hub 4.5.1...................................................................................10 1.18 New Features in Asset Hub 4.5......................................................................................11 1.19 New Features in Asset Hub 4.1......................................................................................11 1.20 New Features in Asset Hub 4.0......................................................................................11
May 2009
2.1.19 Changes to BOMs via Plant Assignment ...........................................................14 2.1.20 Real time Sync of Newly Created Multi-Level Tree ...........................................14 2.1.21 Maintenance Planning Plant and maintenance plan. ........................................14 2.1.22 Measuring Point has a Logical Connection to Maintenance Planning Plant..14 2.1.23 Initial Sync Programs vs. Direct 'Pull' Functionality in Asset Hub..................14 2.1.24 Problem with Direct Download of Maintenance Procedures ...........................15 2.1.25 Order of Objects Processing ...............................................................................15 2.2 Support for Exporting Report Results to PDF..............................................................15 2.3 MDM ..................................................................................................................................15
3 Ability to Turn off Lucene Database Backup on the Single-Server Setup 15 4 Additional Configuration Required When Using the Asset Hub Auditors
Deployed on SAP Web Application Server. ................................................ 16
May 2009
Note: The software and documentation for NRX Asset Hub 4.x is available in the English language only.
1 History of New Features 1.1 Corrections and Enhancements in Asset Hub 4.6.15
Submission back to Passport MR failed if any material added to the material list had a blank part number. Warehouse location removed from CAT ID did not get removed in Asset Hub after synchronization
Bug fix: BOMs fail to synchronize under certain circumstances. Bug fix: Maintenance plan XML failed to import.
May 2009
Improved speed of creating hyperlinks in parts books Classification values for a material were modifiable for synchronized materials regardless of restrictions Corrected issue with disappearing material list when Count Result button clicked in the material filter Child Equipment Type disconnects from the equipment type hierarchy after synching an equipment assigned to that child equipment type from SAP
May 2009
Enhancement: The FROM field when emailing a material list from the Viewer is now read-only and automatically prepopulated with the logged in user's email address. Synchronization fails when previously synched object has been deleted and then manually recreated with the same ERP code Creating SQL report templates with parameters didn't work.
May 2009
Modifying the address for a contact caused the address to be duplicated. Asset Hub Manager could lock up when books were being published while large asset trees were open. Sync session failed when assets were synchronized before BOMs from Indus Passport. Sync session failed when synchronizing certain BOMs from Indus Passport. Workflow task could not be set for a large number of materials . "Storage Bin" column in the materials table was not sorted properly. Importing data retrieved from Excel template through Collaboration failed under certain circumstances. Updated upgrade script from ACM 3.7.1 to Asset Hub 4.0 - issue with outbound SAP synchronization. Multiple Collaboration request items were created even though option was selected for a single request item.
May 2009
Upgrading Asset Hub from earlier versions: no upgrade .sql scripts are needed to upgrade Asset Hub database from 4.6 to 4.6.1. However, if you are running a version of Asset Hub lower than 4.6, please run all .sql scripts from your version up to upgrade_4.5.2.0_to_4.6.0.0.sql. For example, if your ACM server is currently ACM 3.7 and you want to upgrade it to Asset Hub 4.6.1, you must run all seven .sql files, from upgrade_3.7.0.0_to_3.7.1.0.sql to upgrade_4.5.2.0_to_4.6.0.0.sql inclusive
May 2009
10
May 2009
11
May 2009
12
2.1.10
When creating a new material item at the enterprise level in Asset Hub, it is not linked to a plant, and as a result, cannot be synchronized to R/3. This synchronization may be supported in a future release. The same is true for synchronization from R/3 to Asset Hub. If a material item is not an assembly, and it is not liked to any plant in R/3, it cannot be synchronized to Asset Hub
2.1.11
There is no support for changing material type when editing an existing material item in Asset Hub. When a material item is created in R/3, it depends on the material type. Because of this dependence, changing the type later does not make sense.
2.1.12
Numeric values entered as ERP attributes must adhere to the convention, which requires they be the default of the R/3 user used to connect Asset Hub to R/3 (in SU01).
2.1.13
When loading the data dictionary from an XML file, you must ensure the XML is from the correct client, and that it matches data already in Asset Hub. Otherwise, when data is sent to R/3 with these attributes, R/3 may return errors such as Data Inconsistent, and it may appear that there is a configuration problem in R/3, which is not the case. The same applies to downloading the data dictionary directly. You must ensure the R/3 client connection is correct.
May 2009
13
Duplicate BOM items in the same BOM Material Filter in Mat. Extractor from R/3 to Asset Hub Filters for Material Extractors/Delta Sync from R/3 to Asset
Synchronization of Duplicate BOM items in the same BOM are not supported.
Only one filter group supported in this release (in the ALE distribution model) for the material filter
During the synchronization of materials from R/3 to Asset Hub (initial and delta), the Plant filter works such that there needs to be a blank entry in the Plant filter group if the customer makes use of IBAUs (assemblies). Because IBAUs are not connected to any plant, this is the only way to send IBAU materials to Asset Hub. You should also ensure that there is only one filter group for material.
2.1.19
Changes to BOMs via plant assignment are not captured as changes and therefore they are not sent to Asset Hub.
2.1.20
Real time Synchronization of Newly Created Multi-Level Tree Branch Tree is not Supported Workaround: Repeat sending the whole branch as many times as many levels it contains Or Use manual outbound sync
2.1.21
The Maintenance Planning plant for all items must be the same within a maintenance plan. Asset Hub does not support maintenance plans where items are linked to multiple Maintenance Planning Plants.
2.1.23 Hub
In the case of large datasets to be initially synchronized from R/3, NRX recommends that the Initial Synchronization programs /NRX/AH45_INIT* be used (in background jobs),
May 2009
14
and Not the Direct 'Pull' from Asset Hub, for performance reasons.
2.1.24
When pulling down maintenance procedures from R/3 into Asset Hub, components and the unit of measure are not pulled down. Please use the Initial Sync program /NRX/AH45_INIT_TASKLIST for the initial synchronization of Maintenance Procedures.
2.1.25
Due to complexities in tracking newly created objects, it is recommended that each type of object be processed separately. That is, before processing the next type of object in SAPLOAD you must refresh the object data from Asset Hub. For example, if you create a new BOM with new materials you must process the materials first, (re-)sync the BOM, and then process the BOM. Please refer to the configuration guide for the order in which to process the objects.
2.3 MDM
The data extractors for equipment and material produce IDocs in XML format. The program messages indicate that these are initial syncs to Asset Hub. Despite this message, the XMLs that are produced are valid for the MDM repositories for equipment and material as well.
Single-Server Setup
The Lucene database backup process consists of zipping up and uploading the database file to the central database. By default, this backup process is enabled. If the Lucene database is large, this can be a very intensive process. Since the main purpose of the Lucene database backup is cluster support, it is recommended that it be disabled on single-server Asset Hub installations. To disable it, use the following method: Modifying "com.nrx.textsearch.index.backup.enabled" Parameter
May 2009
15
2. On the Cluster tab, expand the tree MachineName... Server 0 0_xxxx... Services... Web Container. 3. In the right panel of the Visual Administrator window, expand the Asset Hub application nrx.com/nrx, and click the assetHub node. 4. Click View. 5. Click the Environment tab, then the Environment Entries sub-tab. 6. Locate the following environment entry: com.nrx.textsearch.index.backup.enabled Set it to false. 7. Click Modify, then Save, to commit your changes. Click OK in the dialog that appears.
May 2009
16