Processing Option Commander
Speed up JDE Upgrades, Document and Compare Processing Options
It's important to have Processing Options documented for many reasons: for reference, in case something stops working, to compare Processing Options across Environments or even different Systems, plus of course to help re-creating Versions in the new system after an Upgrade.
Current version: 4.2.910.200
- Product Brief
- More Details
- System Requirements
Reduce risks and maintenance expenses by having your known good Processing Options documented - when something goes wrong with a Version, there will be a reference ready to instantly rectify the problem.
PO Commander uses Fat Client API's and supports all JDE releases starting from XE upwards. The main advantage of using JDE API's is the database-independence and easier configuration of the tool. It is entirely self-configurable and will work with any DB supported by JDE.
Neither Adobe® Distiller® nor Microsoft® Excel® need to be installed. PO's are reported by Language (the same Version can have multiple sets of PO descriptions in multiple Languages, displayed in OW accordingly to the current user's Language Preferences).
XLS format is highly visual, conveniently packing a lot more data per page than PDF, plus it can also be very useful to compare PO's between different Versions in the same Environment, or even between different Environments and Installations:
PO Commander not only reports PO values, it also analyses the data as it processes it and highlights any versions that have PO values corrupt (see the Versions in red on the screenshot above). This is a very frequent problem in upgraded or updated systems, because this data is simply copied across by the Upgrade process (or stays unaffected by Updates) without fixing any mismatched entries. This normally manifests itself with "PO Change" (or "Processing Option templates changed in versions.") warnings on the spec merge reports.
For example, in a brand-new, pristine ERP8 system, after the application of Update 1, there would be about 600 Versions with corrupt Processing Options!!! Nothing can easily identify them all, except PO Commander. If somebody accidentally runs one of them, without re-viewing the values (i.e.: blind submission), the consequences are unpredictable. For example, this sample report was taken from a fresh E900 installation and shows Processing Options for standard Versions of R42118 UBE. You can see that most of the Versions have corrupt or missing values. The available Trial Version reports a small subset of the available Versions, but even those are likely to be corrupt in almost any system.
Running versions with corrupt PO's may lead to myriads of unpredictable problems. Using PO Commander periodically, to check your system for PO corruption is highly recommended - especially after any Updates or Upgrades. Once such corrupted PO's are opened in JDE, reviewed and OK'ed, the values are automatically fixed in the database. The trick is to find them before they bite you in the back. A Version with corrupt PO's can be executed if a user runs it without a prompt, and most Interactive Programs do not, by default, prompt for Processing Options when started from a menu.
- Having collected a few PO Commander reports over time, it's easy to answer a number of likely questions:
- What PO values did this version have two weeks ago?
- Are there any PO's in the system which are corrupt?
- What PO values are different between various Versions of this Program?
- What PO values for a given Version are different between various Environments?
OS: MS Windows (x32 or x64)
OS Versions: 2000, 2003/Vista, 2008/Windows 7
OS Editions: Workstation or Server, excluding Home Edition
CPU: Intel or AMD (x32 or x64)
System Type: Physical (preferred) or Virtual (please mention this to us when purchasing, because of the licensing differences)
JDE Releases: XE (B7333), ERP8 (B7334), B9 (E1 8.9), E810, E811 (including E811 SP1), E812, E900, E910, E920
JDE Tools Releases (pre-Unicode): SP16 onwards
JDE Tools Releases (Unicode): TR891 onwards
JDE Backend Hardware Platforms: hardware-independent - all platforms supported by JDE are supported
JDE Backend Database Platforms: DB-independent - all platforms supported by JDE are supported
Client Machine Software Requirements: requires pre-existing functional JDE Fat Client installation (including any necessary DB connectivity clients)
Client Machine Hardware Requirements: has no requirements above JDE Fat Client MTR's, but will benefit from additional capacity
This licensing essentially works "as a book", or "one user at a time" and so it can be any user and in any computer.
This software does not have a mechanism that allows it to be used remotely, so in Virtual environments there will be additional considerations: the USB dongle can be plugged in into the Virtual Server and then mounted in the target VM, if the VM host offers USB support. And if it does not, then this software can instead be licensed to a physical HDD, mounted in the target VM (it's an Advanced option, this is not a Virtual Disk, physical disks are not available in VM's by default).
No installation is necessary to use the software - it can be copied to and executed directly from the USB disk, or from any other directory on the target computer, as long as the licensed device is physically available on the machine.
The optional Yearly Update/Upgrade Subscription is available at the time of purchase (not available separately) for an additional yearly fee. It is payable in advance per license, per year. It includes premium support and all software updates released during the paid period. Its cost is calculated as 20% of the product's list price at the time of invoicing, as may change from time to time. Unless the software is purchased for a single use application, we generally recommend to opt in for this Subscription: any future JDE Tools Releases and Releases/Updates may require an updated version of this solution and it's generally more cost-efficient compared to one-off Upgrades.