Skip Headers
JD Edwards EnterpriseOne Tools Development Guidelines for Application Design Guide
Release 9.1.x

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

Go to previous page
Previous
PDF · Mobi · ePub

Index

A  B  C  D  E  F  G  H  I  J  L  M  N  O  P  R  S  T  U  V  W  X  Z 

A

abbreviations
acronyms, 11.1
for translation, 10.3
in reports, 2.2.2
about object naming conventions, 3.1
acronyms
for translation, 10.3
additional features
currency, 9
applications
naming conventions, 3.5.5

B

bi publisher reports
company logo, 8.3.3.2
confidential label, 8.3.3.8
data object alignment, 8.3.4.12
end of report indication, 8.3.4.15
layout editor guidelines, 8.3
layout types, 8.3.1
multiple row tables, 8.3.4.4
no data indication, 8.3.4.16
overview, 8.1
page attributes, 8.3.2
page break, 8.3.4.17
page footer example, 8.3.3.9
page header and footer, 8.3.3
page header example, 8.3.3.9
page numbering, 8.3.3.6
paragraph setting, 8.3.4.13
performance guidelines, 8.5
report data, 8.3.4
report date and time, 8.3.3.5
report example, 8.3.4.18
report name in footer, 8.3.3.7
report subtitles, 8.3.3.4
report title, 8.3.3.3
single data field, 8.3.4.3
tab use, 8.3.4.14
table borders, 8.3.4.11
table cell margin, 8.3.4.10
translation guidelines, 8.4, 8.4
UBE guidelines, 8.2
xpath usage, 8.5
build triggers option, 9.1.3.1
business function
naming conventions, 3.8.2
business function data structures
naming conventions, 3.8.2.1
business view columns
for maximum performance, 6.1
business views
naming conventions, 3.5.2
buttons
for translation, 10.3

C

coexistence
indices and logicals, 3.5.1.3
issues addressed in this guide, 3.2
column space
between report columns, 2.2.2
columns
limitation, 6.1
conditional sections
location of, 2.2.3
constant text
in reports, 2.2.2
constants
use of in report viewing, 2.2.3
control
defined, 2.1.1
control limitations
for maximum performance, 6.1
cover page
report, 2.2.4
currency
advantages, 9.1.2
build trigger options, 9.1.3.1
codeexchange ratebase, 2.1.2.6
creating a currency conversion trigger, 9.2.6
currency implementation, 9.1
currency modeCRRM, 2.1.2.6
displayed in grid, 2.1.2.6
guidelines for all forms, 2.1.2.7
guidelines for Find/Browse forms, 2.1.2.6
multiple currencies, 2.1.2.6
setting up currency conversion, 9.2.4
showing currency-sensitive controls, 9.2.5
single currency, 2.1.2.6
standards for all reports, 2.2.6
understanding, 9
when currency processing is OFF, 2.1.2.6
when to hide fields, 2.1.2.6
working with, 9.1.3
currency conversion trigger. creating, 9.2.6
currency conversion, setting up, 9.2.4
currency fields
currencyexchange ratebaseforeign, 2.1.2.7
in reports, 2.2.6
currency implementation, 9.1.3
Currency process. table event rules, 9.1.3.2

D

data dictionary items
naming conventions, 3.2.1.1
data dictionary naming conventions, 3.2
data item
name, 3.2.2
processing option, 3.3
row description, 3.2.5
table I/O, 3.4
data item description
defined, 3.2.4
data item prefix, 3.5.1.1
and Business Partners, 3.5.1.1
table design, 3.5.1.1
development guidelines
interactive application forms, 2.1.2
DialogIsInitialized
revisions log, 7.1

E

error handling, 2.2.7
event rule variables
naming conventions, 3.8
used as work fields, 6.1
event rules
currency processing, 9.1.3.2
currencybuildtriggers options, 9.1.3.1
external data dictionary items
naming conventions, 3.2.1.1
external developer considerations
for business views, 3.5.2.2
for menus, 3.8.5.1
for tables, 3.5.1.4

F

field, size for translation, 10.3
fields
currency, 2.1.2.7
filter
fiscal year, 2.1.2.1
filter fields
ledger and sub-ledger type, 2.1.2.1
financials
guidelines for all forms, 2.1.2.2
fiscal year filter
example of use, 2.1.2.1
font
standard for reports, 2.2.1
foreign currency, 9
Form Design Aid, 9.2.3
form guidelines
applicable to all forms, 2.1.2.1
form interconnections
naming conventions, 3.5.5.2
forms
General Accounting Constants, 9.2.3, 9.2.4
naming conventions, 3.5.5.1
Object Management Workbench, 9.2.3
System Setup, 9.2.3
forms development guidelines for interactive application form, 2.1.2

G

General Accounting Constants form, 9.2.3, 9.2.4
grid variable
work field, 7.1

H

