Rapid4Cloud Platform - STAGING

Documentation

Jd Edwards Enterprise One
Table of contents
Back to list

JD Edwards EnterpriseOne Event Rules Code Text Export User Guide

Purpose

This guide explains how to export JD Edwards EnterpriseOne Event Rules (ER) code as plain text files for use with the JDE Reporting Platform.

The exported .txt files are used by the platform for:

  • ESU Comparison Report generation
  • Technical Specification Document (TSD) generation
  • Customization analysis
  • Retrofit planning
  • AI-assisted documentation and code review

The JDE Reporting Platform expects JD Edwards ER export files to be available as text files before they are uploaded to object storage or passed into the processing pipeline.

Supported Extraction Options

There are two supported extraction methods:

  1. JD Edwards Native Development Tools

    • Form Design Aid (FDA)
    • Report Design Aid (RDA)
    • Event Rules print-to-file export

  2. PatWel Group Object Browser

    • Individual object export
    • Batch export
    • Text output suitable for large-scale comparison and documentation workflows

Recommended Extraction Priority

Use the following priority when selecting an extraction method:

Priority Method Recommended Use
1 PatWel Object Browser Batch Export Preferred for ESU comparison, large TSD batches, and repeatable client exports
2 PatWel Object Browser Individual Export Useful for validating one object or exporting a small number of objects
3 JD Edwards FDA/RDA Print to File Fallback option when Object Browser is not available

Object Browser is recommended for production use because it provides more consistent text output, supports batch export, and can export from Pristine and Production sources more efficiently than manually printing each object from FDA or RDA.

Export Standards for the JDE Reporting Platform

Required File Format

All source exports provided to the JDE Reporting Platform must be plain text files.

Required:

.txt

Do not provide the following as source inputs:

.pdf
.docx
.xls
.xlsx
.html

PDF output is not supported as source input for this workflow because the platform processes staged text files.

Recommended Character Encoding

Recommended encoding:

UTF-8

If the export tool produces ANSI or another Windows code page, validate that the file opens cleanly in a text editor before uploading or processing.

File Naming Standards

ESU Comparison

The ESU comparison process compares paired Pristine and Production text exports for the same object.

Pristine file naming:

PS920_<OBJECTID>.txt

Production file naming:

PD920_<OBJECTID>.txt

Example:

PS920_P4210.txt
PD920_P4210.txt

TSD Generation

For TSD generation, use the source environment or path code prefix followed by the object ID.

Example:

DV920_P4210.txt
DV920_R42520.txt

Output Folder Standards

Recommended folder structure:

C:\JDE_ER_Exports
  \DV920
  \PS920
  \PD920
  \esu_compare_input

For ESU comparison, the final input folder should contain matched pairs in the same folder:

C:\JDE_ER_Exports\esu_compare_input
  PS920_P4210.txt
  PD920_P4210.txt
  PS920_P01012.txt
  PD920_P01012.txt

Option 1: Export ER Code Using JD Edwards Native Development Tools

Overview

JD Edwards native development tools can export Event Rules by printing the ER listing directly to a file from the Event Rules editor.

This method is best for:

  • Single object review
  • Small test exports
  • Manual validation
  • Environments where PatWel Object Browser is not installed

This method is not ideal for large-scale ESU comparison because each object must be opened and exported manually.

Prerequisites

Before using this option, confirm that you have:

  • Access to a JD Edwards EnterpriseOne development client.
  • Security access to Object Management Workbench (OMW).
  • Access to the relevant path code or environment.
  • Authority to open the target object in design mode.
  • A destination folder where the .txt file can be written.

Important FDA/RDA Print Warning

When using the Event Rules print function, JD Edwards displays the following warning:

Event Rules will be printed only if the specs are saved.
To print the newly added ER lines save the specs and then print again.

Before exporting Event Rules:

  1. Save the object specifications.
  2. Save any recent Event Rules changes.
  3. Reopen or refresh the Event Rules editor if needed.
  4. Print the Event Rules again after saving.

Unsaved Event Rules will not appear in the exported file.

Option 1A: Export ER Code from an Interactive Application Using FDA

Use this process for interactive applications such as P01012, P4210, P55PARMS, or other Pxxxxx objects.

Step 1: Open Object Management Workbench

  1. Sign in to the JD Edwards EnterpriseOne development client.
  2. Open Object Management Workbench (OMW).
  3. Locate or create a project that contains the object you need to export.
  4. Add the interactive application object to the project if the object is not already present.
  5. Select the object in the project window.

