The pace of technological change forces IT managers throughout the world to constantly monitor the revision level of their production JD Edwards systems.

New releases of the EnterpriseOne software are providing not only improved functionality, but also entirely new modules, including:

Demand flow manufacturing

Demand scheduling execution

Engineer to order

CRM

The process of upgrading your system is in many cases straightforward and purely time consuming. If you have completed a number of upgrades yourself then you may be one of the lucky companies that does not require external advice or management. If, like most companies, it is a major upheaval and requires a professional organisation to take account of the process from start to finish then the BMS upgrade team is happy to undertake any one or more of the following tasks to help you achieve your upgrade objectives:

• Review Process Overview;
• Review Environment Overview;
• Review Training Requirements;
• Review Custom Code;
• Review Language Process Overview if the installation involves a secondary language;
• Assess the network;
• Acquire and install any new hardware (By Third Party);
• Post All Batches;
• Clear all variance anomalies;
• Purge and archive data;
• Back up the deployment server;
• Back up the existing language package directory (for language clients only);
• Back up the enterprise server;
• Back up the databases;
• Check media object queues;
• Check modification and merge flags;
• Prepare all environments for upgrade;
• Refresh the business data (optional);
• Refresh the control tables;
• Verify custom changes in master control tables;
• Verify third-party hardware and software;
• Verify that the deployment server hardware and software meet minimum technical requirements;
• Verify that the enterprise server hardware and software meet minimum technical requirements;
• Verify that the workstation hardware and software meet minimum technical requirements;
• Verify that the Java Server hardware and software meet minimum technical requirements (required when using Java Server);
• Verify that the Windows Terminal Services (WTS) hardware and software meet minimum technical requirements (required when using WTS);
• Verify that the deployment server disk space meets minimum technical requirements;
• Verify that the enterprise server disk space meets minimum technical requirements;
• Complete the detail worksheet in the Pre-Upgrade Preparation section of this documentation;
• Install the software on the deployment server;
• Install the latest software Tools Release and one-offs on the deployment server;
• Install the latest Planner Update on the deployment server;
• Run the Installation Planner creating an Upgrade plan for the Pristine, Development and Prototype environments. Pristine is required in order to run table conversions on the Enterprise Server. These may be combined in one plan or multiple plans;
• Upgrade the databases;
• Run table conversion workbench and remaining workbenches;
• Run manual table conversions;
• Verify table conversions;
• Build and deploy packages;
• Retrofit custom modifications;
• Upgrade the production environment;
• Modify the software after the upgrade;
• Set homepage for Solution Explorer;
• Install the data repository;
• Configure the software for use with Vertex;
• Configure workstations.

The advanced features and functionality provided by your upgraded software may well give you the “competitive advantage” your business is looking for. Additionally, the latest software release will give you a direct path to Oracle Fusion. Furthermore, the extensive cross business use of the Internet browser can lower ongoing technology and maintenance costs.

General Software Changes

• Added: PS810 is an extension of the Planner environment and used to improve performance during the Table Conversion Workbench.
• Added: Specs, System, Server Map, Data Dictionary, Object Librarian and the Pristine environment are in Unicode.
• Removed: Coexistence is no longer supported.
• Removed: Replication is no longer supported.
• Changed: SQLServer now uses OLEDB instead of ODBC DS by default.

Please note there have been many reported issues with OLEDB, such as specification merge, and package build errors when communicating with SQL Server 2000 database using OLEDB. This is resolved by reverting back to ODBC exclusively across all data sources.

• Changed: MSDE replaces Access DB.
• Changed: F986116 is used for DB2 UDB for Windows and UNIX table configuration.
• Changed: BLOBs (Control Objects, Work Flow) are now stored in LOB columns for Oracle and iS-eries.

Specifications Merge

• Changed: No longer merge FDA or ER.
• Changed: Retrofit custom code.

The custom code takes into consideration the Unicode impact. A new source slimmer is used.

• Changed: Perform a Visual Compare of FDA and ER.
• Changed: Server Package ER.
• Changed: Object Change table no longer used for net change.

An upgrade preserves all of the following custom data structures:

• Forms.
• Processing options.
• Reports.
• Business functions.

For a free No Obligation Upgrade Planning Session please call Helen or Mark on +44(0) 1527 851 350