handle request
event rule variable, 3.8.1
how table event rules work with currency processing, 9.1.3.2
Hungarian notation
example of, 3.8.1

I

indices
naming conventions, 3.5.1.3
indices and logicals
coexistence, 3.5.1.3
InitializeSection
revisions log, 7.1
interactive applications
guidelines, 2.1.1
international currency, 9
invisible report sections
group section, 2.2.3
report variables, 2.2.3

J

jargon, 3.1.4
joined views
naming conventions, 3.5.2.1

L

ledger and sub-ledger type
used as filter fields, 2.1.2.1
localization
guidelines for all forms, 2.1.2.5

M

M&D
placement of Branch/Plant, 2.1.2.4, 2.1.2.4
static text for MCU, MMCU, 2.1.2.4
manufacturing and Distribution
guidelines for all forms, 2.1.2.4
Math_Numeric
currency, 9.1.3.2
currency implementation, 9.1.3
media objects
naming conventions, 3.8.4
menus
naming conventions, 3.8.5

N

naming conventions, 3.1
applications, 3.5.5
business functions, 3.8.2
business views, 3.5.2
data dictionary items, 3.2.1.1
data structures, 3.8.2.1
event rule variables, 3.8
external data dictionary items, 3.2.1.1
for objects, 3.1.1
form interconnections, 3.5.5.2
forms, 3.5.5.1, 3.5.5.1
indices, 3.5.1.3
joined views, 3.5.2.1
media objects, 3.8.4
menus, 3.8.5
object, 3.1
processing option, 3.3
processing option data structure, 3.5.3.1
purge table, 3.7
table conversions, 3.8.6
table I/O data item, 3.4
tables, 3.5.1
text variables, 3.8.1.1
workflow data structures, 3.8.3.1
workflow process, 3.8.3
next number
do not preload, 2.1.2.1

O

Object Management Workbench form, 9.2.3
object naming conventions, 3.1

P

performance considerations
all forms, 6.1
header detail, 6.3
headerless detail, 6.3
preloading next number, 2.1.2.1
processing option
elements, 3.5.3
naming conventions, 3.3
processing option data item, 3.3
processing options
on a task, 4.2
program and file names, 3.1.3
graphic, 3.1.3
purge table
naming conventions, 3.7

R

report
cover page, 2.2.4
report appearance
guidelines, 2.2.2
report columns
appearance of, 2.2.2
space between, 2.2.2
report definition guidelines, 8.2.2
report variables
in report rendering, 2.2.3
report viewing
guidelines, 2.2.3
reports to file, 2.2.5
reports to output, 2.2.4
reports
BI Publisher report guidelines, 8.1
company name, 2.2.1
error listings, 2.2.7
grand total, 2.2.2
orientation, 2.2.2
page information, 2.2.1
paper size, 2.2.2
printer, 2.2.2
run time, 2.2.1
titles, 2.2.1
total amounts, 2.2.2
use of page footers, 2.2.2
use of report footers, 2.2.2
versions description, 2.2.1
reports to file, 2.2.5
reports to output, 2.2.4
page header, 2.2.4
what a common report contains, 2.2.4
revisions log
use of, 7.1
row description
data item, 3.2.5

S

section names
arranging for report rendering, 3.6
description, 3.6
program name, 3.6
standards that are set up automatically
in batch applications, 2.2.1
Stop Processing system function
for maximum performance, 6.1
system codes, 3.1.2
JD Edwards EnterpriseOne, 3.1.2
System Setup form, 9.2.3

T

table conversions
name, 3.8.6
table I/O
data item, 3.4
event rule variable, 3.8.1
tables
naming conventions, 3.5.1
task processing options
for interactive applicationsfor batch applications, 4.2
templates
category codes, 3.5.6
function use, 3.5.6
name, 3.5.6, 3.5.7
temporary data storage
for maximum performance, 6.1
text
standard for reports, 2.2.1
text overrides, 3.1.4
text variable
for translation, 10.3
use of, 2.1.2.1, 7.1
translation
components eligible for translation, 10.1
triggers, 10.5
translation guidelines, 10.3
trigger
build triggers option, 9.1.3.1
creating a currency conversion trigger, 9.2.6

U

UBEs for report definitions, 8.2.1
upper and lower case
use of in reports, 2.2.2

V

versions
name, 3.5.4
versions naming conventions
called from menuduring installmaster versions, 3.5.4
report, 3.5.4
XJDE, 3.5.4
ZJDE, 3.5.4
viewing
reports, 2.2.3
viewing report sections
comment, 2.2.3
viewing reports
conditional sections, 2.2.3
invisible report sections, 2.2.3

W

work field
using grid variable, 7.1
workflow data structures
naming conventions, 3.8.3.1
workflow process
naming conventions, 3.8.3
workforce management
guidelines for all forms, 2.1.2.3

X

xe & symbol
use of when defining controls, 11.1
XJDE
use of, 3.5.4

Z

ZJDE
use of, 3.5.4