JD Edwards

EnterpriseOne
Tools

Development Guidelines for

Application Design Guide

9.2
JD Edwards EnterpriseOne Tools
Development Guidelines for Application Design Guide

9.2

Part Number: E53575-04

Copyright © 2011, 2022, Oracle and/or its affiliates.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected
by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate,
broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering,
disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report
them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then
the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or
activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or
accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the
applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display,
disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated
software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle computer
documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract. The
terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services. No other rights are
granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for
use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware
in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe
use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks
or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro
Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle
Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and
services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible
for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable
agreement between you and Oracle.
JD Edwards EnterpriseOne Tools
Development Guidelines for Application Design Guide

Contents

Preface .................................................................................................................................. i

1 Introduction to JD Edwards EnterpriseOne Tools Development Guidelines 1

for Application Design
Development Guidelines for Application Design Overview ................................................................................................... 1
Development Guidelines for Application Design Implementation Steps ............................................................................ 1

2 Understanding Application Development Guidelines 3

Interactive Application Fundamentals ....................................................................................................................................... 3
Batch Application Development Guidelines ............................................................................................................................. 7

3 Understanding JD Edwards EnterpriseOne Naming Conventions 11

JD Edwards EnterpriseOne Naming Conventions Overview ................................................................................................ 11
Data Dictionary Naming Conventions ..................................................................................................................................... 14
Processing Option Data Items ................................................................................................................................................... 16
Table I/O Handle Data Item ........................................................................................................................................................ 17
Object Naming Conventions ...................................................................................................................................................... 18
Section Names .............................................................................................................................................................................. 24
Purge Table Program ................................................................................................................................................................... 24
Naming Conventions ................................................................................................................................................................... 25

4 Understanding Tasks 31
Task Design .................................................................................................................................................................................... 31
Task Processing Options ............................................................................................................................................................. 31

5 Understanding Table I/O Guidelines 33

Table I/O Guidelines .................................................................................................................................................................... 33

6 Understanding Performance Considerations 35

Performance Considerations for All Forms ............................................................................................................................ 35
JD Edwards EnterpriseOne Tools
Development Guidelines for Application Design Guide

Performance Considerations for Browse Forms .................................................................................................................... 35

Performance Considerations for Header Detail and Headerless Detail Forms ............................................................... 36

7 Understanding Standard Event Rules Guidelines 37

Standard Event Rules Guidelines .............................................................................................................................................. 37

8 Understanding BI Publisher Report Guidelines 39

BI Publisher for JD Edwards EnterpriseOne Overview ........................................................................................................ 39
JD Edwards EnterpriseOne UBE and Report Definition Guidelines .................................................................................. 39
Oracle BI Publisher Layout Editor Guidelines ......................................................................................................................... 41
Translation Guidelines ................................................................................................................................................................. 57
XPath Usage .................................................................................................................................................................................. 58

9 Using Currency 59
Using Currency ............................................................................................................................................................................. 59

10 Understanding Translation Issues 65

Translation Issues ......................................................................................................................................................................... 65
Writing for Translation ................................................................................................................................................................ 65
Translation Coding Guidelines .................................................................................................................................................. 69
Translation Readiness Guidelines ............................................................................................................................................ 70
Actions that Trigger Translation ................................................................................................................................................ 71

11 Understanding Acronyms and Abbreviations 77

Acronyms and Abbreviations .................................................................................................................................................... 77

12 Understanding Field Sizes 121

Field Sizes ...................................................................................................................................................................................... 121

13 Glossary 125
activity rule ................................................................................................................................................................................... 125
add mode ...................................................................................................................................................................................... 125
BIP .................................................................................................................................................................................................. 125
jargon ............................................................................................................................................................................................. 125
JD Edwards EnterpriseOne Tools
Development Guidelines for Application Design Guide

media storage object ................................................................................................................................................................. 125

RTF ................................................................................................................................................................................................. 125
specification ................................................................................................................................................................................. 126
trigger ............................................................................................................................................................................................ 126
vocabulary override .................................................................................................................................................................... 126
XML ................................................................................................................................................................................................ 126
XMLP ............................................................................................................................................................................................. 126
XPath ............................................................................................................................................................................................. 126
XSL ................................................................................................................................................................................................. 127
Z table ............................................................................................................................................................................................ 127

Index ......................................................................................................................................................... 129

JD Edwards EnterpriseOne Tools
Development Guidelines for Application Design Guide
JD Edwards EnterpriseOne Tools Preface
Development Guidelines for Application Design Guide

Preface
Welcome to the JD Edwards EnterpriseOne documentation.

Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://
www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For
information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/
lookup?ctx=acc&id=trs if you are hearing impaired.

Related Information
For additional information about JD Edwards EnterpriseOne applications, features, content, and training, visit the JD
Edwards EnterpriseOne pages on the JD Edwards Resource Library located at:

http://learnjde.com

Conventions
The following text conventions are used in this document:

Convention Meaning

Bold Boldface type indicates graphical user interface elements associated with an action or terms defined in
text or the glossary.

Italics Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular
values.

Monospace Monospace type indicates commands within a paragraph, URLs, code examples, text that appears on a
screen, or text that you enter.

> Oracle by Example Indicates a link to an Oracle by Example (OBE). OBEs provide hands-on, step- by-step instructions,
including screen captures that guide you through a process using your own environment. Access to
OBEs requires a valid Oracle account.

i
JD Edwards EnterpriseOne Tools Preface
Development Guidelines for Application Design Guide

ii
JD Edwards EnterpriseOne Tools Chapter 1
Development Guidelines for Application Design Guide Introduction to JD Edwards EnterpriseOne Tools
Development Guidelines for Application Design

1 Introduction to JD Edwards EnterpriseOne

Tools Development Guidelines for Application
Design
Development Guidelines for Application Design
Overview
This guide contains guidelines for application design when creating or modifying JD Edwards EnterpriseOne interactive
and batch applications using Form Design Aid (FDA) or Report Design Aid (RDA).

Development Guidelines for Application Design

Implementation Steps
Before you create or modify EnterpriseOne interactive or batch applications, make sure that you have already performed
the following configuration tasks:
• Configure Object Management Workbench.
See "Configuring JD Edwards EnterpriseOne OMW " in the JD Edwards EnterpriseOne Tools Object
Management Workbench Guide .
• Configure Object Management Workbench user roles and allowed actions.
See "Configuring User Roles and Allowed Actions" in the JD Edwards EnterpriseOne Tools Security
Administration Guide .
• Configure Object Management Workbench functions.
See "Configuring JD Edwards EnterpriseOne OMW Functions" in the JD Edwards EnterpriseOne Tools Object
Management Workbench Guide .
• Configure Object Management Workbench activity rules.
See "Configuring Activity Rules" in the JD Edwards EnterpriseOne Tools Object Management Workbench Guide
.
• Configure Object Management Workbench save locations.
See "Configuring Object Save Locations" in the JD Edwards EnterpriseOne Tools Object Management
Workbench Guide .
• Set up default location and printers.
See "Set Up Default Location and Printers" in the JD Edwards EnterpriseOne Tools Report Printing
Administration Technologies Guide .

1
JD Edwards EnterpriseOne Tools Chapter 1
Development Guidelines for Application Design Guide Introduction to JD Edwards EnterpriseOne Tools
Development Guidelines for Application Design

2
JD Edwards EnterpriseOne Tools Chapter 2
Development Guidelines for Application Design Guide Understanding Application Development Guidelines

2 Understanding Application Development

Guidelines

Interactive Application Fundamentals

This section discusses:
• Interactive application guidelines overview.
• Guidelines to use when developing interactive application forms.
JD Edwards EnterpriseOne developers should follow the standards contained in this document when creating JD
Edwards EnterpriseOne applications. These guidelines are intended primarily for JD Edwards EnterpriseOne developers
and quality assurance analysts to ensure that applications comply with the standards.

Interactive Application Guidelines Overview

These guidelines provide standards for issues such as:
• Column title formats
• Report headers
• Currency
• Tab sequence
• Font defaults
The interactive application guidelines provide design standards for the appearance and function of the controls that
developers use in interactive applications. A control is an object on a form that enables the user to interact with an
application.

While many of these standards apply to all form types, separate guidelines contain specific standards for each particular
form type. Where appropriate, the guidelines also include industry-specific instructions, such as one set of instructions
for manufacturing and distribution applications, and another set of instructions for financial applications.

Guidelines for Interactive Application Forms

When you are developing any interactive application form, you should ensure that:
• Static text fields and grid column titles have enough space allocated to allow for translations.
In general, an increase of 30 percent in the size of a static text field provides adequate room for translated text.
Therefore, the text for many static text fields must not occupy more than 70 percent of the field. These are
general guidelines only; to provide ample space for an increase in the number of characters during translation
any static text field on a form should be stretched to the maximum.
Refer to this table for guidelines about how much you must increase a static text field based on the number of
characters of English text:

3
JD Edwards EnterpriseOne Tools Chapter 2
Development Guidelines for Application Design Guide Understanding Application Development Guidelines

Number of English Characters Additional Space Required

1 character 400 percent or 4 characters

2—10 characters 101—200 percent

11—20 characters 81—100 percent

21—30 characters 61—80 percent

31—70 characters 31—40 percent

More than 70 characters 30 percent

• Help information is available for all input-capable fields. You can use data dictionary glossaries to define the
help information.
• A Visual Assist is available for search and UDC fields
• Tab sequences have these characteristics:

◦ Within an application, form tabs are ordered in a logical sequence.

Ensure that the physical order of the tabs is the same as the tab sequence so that the cursor does not
skip fields when the user presses the Tab key.
◦ Within a form, the tab sequence applies to each group box.
When a group box contains two or more columns, the tab sequence should move down the left-most
column of controls and then down the column to the right.
◦ The grid is a tab stop.
◦ In Add mode, the tab sequence begins with the key fields.
◦ In Change mode, the tab sequence begins with the first unprotected field.
Note: If related controls appear side-by-side in different columns, then either create a tab sequence
that moves across the row or rearrange the order of the fields.

Form Guidelines
When developing forms in interactive applications, ensure that you:
• Do not preload a next number.
• Use any of these actions to prevent a user from accessing a form or row exit:

◦ Disable the exit.

◦ Set an error.

4
JD Edwards EnterpriseOne Tools Chapter 2
Development Guidelines for Application Design Guide Understanding Application Development Guidelines

• You use the four-digit data item Fiscal Year (FYR) for a fiscal year filter.
• You use an alpha field to display the fiscal year on a form so that you can distinguish between blank and zero.
When you enter a two-digit mathematical numeric fiscal year on a form, it appears as a single digit for years
zero through nine, and users might not be able to differentiate between a blank and a zero. Use the display field
FYOW for the fiscal year and include this logic:
IF not blank convert FYOW to FY

• You use an asterisk (*) as the default value for Subledger and blank as the default value for Subledger Type,
when you use Subledger and Subledger Types as filter fields.
• You use a text variable rather than a hard-coded text string to load a field or variable. Text variables can be
translated, but hard-coded text cannot.
• You verify:
◦ That grid totals sum only data that is the same date type.
For example, do not sum different currencies or values with different decimal points.
◦ That totals for a form level are generally within the group box that surrounds the grid.

Financials Forms for Interactive Applications

Use these guidelines when developing any form type within a financials application:
• On all forms on which an address book number appears, use Long Address Number, data item ALKY, rather
than Address Book Number, data item AN8, because ALKY allows 20 characters for input.
If necessary, use ALKY to call AN8 for information. Address number controls that are input-capable must accept
an alternate number as input. The symbols in the Address Book Constants determine the default address book
number. Use the business function B0100016, Scrub Address Number, to accomplish this.
• If you enter an asset number in an unknown format, such as ASCII, the system returns the number as the
primary asset number, which is determined by the symbols in the Fixed Asset Constants.
Use the business function X1202-F1201, Validate Asset Number, to accomplish this.

Workforce Management Forms

When developing all form types within workforce management applications.

Ensure that:
• You rename Address Book Number (AN8) to Employee Number or Employee No.
• You do not use associated descriptions for job type and job step.
Retrieve the description for job type/step from the Job Information table (F08001).

Manufacturing and Distribution Forms

Use these guidelines when developing all form types within a manufacturing or distribution application.

Ensure that:
• You place the Branch/Plant identifier in the upper-right corner.
• You use Branch/Plant identifier as the static text for MCU or MMCU, as appropriate.

5
JD Edwards EnterpriseOne Tools Chapter 2
Development Guidelines for Application Design Guide Understanding Application Development Guidelines

• If you enter an item number in an unknown format, such as UITM, ensure that the number returns in the same
format in which you entered it.

Localization Forms
Use these guidelines when developing any form types used within localization applications.

Ensure that:
• The form and row exits to localization requirements from the base application are labeled Regional Info.
• The message box displays the text Regional Information not available for User Preferences when the Country
System field is blank.

Find/Browse Forms with Currency Controls

Use these guidelines when developing Find/Browse forms that use currency controls.

Ensure that:
• Both domestic and foreign amounts, when both are available, are included in the grid.
• If all records in the grid reflect the same currency, then the currency code, exchange rate, and base currency
appear in the header portion of the form.
• If the records potentially have different currency codes, exchange rates, or base currencies, then this
information appears in the grid.
• Columns containing more than one currency have no totals.
Suppress total records, if necessary.
• All currency-related controls and grid columns are hidden (for Dialog is Initialized) when currency processing is
turned off.
To hide the currency-related fields, test the system value for Currency Processing for N.
• Currency Mode (CRRM) does not appear on the Find/Browse form because both foreign and domestic
currencies appear.
• If amounts are applicable to the main portion of the grid, then the domestic amount and currency code appear.
The foreign amounts might exist in the scroll-to grid area.

Note: If you need to include the Base Currency field (the currency that is defined at the company level) in
the QBE row or as a filter field, then consider joining the transaction table to the Company Constants table
(F0010). This join provides direct database access to the Base Currency field, which can be used in the QBE.

Interactive Application Forms with Currency Controls

Use these guidelines when developing any form type that uses currency controls.

Ensure that:
• Currency controls appear directly above the grid in this sequence:

◦ Currency (CRDC)
◦ Exchange (CRR)
◦ Rate Base (CRCD)

6
JD Edwards EnterpriseOne Tools Chapter 2
Development Guidelines for Application Design Guide Understanding Application Development Guidelines

◦ Foreign Option

• Currency fields hold at least 18 digits.

Batch Application Development Guidelines

This section discuses:

• Standards set up automatically by the tool set.

• Report appearance.
• Reports to view.
• Reports to print.
• Reports to file.
• Reports that contain currency.
• Error listings.
You should follow the batch application guidelines when you create a new report or batch application for JD Edwards
EnterpriseOne software. These guidelines assist you with various issues such as presentation of totals and grand totals,
use of error messages and job status messages, placement of any required content for report headers, and use of cover
pages.

Standards Set Up Automatically by the Tool Set

When you create a new report or batch application, the system automatically applies certain standards for you. While
you can change many of the settings, to do so violates design standards for batch applications. This table describes the
standards automatically set by the JD Edwards EnterpriseOne development toolset:

Object Standards

Font 7 point, Arial, regular font.

Report name Appears in the upper-left corner.

Actual run date and run time values Appears on the right side of the first and second lines.

Label Page, followed by the page number Appears in the upper-right corner.

Report titles Centered in the report header.

Company name Appears on the first line of the report title.

7
JD Edwards EnterpriseOne Tools Chapter 2
Development Guidelines for Application Design Guide Understanding Application Development Guidelines

Report Appearance
Use these guidelines for the appearance of the report.

Ensure that you:

• Include space between columns.

The default space between columns is five characters.

• Use landscape orientation for the report.
• Set up the report to run on laser printers.
• Set up the report to use a paper size of 8 1/2 x 11 (standard size in the U.S.), unless you are processing a special
form.
• Underline and center column headings for the width of the column.
• Overline total amounts with a single line.
• Use a single overline and a double underline for a grand total.
• Align total amounts directly beneath the amount fields to which they apply.
• Do not include page footers or report footers in a standard JD Edwards EnterpriseOne report.

Reports to View
Use these guidelines when developing reports for end-user viewing.

Ensure that you:

• Base the level 1 section of the report on a business view that contains all columns in the table to enable data
selection over any column from the table.
• Group a Level 1 section and all of its associated sections together.
• Locate these conditional sections at the bottom:

◦ Conditional sections that are not called.

◦ Conditional sections that are associated with more than one level 1 section.

• Use a group section for processing that does not produce printable output.

You define those section properties as invisible and conditional.

• Use constants to place comments in sections that are invisible or that appear in conditional sections that are
not called.

These comments can appear in report viewing. A constant that contains the section name and description is a
standard comment in these sections.
• The report variables in an invisible section are listed when you select the Report View tab.

A section does not appear in the report output when the Visible option is turned off in the Section Properties.

8
JD Edwards EnterpriseOne Tools Chapter 2
Development Guidelines for Application Design Guide Understanding Application Development Guidelines

Reports to Print
Use these guidelines when developing reports that generate output to print.

Ensure that:

• The page header is located at the top.

• Demo versions of a report should not be set to print a cover page.
• For an error report that prints only errors, when no errors exist, the report header prints, followed by a
confirmation line that states No Errors.
• For reports that do not generate any output, notes, or error messages, a message that indicates whether the
batch job completed successfully is sent to the originator.

Use the send message system function to send this message. You can use a template message to provide as
much information as possible about why the job was unsuccessful, as well as to indicate the job to which the
message pertains.