Step 2: Confirm the Correct Local Specifications

Before printing Event Rules, confirm that the local specifications represent the environment you intend to export.

For TSD generation, use the environment or path code that represents the current-state object you want documented.

For ESU comparison, use the Advanced Get process described later in this guide to retrieve the object from both Pristine and Production before exporting.

Step 3: Open Form Design Aid

  1. Highlight the application object.
  2. Select Design or Start Design.
  3. Form Design Aid (FDA) opens.
  4. Select the form that contains the Event Rules you need to export.

Step 4: Open the Event Rules Editor

  1. Select the form, control, grid, button, or field that contains the logic.
  2. Open Event Rules using the available menu, toolbar, or right-click option.
  3. The Event Rules editor opens for the selected form event or control event.

Common FDA events include:

  • Post Dialog Is Initialized
  • Button Clicked
  • Find Button Clicked
  • Grid Record Is Fetched
  • Field Changed
  • Field Exit
  • Dialog Is Exited

Step 5: Open the Print Dialog

With the Event Rules editor active, select:

File > Print

Step 6: Configure the Event Rules Printing Dialog

In the Event Rules Printing dialog, configure the export as follows.

Destination

Select:

File

Do not select:

Printer

Specify the full output path and filename.

Example:

C:\JDE_ER_Exports\DV920\DV920_P55PARMS.txt

For ESU comparison Pristine export:

C:\JDE_ER_Exports\PS920\PS920_P55PARMS.txt

For ESU comparison Production export:

C:\JDE_ER_Exports\PD920\PD920_P55PARMS.txt

Print Scope

Select:

Application

Selecting Application exports the Event Rules for the entire application. Users do not need to repeat the export for each individual form, control, or event when the goal is to export the full application for the JDE Reporting Platform.

Print ER Options

Recommended options:

[x] Expand Arguments
[x] Show Line Numbers
[x] Date/Time Stamp
[x] Show Comments

These options provide the richest export for ESU comparison, TSD generation, and later code review.

Step 7: Export the Text File

  1. Confirm that File is selected as the destination.
  2. Confirm that the filename ends in .txt.
  3. Confirm that the recommended Print ER options are selected.
  4. Click OK.
  5. Open the generated .txt file in a text editor.
  6. Confirm that the Event Rules code is readable and that the file contains the expected object, form, event, comments, arguments, and line numbers.

Step 8: Validate the Full Application Export

When Application is selected as the Print Scope, the export should contain the Event Rules for the full application. Open the generated .txt file and confirm that the expected application-level ER content is present before uploading or processing the file.

Option 1B: Export ER Code from a Batch Application Using RDA

Use this process for batch applications such as R42520, R09801, or other Rxxxxx objects.

Step 1: Open Object Management Workbench

  1. Sign in to the JD Edwards EnterpriseOne development client.
  2. Open Object Management Workbench (OMW).
  3. Locate or create a project containing the report object.
  4. Add the UBE/report object if needed.
  5. Select the report object.

Step 2: Confirm the Correct Local Specifications

Before opening the report, confirm that your local specifications reflect the environment or path code you intend to export.

For ESU comparison, use Advanced Get to retrieve the report from the appropriate path code before exporting.

Step 3: Open Report Design Aid

  1. Highlight the report object.
  2. Select Design or Start Design.
  3. Report Design Aid (RDA) opens.
  4. Open the report template.

Step 4: Open Event Rules

  1. Select the section that contains the logic.
  2. Open the Event Rules editor.

Common RDA events include:

  • Initialize Section
  • Do Section
  • End Section
  • Column Inclusion
  • Report Initialization
  • Page Header
  • Page Footer

Step 5: Print the Event Rules to a Text File

  1. With the Event Rules editor active, select:

    File > Print

  2. In the Event Rules Printing dialog, select:

    Destination > File

  3. Enter a .txt output file name.

    Example:

    C:\JDE_ER_Exports\DV920\DV920_R42520.txt

  4. Set Print Scope to:

    Application

    Selecting Application exports the Event Rules for the full report/application object. Users do not need to repeat the export for each individual report section when the goal is to export the full object for the JDE Reporting Platform.

  5. Use the recommended ER print options:

    [x] Expand Arguments
[x] Show Line Numbers
[x] Date/Time Stamp
[x] Show Comments

  6. Click OK.

  7. Open the file in a text editor and confirm that the Event Rules are readable and that the expected full object content is present.

