Boomerang Upgrade Suite
The value of the suite is not simply bundling products. It is that the products address different dependencies in the same upgrade: moving Objects, reconstructing Versions and cleaning environment-specific settings.
Boomerang is the centre of the workflow
Boomerang moves JDE Objects between systems and releases using OMW Projects. For upgrade teams, its important architectural effect is that object migration can happen when the team needs it rather than being tied to a single conventional SPEC Merge event.
That makes selective migration and continued source-system development much easier to manage. The surrounding tools then make the Version and environment state easier to carry forward deliberately.
Boomerang
Move the custom object layer across systems and releases.
Processing Option Commander
Capture and compare Version Processing Options before reconstruction.
Data Selection Commander
Capture and compare the selection logic that controls Version behaviour.
Update Queue Names
Remove obsolete Print Queue references without editing Versions one at a time.
Why the tools reinforce one another
An Object can migrate perfectly while its operational context is still wrong. A Version can exist in the target but carry different Processing Options, Data Selections or output routing. The practical upgrade problem is therefore wider than simply transporting specs.
The suite approach lets the team separate the work into explicit layers: move the Object, reproduce the Version configuration, then normalise environment-specific properties.
Use each component only where the target system actually needs it.
Where modern capability work begins
Once the technical baseline and custom layer are stable, the same upgrade programme can move into a different kind of work: identity, Orchestrations, MCP and AI. That is why this site keeps the historic upgrade suite alongside the newer capability-upgrade architecture rather than replacing one story with the other.