Reports to File
When developing reports that generate output to file, ensure that batch programs do not contain a standard page
header section.

Reports that Contain Currency Amounts

Use these guidelines when developing reports that contain currency amounts.

Ensure that:

• The columns for currency amount fields are 21 spaces wide, where possible.
• You do not display totals for amounts that represent different currencies.

Error Listings
If you create a processing option that gives users a choice about where errors are listed, use these design guidelines.

Ensure that you:

• Provide the option to list errors either in the Work Center or in the report.

Errors may not appear in both locations.

• Use this format to list errors in the report:

085X--This record is not correct.

9
JD Edwards EnterpriseOne Tools Chapter 2
Development Guidelines for Application Design Guide Understanding Application Development Guidelines

• Do not repeat errors, and ensure that they appear in a logical order, especially when Parent/Child relationships
are involved.
• Do not stop processing for warning-type error messages.

Error-type messages should stop processing.

10
JD Edwards EnterpriseOne Tools Chapter 3
Development Guidelines for Application Design Guide Understanding JD Edwards EnterpriseOne Naming
Conventions

3 Understanding JD Edwards EnterpriseOne

Naming Conventions

JD Edwards EnterpriseOne Naming Conventions

Overview
A JD Edwards EnterpriseOne application is composed of multiple objects. When you create a new object, you must
name the object and provide a description. Naming conventions provide a standard for each object type that you can
create.

You may further define the characteristics within the object. For example, when you create a table, you may designate a
key that consists of more than one field within that table. When you create the index of the table, you should follow the
standard for naming that index.

To provide consistency for developers and users, all JD Edwards EnterpriseOne objects follow standard naming
conventions. The naming conventions require that each object, such as a table, report, interactive application, or menu,
has a unique name. The naming conventions help you identify types of objects and prevent users from creating objects
with duplicate names.

Naming Conventions for Objects

This diagram illustrates naming conventions for objects:

11
JD Edwards EnterpriseOne Tools Chapter 3
Development Guidelines for Application Design Guide Understanding JD Edwards EnterpriseOne Naming
Conventions

System Codes
The system code is included in an object name. For a complete list of JD Edwards EnterpriseOne system codes, see UDC
table 98/SY.

12
JD Edwards EnterpriseOne Tools Chapter 3
Development Guidelines for Application Design Guide Understanding JD Edwards EnterpriseOne Naming
Conventions
If you are performing JD Edwards EnterpriseOne custom work, use system codes 55 and 60-69.

Example: Program and File Names

This diagram illustrates examples of the naming conventions for tables, forms, and applications:

Text Overrides and Jargon

JD Edwards EnterpriseOne provides several options for overriding text in forms and reports to enable different terms
and languages. However, you should be aware of these restrictions when you decide how to override text and use
jargon:

• You can use jargon in the data dictionary to override text for the entire system, but if the text is overridden
again in Form Design Aid (FDA) or Report Design Aid (RDA), then jargon terms do not appear.

13
JD Edwards EnterpriseOne Tools Chapter 3
Development Guidelines for Application Design Guide Understanding JD Edwards EnterpriseOne Naming
Conventions
• You can use text variables to present different text strings under different conditions; but test all valid cases to
ensure that you have allowed enough space on the form or report for translation.

Data Dictionary Naming Conventions

This section discusses:
• Data item alias
• Data item name
• Data item description
• Row description
You must adhere to data dictionary naming conventions to ensure database integrity and prevent data items from being
overwritten by other data items.

Data Item Alias

A data item alias is five or more alpha characters in length. The software uses the data item alias when searching within
database routines (for example, application program interfaces (APIs) used in business functions) and within Table
Design Aid when you create a table. For each table that you create, a prefix is added to the alias, which makes it unique
to this table. For example, the alias ABMCU indicates that the data item MCU is used within the Address Book (AB)
applications. You can also identify a data item by the data item name or alpha description.

Note: After you add a data item, you cannot change its name or alias.

When assigning an alias, do not:

• Begin the alias with the characters TIP or TERM.
Aliases that begin with TIP are reserved for JD Edwards EnterpriseOne tips information; aliases that begin with
TERM are reserved for term glossaries.
• Use blanks or special characters such as %, &, ,, ., and +.
Neither blanks nor these characters are allowed as part of a data item alias in JD Edwards EnterpriseOne
software.

Alias for an External Data Dictionary Item

An external data dictionary item is one that is created by a developer outside of JD Edwards EnterpriseOne for use in
JD Edwards EnterpriseOne software. When you create an external data item, you must use a Y or Z in the first character
of the data item name to distinguish an external data dictionary item from a JD Edwards EnterpriseOne data dictionary
item.

For external data items, the data dictionary alias can be a maximum of eight alphanumeric characters and adheres to
this format:

Ysssdddd, where:

Y or Z = The first digit of any JD Edwards EnterpriseOne system-assigned external system code. This character indicates
that the data dictionary item is external.

14
JD Edwards EnterpriseOne Tools Chapter 3
Development Guidelines for Application Design Guide Understanding JD Edwards EnterpriseOne Naming
Conventions
sss = The system code number, which is 55x-59x for enterprise-level development of new modules, or 60x-69x for
custom development of a JD Edwards EnterpriseOne system.

dddd = The name of the data item.

Data Item Name

A data item name is a 32-character, alphabetic field that identifies and defines a data item. You must leave enough room
in the field name for a 30 percent expansion of the English text for translation. You can also identify a data item by its
alias or alpha description.

The data item name forms the C data name (for example AddressNumber) that you use in business functions, data
structures, and event rules.

Note: After you add a data item, you cannot change its name or alias.

Do not use blanks or special characters such as %, &, ,, ., and +. Neither blanks nor these characters are allowed as part
of a data item alias in JD Edwards EnterpriseOne software.

Data Item Name for an External Data Dictionary Item

When you create an external data item, you must use a Y or Z in the first character of the data item name to distinguish
an external data dictionary item from a JD Edwards EnterpriseOne data dictionary item.

The data item name can be a maximum of 32 alphanumeric characters, and adheres to this format:

Ysssdddddddddddddddddddddddddddd, where:

Y or Z = The first digit of any JD Edwards EnterpriseOne system-assigned external system code. This character indicates
that the data dictionary item is external.

sss = The system code number, which is 55x-59x for enterprise-level development of new modules, or 60x-69x for
custom development of a JD Edwards EnterpriseOne system.

ddddddddddddddddddddddddddddd = The name of the data item.

Data Item Description

The data item description categorizes a data item so that you can search for it in the JD Edwards EnterpriseOne Data
Dictionary. When you create a new data item, provide a description using these conventions, depending on the data
item type:

Data Item Data Item Description Convention

Address Number Begin all address numbers, such as employee, customer, owner, with Address Number.

15
JD Edwards EnterpriseOne Tools Chapter 3
Development Guidelines for Application Design Guide Understanding JD Edwards EnterpriseOne Naming
Conventions

Data Item Data Item Description Convention

Amount Begin all unit, quantity, and volume fields with Amount.

Code Begin all code fields with Code.

Date Begin all date fields with Date.

Factor Begin all factor fields with Factor.

Name Begin all 30-byte description fields with Name.

Prompt Begin all Y/N prompting fields with Prompt.

Units Begin all units, quantity, and volume fields with Units.

Row Description
Provide a description that appears for the field description on forms and reports. English text must leave room for an
expansion of 30 percent for translation.

Processing Option Data Items

You use processing options with interactive and batch applications to enable users to supply parameters that direct the
functions of an application. For example, processing options enable you to specify default values for certain fields on
forms, control the format in which information prints on reports, change the way in which a form displays information,
and activate additional logic. Users access processing options from a processing option tab form. A processing option
tab form can contain one or more processing option fields.

You define processing option fields in the data dictionary, similar to other data dictionary items. Each processing option
field can also have special, defined help information. This help information is displayed when the end user presses F1
when the focus is on a processing option item. You define the help text using a separate data item called help data
dictionary item.

Glossary Group for Processing Options

Use the H glossary group when you add the help data dictionary item for a processing option.

16
JD Edwards EnterpriseOne Tools Chapter 3
Development Guidelines for Application Design Guide Understanding JD Edwards EnterpriseOne Naming
Conventions

Data Item Name for Processing Option Help Item

You must create a separate alias for each processing option help item (F1 data item text) for each application or report.
You can share similar text, if applicable, but each processing option must have a unique alias. The naming convention
for a processing option help item is as follows:

Syyyyyzz, where:

S = Processing option

yyyyy = The program number

zz = A sequential number

For example, for report R12855, the first processing option data item is S1285501.

Processing Option Glossary Description

After you name a processing option data item, you must specify a glossary description. Follow these guidelines when
you enter the glossary description for a processing option data item:

• Use the same text for the data item description field as the processing option title on the processing option tab
form.
• Capitalize the first letter of each word, such as G/L Date (alias GLD in the data dictionary).
• Leave room for translation of the description by using only 70 percent of the allowed character space.

This technique allows for up to 30 percent expansion in translation.

• Number the processing option on the tab on which the processing option data item is used, but never refer to a
processing option by its number in the description in the data dictionary.

Note: You must enter a glossary. Do not simply enter a period in the Description field.

Table I/O Handle Data Item

In table Input/Output (I/O) statements you can use a special type of data dictionary items, called handle items, to
represent the table that you need to access. The data item name can be a maximum of eight characters and should be
formatted as HFxxxxxx, where:

H = A table handle data item.

Fxxxxxx = The name of the table.

For example, the table handle data item name for table F4211 is HF4211.

17
JD Edwards EnterpriseOne Tools Chapter 3
Development Guidelines for Application Design Guide Understanding JD Edwards EnterpriseOne Naming
Conventions

Object Naming Conventions

Object naming conventions provide a methodology for identifying object names used in applications. An interactive
application, batch application, or report consists of multiple objects, such as a table, business view, form, and event
rules. Before you can begin to create an interactive application, batch application, or report, you must add the objects
required for the application.

This section discusses:

• Tables
• Business Views
• Processing Options
• Versions
• Interactive Applications
• Batch Applications
• Embedded BI Publisher Naming Conventions

Tables
The Object Management Workbench (OMW) name for a table can be a maximum of eight characters. It is recommended
that you format it asFxxxxyyy, where:

F = data table

xx (second and third digits) = the system code, such as:

00 - Foundation environment

01 - Address Book

03 - Accounts Receivable

xx (fourth and fifth digits) = the group type, such as:

01 - Master

02 - Balance

1X - Transaction

yyy (sixth through eighth digits) = object version, such as programs that perform similar functions but vary distinctly in
specific processing, such as:

JA through JZ - Table join

You provide up to a 60-character description for a table.

The table description is the topic of the table. If the table came from the IBM i , it should be the same name as the file it
represents, such as Address Book Master (F0101) or Item Master (F4101).

However, for a work table, make sure to include the name Work Table in the descriptions and insert UI after the system
code; for example, Organization Structure Report Work Table (F10UI005).

18
JD Edwards EnterpriseOne Tools Chapter 3
Development Guidelines for Application Design Guide Understanding JD Edwards EnterpriseOne Naming
Conventions
Another consideration is Z tables. Z tables are used for importing data from another system as well as used in batch
processes. When you name a Z table, ensure that the letter Z is the sixth digit; for example, Address Book - Batch File
(F0101Z1).

Data Item Prefix

In a JD Edwards EnterpriseOne table, a data item represents a column in a table. The Table Design Aid tool assigns a
table column prefix to each column. The column prefix that is assigned to the table does not have to be unique. For
example, table F0101 has a column prefix AB, and AN8 (Address Number) is a data item AB in that table. The system
references AN8 as F0101_ABAN8. If another table, F740101, uses AN8 and the same prefix AB, the system references
that column as F740101_ABAN8, so that it is unique, as well.

Adding a Table
Before adding a new table, determine whether an existing table contains the data items required by the application. If an
existing table does not exist, you must add a new table.

When you add a new table, you must include these audit trail columns:

• User ID (USER)
• Program ID (PID)
• Machine Key (MKEY)
• Date Updated (UPMJ)
• Time of Day (UPMT)

Indices
Name the index with the key fields in the index.

If there is only one field in the index, list the field as the index name, such as Address Number.

If the index has two fields, list them consecutively, such as Address Number, Line Number ID.

The total length of the index name cannot exceed 19 characters. If you have more than two key fields in the index, name
the index carefully, so that it does not exceed 19 characters. If you exceed 19 characters, the table may not be generated,
and any business functions the use the table may not compile.

Do not use special characters or C reserved words, such as "+" in the index name.

External Developer Considerations for Tables

External development is the process by which developers who work for outside organizations, such as consultants,
create custom applications for specific clients. You must use caution when you name a table so that you can distinguish
between objects created by JD Edwards EnterpriseOne developers and non-JD Edwards EnterpriseOne developers.
When you create a new table, use the naming convention Fxxxxyyy, where:

F = A data table

xxxx = The system code applicable to the enterprise

yyy = A unique next number or character pattern unique within the enterprise

19
JD Edwards EnterpriseOne Tools Chapter 3
Development Guidelines for Application Design Guide Understanding JD Edwards EnterpriseOne Naming
Conventions

Business Views
The OMW name for a business view can be a maximum of eight characters and should be formatted as VzzzzzzA,
where:

V = Business view.

zzzzzz = The characters of the primary table.

A = The letter that indicates the view. For example, V0101A is the first view of the table F0101; V0101B is the second view
of the same table.

Ensure that you provide up to a 60-character description for a business view. The description should reflect the
application description followed by the form type, such as Item Master Browse and Item Master Revisions.

The primary, unique, key fields should remain in the business view. Do not reorganize the primary, unique, key fields.

Note: Each table should have only one business view that includes all columns. Use this business view for the level 01
section in all reports that are based on the table. Also, only one business view is enabled for each form type, except for
Header/Detail forms. For Header/Detail forms, you can select two business views, one for the header portion of the
form and one for the detail portion of the form.

Joined Views
To format the name for joined views, use the names of the two tables that you are joining and separate them with a
forward slash. Ensure that you place the primary table first.

For example, if F4101 is the primary table in the joined view between F4101 and F4102, use the name F4101/F4102.

External Developer Considerations for Business Views

External development is the process by which developers who work for organizations other than Oracle, such as
consultants, create custom applications for specific clients. You must use caution when you name a business view so
that you can distinguish between JD Edwards EnterpriseOne objects and non-JD Edwards EnterpriseOne objects. When
you create a new business view for a standard JD Edwards EnterpriseOne table, use the naming convention Vssss9999,
where:

V = Business view.

ssss = The system code for the enterprise.

9999 = A next number or character pattern that is unique within the enterprise.

Processing Options
This section discusses the elements of processing options.

20
JD Edwards EnterpriseOne Tools Chapter 3
Development Guidelines for Application Design Guide Understanding JD Edwards EnterpriseOne Naming
Conventions

Processing Option Data Structure

The OMW name for a processing option data structure can be a maximum of 10 characters and should be formatted as
Txxxxxyyyy where:

T = Processing option data structure

xxxxxyyyy = The program number for the application or report

Versions
When you create a new version, provide a description of the version. The description should indicate what the report
does and how to set the processing options for the version. The description may be up to 60 characters long.

XJDE versions are used for demo purposes and are typically batch applications. When called from a menu, batch
applications display the versions list so that clients can create production versions. During an installation, JD Edwards
EnterpriseOne will overwrite XJDE versions.

ZJDE versions are used for default purposes and are typically interactive applications, or they are called from another
application. You usually attach these versions to a menu. Customers can set these versions. When called from a menu,
interactive applications with a version are called with a blind execution based on predetermined processing option
values. During an installation JD Edwards EnterpriseOne will not overwrite ZJDE processing option data.

Note:
• "Creating Data Structures" in the JD Edwards EnterpriseOne Tools Data Structure Design Guide .

Interactive Applications
The OMW name for an application can be a maximum of eight characters. Although the software accepts up to 10
characters, if you enter more than eight characters the entry will be truncated. Format the name as Pxxxxyyy, where:

P = Application

xxxx = The system code

yyy = A next number, such as 001 and 002

Ensure that you provide a description of up to 60 characters. The description should reflect the subject of the forms
within the application; for example, Companies and Constants.

Naming Conventions for Forms

Form Design Aid automatically assigns a name to the form using the format WzzzzzzzzA, where:

W = Form.

zzzzzzzz = The application name.

A = The first form created in the application. It is usually, but not always, the entry point to the application. Subsequent
forms are assigned sequential letters, such as B for the second form, C for the third form, and so on.

21
JD Edwards EnterpriseOne Tools Chapter 3
Development Guidelines for Application Design Guide Understanding JD Edwards EnterpriseOne Naming
Conventions
Ensure that you provide a form description that is based on the form type. This table provides examples of form
descriptions:

Form Type Form Description

Find/Browse The words Work With followed by the subject of the application, such as Work With Companies or Work
With Constants.

Fix/Inspect, Header/Detail, and A title that reflects the topic of the form, such as Supplier Information, Item Master Revisions, or
Headerless/Detail Purchase Order Entry.

Lower-Level Windows A title that reflects the topic of the window, with the title of the calling form appended to it, such as
Enter Voucher - G/L Distribution. When the title of a window includes a verb, use an active verb, not a
nominalization; such as Work With Vouchers.

Form Interconnection Data Structures

The JD Edwards EnterpriseOne toolset automatically creates form interconnection data structures using the key fields in
the business view.

You can change the data item name and description to describe the item that is passed between forms.

Because Message forms do not have Business Views, you must manually create the form interconnect data structure.

Note:
• "Working with Forms" in the JD Edwards EnterpriseOne Tools Form Design Aid Guide .

