Skip Headers
JD Edwards EnterpriseOne Tools Translation Tools Guide
Release 8.98 Update 4

Part Number E14722-02
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

14 Understanding Jargon and Overrides

This chapter contains the following topic:

14.1 Overrides and Jargon

The use of overrides and jargon is the most complex aspect of translating Oracle's JD Edwards EnterpriseOne software. Jargon and overrides are features that apply to the Data Dictionary (DD), Form Design Aid (FDA), and Report Design Aid (RDA) translation tools.

Jargon and overrides tell the software what type of information should appear in certain situations. Developers apply jargon when modifying items within the data dictionary, and they apply overrides when modifying the descriptions that appear on forms.

You might see different text on a form if you run it from the Fast Path field instead of running it from a task.

Developers must define different field descriptions on the same form depending on how the programs are called. For example, program P1234 calls form W1234A, which has a field description abc. If another program calls form W1234A, for example P5678, then form W1234A displays this field description as xyz instead of abc. This table illustrates this concept:

Program Called Form Displayed Data Item
P1234 W1234A abc
P5678 W1234A xyz

According to programming standards, programmers must program jargon and overrides without using event rules (ER). Runtime engines run the ER. When you run a program from the Fast Path field, the runtime engines run this ER.

To understand jargon and overrides, you must first understand the data dictionary.