TURNOVER Lifecycle Manager JD Edwards World Interface

Lesson Objectives

By the end of this lesson, you will be able to:

• Understand how TURNOVER® Lifecycle Manager integrates with JD Edwards World on IBM i for comprehensive change management.
• Configure the interface, including application definitions, type codes, and exits for JDE-specific artifacts like SVR entries, data dictionaries, FASTrs, DREAM Writers, and menus.
• Manage JDE World changes using PWM, forms, checkouts, promotions, and distributions while maintaining auditability.
• Handle custom JDE workflows, such as source versioning, recompiles, and integrations with TURNOVER® tools.
• Troubleshoot common integration issues and apply best practices for compliance in regulated environments.

This summary distills the 80-page guide (likely pre-2018 edition) into modules for developers, administrators, and JDE specialists. It focuses on extending TURNOVER®'s ALM to JDE World artifacts for controlled changes. Note: JD Edwards World is a legacy ERP (last major release A9.4), largely superseded by EnterpriseOne. As of October 24, 2025, TURNOVER® Lifecycle Manager (Release 2.100+) supports JDE integrations, but verify with UNICOM/SoftLanding for updates, as no public newer JDE World-specific guide was found; related docs emphasize artifact management like SVR and data dictionaries.

Key Concepts

• JDE World Artifacts: Managed items include Software Version Repository (SVR) entries, Data Dictionaries, FAStrs (Financial Analysis Spreadsheets), DREAM Writers (report writers), menus, and custom source/objects.
• Integration: TURNOVER® treats JDE as an application; uses custom type codes (e.g., *SVR, *DDICT) with methods for checkout, compile, promote.
• Workflow: From helpdesk requests to PWM worklists, forms for promotions, and distributions to remotes.
• Exits and APIs: Customize JDE-specific logic (e.g., pre-checkout validation for SVR).
• Auditing: Ensures traceability for compliance (e.g., SOX via forms/reports).
• Prerequisites: TURNOVER® v100+; JDE World A7.3+ on IBM i; configured cross-references (e.g., Hawkeye for JDE dependencies).

Module 1: Introduction to the JDE World Interface

Overview

• TURNOVER® provides seamless ALM for JDE World, automating changes while respecting JDE's structure (e.g., SVR for versioning).
• Benefits: Reduces errors, enforces approvals, supports multi-environment (dev/test/prod), and integrates with JDE tools.

Interface Components

• App Definitions: Model JDE as an application with levels (e.g., CRPDTA for prod data).
• Type Codes: Custom for JDE (e.g., *SVR for versions, *MENU for menus).
• Exits: JDE-specific (e.g., post-checkout to update SVR).

Module 2: Configuring the Interface

Setup Steps

1. Install/Verify: Ensure TURNOVER® and JDE libraries (e.g., JDFSRC, JDFOBJ) are accessible; apply JDE interface via supplements.
2. App Definitions: TURNOVER 1 > Create JDE app; add levels with JDE libs/paths.
3. Type Codes: Define methods (e.g., for *DDICT: promote with custom CL to update data dictionary).
4. Exits/APIs: Activate JDE exits (e.g., EXIT for SVR check-in); use APIs like ADDPWLITM for JDE items.
5. Cross-References: Integrate Hawkeye or JDE tools for dependency analysis.

JDE-Specific Configurations

• SVR: Manage versions as objects; checkout reserves SVR entry.
• Data Dictionaries: Promote changes with recompiles of affected programs.
• FAStrs/DREAM Writers: Handle as reports; custom promotions.

Module 3: Managing Changes in PWM and Forms

Using PWM for JDE

• STRPWM: Add JDE items (e.g., F6 for SVR entry); Option 21 checkout (reserves in JDE).
• Edit: Use JDE tools (e.g., Dream Writer designer); compile with JDE commands.
• Cross-Ref: Option 15 to find JDE dependencies (e.g., programs using a data item).

Building and Running Forms

• Option 46: Build form with JDE lines; edit (42) for JDE overrides (e.g., pre-run to quiesce JDE).
• Approvals: Mandate for prod (Option 48).
• Promotion: Move to next level; handle JDE recompiles automatically.
• Distributions: To remote JDE instances via *FTP/*SNA.

Module 4: Advanced Features and Workflows

Custom Workflows

• Emergency Changes: Use dedicated JDE emergency app (Supplement #24).
• Multi-Version: Manage JDE releases (e.g., A9.3 to A9.4) with related apps.
• Integrations: With RDi for modern JDE dev; exits for JDE-specific validation.

Auditing and Reporting

• History: Option 4 for JDE object trails.
• Reports: Option 10 for JDE-specific (e.g., SVR changes, menu updates).

Module 5: Troubleshooting and Best Practices

Common Issues

• SVR Conflicts: Resolve with multiple checkout.
• Dependencies: Ensure cross-ref setup for JDE.
• Distributions: Verify remote JDE libs match.

Best Practices

• Segregate: Use separate apps for JDE modules (e.g., financials vs. distribution).
• Test: Promote in dev/test before prod.
• Compliance: Enable archiving for all JDE changes.

Assessment and Next Steps

• Quiz Ideas: Steps to configure a JDE type code? How to handle SVR checkouts? Benefits for auditing?
• Practice: Set up a JDE app in test, checkout a data dictionary item, promote via form.
• Further Learning: User Guide (v101) for PWM/forms; Administrator’s Guide (Release 2.100) for exits; Supplements #30 (Exits/APIs), #14 (Change Process). Explore EnterpriseOne migrations if upgrading from World. Contact UNICOM support (tech.support@unicomsi.com or +1-603-924-8818) for 2025 integrations or JDE-specific licensing