Batch Applications
Object naming conventions ensure consistency and make batch applications easier to identify and locate. For batch
applications, the name can be a maximum of eight characters and should be formatted as Rxxyyyyy, such as R09800,
R30440, and so on, where:

R = Batch (report) application

xx = System code

yyyyy = For these digits, follow the same naming convention as you use on IBM i .

The Function Use field follows the same naming standards as IBM i, such as:

130-139 = Batch Processes

160-169 = Reports

Report Category Codes follow the same standards as the Form Design standards.

22
JD Edwards EnterpriseOne Tools Chapter 3
Development Guidelines for Application Design Guide Understanding JD Edwards EnterpriseOne Naming
Conventions

Embedded BI Publisher Naming Conventions

JD Edwards EnterpriseOne Object naming conventions ensure consistency and make report templates and report
definitions for JD Edwards EnterpriseOne embedded BI Publisher reports easier to identify and locate.

See BI Publisher for JD Edwards EnterpriseOne Overview for more information about JD Edwards EnterpriseOne
integrations with Oracle BI Publisher.

Template Names
Templates are required to format JD Edwards EnterpriseOne Embedded BI Publisher reports, translations, and
transformations. The template uses data that resides in the JD Edwards EnterpriseOne database.

See "Templates" in the JD Edwards EnterpriseOne Tools BI Publisher for JD Edwards EnterpriseOne Guide

After you design a template, you must upload it to JD Edwards EnterpriseOne to create a template object. The
template name should be the same as the template object name. A template object is required as part of a JD Edwards
EnterpriseOne report definition.

Template object names in OMW can be a maximum of 100 characters and should be formatted as TPwwwxxxxyyzz,
such as TP743005TR1 where:

TP = Template for JD Edwards EnterpriseOne Embedded BI Publisher

www = Two or three characters for the system code

xxxx = Three to four characters to identify the associated UBE. For example, use 3005 if the source UBE is R743005.

yy = Template type. The template types are:

BI Publisher Object BI Publisher Object Type File Type

Templates TE .rtf

- TL .xls

- TP .pdf

- TR .rtf

- TS .xsl

Translation template XL .xml or .xlf

Transformation template XF .xsl

zz = A sequentially assigned number to identify the different outputs associated with the same UBE. For example,
TP743005TR1 and TP743005TR2 could produce different .rtf outputs, whereas TP743005TS1 could produce .xsl output.

23
JD Edwards EnterpriseOne Tools Chapter 3
Development Guidelines for Application Design Guide Understanding JD Edwards EnterpriseOne Naming
Conventions

Report Definitions
JD Edwards EnterpriseOne report definitions specify the information that BI Publisher requires to process and deliver BI
Publisher output.

See "Creating JD Edwards EnterpriseOne BI Publisher Report Definitions" in the JD Edwards EnterpriseOne Tools BI
Publisher for JD Edwards EnterpriseOne Guide

Report definition names can be a maximum of 10 characters and should be formatted as RDwwwxxxxyy, such as
RD743005A where:

RD = Report definition template

www = Three characters for the system code

xxxx = Three to four characters to identify the associated UBE. For example, use 3002 if the source UBE is R743005)

yy = One to two sequential characters to identify the different report definitions associated with the same UBE, for
example RD743005A and RD753005B.

Section Names
A section name within a report can be a maximum of 10 characters and should be formatted as SzzzzzzzzA, such as
S09800A, S30440B, and so on, where:

S = Report section name

zzzzzzzz = Program name

A = A sequentially assigned letter

The tool set uses next numbers to automatically assign section names. Examples include S1, S2, S3, and so on.

The section description should include the section type, such as Batch Total Section, Payment Level Break Header
Section.

Sections should be logically arranged in report rendering.

Purge Table Program

The Table Conversion-Batch Delete program is the generic purge program in JD Edwards EnterpriseOne that removes
selected records from a table and stores the data in a backup file. To use this batch program, you must first create a
table conversion in the OMW, rather than a new version, for the table that you want to purge.

The purge table conversion name can be a maximum of eight characters and should be formatted as Pxxxxxxp, where:

P = The purge table

xxxxxxp = The table (file) name

24
JD Edwards EnterpriseOne Tools Chapter 3
Development Guidelines for Application Design Guide Understanding JD Edwards EnterpriseOne Naming
Conventions
Note:
• See "Section Processing" in the JD Edwards EnterpriseOne Tools Report Design Aid Guide .
• See "Report Sections" in the JD Edwards EnterpriseOne Tools Report Design Aid Guide .
• See "Creating Batch Versions in the JD Edwards EnterpriseOne Tools Report Design Aid Guide .

Naming Conventions
This section discusses naming conventions for:

• Event rule variables

• Business functions
• Workflow processes
• Media objects
• Menus
• Table conversions

Event Rule Variable Names

Event Rule variables are named similarly to C variables and should be formatted as xxx_yyzzzzzz_AAAA, where:

xxx = A prefix that varies depending on the scope. The system automatically assigns the prefix, such as:

frm_ (form scope)

evt_ (event scope)

yy = Hungarian Notation for C variables, including:

c - Character

h - Handle Request

mn - Math Numeric

sz - String

jd - Julian Date

id - Pointer

zzzzzz = A programmer-supplied variable name. Capitalize the first letter of each word.

AAAA = The data dictionary alias (all upper case).

For example, a branch/plant event rule variable would be evt_szBranchPlant_MCU. Do not include any spaces.

25
JD Edwards EnterpriseOne Tools Chapter 3
Development Guidelines for Application Design Guide Understanding JD Edwards EnterpriseOne Naming
Conventions

Text Variables
The system automatically assigns a name using the format TVzzzzzzzz, where:

TV = Text Variable

zzzzzzzz = Programmer-supplied variable name

Note:
• "Working with Event Rules Design" in the JD Edwards EnterpriseOne Tools Event Rules Guide .

Business Functions
The source code for business functions should be formatted as Bxxxyyyy or Nxxxyyyy, where:

B = C Business function (for example, B3101260)

N = Named Event Rule (NER) Business function (for example, N0400121)

xxx = The system code

yyyy = A next number (the numbering assignments follow current procedures in the respective application groups)

Note: To preserve the data structure or D names, the next numbering for business functions and named event rules
should not be shared.

Business Function Data Structures

The data structure for business function event rules and business functions should be formatted as DxxxyyyyyA, where:

D = The data structure.

xxx = The system code

yyyy = A next number (the numbering assignments follow current procedures in the respective application groups)

A = An alphabetical character, such as A, B, C, and so on, that you include at the end of the data structure name when
multiple data structures exist for a function. For example, the data structures for business function B3101260 are
D3101260A, D3101260B, D3101260C.

The data element in the data structure should use Hungarian Notation, with the data item alias appended. For example,
if the alias for a data structure element is LANO, its name would be mnSite_LANO.

When you add parameters to an existing data structure, add the new parameters at the bottom of the list. Also, do not
resequence an existing data structure. Resequencing and adding parameters to the middle of the data structure might
cause a runtime memory error.

26
JD Edwards EnterpriseOne Tools Chapter 3
Development Guidelines for Application Design Guide Understanding JD Edwards EnterpriseOne Naming
Conventions
Note:
• "Creating Data Structures", "Creating Business Function Data Structures" in the JD Edwards EnterpriseOne
Tools Data Structure Design Guide .
• "Using Business Functions" in the JD Edwards EnterpriseOne Tools APIs and Business Functions Guide .

Workflow Processes
The name for a workflow process can include up to 10 characters and should be formatted as Kxxxxyyyyy, where:

K = A Workflow process

xxxx = A system code that be up to four digits (use codes 55 through 59 for customer-specific processes)

yyyyy = A next number

You must also provide a description of up to 32 characters that indicates the purpose of the workflow process.

Workflow Data Structures

A workflow process has two data structures: key data and additional data. The key data are the data items that make an
instance of a process unique. Additional data contains all of the data that the process needs to complete the process
flow.

The Process Master program (P98800) allows you to create the workflow data structure as you define a workflow
process. When you create a workflow data structure within the Process Master program, the system automatically
names the key data or additional data for you. However, you can rename the data structures to something else by
entering a new name. The name for the key and additional structure are the same, except for the last character. Begin
both structures with WF, formatted as WFxxxxyyyA or WFxxxxyyyB, where:

WF = The workflow data structure

xxxx = The system code

yyy = A next number (the numbering assignments follow current procedures in the respective application groups)

A = The key data structure

B = The additional data structure

Media Objects
The Object Librarian name for a media object data structure can be a maximum of eight characters and is formatted as
GTxxxxyyA, where:

GT = Media object.

xxxx = The file name, excluding the letter F.

yy = A next number.

27
JD Edwards EnterpriseOne Tools Chapter 3
Development Guidelines for Application Design Guide Understanding JD Edwards EnterpriseOne Naming
Conventions
A = An alphabetical character, such as A, B, C, and so on, that you include at the end of the media object name if
multiple media objects exist for a file.

Provide a description of up to 60-characters. It should reflect the subject of the media object.

Menus
The name of a menu can be a maximum of nine characters and is formatted as Gxxxxyyyy, where:

G = Menu.

xx (second and third digits) = The system code. Numbers 55 through 59 are reserved for customer-specific processes.

xx (fourth and fifth digits) = An additional identifier for the menu (optional).

y (sixth digit) = The display level or skill level, such as:

1 - Basic, such as daily processing

2 - Intermediate, such as periodic processing

3 - Advanced, such as advanced or technical operations

4 - System administration, such as system setup

y (seventh digit) = An additional character that you use to differentiate between two menus of the same system with the
same skill level.

For example, the menu name G0911 consists of:

G = The menu prefix

09 = The system code

1 = The basic skill level

1 = The first menu of multiple menus

External Developer Considerations for Menus

External development is the process by which developers who work for organizations other than Oracle, such as
consultants, create custom applications for specific clients. You must use caution when you name a menu so that you
can distinguish between JD Edwards EnterpriseOne and non-JD Edwards EnterpriseOne objects. When you create a
new menu, use the naming convention Gxxxxyy, where:

G = The menu prefix.

xx (second and third digits) = Use a number between 55 and 59, to indicate that it is a custom menu.

xx (fourth and fifth digits) = The system code.

y (the sixth digit) = The display level or skill level. Use this digit only if you need multiple custom menus for each
application.

1 - Basic, such as daily processing

2 - Intermediate, such as periodic processing

28
JD Edwards EnterpriseOne Tools Chapter 3
Development Guidelines for Application Design Guide Understanding JD Edwards EnterpriseOne Naming
Conventions
3 - Advanced, such as advanced or technical operations

4 - System administration, such as system setup

y (the seventh digit) = An additional character that differentiates between two menus of the same system with the same
skill level.

For example, the menu name G550911 consists of:

G = The menu prefix

55 = Custom menu

09 = The system code

1 = the basic skill level

1 = The first menu of multiple menus

Table Conversions
The name of a table conversion can be a maximum of 10 characters and should be formatted as R89xxxxyyy, where:

R89 = Conversion program

xxxx = The system code

yyy = The table or file name

For a table conversion, provide a description of up to 60-characters. The description should be formatted as [File name]
Conversion From yyy To zzz, where:

yyy = The release from which the table is being converted

zzz = The release to which the table is being converted

29
JD Edwards EnterpriseOne Tools Chapter 3
Development Guidelines for Application Design Guide Understanding JD Edwards EnterpriseOne Naming
Conventions

30
JD Edwards EnterpriseOne Tools Chapter 4
Development Guidelines for Application Design Guide Understanding Tasks

4 Understanding Tasks

Task Design
Task design provides you with the features that you need to efficiently design and manage tasks. Ensure that the
JD Edwards EnterpriseOne tasks that you create comply with task standards so that they are consistent with tasks
throughout all JD Edwards EnterpriseOne applications.

Use this task hierarchy when you create task structures:

GXX - system task

GXXYY - module description

GXX10 - Daily Processing

GXX20 - Periodic Processing

GXX31 - Advanced and Technical Operations

GXX41 - System Setup

Task Processing Options

When you create tasks for an interactive application or batch application, you can designate processing options to
be used with them. Processing options for a task determine how the interactive application or batch application is
executed, such as whether to prompt the user for a version of an application or to execute an application blindly.

The UDC table 98/CD assists you when defining the task processing options. You access the UDC table 98/CD Task
Design on the Task Selection Revisions form (W0082C).

Generally, you should set up UBEs (batch applications) on a task to prompt for a version if there are processing options
associated with the UBE. When there are multiple versions of a batch application, the user must select the version
before the application executes.

With interactive applications, you should set up blind execution on a task. When an application is set up on a task using
the blind execution option, the application executes without any interaction from the user.

This table lists more detailed information about setup options:

Option Code 98/CD ZJDE0000 XJDE0000 Blank (or not version

defined)

Blank = No processing Warning: Currently, this OK: No warning given. OK: No version exists
option setup produces the The versions list will be or more than one UBE
versions list. Calling the presented. version exists. The
versions list contradicts versions list will display.
the definition and For an interactive
purpose of a ZJDE application where there

31
JD Edwards EnterpriseOne Tools Chapter 4
Development Guidelines for Application Design Guide Understanding Tasks

Option Code 98/CD ZJDE0000 XJDE0000 Blank (or not version

defined)

version. Set the Options are no versions, use this

Code to 1 or 3. setup.

1 = Blind execution OK: A blind submit Warning: An XJDE is not Warning: If you are
will occur. Use for usually a blind execution blindly submitting, you
interactive applications submit. Set the Option should have a ZJDE
or batch applications Code to Blank or 2, or version defined.
with ZJDE versions. determine if the version
should be a ZJDE. Resolution: Determine
which version type you
have and set the Option
Code accordingly.

2 = Prompt for Versions Warning: A ZJDE is a OK: Multiple XJDE OK: Versions list will be
blind version submit. It versions exist or user- displayed.
is incorrect to ask for defined versions exist
the versions list to be and you want to select
displayed with a ZJDE from the versions list.
version. Change the Option Code Blank
Option Code to 1 or 3, or displays the versions
determine if the version list.
should be a XJDE.

3 = Prompt for Values OK: The processing OK: This could happen. Warning: If you have
options will display and Probably more likely to not set up a version,
an automatic launch will see this at a client site. prompting for values is
occur. incorrect. If no versions
exist, set Option Code to
Blank.

32
JD Edwards EnterpriseOne Tools Chapter 5
Development Guidelines for Application Design Guide Understanding Table I/O Guidelines

5 Understanding Table I/O Guidelines

Table I/O Guidelines

Use these guidelines when you create table I/O functionality.

Ensure that you:

• Update the date, time, user, and program name when updating a table.
• Create a business function for each table to provide an API to retrieve, insert, delete, and update data from the
table.

For simple retrievals, insertions, deletions, and updates, use table I/O statements in Event Rules Design.
• Avoid updating a table with a business function from a different vertical than the vertical for the table.

If a business function accesses multiple tables, limit the table I/O or API to the tables within same vertical as
the business function. Ensure that a business function calls additional functions to retrieve data from other
verticals.

Note:
• "Understanding Events", "Event Rules", and "Runtime Processing" in the JD Edwards EnterpriseOne Tools Event
Rules Guide .

33
JD Edwards EnterpriseOne Tools Chapter 5
Development Guidelines for Application Design Guide Understanding Table I/O Guidelines

34
JD Edwards EnterpriseOne Tools Chapter 6
Development Guidelines for Application Design Guide Understanding Performance Considerations

6 Understanding Performance Considerations

Performance Considerations for All Forms

When you create forms, consider the recommended performance guidelines, which ensure that the forms perform
optimally.

Use these guidelines as standards to increase performance for all form types:

• Limit the number of columns in the grid to the minimum that is required by the application.
• Limit the number of columns in the business view to the minimum that is required by the application.
• Limit the number of form controls, whether hidden or visible, to the minimum needed by the application.
• Use event rule variables as work fields instead of hidden form controls.
• On form and grid controls, disable the data dictionary functions that are not required, such as edits and default
values.

This guideline applies to both hidden and visible controls.

• Limit the amount of input and output performed for each grid row to the minimum that is required for the
application.
• Use the Stop Processing system function whenever feasible to skip the processing of unnecessary event rules.
• For temporary data storage, use the most efficient method that is available at the time.

For example, consider the relative efficiency of cache, linked lists, and work files.
• If performance diminishes when you load data into a form, use media object system functions to edit and
display attachments instead of enabling automatic media object functionality.

When you use media object system functions, you do not need to verify whether an attachment exists before
you can display a bitmap. When you use automatic media object functionality, you must verify whether an
attachment exists before you display a bitmap.

Performance Considerations for Browse Forms

Use this guideline as a standard to increase performance for Browse (Find/Browse, Parent/Child, and Power Browse)
forms.

Ensure that the sort order on the grid partially or completely matches both an index that is defined in JD Edwards
EnterpriseOne software and a logical that is defined on the IBM i .

The logical AND index must contain at least all of the fields in the grid sort. The fields selected for the grid sort must be
in the same sequence as the logical AND index fields. The index or logical might include additional fields that are not
included in the grid sort. For example, in a partial match, the grid sort can be KIT, MMCU, and the logical and index can
include KIT, MMCU, TBM, and BQTY.

35
JD Edwards EnterpriseOne Tools Chapter 6
Development Guidelines for Application Design Guide Understanding Performance Considerations

Performance Considerations for Header Detail and

Headerless Detail Forms
Use this guideline as a standard to increase performance for header detail and headerless detail forms.

Ensure that the sort order on the grid partially or completely matches both an index that is defined in JD Edwards
EnterpriseOne software and a logical that is defined on the IBM i .