Advanced Get Process for ESU Comparison

Why This Is Required

The ESU Comparison Report compares Oracle-delivered Pristine objects against the client's customized Production objects.

To support this comparison, export two text files for the same object:

  1. A Pristine export from the Pristine path code.
  2. A Production export from the Production path code.

These files must be named as a matched pair:

PS920_<OBJECTID>.txt
PD920_<OBJECTID>.txt

The comparison tool uses the object ID to pair the Pristine and Production files.

Important Warning

Advanced Get updates the local specifications used by the signed-in JD Edwards user. Use a controlled workstation, a dedicated export user, or a clearly defined export process so local specs are not accidentally mixed between Pristine and Production exports.

After each Advanced Get, open and export the object immediately, then repeat the Advanced Get process for the next source path code.

Advanced Get from Pristine

Use this process to retrieve the Oracle-delivered Pristine version of the object.

Step 1: Open OMW

  1. Sign in to the JD Edwards development client.
  2. Open Object Management Workbench.
  3. Add the target object to an OMW project if the object is not already present.
  4. Select the object in the project window.

Step 2: Run Advanced Get

  1. With the object selected, open the row menu.

  2. Select:

    Advanced > Advanced Get

  3. When prompted to overwrite local specifications, choose the option that allows the Pristine specifications to replace the current local copy.

  4. In the path code search window, select the Pristine path code.

    Common example:

    PS920

  5. Complete the Advanced Get.

Step 3: Export the Pristine ER Code

  1. Open the object in FDA or RDA.

  2. Open the Event Rules editor.

  3. Select:

    File > Print

  4. Select:

    Destination > File

  5. Save the output using the Pristine naming convention:

    PS920_<OBJECTID>.txt

Example:

C:\JDE_ER_Exports\PS920\PS920_P01012.txt
  1. Validate the .txt file.

Advanced Get from Production

Use this process to retrieve the client's customized Production version of the same object.

Step 1: Return to OMW

  1. Return to Object Management Workbench.
  2. Select the same object.

Step 2: Run Advanced Get

  1. Open the row menu.

  2. Select:

    Advanced > Advanced Get

  3. When prompted to overwrite local specifications, choose the option that allows the Production specifications to replace the current local copy.

  4. Select the Production path code.

    Common example:

    PD920

  5. Complete the Advanced Get.

Step 3: Export the Production ER Code

  1. Open the object in FDA or RDA.

  2. Open the Event Rules editor.

  3. Select:

    File > Print

  4. Select:

    Destination > File

  5. Save the output using the Production naming convention:

    PD920_<OBJECTID>.txt

Example:

C:\JDE_ER_Exports\PD920\PD920_P01012.txt
  1. Validate the .txt file.

ESU Comparison File Checklist

Before uploading or processing files, confirm the following:

  • Both files exist for each object.
  • The Pristine file starts with PS920_.
  • The Production file starts with PD920_.
  • Both files use the same object ID.
  • Both files have the .txt extension.
  • The files contain readable ER code, not PDF or binary content.
  • The files are stored in the same input folder for comparison.

Example valid pair:

PS920_P4210.txt
PD920_P4210.txt

Example invalid pair:

PS920_P4210.pdf
PD920_P4210.txt

Option 2: Export ER Code Using PatWel Group Object Browser

Overview

PatWel Group Object Browser is a third-party JD Edwards utility that can inspect JD Edwards objects and export object specifications and Event Rules to text or HTML files.

For the JDE Reporting Platform, use Text output.

Object Browser is recommended for:

  • Batch extraction
  • Repeatable export runs
  • ESU comparison preparation
  • Large-scale TSD input preparation
  • Reducing manual print-to-file effort

Downloading Object Browser

Object Browser is provided by PatWel Group Inc.

Step 1: Open the PatWel Downloads Page

  1. Open a web browser.

  2. Navigate to the PatWel Object Browser download page:

    PatWel Object Browser Downloads

Step 2: Select the Correct Version

Download the version that matches the JD Edwards development client architecture installed on the workstation:

  • 32-bit Object Browser for 32-bit JD Edwards developer clients
  • 64-bit Object Browser for 64-bit JD Edwards developer clients

The PatWel download page lists separate 32-bit and 64-bit versions and identifies the required Microsoft Visual Studio redistributable for each architecture.

Step 3: Remove Existing Versions if Needed

