Expert Tips: Unlocking the Power of UDOs in JDE 9.2 and 5-Step Acquisition Lifestyle – Stages & Finance System Tips

In this month’s issue of The Catch Up, we hear from Yvette Holt regarding the benefits of UDOs in JDE’s Release 9.2, and the opportunities they provide. Bradley Cooper gives us insight into the 5-Step Acquisition Lifestyle.

Unlocking the Power of UDOs in JDE 9.2

With Release 9.2, JD Edwards introduced User Defined Objects (UDOs) – web-based tools that allow users to create and customise objects in EnterpriseOne without the need for traditional development. These tools open up new opportunities for flexibility, efficiency, and user-driven improvements. Some of the most valuable UDO features include:

CafeOne Layouts
- Display two screens side by side to view related data in one place (e.g. sales order with invoice, or invoice with cash receipt).
Watchlists
- Monitor key business conditions in real time (such as overdue orders or inventory levels), with alerts displayed directly on the EnterpriseOne homepage.
Form Personalisation & Extensions
- Simplify screens by hiding or rearranging fields, or add new fields without modifying the core application.
Orchestrations
- Automate processes and integrate with other systems, offering a low-code approach to modifications.

“These UDO capabilities provide a powerful way to streamline workflows, improve user experience, and enhance visibility – helping organisations get even more value from their JDE 9.2 environment.”

Article content — Yvette Holt – Senior JDE Business Analyst

5-Step Acquisition Lifestyle – Stages & Finance System Tips

The below is Part 4 of a 5 part exclusive short series representing the different stages of a conceptual acquisition lifecycle model – a product of our learning lessons in Finance ToM and EPM design from mid-sized highly acquisitive businesses.

Stage 4: Integration

When: Onboarding and integration readiness (op model strategy and change plan is clear and socialised) completed.

What: Core system integration and first full integrated month-end and plan cycle.

Decision:

ERP, EPM, Sales & MI platforms:
- Direct vs indirect integration (cost & time to develop vs benefit).
- Centralised vs decentralised workflows (responsibility structure).
- Incremental delta load vs period override (system limitations).
- Critical systems first.
Local data history and migration:
- Balance vs transaction level (granularity benefit vs performance impact).
- Starting point and phasing.
Historic overlay restatements:
- YTD catch-up vs full restatement with commentary

Tips

Use a separate data audit dimension member in the EPM for each data source.
Local actuals now supersede Historic P&L overlays.
Reconcile P&L overlay history and agree approach on any delta with local actuals -e.g. an YTD catch-up keeps the periodic P&L history unchanged for group management reporting but causes a misalignment on period-by-period basis with local data.
Unless there is a strong regulatory or group commercial rationale for it, load no more than 2 years of target’s actual local periodic data (per GL instance) in the EPM system.
Unless there is a strong regulatory or group commercial rationale for it, loadbalances rather than transactions in your EPM, especially if the local system is to remain in use and not be decommissioned.
Assuming onboarding and overlays stages have been correctly executed, no material changes in the target’s data model & reporting structures (e.g. PCs/CCs/Segments) for group reporting/planning should occur during or immediately afterintegration. Any significant structural changes (e.g. splitting PCs ) should be moved to stage 5 ie Divisionalisation.
Ensure adjustments and splits relating to late changes in completion accounts, group consol / audit adjustments and pre vs post-acq P&L data can be separately identified from local actuals data in the EPM.