The logical and index must contain at least all of the fields in the grid sort. The fields selected for the grid sort must be
in the same sequence as the logical and index fields. The index or logical might include additional fields that are not
included in the grid sort. For example, in a partial match, the grid sort can be KIT, MMCU; and the logical and index can
include KIT, MMCU, TBM, and BQTY.

36
JD Edwards EnterpriseOne Tools Chapter 7
Development Guidelines for Application Design Guide Understanding Standard Event Rules Guidelines

7 Understanding Standard Event Rules

Guidelines

Standard Event Rules Guidelines

Use these guidelines when you create event rules (including Table I/O).

Ensure that you:

• Set up the option to accept a numeric value rather than a character for options that are passed back from the
business function (this is more acceptable internationally).

For example, use 1 (rather than T or Y) for true and 0 (rather than F or N) for false.
• Include a blank line before and after each comment; separate logical sections of event rules with a dashed line.
• Use a grid variable if the work field is a grid column.
• Do not use a hard-coded text string to load a field or variable; use a text variable instead.
• Use the data item Program ID (PID) to update the database; for example, P01021 for an Address Book event rule
from an interactive application.
• Always use the directional arrows to attach business functions.

If you do not use a parameter, then use the # symbol. This symbol identifies a parameter that is not used by
the application that calls the business function. Additionally, it provides documentation to other readers of the
code.
• Include a revisions log at the top of DialogIsInitialized for the entry point form for an interactive application
and InitializeSection for a batch application.

The revisions log contains the date, user, and software action request (SAR) number of the modifications made
to the application.

Note:
• "Working with Forms"," Understanding Forms" in the JD Edwards EnterpriseOne Tools Form Design Aid Guide
.

37
JD Edwards EnterpriseOne Tools Chapter 7
Development Guidelines for Application Design Guide Understanding Standard Event Rules Guidelines

38
JD Edwards EnterpriseOne Tools Chapter 8
Development Guidelines for Application Design Guide Understanding BI Publisher Report Guidelines

8 Understanding BI Publisher Report

Guidelines

BI Publisher for JD Edwards EnterpriseOne Overview

JD Edwards EnterpriseOne has three integrations with Oracle Business Intelligence (BI) Publisher:
• Embedded BI Publisher for JD Edwards EnterpriseOne: Transforms the output from a UBE into customer
facing documents (Pixel Perfect). Common use cases for Embedded BI Publisher with JD Edwards
EnterpriseOne are invoices, statements, pick slips, and checks.
See the JD Edwards EnterpriseOne Tools BI Publisher for JD Edwards EnterpriseOne Guide for more
information.
• One View Reporting: Enables end users to create and run their personalized reports directly from JD Edwards
EnterpriseOne interactive applications. These reports are typically specific to the user or role and are those that
users will run on a daily, weekly, or other periodic basis as part of their normal activities. Users require a high
degree of personalization regarding data selection, sequencing, data columns included, and data visualization
(charts, tables, graphs) with this type of report. These end user reports improve user productivity by providing
users with better visibility into operational data as part of their standard day-to-day business process. One
View Reporting enables users to select data fields and perform specific data selection from within JD Edwards
EnterpriseOne applications and leverage the layout capabilities within BI Publisher to define the report output
formatting. Common use cases might be sales reports, customer reports, supplier reports, and employee
reports.
See the JD Edwards EnterpriseOne Applications One View Reporting User Guide for more information.
• Ad Hoc Reporting: Allows power users and IT staff to build powerful queries to interrogate data on an ad
hoc basis. This type of report is typically created to meet a specific business requirement outside of the
normal business process, and it is only run once or twice. These reports typically require users to create a
SQL statement to retrieve the data (query builder). The query is usually created by the IT department or a
power user who understands the JD Edwards EnterpriseOne data schema. After building the query, IT or
a power user will create a report layout with tables and charts to display the data (template builder). This
integration leverages the JD Edwards EnterpriseOne JDBC Driver and Oracle BI Publisher Enterprise Edition.
This integration has commonly been called "interactive reporting." By definition, there are no common use
cases.
See "Creating Oracle BI Publisher Reports with JD Edwards Data Access Driver" in the JD Edwards
EnterpriseOne Tools BI Publisher for JD Edwards EnterpriseOne Guide .

JD Edwards EnterpriseOne UBE and Report Definition

Guidelines
Each JD Edwards EnterpriseOne Embedded BI Publisher report requires a template, a UBE, and a report definition.
The template is used to define the report layout. The UBE is a Report Design Aid (RDA) report template that is used to

39
JD Edwards EnterpriseOne Tools Chapter 8
Development Guidelines for Application Design Guide Understanding BI Publisher Report Guidelines

generate data for the report defintion.The template and UBE are associated with the report definition, which specifies
the information that BI Publisher requires to process and deliver BI Publisher output.

See the JD Edwards EnterpriseOne Tools BI Publisher for JD Edwards EnterpriseOne Guide for more information.

UBEs for JD Edwards EnterpriseOne Report Definitions

Use these guidelines when designing a JD Edwards EnterpriseOne report to use as the batch application (UBE) for a JD
Edwards EnterpriseOne report definition. Use the JD Edwards EnterpriseOne Report Design Aid to create the UBE.

• Report Constants

Avoid including any report constants in the UBE layout, unless the constant is used in the BI Publisher report
layout.
• Report Variables

Report variable names act as a root element data tag in the resulting XML file. Make the report variable name as
representative as possible. The data dictionary alias, type and length should be included in the report variable
name. Report variables must be unique in the report design.
• Section Names

Section names act as group element data tag in the resulting XML file. Make the section name as
representative as possible.
• Level Breaks

Level breaks represent the grouping in the XML structure. Include as many level breaks as the number of
groups you will have in the BI Publisher layout. It is preferable to have level break footer totals processed by the
UBE to avoid calculation during BI Publisher processing.
• Sorting

Sort the data in the UBE design as you want it to appear in the BI Publisher report. Sorting in the BI Publisher
template will affect performance and should be avoided.
• Page Related Data

Headers, Footers, Brought Forward and Carried Forward sections should be avoided. Any data related to a page
should not be included in the UBE design. The UBE used in a BI Publisher report definition does not generate
pages as the output, it generates an XML file without pages. Any page related information loses context when
the XML file is generated.
• Conditional Sections

Group similar information in conditional sections. For example, Address Book information could be in an
AddressBookInformation Section called from the Customer or from the Supplier sections.
• Data Formatting

Ensure the data is formatted properly in the UBE. BI Publisher does not have access to user preferences, so the
date format and the amount decimal separator must be handled by the UBE engine.

40
JD Edwards EnterpriseOne Tools Chapter 8
Development Guidelines for Application Design Guide Understanding BI Publisher Report Guidelines

Report Definition Guidelines

Use these guidelines when designing a JD Edwards EnterpriseOne report definition.

• Output Types

All the possible output types should be selected when generating a report definition.
• Default Output Types

PDF output type should be the default output type.

• Default Language

User Preference Language should be selected.

Oracle BI Publisher Layout Editor Guidelines

Use the following guidelines for Oracle's BI Publisher Layout Editor when designing BI Publisher reports for JD Edwards
EnterpriseOne.

Report Layout Types

Use these guidelines when designing BI Publisher report layouts.

• Listing Report

This is the most common type of report. These reports are intended to present information that is useful
for performing a specific business function. Developers creating this kind of report should comply with the
standards listed in this document.
• Letter

This format is used to communicate information in a more personal letter format. Standards described in this
document shall be used as guidelines for this kind of report
• Fixed Form Reports

These reports include both pre-printed and application-printed forms, such as pre-printed forms for
government and business forms such as1099s,W-2s, and mailing labels. These reports have their own
formatting standard as defined by the requirements of the form.
• Batch Update UBEs

BI Publisher is not intended for simple error reports or UBEs that do not produce any output.
• Customer Facing Documents

These are documents that are highly customized and might include barcodes, repeating headers, page totals,
and so forth. Purchase orders and invoices are examples of this type of report. Standards described in this
document should be used as guidelines for this type of report.

41
JD Edwards EnterpriseOne Tools Chapter 8
Development Guidelines for Application Design Guide Understanding BI Publisher Report Guidelines

Page Attributes
Use these guidelines when designing page attributes.

• Page Size

Use the standard Letter (8 ¾ x 11inches) size for reports. Most reports are destined to be printed. Consequently,
using custom paper sizes is not acceptable. For those customers where the standard paper size is A4, the
rendering engine will scale the report up to the A4 size.
• Orientation

Standard report layouts should be defined as landscape or portrait. Landscape should be used as the default
for most reports. Considerations for using a portrait layout include the width of data to be printed (for example,
table data is 7 inches wide or less), industry standards, or common business practice. For example, customer
invoices are customarily portrait orientation, thus the report layout is set up to print using portrait.
• Page Margins

Margins for the top and bottom of the page shall not exceed 0.5 inches.

The minimum margins are:

Page Margin Minimums Size

Top .03 inches

Bottom .03 inches

Left .03 inches

Right .03 inches

For reports that contain data in table format, left and right page margins should be set to match the margins shown
when the table is centered. Report header and footer contents should align with the same margins as the displayed
table data.

For additional alignment standards, see Multiple Row Tables - Position and Alignment Between Report Data Objects.

Page Header and Footer

Use these guidelines when designing the page header and footer in the Oracle BI Publisher Layout Editor.

42
JD Edwards EnterpriseOne Tools Chapter 8
Development Guidelines for Application Design Guide Understanding BI Publisher Report Guidelines

General Guidelines
The report template should contain a report header and footer unless it is a legal requirement to exclude them, or it is a
report type (such as a letter or invoice) that does not require a header.

The use of tables to organize information (including header information) on a report is required. This is necessary
because of the way the XML is formatted and for translations. The table borders should be turned off for the table in the
header so that they do not appear in the final output document.

Note: Do not use Microsoft Word's built in features for page headers and footers, because they cause performance
issues with Oracle BI Publisher. Use <?start:body?> <?end body?>. Everything above <?start:body?> is interpreted
as page header information by the BI Publisher engine, and everything below <?end body?> is interpreted as footer
information.

Include a page header on every page of a report and span the entire page width. Include the following information in the
page header:

Feature Position Comment

Report Title Centered in the page header

Report Version Description or Upper-centered under Report Title Optional

Subtitle

Company Logo Upper-left page corner

Report Date and Time Upper-right page corner Report time is optional

Page Number Upper-right page corner under the Use "Page x of x" format
Report Date

This is an example of a correctly designed page header:

Include a page footer on every page of a report and span the entire page width. Include the following information in the
page footer:

Feature Position Comment

Report ID/Version ID/Template Name Lower-left page corner

Confidential Label Centered in the page footer Optional

43
JD Edwards EnterpriseOne Tools Chapter 8
Development Guidelines for Application Design Guide Understanding BI Publisher Report Guidelines

This is an example of a correctly designed page footer:

Company Logo
The standard for Oracle JD Edwards EnterpriseOne developers is to hardcode the Oracle JD Edwards EnterpriseOne
logo into the template. The logo should be used at its original size.

JD Edwards EnterpriseOne customers may or may not use logos on their custom BI Publisher reports, according to their
preferences.

Report Title
Include a report title for each page header. Format the title as follows:

Note: These font, size, color, and format standards apply to the reports that JD Edwards EnterpriseOne ships with its
software. Custom reports may use other standards for these attributes.

Format Value

Font Arial

Size 14 point

Color Black

Text format Bold

Position Centered

Map the report title to the UBE title <Title> from the XML properties group.

Following is an example of the XML <Title> value (Business Unit Report in this example), which would be used as the BI
Publisher report title:

44
JD Edwards EnterpriseOne Tools Chapter 8
Development Guidelines for Application Design Guide Understanding BI Publisher Report Guidelines

Report Subtitles
Report subtitles should be centered below the report title in another row of the table. The subtitle should be the version
description or a user-defined subtitle. Using a version subtitle is optional. Format the subtitle as follows:

Note: These font, size, color, and format standards apply to the reports that JD Edwards EnterpriseOne ships with its
software. Custom reports may use other standards for these attributes.

Format Value

Font Arial

Size 12 point

Color Black

Text format Bold

Position Centered

Report Date and Time

Place the report date in the top right corner of the report. The report date is the date the report is generated. Format
the date as follows:

Note: These font, size, and color standards apply to the reports that JD Edwards EnterpriseOne ships with its
software. Custom reports may use other standards for these attributes.

Format Value

Font Arial

Size 7 point

Color Black

Do not format the date value. Map the BI Publisher report date and time to the UBE report date <Date> and time
<Time> from the XML properties group:

45
JD Edwards EnterpriseOne Tools Chapter 8
Development Guidelines for Application Design Guide Understanding BI Publisher Report Guidelines

Page Numbering
Display the page number in the top right corner of the report under the report date. Format the page numbers as
follows:

Note: These font, size, and color standards apply to the reports that JD Edwards EnterpriseOne ships with its
software. Custom reports may use other standards for these attributes.

Format Value

Font Arial

Size 7 point

Color Black

Use two cells, one for the word "Page" and the other for the page numbers. Use the following format for page numbers:

Page 1 of 10

For reports with a large amount of data, including the total number of pages can cause performance issues. In this case,
simply print the word "Page" in one cell and the page number in a second cell as shown in this example:

Page 1

If you do not include the total number of pages in the page numbering format, display a notice at the end of the report
that the last page has been reached.

Report Name / Version ID / Template Name

Display the report name, version ID, and template name in the page lower left corner. Use the following format:

Note: These font, size, and color standards apply to the reports that JD Edwards EnterpriseOne ships with its
software. Custom reports may use other standards for these attributes.

46
JD Edwards EnterpriseOne Tools Chapter 8
Development Guidelines for Application Design Guide Understanding BI Publisher Report Guidelines

Format Value

Font Arial

Size 7 point

Color Black

Map the version name to the UBE <Version> value (JCB0001 in the example below) from the XML properties group.

Labeling Confidential Reports

Because they are not translatable, do not use Microsoft Word hard-coded watermark strings to indicate that a report is
confidential. To indicate confidentiality, add a subtitle in the page footer. Center the confidential subtitle in the center of
the page footer. Format the confidential subtitle as follows:

Note: These font, size, color, and format standards apply to the reports that JD Edwards EnterpriseOne ships with its
software. Custom reports may use other standards for these attributes.

Default Formatting for Confidential Subtitle

Format Value

Font Arial

Size 7 point

Color Black

Text format Bold

Position Centered in footer

47
JD Edwards EnterpriseOne Tools Chapter 8
Development Guidelines for Application Design Guide Understanding BI Publisher Report Guidelines

Maximum Formatting Options for Confidential Subtitle

Format Value

Font Arial

Size 9 point

Color Black

Text format Bold

Position Centered in footer

Page Header and Footer Example

Following is an example of a correctly formatted header and footer for a JD Edwards EnterpriseOne BI Publisher
report.

Report Data
Use the following guidelines for displaying data in a BI Publisher report.

48
JD Edwards EnterpriseOne Tools Chapter 8
Development Guidelines for Application Design Guide Understanding BI Publisher Report Guidelines

Font
In general, for the reports that JD Edwards EnterpriseOne ships with its software, use Arial 7 point font for all text on
the report. If the report does not have much information on it, Arial 9 point font is acceptable as the maximum font size.
Custom reports may use other fonts.

Table Use
Because the RTF template facilitates the use of tables to organize the data in a report, Oracle recommends that you use
the RTF format.

Use a Microsoft Word table for single data items, labels, and data tables in a BI Publisher report. The header, tables,
footers, and any object must be contained in a Microsoft Word table cell.

Single Data Field

Single field values must be displayed with a left-aligned, Arial, 7 point, bold label and left-aligned 7 point values. Do not
use a colon after the label. These standards apply to the reports that JD Edwards EnterpriseOne ships with its software.
• Display single field labels as left-aligned, Arial, 7 point, bold formatting.
• The field labels should have the first letter of each word in upper case.
• Do not separate the field label and the field value with a colon.
• The field values should be left-aligned, Arial, 7 point.
• Use a 15% border table border for the table.
• A single data label and single data value should have a 15% grey border for separation.
• A single data value and single data description should not have any separation.
This is an example of single data field formatting:

Multiple Row Tables

In general, a table with multiple rows should consist of a header that is shaded for clarity and data rows with alternate
15% grey shading, as this example illustrates:

Note: These color standards apply to the reports that JD Edwards EnterpriseOne ships with its software. Custom
reports may use other colors for these rows.

Multiple Row Tables - Header Alignment

All table headers should be centered unless the header is used for wide column. In this case, the table header for that
column can be left-aligned.

49
JD Edwards EnterpriseOne Tools Chapter 8
Development Guidelines for Application Design Guide Understanding BI Publisher Report Guidelines

Multiple Row Tables - Header Color

For multiple row table headers, set the header background shading to (Red, Green, Blue) (207, 224, 241).

Multiple Row Tables - Alternate Row Shading

Data table rows should be alternately shaded with a 15% grey shade, as this example illustrates:

Note: To achieve alternate grey shading, the next conditional formatting must be included after the for-each
sentence:
<?if@row: position()mod 2 = 0?>
<xsl:attribute name="background-color" xdofo:ctx="incontext">#d9d9d9</xsl:attribute>
<?end if?>

Multiple Row Tables - Totals Shading

Reports with multiple child levels should use the following shading for separating totaling levels.

Level Background Color

(Red, Green, Blue)

1 (207, 224, 241)

2 (185, 209, 227)

3 (165, 195, 219)

4 (145, 181, 211)