If an older Object Browser version is already installed, remove the existing version from Windows Add/Remove Programs before installing the new version.

Step 4: Install Required Redistributable

Install the Microsoft Visual Studio redistributable listed on the PatWel download page if it is not already installed.

Step 5: Install Object Browser

  1. Run the downloaded installer.
  2. Follow the installation prompts.
  3. Launch Object Browser after installation.
  4. Confirm that the tool opens successfully on the JD Edwards developer workstation.

Object Browser Requirements

Object Browser requires access to a JD Edwards developer or fat client workstation.

Before exporting, confirm:

  • Object Browser is installed on the workstation.
  • The workstation has access to the required JD Edwards path codes.
  • The correct source path code is available.
  • You know whether the export is for TSD generation or ESU comparison.
  • The selected output format is Text, not HTML.

Option 2A: Export an Individual Object to Text

Use this process when exporting one object at a time.

Step 1: Launch Object Browser

  1. Open Object Browser.
  2. Connect using the appropriate JD Edwards credentials.
  3. Select the required source environment or path code.

Step 2: Locate the Object

  1. Use Object Search to locate the target object ID.
  2. Select the appropriate object type.

Examples:

P01012
P4210
R42520
B95110A
N55EXAMPLE

Common object types include:

  • APPL
  • UBE
  • BSFN
  • NER
  • TER

Step 3: Review the Event Rules or Source

  1. Open the object.
  2. Navigate to the Event Rules or source code section.
  3. Confirm that the displayed logic is the logic you intend to export.

Step 4: Export to Text

  1. Select the export option for the object.
  2. Choose the option that exports Event Rules, object properties, or both, depending on the intended downstream use.
  3. Select text output.
  4. Choose the destination folder.
  5. Save the object export as a .txt file.

Recommended TSD naming:

DV920_<OBJECTID>.txt

Recommended ESU comparison naming:

PS920_<OBJECTID>.txt
PD920_<OBJECTID>.txt

Step 5: Validate the Export

  1. Open the .txt file.
  2. Confirm that the file contains readable Event Rules code or source content.
  3. Confirm that the object ID and source path code are correct.
  4. Confirm that the file is not HTML or PDF.

Option 2B: Batch Export Multiple Objects to Text

Use this process for ESU comparison projects, large TSD generation batches, or a full object extraction run.

Step 1: Prepare the Object List

Create a list of objects to export.

Example:

P01012
P4210
R42520
B95110A

Keep separate export runs for each source path code used in ESU comparison.

Recommended folders:

C:\JDE_ER_Exports\PS920
C:\JDE_ER_Exports\PD920
C:\JDE_ER_Exports\DV920

Step 2: Launch Object Browser

  1. Open Object Browser.
  2. Connect to the correct JD Edwards environment.
  3. Confirm that the correct path code/source is available.

Step 3: Open Batch Export

From Object Browser, select:

Tools > Batch Export

Step 4: Configure Object Selection

In the Batch Export dialog, choose one of the following selection methods:

Selection Method Use Case
Object Export one object or object name pattern
Project Export objects from an OMW project
Input File Export objects listed in an external input file

For object type, select the appropriate type, such as:

APPL
UBE
BSFN
NER
TER

If exporting a known system code, populate the System field as needed.

Step 5: Configure OMW Date Updated Filter

The Batch Export dialog includes an OMW Date Updated filter with these options:

  • No Selection
  • Equal to selected date
  • Less than selected date
  • Greater than selected date

For most JDE Reporting Platform exports, use:

No Selection

Use date filtering only when the export needs to be limited to objects updated before, on, or after a specific OMW date.

Step 6: Configure Source

The Source field determines the source path code used for the export.

For TSD generation, select the current-state environment or path code.

Example:

DV920

For ESU comparison, run the export twice:

Pristine run:

Source = PS920

Production run:

Source = PD920

Step 7: Configure Required Export Options

For the JDE Reporting Platform, enable the following options:

[x] Export ER
[x] Show ER Line #s
[x] Show Logic Lines

These options are recommended because:

  • Export ER provides the Event Rules text required by the platform.
  • Show ER Line #s supports line-level review and retrofit discussions.
  • Show Logic Lines improves readability of program flow and conditional logic.

Step 8: Configure Optional Export Options

Enable these only when the project requires additional information:

[ ] Export Object Properties
[ ] Show BSFN Path
[ ] Export Versions
[ ] Hide Disabled

Guidance:

Option Recommendation
Export Object Properties Useful for fuller technical documentation, but increases output size
Show BSFN Path Useful when troubleshooting business function references
Export Versions Useful when version-specific details are part of the analysis
Hide Disabled Use only if disabled ER should be excluded from analysis

For most ESU comparison exports, include disabled logic unless the project explicitly decides otherwise. Disabled logic may still be relevant for retrofit planning or technical documentation.

Step 9: Configure Output Format

Select:

Text

Do not select:

HTML

HTML may be useful for manual review, but it should not be used as the primary input for the JDE Reporting Platform unless the ingestion logic has been explicitly updated to support HTML.

Step 10: Configure Export Location

Choose an export directory that identifies the source path code.

Examples:

C:\JDE_ER_Exports\PS920
C:\JDE_ER_Exports\PD920
C:\JDE_ER_Exports\DV920

Step 11: Configure Filename Options

The Batch Export dialog includes these filename options:

[x] Prepend Spec Location to Filename
[ ] Append Timestamp to Filename

Recommended setting for the JDE Reporting Platform:

[x] Prepend Spec Location to Filename
[ ] Append Timestamp to Filename

Prepending the spec location helps identify source environment/path code in the filename. Avoid appending timestamps when the files will be consumed by automated pairing logic, unless the files will be renamed before processing.

Step 12: Run the Batch Export

  1. Review all settings.
  2. Confirm that output format is set to Text.
  3. Confirm that the selected Source is correct.
  4. Confirm that the export location is correct.
  5. Click OK.
  6. Allow the export to complete.
  7. Review the generated .txt files.

Recommended Object Browser Configuration for R4C

ESU Comparison Configuration

Run the batch export twice, once from Pristine and once from Production.

Pristine Export

Source: PS920
Output: Text
Export Location: C:\JDE_ER_Exports\PS920

Recommended options:

[x] Export ER
[x] Show ER Line #s
[x] Show Logic Lines
[x] Prepend Spec Location to Filename
[ ] Append Timestamp to Filename

Recommended final filename pattern:

PS920_<OBJECTID>.txt

Production Export

Source: PD920
Output: Text
Export Location: C:\JDE_ER_Exports\PD920

Recommended options:

[x] Export ER
[x] Show ER Line #s
[x] Show Logic Lines
[x] Prepend Spec Location to Filename
[ ] Append Timestamp to Filename

Recommended final filename pattern:

PD920_<OBJECTID>.txt

TSD Generation Configuration

Use the source that represents the current-state object to be documented.

Example:

Source: DV920
Output: Text
Export Location: C:\JDE_ER_Exports\DV920

Recommended options:

[x] Export ER
[x] Show ER Line #s
[x] Show Logic Lines
[x] Prepend Spec Location to Filename
[ ] Append Timestamp to Filename

Recommended final filename pattern:

DV920_<OBJECTID>.txt

Object Browser ESU Comparison Workflow

Goal

Use Object Browser to export the same object list from both Pristine and Production, then provide the paired .txt files to the ESU comparison tool.

Step 1: Export from Pristine

  1. Launch Object Browser.

  2. Open:

    Tools > Batch Export

  3. Select the object list, project, or input file.

  4. Set Source to:

    PS920

  5. Select output format:

    Text

  6. Enable:

    [x] Export ER
[x] Show ER Line #s
[x] Show Logic Lines

  7. Export to:

    C:\JDE_ER_Exports\PS920

  8. Confirm the files follow this naming pattern:

    PS920_<OBJECTID>.txt

Step 2: Export from Production

  1. Launch Object Browser or return to Batch Export.

  2. Use the same object list, project, or input file used for the Pristine export.

  3. Set Source to:

    PD920

  4. Select output format:

    Text

  5. Enable:

    [x] Export ER
[x] Show ER Line #s
[x] Show Logic Lines

  6. Export to:

    C:\JDE_ER_Exports\PD920

  7. Confirm the files follow this naming pattern:

    PD920_<OBJECTID>.txt

Step 3: Combine Matched Pairs for Processing

Copy matched file pairs into a single input folder.

Example:

C:\JDE_ER_Exports\esu_compare_input
  PS920_P01012.txt
  PD920_P01012.txt
  PS920_P4210.txt
  PD920_P4210.txt

Step 4: Validate the Input Folder

Before running the ESU comparison process, confirm:

  • Every PS920_ file has a matching PD920_ file.
  • The object IDs match exactly after the path code prefix.
  • Files are text files.
  • Files are not empty.
  • Files open cleanly in a text editor.
  • Timestamp suffixes have been removed if the processing script expects exact pair names.

Step 5: Run the ESU Comparison Tool

The JDE Reporting Platform compares paired Pristine and Production exports from the same input directory.

Example command:

python compare_esu.py examples/esu_compare output/

Single object example:

python compare_esu.py examples/esu_compare output/ --object P01012 --format docx

Client-specific output example:

python compare_esu.py examples/esu_compare output/ --client-id ACME

TSD Generation Workflow

Goal

Use a single text export for each object that should be documented.

Example input:

DV920_P01012.txt
DV920_R42520.txt

Step 1: Export the Object

Use one of the supported methods:

  • JD Edwards FDA/RDA print-to-file
  • PatWel Object Browser individual export
  • PatWel Object Browser batch export

Step 2: Validate the Text File

Confirm:

  • The file has a .txt extension.
  • The object ID is present in the file name.
  • The file contains readable ER code or source content.
  • The file is not PDF, DOCX, or HTML.

Step 3: Run the TSD Generation Tool

Single file example:

python generate_tsd.py examples/tsd/DV920_R57M95921.txt

Folder example:

python generate_tsd.py examples/tsd output/

Folder example with skipped existing outputs:

python generate_tsd.py examples/tsd output/ --skip-existing

Recommended Method by Use Case

Use Case Recommended Extraction Method Required Output
Single object review FDA/RDA print-to-file .txt
Small TSD sample FDA/RDA print-to-file or Object Browser individual export .txt
Production TSD batch Object Browser batch export .txt
ESU comparison Object Browser batch export from PS920 and PD920 PS920_*.txt and PD920_*.txt
Large client conversion or retrofit analysis Object Browser batch export .txt

Troubleshooting

The Event Rules print output is missing recent changes

Possible cause:

  • The specifications were not saved before printing.

Recommended fix:

  1. Save the object specifications.
  2. Save recent Event Rules changes.
  3. Reopen or refresh the Event Rules editor if needed.
  4. Print the Event Rules again.

The output file is unreadable

Possible causes:

  • The wrong output destination was selected.
  • The output was generated as printer output instead of file output.
  • The file extension was changed to .txt, but the content is not actually text.

Recommended fix:

  • Use Destination > File in the Event Rules Printing dialog.
  • Re-export the ER code directly to a .txt file.
  • Open the output in Notepad or VS Code before processing.

The ESU comparison cannot find object pairs

Possible causes:

  • File names do not follow the expected naming convention.
  • The Pristine and Production files are in different folders.
  • The object IDs do not match exactly.
  • Timestamp suffixes were appended to the filenames.

Recommended fix:

Rename files using:

PS920_<OBJECTID>.txt
PD920_<OBJECTID>.txt

Place matched pairs in the same input directory.

Object Browser export creates HTML instead of text

Possible cause:

  • HTML was selected as the export format.

Recommended fix:

  • Re-run the export and select:
Output > Text

Advanced Get exported the wrong version

Possible causes:

  • The wrong path code was selected.
  • Local specifications were not overwritten.
  • The object was opened before the correct Advanced Get was completed.

Recommended fix:

  • Repeat Advanced Get from the correct path code.
  • Overwrite the local specifications when prompted.
  • Export immediately after retrieving the correct version.

Object Browser export does not include ER line numbers

Possible cause:

  • Show ER Line #s was not selected.

Recommended fix:

Re-run the export with:

[x] Show ER Line #s

Object Browser export does not show program flow clearly

Possible cause:

  • Show Logic Lines was not selected.

Recommended fix:

Re-run the export with:

[x] Show Logic Lines

Final Export Checklist

Before sending files to the JDE Reporting Platform, confirm:

  • Files are plain text files.
  • Files use the .txt extension.
  • PDF output was not used.
  • HTML output was not used as the source input.
  • FDA/RDA exports used Destination > File.
  • FDA/RDA exports were printed after specifications were saved.
  • Object Browser exports used Output > Text.
  • Object Browser exports included Export ER.
  • Object Browser exports included Show ER Line #s.
  • Object Browser exports included Show Logic Lines.
  • ESU comparison files are paired correctly.
  • Pristine files use the PS920_ prefix.
  • Production files use the PD920_ prefix.
  • Object IDs match exactly across paired files.
  • Files are stored in the correct input location.
  • Files contain readable JD Edwards ER code or source content.
Back to list