5 (114, 161, 200)

These colors were designed to work well on both monitors and the printed page. You should use these shading levels to
help distinguish between levels of a report.

In order to use the different styles of shading, each shaded row requires its own table, as shown in this example:

50
JD Edwards EnterpriseOne Tools Chapter 8
Development Guidelines for Application Design Guide Understanding BI Publisher Report Guidelines

Multiple Row Tables - Position

The default position for multiple row tables is the center of the page. If the table is narrow, left alignment is acceptable.

To set the table alignment and preferred width, select Table Properties.

Note: Although it is optional, setting the preferred width will help when aligning the different report objects in the
layout. Set the preferred width to display the data properly in the report layout.

Table Cell Margin

Set table cell margins as shown in the following illustration:

Cell margin values apply to single data tables, multiple row tables, and totals tables.

51
JD Edwards EnterpriseOne Tools Chapter 8
Development Guidelines for Application Design Guide Understanding BI Publisher Report Guidelines

Table Borders
The entire table should have solid, 1/2 point lines, and the table border color should be 25% grey, as shown in the
following illustration:

Alignment Between Report Data Objects

Use the following guidelines for alignment between report data objects:

• Single data tables should be left-aligned with the associated multiple row tables.
• Totals should be right-aligned with the multiple row tables.
This example shows a left-aligned single data table, with right-aligned total row tables:

52
JD Edwards EnterpriseOne Tools Chapter 8
Development Guidelines for Application Design Guide Understanding BI Publisher Report Guidelines

You may display data in more than one table on a report. For reports with more than one table, set the margins so that
the widest table is centered on the page. By doing so, the margins will be set according to the widest table, and the
remaining tables will then be aligned to the left side of the widest table.

An exception to multiple table alignment is when tables and their related graphs display on the same page. For reports
containing graphs and their related tables, center each table with its graph. For any other tables on a report containing
graphs, the widest table standard applies. Use page breaks to separate tables that are related to graphs and non-related
tables.

Paragraph Setting
Use table cells and margins to lay out the data in the report. Do not use special paragraph settings when creating the
report template. Use the paragraph settings shown in the following illustration:

53
JD Edwards EnterpriseOne Tools Chapter 8
Development Guidelines for Application Design Guide Understanding BI Publisher Report Guidelines

Tab Use
Do not use tab characters in the report. Tab characters might cause problems when the template is translated. In place
of tabs, use tables without borders to organize objects in the report layout.

54
JD Edwards EnterpriseOne Tools Chapter 8
Development Guidelines for Application Design Guide Understanding BI Publisher Report Guidelines

End of a Report Indication

If you do not show the total number of pages in the page header, print the phrase "End of Report" centered on the last
page. Center the phrase on the last page that contains a report body and place it inside a single-celled table after the
end of the template content.

Format the "End of Report" phrase as follows:

Format Value

Font Arial

Size 7 point

Color Black

Text format Bold

Position Centered on last page that contains a report body

No Data Indication
To indicate that no data was found, print the title, page headings and column headings followed by the centered
phrase "No Data Selected." Place the phrase inside a single-celled table after the end of the template content. Use an If
condition for the data generated by the JD Edwards EnterpriseOne UBE XML to determine whether the phrase should
appear on the report.

Format the "No Data Selected" phrase as follows:

Format Value

Font Arial

Size 7 point

Color Black

Text format Bold

Position Centered after the end of the template content

55
JD Edwards EnterpriseOne Tools Chapter 8
Development Guidelines for Application Design Guide Understanding BI Publisher Report Guidelines

Note: The following condition must be included before the "No Data Selected" message:

<?if:ErrorMessage_ID0='No Data
Selected'?> No data Selected <?end if?>

Page Break
To avoid an extra blank page at the end of the report, do not use the native Microsoft Word page break.

Use <?split-by-page-break:?> syntax immediately before the <?end for-each?> instead.

BI Publisher Report Example

The following example shows a BI Publisher report with these options correctly formatted:

• Single Data Labels

Align right; in their own cell; Arial, 7 point, black, bold font.
• Single Data Values

Align left; in their own cell; Arial, 7 point, black font.

• Column Headers

Centered; in their own cell; Arial, 7 point, black, bold, font.

• Column Data

Align left or right, depending on data; in their own cell; Arial, 7 point, black font.
• Multiple Data Row Shading

Alternate 15% grey shading.

• Report Total Labels

Match background color to the level they represent; Arial, 7 point, black, bold font.
• Report Totals

Embed column value within label text.

• Report Total Data

Align right; in their own cell; Arial, 7 point, black, bold font.

56
JD Edwards EnterpriseOne Tools Chapter 8
Development Guidelines for Application Design Guide Understanding BI Publisher Report Guidelines

Translation Guidelines
Language translation of reports can be a particularly time-consuming and expensive endeavor. To facilitate report
translation, follow these guidelines for spacing and anchoring all boilerplate text. Oracle recommends that you allow
30% for text expansion.
• Do not format the document by using characters. For example the following string is not acceptable:

Instead, it is recommended that you use a 2-celled table and bold the text, as shown in this example:

• Do not use consecutive symbols in a translatable string, for example, By: ________. If you need to create this
type of text along with consecutive underscores to indicate a line, use a 2-celled, borderless table with the text

57
JD Edwards EnterpriseOne Tools Chapter 8
Development Guidelines for Application Design Guide Understanding BI Publisher Report Guidelines

in the left column (such as the word "By" in the previous example). Then use the lower border of the second cell
to achieve the line.
• Do not use words connected with underscores, for example, ACCOUNTING_SEQUENCE_NAME. This type of
string will not be translated.
• Do not concatenate a variable string with a static string at runtime to create a string. There are several
translatability issues with this approach. The translator will not be able to determine the variable string value.
• Do not use incorrect spelling in templates. Use a spell checker to ensure that the words are spelled correctly.

XPath Usage
Oracle BI Publisher uses XPath to access data elements. The following example shows a typical hierarchy tree of data
elements:

The XPath search procedure for DEPARTMENT_NAME in the example above is as follows:

1. DEPARTMENT_NAME is inserted as <?DEPARTMENT_NAME?>

2. <?DEPARTMENT_NAME?> is translated to the XPath .//DEPARTMENT_NAME
3. .//DEPARTMENT_NAME searches for DEPARTMENT_NAME in the complete sub-tree, starting from the current
context. That is, it searches for any element with the name field in the correct context. With large data sets, this
search procedure can affect system performance.
For small documents, search time is negligible, but with large data sets use the full relative path to improve
performance. For example, in the hierarchy tree above:

• Instead of <?for-each:DEPT?> use <?for-each:/DEPT_SALS/DEPT?>

• Instead of <?DEPARTMENT_NAME?> use <?./DEPARTMENT_NAME?>
Additionally, large documents might not fit into memory, thereby requiring disk access for searches. By using the full
relative path, full tree searches are avoided, resulting in large performance improvements.

58
JD Edwards EnterpriseOne Tools Chapter 9
Development Guidelines for Application Design Guide Using Currency

9 Using Currency

Using Currency
Enterprises that do business internationally require additional accounting considerations and added complexity.
This complexity arises from doing business in different currencies and the obligation to follow different reporting and
accounting requirements. Some fundamental requirements for an international enterprise include:
• Conversion of foreign currencies to the local currency.
• Conversion of multiple currencies into one currency for reporting and comparisons.
• Obligation to regulations mandated in the countries of operation.
• Continued evaluation of currencies due to fluctuation in exchange rates.

Currency Implementation
This section provides overviews of:
• Currency implementation.
• Advantages of developers controlling currency.
• Working with currency.

Understanding Currency Implementation

JD Edwards EnterpriseOne currency implementation includes these features:
• Currency retrieval
Accomplished through database triggers and table event rules.
• Currency retrieval logic
Handled using business functions.
• System Application Programming Interface modules (APIs)
Assist you in accessing cached tables.

Advantages of Developers Controlling Currency

JD Edwards EnterpriseOne enables developers to control currency retrieval. Enabling developers, instead of the system,
to control currency, provides greater flexibility and easier maintenance. Some of the advantages of enabling developers
to control currency are:
• The addition of currency tables does not require changes to system modules. Only new business functions
need to be added.
• Business logic is captured in business functions, rather than in system modules that assume knowledge of
business logic.
• Table event rules enable you to attach currency retrieval logic at the table object level.
• Table event rules are triggered by table events instead of application events.

59
JD Edwards EnterpriseOne Tools Chapter 9
Development Guidelines for Application Design Guide Using Currency

• Any application that uses the table that has currency business functions attached to it receives the same logic,
so you do not need to modify each application.
• No hard-coded logic is embedded in the runtime engine.

Working with Currency

When identified amounts are written to or retrieved from a database, or when they are used in calculations during
processing, proper decimal placement is extremely important. Currency implementation is needed to adjust decimal
placement on Math_Numeric currency fields according to a specified currency. Common applications of currency
implementation include conversion of currency amounts and revaluation of currency due to fluctuations in exchange
rates.

Implementing currency involves:

• Performing currency setup.

• Creating a business function that contains logic to retrieve currency information. Currency business functions
are known as currency triggers.
• Attaching a currency trigger to the Currency Conversion event in Table Event Rules (TER).
• Designing TER functions through Event Rules Design. The system then converts the event rules to C and
compiles them into a consolidated DLL through the Object Management Workbench (OMW) application.
• Modifying applications as necessary.
The JD Edwards EnterpriseOne database middleware then calls the appropriate TER function when the Currency
Conversion event is triggered.

Understanding the Build Triggers Option

The Build Triggers option performs these steps:

• Converts event rules to C source code.

This creates the files OBNM.c and OBNM.hxx (where OBNM is the Object Name). The source file will contain
one function per TER event.

For example, if you are working with the F0411 table, the Build Triggers option creates a C source member
called F0411.c. You can browse through the C code and ensure that all of the parameters are set up correctly.
The system generates an error log if an error occurs during the ER-to-C conversion. The error log is called
eF0411.log.
• Compiles the new functions and adds them to JDBTRIG.DLL. This is the consolidated DLL that contains TER
functions.

Understanding How Table Event Rules Work with Currency Processing

The Currency Conversion event runs if currency processing is enabled.

Table triggers for currency run after the record is fetched and before the record is added to the database.

This process flow illustrates the currency conversion process:

60
JD Edwards EnterpriseOne Tools Chapter 9
Development Guidelines for Application Design Guide Using Currency

On FETCH: On ADD/UPDATE:

1. Application requests data. 1. Application sends data.

2. Is currency on? 2. Is currency on?

3. If yes, run currency trigger. 3. If yes, run currency trigger.

4. Currency Trigger calls TER, The TER: 4. Currency Trigger calls TER. The TER:

• Executes the business function. • Executes the business function.

• Performs the business logic. • Performs the business logic.
• Scrubs data accordingly. • Scrubs data accordingly.

5. Return data to database, and then to 5. Update database.

application

When passing Math_Numeric currency fields into a business function, the currency values in the respective data
structure must be populated. Math_Numeric work fields that contain currency values also need the proper currency
information.

You can copy currency information to controls (work fields or others) in event rules by using the system function Copy
Currency Info. You can call the currency triggers from within an application's event rules or from another business
function.

Implementing Currency Conversion

This section discusses how to:

• Set up currency conversion.

• Show currency-sensitive controls.

61
JD Edwards EnterpriseOne Tools Chapter 9
Development Guidelines for Application Design Guide Using Currency

• Create a currency conversion trigger.

Understanding Currency in Applications and Tables

If your business uses more than one currency, you must designate the method of currency conversion to use.

When you design an application, you can decide whether to hide or show currency-sensitive controls at runtime.

If the table that you are using for the application contains currency fields, you must specify how many decimal places
exist in each column. When the source or destination fields are currency fields and you have not created a currency
trigger, problems might arise if the value is used in a calculation. If you do not create a currency conversion trigger, the
system cannot determine where to locate the decimal within a field.

Prerequisites
Create a project in Object Management Workbench. Create an interactive application or locate an interactive application
that you want to modify for currency conversion and add it to the project.

Forms Used to Work With Currency Conversion

Form Name FormID Navigation Usage

System Setup W0000A JD Edwards Set up currency

EnterpriseOne Menus, conversion.
Multi-Currency Setup
(G1141), Set Multi
Currency Option

General Accounting W0000B System Setup, click Set up currency

Constants General Accounting conversion.
Constants

Form Design Aid NA Object Management Show currency sensitive

Workbench, select an controls
interactive application
and click the Design
button.

Object Management W98220A Type OMW in the Fast Create a currency

Workbench Path field of Solution conversion trigger.
Explorer

Setting Up Currency Conversion

Access the General Accounting Constants form.
Multi-Currency Conversion (Y, N, Z)
Select a code that specifies whether to use multi-currency accounting, and the method of multi-currency accounting to
use:

Codes are:

62
JD Edwards EnterpriseOne Tools Chapter 9
Development Guidelines for Application Design Guide Using Currency

N Do not use multi-currency accounting. Use this option if you enter transactions in only one currency for all
companies. The multi-currency fields do not appear on forms. The system supplies a value of N if you do not enter a
value.

Y Activate multi-currency accounting and use multipliers to convert currency. The system multiplies the foreign amount
by the exchange rate to calculate the domestic amount.

Z Activate multi-currency accounting and use divisors to convert currency. The system divides the foreign amount by
the exchange rate to calculate the domestic amount.

Showing Currency-Sensitive Controls

Check out and open an interactive application in Form Design Aid.

1. Double-click the control that you want to appear on the form.

2. Select the Control Options tab.
3. If you want to display currency fields, verify that the No Display if Currency is Off option is deselected.

When the No Display if Currency is Off option is selected, currency-sensitive controls do not appear. If the No
Display if Currency is Off option is deselected, currency fields are visible.
You must exit the current JD Edwards EnterpriseOne session and begin a new one to apply currency conversion
changes.

Creating a Currency Conversion Trigger

Access Object Management Workbench

1. Move the table to which you want to attach the currency trigger into the project.
2. Check out the table.
3. Ensure that the table is highlighted, and then click the Design button in the center column.
4. On Table Design, select the Design Tools tab, and then click Start Table Trigger Design Aid.
5. On Event Rules Design, select the Currency Conversion event and attach the currency trigger business function
that you want to use.
6. Click the Business Functions button.
7. On Business Function Search form, use the query by example (QBE) line to search for business functions.

You can use Category CUR or System Code 11 to find existing currency business functions. To read notes
that describe the purpose of the business function, its parameters, and program requirements, click the
Attachments button.
8. Select the business function with which you want to work, and then click Select.
9. On Business Functions, attach the table columns to the business function data structure, and then click OK.

The available objects that appear are for table column only.
10. On Event Rules Design, click Save, and then click OK.
11. On Table Design, select the Table Operations tab, and then click Generate Table.
12. Select the data source for the table, and then click OK.
13. On Table Design, select the Design Tools tab, and then click Build Table Triggers.

The system creates the table event rule (TER). The newly created or modified table event rule functions are now
called from the JD Edwards EnterpriseOne system whenever the corresponding event occurs against the table.

63
JD Edwards EnterpriseOne Tools Chapter 9
Development Guidelines for Application Design Guide Using Currency

64
JD Edwards EnterpriseOne Tools Chapter 10
Development Guidelines for Application Design Guide Understanding Translation Issues

10 Understanding Translation Issues

Translation Issues
JD Edwards EnterpriseOne software is translated into several different languages. Adhering to translation standards
ensures that components can be accurately translated. These software components are subject to translation:
• Data dictionary items (Alpha, Row, and Column descriptions).
• Data dictionary glossaries (used for F1 help).
• Menus.
• Tasks.
• User Defined Codes (UDCs) (Column 1 description only).
• Reports.
• Forms.
• Text variables in forms and reports.
• Processing options.
• Processing option glossaries (used for F1 help)
• Resource files.
Use short, complete sentences. Keep sentences as simple and straightforward as possible. In general, use active voice.
Active voice clarifies who or what is doing the action, and is usually more direct and less wordy than passive voice.
Compare these examples:
• Active voice: Use this program to enter vouchers.
• Passive voice: This program is used to enter vouchers.

Writing for Translation

This section discuses:
• Using consistent terminology.
• Avoiding telegraphic English.
• Identifying placeholders.
• Avoiding technical jargon, slang and Americanisms.
• Using abbreviations and acronyms judiciously.
• Including that in relative clauses.
• Avoiding false subjects.
• Using parallel structure in lists.
• Capitalizing words consistently and appropriately.

65
JD Edwards EnterpriseOne Tools Chapter 10
Development Guidelines for Application Design Guide Understanding Translation Issues

Using Consistent Terminology

Use terms consistently. Use the one term, one concept rule: Avoid the use of different terms to convey the same concept,
and avoid the use of one term to convey different concepts. These terms are sometimes used to convey the same
concept:
• Match and reconcile.
• Spread, distribute, and allocate.
• Move and transfer.
• Change, revise, alter, and modify.
These terms are sometimes used to convey different concepts:
• Item
• Order
• Rate
• Schedule
In some cases, a word can be used either as a noun or a verb. In such cases, try to use the word in only one way. For
example, use default only as a noun. For example:

Incorrect Correct

The system defaults the value. The system supplies the default value.

Avoiding Telegraphic English

The term telegraphic English refers to writing in which words have been omitted for brevity. Functional words, such as
articles and pronouns, are frequently omitted. Adjectives and linking verbs, such as is and are, are sometimes omitted.
Telegraphic English is frequently ambiguous. Consider this message:

Empty File

Is Empty a verb (Empty the file) or is it an adjective (The file is empty)? Evaluate error messages, and if they might be
ambiguous because of telegraphic English, reinstate the omitted words. This message contains two words that might or
might not be verbs:

Quantity Changes Impact Rate Master

If Changes is a verb and Impact is an adjective, rewrite as The quantity changes the impact rate master. If Changes is a
plural noun and Impact is a verb, rewrite as Changes in quantity impact the rate master.

Identifying Place Holders

When using placeholders (&n), precede the placeholder with a noun that identifies what it is. Translators need to know,
among other things, the gender of nouns to effectively translate them. Consider this example:

66
JD Edwards EnterpriseOne Tools Chapter 10
Development Guidelines for Application Design Guide Understanding Translation Issues

The &1 of test &2, branch &3, effective &4 through &5, has been approved.

We know what &2 and &3 are, because they are identified by the nouns test and branch. However, we do not know what
&1 is. We can assume that &4 and &5 are dates, but that is only an assumption from the context of the sentence, and it
could be wrong.

In this example, all placeholders are effectively identified:

The specified month &2 and year &3 have not been defined in the workday calendar file (F0007) for Branch/Plant &1.

Avoiding Technical Jargon, Slang, and Americanisms

Technical jargon, slang, and Americanisms are difficult to translate. The term hyperitem in this example is technical
jargon:

The hyperitem option is not valid for the selected row.

Examples of phrases that are Americanisms are on the fly and beef up the functionality.

Using Abbreviations and Acronyms Judiciously

American English uses abbreviations far more freely than some other languages and cultures. Abbreviations are
sometimes misunderstood by translators and sometimes cannot be translated. Some languages do not have
abbreviations. Therefore, a judicious use of abbreviations and acronyms is important. Observe these guidelines:

• Use only standard, common abbreviations.

• Do not overuse JD Edwards EnterpriseOne-created abbreviations and acronyms.
• Do not invent abbreviations, not even to meet space requirements.
• If you use an abbreviation, use it to mean only one thing.

For example, LT can mean either ledger type or less than.

Including "That" in Relative Clauses

English allows the omission of the relative pronoun that in many cases. In most European languages, inclusion of the
relative pronoun is mandatory. Even for English speakers, the use of that helps comprehension. Consider this sentence:

Verify the draft is at the appropriate status.

Initially, a reader might understand the meaning to be Verify the accuracy of the draft. Including that prevents an initial
misreading and speeds comprehension:

Verify that the draft is at the appropriate status.

A good practice is to include that even when you do not anticipate that a sentence will be misunderstood. For example:

Changes that you have made will affect the total quantity requested for this rate.

67
JD Edwards EnterpriseOne Tools Chapter 10
Development Guidelines for Application Design Guide Understanding Translation Issues

Avoiding False Subjects

A false subject is a construction in which it or there appears to be the subject of a sentence or clause, but upon analysis
is really a nonsensical word. The true subject is either missing or buried in the sentence, that is, it is not obvious. For
example, a common expression in English is It is raining. But what is it? The three constructions that commonly indicate
a false subject are It is, There is, and There are.

The use of false subjects in English is acceptable, idiomatic, and usually clear to English speakers. But most other
languages have no comparable idiom. Translators have difficulty translating sentences with false subjects because they
have trouble identifying the true subject of the sentence.

Most sentences that contain false subjects can be easily revised so that the subject is easily identified. Consider this
example:

There are currently no logs on this server.

From the structure of the sentence, there appears to be the subject but the actual subject is logs. The sentence can be
revised as follows:

No logs are currently on this server.

Using Parallel Structure in Lists

When creating bulleted or numbered lists, ensure that all items in the list have the same structure. For example, all items
begin with an imperative verb or all items begin with a noun; all items are complete sentences or all items are phrases

Capitalizing Words Consistently and Appropriately

Use capital letters consistently and appropriately. Most technical documentation tends to overuse capital letters.
Translators usually assume that capital letters indicate a program, a form, a table, a field, and so on. Use capitalization
for:

• The first letter of the first word of a sentence.

• Acronyms.
• Headings and names of things.
• In headings, capitalize the first and last words and all other words except articles (the, a, an), conjunctions (and,
or, but, and so on), and prepositions (in, to, on, from, and so on).
• Capitalize names of things, such as systems, programs, forms, tables, and fields. Always precede the name
with the and follow it with what it is. For example, access the Speed Invoice Entry form not access Speed Invoice
Entry.
• Capitalize names as they appear in the software, even if they do not follow the conventions for headings.
Do not capitalize terms when they are used in a generic sense, even if the same term might be used as a name and
capitalized in some other context. For example, in the sentence Enter a pay code in the Pay Code field, the term pay
code is capitalized only when it is the name of the field.

68
JD Edwards EnterpriseOne Tools Chapter 10
Development Guidelines for Application Design Guide Understanding Translation Issues

This is a list of terms that should be not capitalized when used generically:
• address book
• automatic accounting instructions
• category codes
• chart of accounts
• company constant
• detail area
• processing options
• user defined codes
• multicurrency
• general ledger

Translation Coding Guidelines

Use these guidelines to ensure a successful translation of JD Edwards EnterpriseOne software components:
• Limit the size of text items to no more than 70 percent of the space allotted to them.
Many words and phrases increase in size when translated; therefore, ensure that all field sizes leave room for
text expansion of up to 30 percent. If you exceed the space allotted, you will receive a Warning Message in
event rules (ER). Do not ignore this message.
• Verify that push buttons can change size dynamically to compensate for any text size increase that occurs in
translation.
• Use only approved acronyms and abbreviations.
• Use text variables instead of hard-coded text.
Text variables are translated, while hard-coded text cannot be translated.
• Do not use contractions.
• Avoid long or ambiguous noun strings.
• Leave controls visible in the Properties and use the hide/show functionality in ER.
Any control set to hidden in the control's properties (the Visible check box is cleared) is not extracted for
translation and, therefore, cannot be translated. If the control is never to be displayed, then clear the Visible
option. If the control is sometimes displayed, select the Visible option and use the hide/show functionality in
ER.
• Whenever Table I/O is used to retrieve user-defined code (UDC) descriptions, ensure that you enable retrieval
from either the User Defined Codes table (F0005) or the User Defined Codes - Alternate Language Descriptions
table (F0005D), depending on the user's logon language setting.
Translated UDC descriptions and UDC type descriptions are not stored in the same tables for all languages.
For the English language, they are stored in the User Defined Code Types table (F0004) and the User Defined
Codes table (F0005), respectively. For all other languages, they are stored in the User Defined Codes - Alternate
Language Descriptions table (F0004D) and the User Defined Codes - Alternate Language Descriptions table
(F0005D).

69
JD Edwards EnterpriseOne Tools Chapter 10
Development Guidelines for Application Design Guide Understanding Translation Issues

Translation Readiness Guidelines

Use these guidelines when either creating new applications or enhancing existing applications. If you do not adhere to
these guidelines, any translation efforts will take more time and, therefore, be more costly.

This table lists the questions you should ask yourself to ensure that translation efforts and costs are optimized:

Item Question

Abbreviations and Acronyms Did I use only approved abbreviations and acronyms?

Concatenated Text Was concatenation of text removed?

Controls Are the controls listed in ER selected as visible?

Cultural References Were puns and cultural references removed?

Data Dictionary Were data dictionary glossaries written and formatted according to standards?

Font Overrides Was the font override removed?

Hard-coded text Was hard-coded text removed and replaced with text variables?

Icons and other Images Was text removed from icons and other images?

Are icons generic enough to be understood in all target markets?

Sizing of Text Areas and Buttons Were text areas stretched to the maximum width to provide sufficient room for text expansion when
the text is translated?

Were buttons sized wide enough to provide sufficient room for text expansion?

Source Text Is the source text grammatically correct and easy to understand?

Terminology Did I use terminology consistently?

Text Variables Were the text variables assigned to an identifier?

UDCs Do UDCs retrieve the description in user language preference?

70
JD Edwards EnterpriseOne Tools Chapter 10
Development Guidelines for Application Design Guide Understanding Translation Issues

Actions that Trigger Translation

When you create or change a JD Edwards EnterpriseOne component that is extracted for translation, the component
is flagged in the system for either first-time translation or retranslation, as appropriate. Changing the layout, tab
sequence, or control location for a component does not trigger a retranslation. These actions trigger a retranslation in
the system:
• Adding text.
• Deleting text.
• Changing text, including correcting typographical errors and punctuation.
• Changing the formatting of text, text alignment, and line indentation.
• Adding or deleting spaces between text.
• Changing the size of a field and so on.
• Adding or deleting line breaks.
• Changing menu sequence, even if you do not change the text.
• Changing processing option sequence on a processing option tab.
• Adding or changing menu toolbar exits.
This section discuses how to:
• Identify text strings used in JD Edwards EnterpriseOne software.
• Identify approved text strings.
• Identify system codes for translating global product solutions.

Working with Noun Strings

This section discusses:
• Working with noun strings.
• Noun strings used in JD Edwards EnterpriseOne applications.
• Approved text strings.
• System codes for translating global product solutions.
Avoid long noun strings. A noun string is a group of three or more nouns in succession. Noun strings are difficult to
translate because the relationship between words is not always clear. Consider this example:

Manual G/L Transactions Entry

Does this mean manual entry of G/L transactions or entry of manual G/L transactions? A good way to rewrite a noun
string is to change the order of the words (often starting at the end and reversing the order) and to use prepositional
phrases to clarify relationships:

Manual Entry of G/L Transactions

If any word is a nominalization (a noun formed from a verb), change it back to a verb:

Entering G/L Transactions Manually

71
JD Edwards EnterpriseOne Tools Chapter 10
Development Guidelines for Application Design Guide Understanding Translation Issues

If space is a consideration, you can use hyphens to indicate the relationship between words:

Manual G/L-Transactions Entry

Use one of these strategies to avoid noun strings:

• Insert helpful words such as of, for, and to.
• Add -ing or -ed to indicate what has been or is being acted upon.
For example, depending on the intent, consider rewording Install System Code to:
• Installed System Code.
• Install the System Code.
• Code for Install System.
• Install Code for System.
• Code the Install System.
The Install System Code example is particularly confusing because both install and code could be verbs. This phrase
could be one very long noun, a request for action, or an action already taken.

To effectively translate text, translators often require more information than English readers do. The translator must
know who or what is performing an action. Translators also face gender issues. Depending on how the words are
organized, a word can be feminine or masculine.

If you are in doubt about how to separate a long string of nouns, ask whether one of the nouns is a verb. If so, then
insert a verb helper, like to, the, of, or for, or change the tense of the verb. Consider shortening a long noun string by
eliminating words that might not be necessary. For the noun string Install System Code, either Install Code or System
Code is easier to translate.

Noun Strings Used in JD Edwards EnterpriseOne Applications

Some noun strings present translation challenges because the translator must first determine whether words contained
in the string are nouns or verbs. For example, in the field name Install System, is the word install a verb or a noun?
In this instance, install system is a compound noun string. Many developers understand this string because they
are familiar with the way in which JD Edwards EnterpriseOne implementations use it. However, for a translator or
international user, the meaning of the string is unclear.

This table lists examples of text strings that are currently used in JD Edwards EnterpriseOne applications and a
description of the confusion that each one can cause a translator or an international user:

Field Name Question Asked By a Translator

Log File Name Does this mean to log the filename or the name of the log file?

Setup Function Does this mean to set up the function or the function for the setup?

Setup Menu Does this mean to set up the menu or the menu containing setup options?

Install Data Does this mean to install data or data referring to the installation?

72
JD Edwards EnterpriseOne Tools Chapter 10
Development Guidelines for Application Design Guide Understanding Translation Issues

Field Name Question Asked By a Translator

Install Data Sources Does this mean to install data sources or data sources referring to the installation?

Install Environments Does this mean to install environments or environments referring to the installation?

Install Hosts Does this mean to install hosts or hosts referring to the installation?

Add Following Add the word following or add after?

LineNumber Why are the words not separated by a space? Is this a parameter or does it mean the number of lines?

Approved Noun Strings

This is a list of approved, standard noun strings. For better understanding, easier translation, and consistent usage
across JD Edwards EnterpriseOne applications, refer to this list when you name fields:

Text String Usage

Data Structure Data structure is a noun string. Data structure means the structure of the data. The JD Edwards
EnterpriseOne tool set contains different types of structures. Any text that precedes the text data
structure refers to the type of the data structure and functions as an adjective.

Examples:

• Business function data structure

• Form data structure
• Media object data structure
• Processing option data structure
• Report data structure

[noun] Design The JD Edwards EnterpriseOne tool set includes many design tools, each of which is a different type of
tool for creating a specific object type. For example, the Table Design tool creates a table.

Examples:

• Application Design
• Business View Design
• Data Dictionary Design
• Event Rule Design
• Form Design
• Parameter Design
• Table Design

73
JD Edwards EnterpriseOne Tools Chapter 10
Development Guidelines for Application Design Guide Understanding Translation Issues

Text String Usage

[noun or verb] Event Numerous events or activities exist in JD Edwards EnterpriseOne. The text that precedes the type of
event can be a string of nouns, a verb, or a combination of nouns and verbs. In any case, the text string
that precedes the word event is an adjective and describes the purpose of the event.

Examples:

• Button Clicked event

• Row is Exited event

High-level Default Trigger High-level is an adjective for the noun string default trigger. A high-level default trigger is criteria that
are automatically evaluated for data in a field.

Install [noun] Install is an adjective, not a verb.

Examples:

• Install system
• Install data
• Install data sources
• Install environments
• Install hosts

Line Number The number of the line.

Menu Revisions Menu Revisions is a noun string. This JD Edwards EnterpriseOne tool maintains interactive and batch
application menus.

Object Librarian Object Librarian is a noun string. This JD Edwards EnterpriseOne tool maintains objects or building
blocks that make up applications.

Object Type Object type is a noun string. Object type means the type of object.

Process Function A function of a process. On a form, process function is a noun string, where process describes the
function.

Process Usage A usage of a process. On a form, process usage is a noun string, where process describes the usage.

Set Up Set up, when spelled as two words, is a verb

Setup [noun] Setup, when spelled as one word, is a noun or an adjective, not a verb.

Examples:

• Setup function
• Setup menu

74
JD Edwards EnterpriseOne Tools Chapter 10
Development Guidelines for Application Design Guide Understanding Translation Issues

System Codes for Translating Global Product Solutions

Most software products provide global solutions, and they are translated into all supported languages. The system code
assigned to a global solution is also global. It does not specify a country or region. Some software products, however,
provide solutions to a specific country or region. The system code of these products must specify the country or region
where the products will be used. The system codes indicate into what language the products need to be translated.

These are two examples:

• Address Book (system code 01) provides a global solution that is translated into all supported languages.
• HR & PR Foundation Canada (system code 05C) provides a solution for a specific country, Canada.

Since Canada has two official languages, English and French, HR & PR Foundation Canada must be translated
into French.

75
JD Edwards EnterpriseOne Tools Chapter 10
Development Guidelines for Application Design Guide Understanding Translation Issues

76
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

11Understanding Acronyms and

Abbreviations

Acronyms and Abbreviations

Oracle maintains a list of acronyms and abbreviations that you can use in JD Edwards EnterpriseOne applications. You
must refer to this list before you use an acronym or abbreviation. If a specific acronym or abbreviation is not in this list,
request that your application development manager add it.

Several acronyms and abbreviations contain the ampersand (&) symbol. When you define a form control or menu that
includes an acronym or abbreviation that contains the ampersand symbol, you must enter two ampersands rather than
a single one. Otherwise, the runtime engine interprets the & as an underscore ( _ ).

This table is the list of acronyms and abbreviations that you can use in JD Edwards EnterpriseOne applications:

Acronym or Abbreviation Description

A/B or AB Address Book

A/P Accounts Payable

A/R Accounts Receivable

A/V According to Value

AAI Automatic Accounting Instruction

AAP Affirmative Action Planning

AB Aktiebolag (Sweden)

ABC Activity-Based Costing

ABI Application Binary Interface

ABM Activity-Based Management

ACD Automatic Call Distributor

ACE Adjusted Current Earnings

ACH Automated Clearing House

77
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

ACP Actual Contribution Percentage

ACP Average Contribution Percentage

ACRS Accelerated Cost Recovery System

AD&D Accidental Death and Dismemberment

ADA Americans with Disabilities Act

ADDL Additional

ADJ Adjustment

ADP Actual Deferral Percentage

ADR Assets Depreciation Range

AEC Architecture, Engineering, and Construction

AF Advanced Forecasting

AFE Authorization for Request

AFRA Average Freight Rate Assessment

AFS Available for Sale

AG Aktiengesellschaft (Germany)

AGI Adjusted Gross Income

AGM Auto Generate Master

AGVS Automated Guided Vehicle System

AIA American Institute of Architects

AIX Advanced Interactive Executive (IBM's proprietary version of UNIX)

AKA or aka Also Known As

78
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

Amt Amount

AMT Alternative Minimum Tax

AN Address Number

ANSI American National Standards Institute

AOQL Average Outgoing Quality Level

AP Accounts Payable

AP/C Agricultural Products, Crops

APA Advanced Price Analysis

APD Application Program Driver

API Air Position Indicator

API American Petroleum Institute

API Application Program Interface

APICS American Production and Inventory Control Society, Inc.

APPL Application

APR Annual Percentage Rate

AQL Acceptable Quality Level

AR Accounts Receivable

AS Agricultural Services

AS Application System

AS/RS Automatic Storage/Retrieval System

ASAP As Soon As Possible

79
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

ASCII American Standard Code for Information Interchange

ASI Application Specific Instructions

ASI Application Specific Instrument

ASN Advanced Ship Notice

ASP Auxiliary Storage Pool

ASTM American Society for Testing and Materials

ATM Automated Teller Machine

ATO Associated Text Output

ATO Assembly to Order

ATP Available to Promise

ATPU Available to Promise Unadjusted

ATRS American Tanker Rate Schedule

AU Actual Units

Avl Availability

AWOL Absent Without Leave or Absent Without Official Leave

B/D Barrels per Day

B/L Bill of Lading

BA Beginning Available

BA Budget Amount

BACS Bank Automated Clearing System

BASIC Business Application Software Introduction Class

80
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

BAU Beginning Available Unadjusted

BCI Billing Control Identification

BDA Business View Design Aid

BEF Belgian Francs

BEP Break-Event Point

BFOE Barrels of Fuel Oil Equivalent

BIPS Billion Instructions per Second

Blk Blank

BLOB Binary Large Object

bn Billion

BO Back Order

BOC Building Operating Costs

BOL Bill of Lading

BOM Bill of Materials

BP Business Partner

BPI Bits per Inch

BPS Bits per Second

BPT Bulk Product Transaction

Br Branch

Brn Branch

Brn/Plt Branch/Plant

81
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

BS&W Bottom Sediment and Water

BSFN Business Function

BSVW Business View

BTU British Thermal Unit

BTX Benzene, Toluene, and Xylene

BU Budget Units

BU Business Unit

C&F Cost and Freight

C/O or c/o Care of

C/R Cash Receipts

C/S Client/Server

CA Contract Administration

CAD Computer Assisted Design

CAE Common Applications Environment

CAE Computer-Aided Engineering

CAIT Computer-Aided Inspection and Test

CAM Common Area Maintenance

CAM Computer-Aided Manufacturing

CAP Computer Assisted Programming

CAT Category

CAPP Computer-Aided Process Planning

82
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

CASE Computer-Aided Software Engineering

CATP Cumulative Available to Promise

CBD Cash Before Delivery

CBO Cash Basis Only

CBT Computer Based Training

CC Cost Center

CCC Cycle Count Code

CCITT Consultative Committee for International Telephony and Telegraphy

CCQ Office de la construction du Quebec (French)

Cd Code

CD Certificate of Deposit

CD-ROM Compact Disc-Read Only Memory

CEO Chief Executive Officer

CFO Chief Financial Officer

CFPIM Certified as a Fellow in Production and Inventory Management

Chg Change

Chk Check

CID Computer-Integrated Distribution

Cie Compagnie (France)

CIF Central Information File

CIF Computer-Integrated Fax

83
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

CIF Cost, Insurance, and Freight

CIM Computer-Integrated Manufacturing

CIS Customer Information System

CISC Complex Instruction Set Computer

CL Control Language

CM Change Management

CM Corrective Maintenance

CMMS Computerized Maintenance Management Systems

Cmp Compensation

CMS Cost Management System

CNC Computer Numeric Control

Co Company

CO Change Order

COA Certificate of Analysis

COBRA Consolidated Omnibus Reconciliation Act

COBOL Common Business Oriented Language

COD Cash on Delivery

COFC Container on a Railroad Flatcar

COGS Cost of Goods Sold

COLA Cost-of-Living Adjustment

COLA Cost-of-Living Allowance

84
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

COLD Computer Output to Laser Disk

COM Computer Output to Microform

COM Component Object Model

COMMS Customer Oriented Manufacturing Management Systems

COO Chief Operating Officer

COQ Cost of Quality

COR Collision Repair

CORBA Common Object Request Broker

Core The central and foundational systems of JD Edwards EnterpriseOne software (Financials)

Corp Corporation

COS Corporation for Open Systems

CP Configurator Processing

CPA Certified Public Accountant

CPI or cpi Characters per Inch

CPI Consumer Price Index

CPI Continuous Process Improvement

CPIM Certified in Production and Inventory Management

CPM Critical Path Method

CPU Central Processing Unit

CR Change Request

CR or Cr Credit

85
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

CREDITEL CREDITEL (Credit Reporting Agency)

CRP Capacity Requirements Planning

CRP Conference Room Pilot

CRT Cathodic Ray Tube

CS Client/Server

CSC Client Service Coordinator

CSR Customer Service Representative

CSW Customer Service Workstation

CTD Cumulative Trauma Disorder

CTI Computer-to-Telephone Integration

CTI Computer Telephony Integration

CTO Chief Technical Officer

CTRL or Ctrl Control

CTRY Century

CUA Common User Access

Cum Cumulative Update

CUM Cubic Meter

CUR Currency Code

Curr Current

CVP Cost/Volume/Profit

D&B Dun & Bradstreet (Credit Reporting Agency)

86
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

DA Day

DASD Direct Access Storage Device

DBA Deductions, Benefits, and Accruals

DBA Doing Business As

DBMS Data Base Management System

DCE Distributed Computing Environment

DCF Discounted Cash Flow

DD Data Dictionary

DDE Dynamic Data Exchange

DDP Distributed Data Processing

DDS Data Description Specifications

DE Design Engineering

DEMO Demonstration

DFI Deposit Financial Institution

DFU Data File Utility

DIF Data Interchange Format

DIL Data Import Language

DIN Deutsche Industrie Norm

DISOSS Distributed Office Support System

DIST Distribution

DLL Dynamic Link Library

87
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

Dlt Delete

DNC Direct Numerical Control

DNS Do Not Spread

Do Ty Document Type

DOB Date-of-Birth

DOI Division of Interest

DPI or dpi Dots per Inch

Dpt Department

DR or Dr Debit

DREAM Writer Data Record Extraction and Management Writer

DRP Distribution Requirements Planning

DRP Distribution Resource Planning

DS Data Structure

DSO Days Sales Outstanding

Dsp Display

DSS Decision Support System

DSTR Data Structure

DT Document Type

Dta Data

DTF Demand Time Fence

Dup Duplication

88
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

DW DREAM Writer

DZ Dozen

E&P Earnings and Profits

E&O Expenses and Others

E.P. Expense Participation

Email Electronic Mail

E&OE Errors and Omissions Excepted

EA Each (Unit of Measure)

EA Ending Availability

EAC Estimate at Completion

EADT Everest Application Development Tool

EAP Employee Assistance Program

EBB Electronic Burst and Bind

EC Edit Code

EC European Community

ECM Engineering Change Management

ECN Engineering Change Notice

ECO Engineering Change Order

ECR Efficient Consumer Response

ECS Electronic Customer Support

ECS Energy and Chemical Systems

89
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

EDA Estimated Date Available

EDC Everest Development Center

EDI Electronic Data Interchange

EDP Electronic Data Processing

EE Employee

EEO Equal Employment Opportunity

EEOC Equal Employment Opportunity Commission

EFP Enterprise Facility Planning

EFT Electronic Funds Transfer

EFTS Electronic Funds Transfer System

EI Employee Involvement

EIC Earned Income Credit

EIN Employer's Identification Number

EIS Enterprise Information Systems

EIS Executive Information System

EM Equipment Management

EMEA Europe, Middle East, and Asia

EMS Environmental Management System

EOI Evidence of Insurability

EOJ End of Job

EOM End of Month

90
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

EOQ Economic Order Quantity

EP Expense Participation

EPOS or epos Electronic Point of Sale

EPS Earnings Per Share

EPSS Expert Performance Support System

EQ Equal To

EQP Equipment

ER Employer

ER Event Rule

ERISA Employee Retirement Income Security Act

ERPx Enterprise Requirements Planning Execution

ERR Error

ESOP Employee Stock Ownership Plan

ETC Estimate to Complete

ETO Engineer to Order

EVP Executive Vice-President

EVS Enumeration Verification System

Exc Exclude

EXW Ex Works

F & F or f & f Fixtures and Fittings

F/A Fixed Asset

91
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

FA Functional Acknowledgement

FAP Final Average Pay

FAS Final Assembly Schedule

FAS Free Alongside Ship

FASB Financial Accounting Standards Board

FASTR Financial Analysis Spreadsheet Tool and Report Writer

FCST Forecast

FCU Fax Control Unit

FDA Form Design Aid

FDP Fiscal Date Pattern

FED Federal Tax

FHA Federal Housing Administration

FHC Freight Handling Code

FICA Federal Insurance Contribution Act

FIFO First In, First Out

FIGS French, Italian, German, Spanish

FIT Federal Income Tax

FK Function Keys

FLSA Fair Labor Standard Act

FMC Flexible Machine Center

FMLA Family Medical Leave Act

92
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

FMS Flexible Manufacturing System

FOB Free on Board

FOQ Fixed Order Quantity

FPO Firm Planned Order

FR Financial Reporting

FREQ Frequency

FRF French Francs

FRS Federal Reserve System

FSA Flexible Spending Account

ft Foot

FTC Federal Trade Commission

FTE Federal Tax Entry

FTE Full-Time Employee

FTE Full-Time Equivalent

FTO Finish-to-Order

FTP File Transfer Protocol

FTZ Foreign Trade Zones

FUI Federal Unemployment Insurance

FUTA Federal Unemployment Tax Act

FWO Firm Work Order

FY Fiscal Year

93
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

FYI For Your Information

G&A General and Administrative Expenses

G/A General Accounting

G/L General Ledger

GAAP Generally Accepted Accounting Principles

GAO General Accounting Office

GBC General Building Contractor

GBP British Pounds

GE Greater Than or Equal To

gig Gigabyte (one billion bytes)

GIF Graphics Interchange Format

GL Glossary

GmbH Gesellschaft mit beschränkter Haftung (Germany)

GOSIP Government Open Systems Interconnect Profile

GST Goods and Services Tax (Canada)

GT Greater Than

GTE Gross Tax Exclusion

GUI Graphical User Interface

GUID Globally Unique Identifier (technical system codes)

H&S Health and Safety

HCE Highly Compensated Employee

94
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

HEX Hexadecimal

HLL High-Level Language

HQ Headquarters

HR Workforce Management

HRM Workforce Management

HS Hidden Selection

HT Hypertext

HTML Hypertext Markup Language

HTTP Hypertext Transfer Protocol

HVAC Heating, Ventilation, and Air Conditioning

I/O Input / Output Control

ICCC Inter Company Cost Center

ICD Identification Code Designator

ICH Inter Company Hub

ID Identification

ID Inter-Plant Demand

IDC Intangible Depletion Cost

IDL Interface Definition Language

IEEE Institute of Electrical and Electronic Engineers

IM Inventory Management

In Inch

95
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

Inc Include

Inc Incorporated

Inv Invoice

IOU I Owe You

IP Internet Protocol

IPL Initial Program Load

IPS Implementation Planning Session

IR In Receipt

IRA Individual Retirement Account

IRS Internal Revenue Service

ISO International Standards Organization

ISSN International Standard Serial Number

IT Information Technology

ITC Income Tax Credit

ITC Investment Tax Credit

ITD Inception-to-Date

Itm Item

J/E Journal Entry

JAD Joint Application Development

JC Job Cost

JCA Job Cost Accounting

96
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

JCB Job Cost Billing

JE Journal Entry

JF Join File

JIT Just-in-Time

JPO Java Persistent Object

JT Journal Type

JVI Joint Venture Interest

K Thousand

Kb Kilobyte (1,024 bytes)

KBG Knowledge-Based Generator

KK Kabushiki-Kaisha

L/C Letter of Credit

L/O Line/Order

LAN Local Area Network

lb Pound

LBO Leveraged Buyout

LC Landed Cost

LCL Less than a Carload

LD Level of Detail

LDA Local Data Area

LE Less Than or Equal To

97
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

LF Logical File

LIFO Last In, First Out

LIMIT Lot-Size Inventory Management Interpolation Technique

LIPL License Plate

LOA Leave of Absence

LOB Line of Business

LOD Level of Detail

LPG Liquid Petroleum Gas

LPI or lpi Lines per Inch

LRP Long Range Planning

LRS Loading Rack System

LSN Lot Serial Number

LT Ledger Type

LT Less Than

LT Line Type

Ltd Limited

LTD Life-to-Date

LTD Long Term Debt

LTD Long Term Disability

LTL Less than a Truckload

MACRS Modified Accelerated Cost Recovery System

98
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

MAD Mean Absolute Deviation

MAP Manufacturing Automation Protocol

MAPI Messaging Application Program Interface

MAS Management Advisory Services

Max Maximum

MB Megabyte (one million bytes)

MBD Mechanical Breakdown

MBO Management by Objectives

MC Method of Computation

MCI Media Control Interface

MDS Material-Dominated Scheduling

MDY Month, Day, Year

ME Manufacturing Engineering

meg or mega Megabyte (one million bytes)

Mfg Manufacturing

MI Machine Instruction

MI Manufacturing Instruction

MICR Magnetic Ink Character Recognition

MIL-SPEC Military Inspection Standard

Min Minimum

MIPS Millions of Instructions per Second

99
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

MIS Management Information System

Misc Miscellaneous

MMbpd Million Barrels per Day

MMS Manufacturing Management Systems

MMS Minerals Management Service

MNC Multinational Company

MNP Multinational Products

MO Month

MOD Method of Delivery

Mogas Motor Gasoline

MOQ Maximum Order Quantity

MOT Mode of Transportation

MPS Master Production Schedule

MRB Material Review Board

MRI Machine Readable Instructions

MRO Maintenance, Repair, and Operation Supplies

MRP Material Requirements Planning

MRP II Manufacturing Resource Planning

MRPx Materials, Resource, Planning, and Execution

MSDS Material Safety Data Sheet

Msg Message

100
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

MTD Month-to-Date

MTM Methods-Time Measurement

MTO Make-to-Order

MTOP Make-to-Order Product

MTS Make-to-Stock

MTSP Make-to-Stock Product

MURB Multiple Unit Residential Building

MWO Model Work Order

N&A Name and Address

N/A Not Available

N/S Name Search

NA Not Applicable

NACH National Automated Clearing House

NASDAQ National Association of Securities Dealers Automated Quotations

NBV Net Book Value

NC Numerical Control

NCSA National Center for Supercomputing Applications

NDT Nondiscrimination Test

NE Not Equal To

NER Named Event Rule (also called event rule business function)

NFS Network File System

101
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

NG Not Greater Than

NGM Netware Global Messaging

NIFO Next In, First Out

NIST National Institute for Standards and Technology

NL Not Less Than

NLM Netware Loadable Module

NNN Triple Net

No Number

NOA Net Operating Assets

NOL Net Operating Loss

NOR Notice of Readiness

NPBT Net Profit Before Taxes

NSF Non-Sufficient Funds

NT New Technology

NTE Not to Exceed

NTED No Touch Exchange of Dies

NV Naamloze Vennootschap (Holland)

NYSE New York Stock Exchange

O Option

O/T Overtime

OBJ Object

102
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

OCE Open Collaboration Environment

OCL Over Credit Limit

OCM Object Configuration Manager

OCR Optical Character Recognition

OD Organizational Development

ODBC Open Data Base Connectivity

OEE Overall Equipment Effectiveness

OEM Original Equipment Manufacturer

OH Overhead

OJT On-the-Job Training

OL Object Librarian

OLE Object Linking and Embedding

OLTP Online Transaction Processing

OM Object Map

OMB Office of Management and Budget

OMI Open Messaging Interface

OOP Out-of-Pocket

OP Option

OP Order Processing

Ops Seq No Operation Sequence Number

Or Ty Order Type

103
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

Org Organization

OS Open Systems

OS Operating System

OS&D Over, Short, and Damaged

OSF Open Systems Foundation

OSHA Occupational Safety and Health Act

OSI Open Systems Interconnection

OT Overtime

OTC Over-the-counter

OTED One Touch Exchange of Dies

oz Ounce

P & P or p & p Postage and Packing

P&L Profit and Loss

P&E Property and Equipment

P/B/A Planning/Budgeting/Allocations

P/E Price/Earnings

P/O Purchase Order

P/V Profit/Volume

pa Per Annum

PAC Production Activity Control

PACO Posting After Cutoff

104
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

PBCO Posting Before Cutoff

PBYE Posting Before Year End

PC Personal Computer

PCO Planned Change Order

PCS Personal Computer Support

PDBA Payments, Deductions, Benefits and Accruals

PDCA Plan-Do-Check-Action

PDL Program Design Language

PdM Predictive Maintenance

PDM Product Data Management

PDS Processor-Dominated Scheduling

PEC Posting Edit Code

PERT Program Evaluation and Revue Technique

PF Physical File

PFC Projected Final Cost

PFP Projected Final Profit

PFR Projected Final Revenue

PFS Process Flow Scheduling

PI Payment Instrument

PIF Program Information File

PLC Programmable Logic Controller

105
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

PLC Public Limited Company (United Kingdom)

PLO Planned Order

Plt Plant

PM Preventive Maintenance

PM Property Management

PN Period Number

PO Processing Option

PO Purchase Order

POB Post Out of Balance

POE Purchase Order Entry

POP Purchase Order Processing

POS Point of Sale

POSIX Portable Operating System Interface for Computer Environments

PPAT People, Places, and Things

PPB Part Period Balancing

PPBS Program-Planning-Budgeting System

PPD Prearranged Payments and Deposits

PPED Pay Period Ending Date

PPM Parts per Million

PPO Preferred Provider Organization

PPV Purchase Price Variance

106
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

PR Payroll

PR Public Relations

PS Pay Status

PSF Per Square Foot

PSI Pounds per Square Inch

PSIA Pounds per Square Inch Absolute

PSIG Pounds per Square Inch Gauge

PST Provincial Sales Tax (Canada)

PSW Project Strategy Workshop

PTD Period-to-Date

PTE Part-Time Employee

PTF Program Temporary Fix

PTM Payroll Tax Management

Pty Priority

PWO Plan Work Order

PYE Previous Year-End

PYEB Prior Year-End Balance

PYEC Prior Year-End Cumulative

PYEN Prior Year-End Net

Q&A Questions and Answers

QA Quality Assurance

107
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

QB Qualified Beneficiary

QBE Query by Example

QE Qualifying Event

QFD Quality Function Deployment

QM Quality Management

QO Quote Order

Qry Query

QTD Quarter-to-Date

Qty Quantity

R&D Research and Development

R/L Right/Left

R/O Required/Optional

R/V Reverse/Void

RA Revised Amount

RAD Rapid Application Development

RAM Random Access Memory

Rand Random

RCCP Rough Cut Capacity Planning

RDA Report Design Aid

RDBF Running Dollars Balance Format

RDM Relational Database Management

108
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

RDM Relational Document Management

RE Real Estate

Rec Record

REC Reverse Entry Control

Ref Reference

Rel Relationship

REP Rapidly, Economically, and Predictably

Rev Revenue

RF Radio Frequency

RFP Request for Proposal

RFQ Request for Quote

RI Residual Income

RiBa Ricevuta Bancaria

RISC Reduced Instruction Set Computer

RL Response Line

RL/SU Response Line/Software Update

Rmk Remark

ROA Return on Assets

ROE Record of Employment

ROI Return on Investment

ROM Read Only Memory

109
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

ROP Reorder Point

ROQ Reorder Quantity

RPC Remote Procedure Call

RPG Report Program Generator

RPM Residential Property Management

RPS Requirements Planning System

RQBF Running Quantity Balance Format

RRA Reserve Recognition Accounting

RRN Relative Record Number

RRP Resource Requirements Planning

RS RISC System

RT Record Type

RTP Return to Production

RU Revised Units

RUIA Railroad Unemployment Insurance Act

S & H or s & h Shipping and Handling

S/N Serial Number

S/O Sales Order

S.O. Sales Order

SA Société Anonyme (France)

SA Stand Alone

110
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

SAA Systems Application Architecture

SAR Software Action Request

SARA Superfund Amendment Reauthorization Act

SAW Server Administration Workbench

SB Service Billing

SBL Subledger

SBQ Standard Batch Quantity

SC Status Code

SCC Service Class Code

SCSI Small Computer Systems Interface

SDA Screen Design Aid

SDI State Disability Insurance

SDQ Shipping, Destination, and Quantity

SEC Securities and Exchange Commission

SEC Standard Entry Class

Seq Sequence

SEU Source Entry Utility

SFAS Statement of Financial Accounting Standards

SFC Shop Floor Control

SFL Subfile

Sfx Suffix

111
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

SIA Single Item Authorization

SIC Standard Industry Classification

SIG Special Interest Group

SIN Social Insurance Number

SIT State Income Tax

SKU Stocking Keeping Unit

SKU Stockkeeping Unit

Sls Sales

SMAC Standard Maintenance Agreement Contract

SME Subject Matter Expert

SMED Single Minute Exchange of Dies

SMF Standard Message Format

SMS Shipper Management System

SNA Systems Network Architecture

SNADS Systems Network Architecture Distribution Services

SO Sales Order

SOE Sales Order Entry

SOP Sales Order Processing

SOP Statement of Position

SOQ Suggested Order Quantity

SP Service Provider

112
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

SpA Societá per Azioni (Italy)

SPC Statistical Process Control

Specs Specifications

SPI System Provided Interface

SPRI Société de Personnes à Responsibilité Limitée (Belgium)

SPT Shortest Process Time Rule

SQC Statistical Quality Control

SQL (Sequel) Structured Query Language

SRM Scheduled Routine Maintenance

SRV Solutions, Relationships, Value

SSN Social Security Number

STAR Spreadsheet Tool For Asset Reporting (Fixed Asset Report Writer)

Std Standard

STD Short-Term Disability

SUI State Unemployment Insurance

SVH Sick Days, Vacation, Holidays

SVO Service Order

SVR Software Versions Repository

SWIFT Society for Worldwide Interbank Financial Telecommunications

Sy System

SYD Sum-of-the-Years'-Digits

113
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

T&M Time and Materials

T/B Trial Balance

T/E Time Entry

TA Time Accounting

TAM Table Access Manager

TBLE Table

TC Table Conversion

TCOS Technical Committee on Operating Systems

TCP/IP Transmission Control Protocol/Internet Protocol

TDA Table Design Aid

TE Time Entry

TEI Total Employee Involvement

TER Table Event Rule

TI Type of Input

Time Last Upd Time Last Updated

TL Truckload

TM Translation Manager

TOC Table of Contents

TOP Technical/Office Protocol

TPC Transaction Processing Council

TPM Total Productive Maintenance

114
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

TPOP Time-Phased Order Point

TQC Total Quality Control

TQE Total Quality Engineering

TQM Total Quality Management

TRW TRW (Credit Reporting Agency)

TT Translation Tools

U/M Unit of Measure

UBE Universal Batch Engine

UCIS Utility of Customer Information System

UDC User Defined Code

UDD User Defined Depreciation

UFC Universal File Converter

UFO Unidentified Foreign Object

UK United Kingdom

ULI Urban Land Industry

UM or Um Unit of Measure

UOM Unit of Measure

UPC Universal Product Code

UPD or Upd Update

UPS Uninterrupted Power Supply

UQF Untested Quick Fix

115
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

URL Uniform Resource Locators

USD United States Dollars

VAN Value Added Network

VAT Value Added Tax

VCF Volume Correction Factor

Vchr Voucher Journal

VD Video Display

VDT Video Display Terminal

VDU Video Display Unit

VETS-100 Veterans Employment

VI Viscosity Index

VIN Vehicle Identification Number

VLCC Very Large Crude Carrier

VMI Vendor Managed Inventory

VO Vocabulary Overrides

VOL or vol Volume

VP Vice-President

VRS Vendor Release Scheduling

VRU Voice Recognition Unit

VS Vendor Scheduling

VTX Video Text

116
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

W/ or w/ With

W&M Weights and Measures

W/C Work Center

W/H or w/h Withholding

W/I or w/i Within

W/O or w/o Without

W/O Work Order

W/Tax Withholding Tax

W/W JD Edwards World Writer

W-2 Wage and Tax Statement

W-4 Employee's Withholding Allowance Certificate

W-9 Exception Report

WACO Way After Cutoff

WAN Wide Area Network

WARN Warning

WB Workbench

WBS Work Breakdown Structure

WCA Workmen's Compensation Act

WF Work File

WF Workflow

WIP Work in Process

117
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

Wk Week

WLC Warehouse, Location, Cost Center

WM Warehouse Management

WMS Warehouse Management System

WO Work Order

WOP Work Order Processing

WORM Write Once, Read Many

WPT Windfall Profit Tax

WPUM Weight per Unit of Measure

WRN Warning

WRT Write

WTD Week-to-date

WW Who's Who?

WW JD Edwards World Writer

WWW JD Edwards World Wide Web

WYSIWYG What You See Is What You Get

X Cross

X Phone Extension

X-Ref Cross Reference

XO Crossover

Y/N Yes/No

118
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

Acronym or Abbreviation Description

yd Yard

YE Year End

YLD or yld Yield

YR Year

YTD Year to Date

ZIP Zone Improvement Plan (Postal Code)

119
JD Edwards EnterpriseOne Tools Chapter 11
Development Guidelines for Application Design Guide Understanding Acronyms and Abbreviations

120
JD Edwards EnterpriseOne Tools Chapter 12
Development Guidelines for Application Design Guide Understanding Field Sizes

12 Understanding Field Sizes

Field Sizes
The JD Edwards EnterpriseOne system maintains a list of field names and corresponding alias examples that represent
commonly used data types that appear in a form. The Bs represent the number of characters that alphabetical fields can
contain. For example, the field MCU (Cost Center) enables you to enter ABCDEFGHIJKL. The number of 8s represents
the same thing for numeric fields. For example, the field ICU (Batch Number) enables you to enter 12345678.

The size column that precedes the B column refers to the size that the field should be in design so that you have enough
room to enter and display the data correctly. For example, 133 is the correct size for the Cost Center Details field.

This table provides guidelines for placing and sizing controls:

Category Alias Description Application B's 8's

Field Location

Branch/Plant *MCU* Any branch/ Top-right 12

plant field corner

Address AN8 Any Address 88 8

Number Number field,
including
internal and
external
numbers

Date DATE Any date field 88/88/8888

Time TIME Any time field 88:88:88

UDC UDC 1 - Character 1

UDC UDC 10 - Character 10

UDC UDC 2 - Character 2

UDC UDC 3 - Character 3

UDC UDC 4 - Character 4

UDC UDC 8 - Character 8

Amount AEXP Extended Cost After Unit Cost 15

121
JD Edwards EnterpriseOne Tools Chapter 12
Development Guidelines for Application Design Guide Understanding Field Sizes

Category Alias Description Application B's 8's

Field Location

Company CO Company 5

Amount CRR Currency 15

Exchange Rate

Document DOC* Document 8

Number

Document DCT* Document After Doc 2

Type Number/No
desc.

Document KCO* Key Company After Doc 5

Type/No desc.

Location LOCN Location 20

Location LOTN Lot Number After LOCN 30

Location TKID Bulk - Tank ID 8

Quantity TRQT Quantity 15

Item Number UITM Item Number - Left with desc. 26

Unknown after

Amount UNCS Unit Cost Before 15

Extended
Amount

Density DEND Density After TEMP 8

Density Type DNTP Density Type After DEND/No 1

desc.

Pressure VAPP Vapor Pressure After DETP 15

Unit of PREU Pressure UOM After VAPP/No 2

Measure desc.

Temperature DETP Density After DEND 8

Temperature

122
JD Edwards EnterpriseOne Tools Chapter 12
Development Guidelines for Application Design Guide Understanding Field Sizes

Category Alias Description Application B's 8's

Field Location

Temperature DTPU Density After DETP/No 1

Type Temperature desc.
Type

Temperature LPGV LPG Vapor After VAPP 8

Temperature

Temperature TPU1 Temperature After LPGV/No 1

Type Type desc.

Temperature TEMP Temperature 8

Temperature STPU Temperature After TEMP/No 1

Type Type desc.

Volume LIQV Liquid Volume 15

Unit of BUMx UOM After Vol/ No 2

Measure desc.

Correction VCF Volume 7

Factor Correction
Factor

Weight LIQW Liquid Weight 15

Volume AMBR Ambient 15

Volume

Volume VAPV Vapor Volume 15

Volume OVOL Other Volume 15

Quantity STUM Stock Total Not normally 15

on a form

Quantity STOK Stock Volume After AMBR 15

Weight WGTR Weight Result After STOK 15

Line Number JELN Journal Entry 7

Line Number

Batch Number ICU Batch Number 8

123
JD Edwards EnterpriseOne Tools Chapter 12
Development Guidelines for Application Design Guide Understanding Field Sizes

Category Alias Description Application B's 8's

Field Location

User ID USER User ID 10

Program ID PID Program ID 10

124
JD Edwards EnterpriseOne Tools Chapter 13
Development Guidelines for Application Design Guide Glossary

13 Glossary

activity rule
The criteria by which an object progresses from one given point to the next in a flow.

add mode
A condition of a form that enables users to input data.

BIP
Business Intelligence Publisher, formerly known as XMLP.

jargon
An alternative data dictionary item description that JD Edwards EnterpriseOne appears based on the product code of
the current object.

media storage object

Files that use one of the following naming conventions that are not organized into table format: Gxxx, xxxGT, or GTxxx.

RTF
Rich Text Format, a Microsoft Word file format.

125
JD Edwards EnterpriseOne Tools Chapter 13
Development Guidelines for Application Design Guide Glossary

specification
A complete description of a JD Edwards EnterpriseOne object. Each object has its own specification, or name, which is
used to build applications.

trigger
One of several events specific to data dictionary items. You can attach logic to a data dictionary item that the system
processes automatically when the event occurs.

vocabulary override
An alternate description for a data dictionary item that appears on a specific JD Edwards EnterpriseOne form or report.

XML
Extensible Markup Language (XML) is a general-purpose specification for creating custom markup languages. XML
is classified as an extensible language because it allows you to define your own elements. Its primary purpose is to
facilitate the sharing of structured data across different information systems, particularly via the Internet. XML is used
both to encode documents and to serialize data.

XMLP
XML Publisher, also called Business Intelligence Publisher (BIP). Oracle XML Publisher is a template-based publishing
solution delivered with Oracle E-Business Suite, PeopleSoft Enterprise, and JD Edwards EnterpriseOne. It provides a
flexible and robust approach to report design and publishing by integrating familiar desktop word processing tools
with existing data reporting. XML Publisher leverages standard, well-known technologies and tools, so you can rapidly
develop and maintain custom report formats.

XPath
XPath, the XML Path Language, is a query language for selecting nodes from an XML document.

126
JD Edwards EnterpriseOne Tools Chapter 13
Development Guidelines for Application Design Guide Glossary

XSL
eXtensible Stylesheet Language is a family of transformation languages which enables you to describe how files
encoded in the XML standard are to be formatted or transformed.

Z table
A working table where non-JD Edwards EnterpriseOne information can be stored and then processed into JD Edwards
EnterpriseOne. Z tables also can be used to retrieve JD Edwards EnterpriseOne data. Z tables are also known as
interface tables.

127
JD Edwards EnterpriseOne Tools Chapter 13
Development Guidelines for Application Design Guide Glossary

128
 JD Edwards EnterpriseOne Tools | Index | 129

Index
A constant text
in reports 8
abbreviations constants
acronyms 77 use of in report viewing 8
for translation 69 control
in reports 8 defined 3
about object naming conventions 11 control limitations
acronyms for maximum performance 35
for translation 69 currency
additional features advantages 59
currency 59 build trigger options 60
codeexchange ratebase 6
creating a currency conversion trigger 63
B currency implementation 59
bi publisher reports currency modeCRRM 6
company logo 44 displayed in grid 6
confidential label 47 multiple currencies 6
end of report indication 55 single currency 6
layout editor guidelines 41 standards for all reports 9
layout types 41 understanding 59
multiple row tables 49 when currency processing is OFF 6
no data indication 55 when to hide fields 6
overview 39 working with 60
page attributes 42 currency conversion trigger. creating 63
page break 56 currency fields
page footer example 48 currencyexchange ratebaseforeign 6
page header and footer 42 in reports 9
page header example 48 currency implementation 60
page numbering 46 Currency process. table event rules 60
paragraph setting 53
performance guidelines 58 D
report data 48
report date and time 45 data dictionary items
report example 56 naming conventions 15
report name in footer 46 data dictionary naming conventions 14
report subtitles 45
report title 44
single data field 49
E
tab use 54 event rule variables
table borders 52 used as work fields 35
table cell margin 51 event rules
translation guidelines 57, 57 currency processing 60
UBE guidelines 39 currencybuildtriggers options 60
xpath usage 58
build triggers option 60
business view columns F
for maximum performance 35
field, size for translation 69
buttons
fields
for translation 69
currency 6
filter
C fiscal year 5
filter fields
coexistence ledger and sub-ledger type 5
indices and logicals 19 fiscal year filter
issues addressed in this guide 14 example of use 5
column space foreign currency 59
between report columns 8 Form Design Aid 62
columns forms
limitation 35 General Accounting Constants 62, 62
conditional sections Object Management Workbench 62
location of 8 System Setup 62
 JD Edwards EnterpriseOne Tools | Index | 130

G R
General Accounting Constants form 62, 62 report appearance
guidelines 8
report columns
H appearance of 8
handle request space between 8
event rule variable 25 report definition guidelines 41
how table event rules work with currency processing 60 report variables
Hungarian notation in report rendering 8
example of 25 report viewing
guidelines 8
reports
I BI Publisher report guidelines 39
grand total 8
indices and logicals
orientation 8
coexistence 19
paper size 8
interactive applications
printer 8
guidelines 3
total amounts 8
international currency 59
use of page footers 8
invisible report sections
use of report footers 8
group section 8
report variables 8
S
L section names
arranging for report rendering 24
ledger and sub-ledger type
description 24
used as filter fields 5
program name 24
Stop Processing system function
M for maximum performance 35
system codes 13
M((amp))D System Setup form 62
placement of Branch/Plant 6, 6
static text for MCU, MMCU 5
Math_Numeric T
currency 60
table conversions
currency implementation 60
name 29
table I/O
N event rule variable 25
templates
naming conventions 11 category codes 22
data dictionary items 15 function use 22
forms 21 name 22, 23
object 11 temporary data storage
table conversions 29 for maximum performance 35
text variables 26 text variable
next number for translation 69
do not preload 4 use of 5
translation
O components eligible for translation 65
trigger
Object Management Workbench form 62 build triggers option 60
object naming conventions 11 creating a currency conversion trigger 63

P U
performance considerations UBEs for report definitions 40
all forms 35 upper and lower case
header detail 36 use of in reports 8
headerless detail 36
preloading next number 4 V
versions naming conventions
called from menuduring installmaster versions 21
XJDE 21
 JD Edwards EnterpriseOne Tools | Index | 131

ZJDE 21
viewing
reports 8
viewing report sections
comment 8
viewing reports
conditional sections 8
invisible report sections 8

X
xe ((amp)) symbol
use of when defining controls 77
XJDE
use of 21

Z
ZJDE
use of 21
JD Edwards EnterpriseOne Tools | Index | 132