JD Edwards EnterpriseOne Tools

Development Tools: Data Dictionary Guide

Release 8.98 Update 4

E14703-02

March 2011

JD Edwards EnterpriseOne Tools Development Tools: Data Dictionary Guide, Release 8.98 Update 4

E14703-02

Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

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, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

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 Xeon 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, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark licensed through X/Open Company, Ltd.

This software or hardware and documentation may provide access to or information on 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. 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.

Contents

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

1 Introduction to JD Edwards EnterpriseOne Data Dictionary

- 1.1 Data Dictionary Overview

- 1.2 Data Dictionary Implementation

2 Understanding the Data Dictionary

- 2.1 Data Dictionary Concepts

- 2.2 Data Dictionary and Data Dictionary Item Storage

- 2.3 Data Dictionary Triggers

- 2.3.1 Data Dictionary Triggers Overview

- 2.3.2 Default Value Triggers

- 2.3.3 Visual Assist Triggers

- 2.3.4 Edit Rule Triggers

- 2.3.5 Display Rule Triggers

- 2.3.6 Next Number Triggers

- 2.3.6.1 IBM Modulus 11 Self-Check Algorithm

- 2.3.7 Smart Field Triggers

3 Defining a Data Dictionary Item

- 3.1 Common Fields Used in This Chapter

- 3.2 Creating a Data Dictionary Item

- 3.2.1 Forms Used to Create a Data Dictionary Item

- 3.2.2 Creating a Data Dictionary Item

- 3.3 Adding Glossary Text for Languages

- 3.3.1 Form Used to Add Glossary Text for Languages

- 3.3.2 Adding Glossary Text for Languages

- 3.4 Defining Jargon and Alternate Language Terms

- 3.4.1 Understanding Jargon and Alternate Language Terms

- 3.4.2 Forms Used to Define Jargon and Alternate Language Terms

- 3.4.3 Changing Row and Column Text for All Applications

- 3.4.4 Defining Jargon

- 3.4.5 Updating a Data Item for Languages

4 Adding Tips of the Day

- 4.1 Understanding Tips of the Day

- 4.1.1 Prerequisite

- 4.2 Working with Tips of the Day

- 4.2.1 Forms Used to Work with Tips of the Day

- 4.2.2 Adding Tips of the Day to an Object

Glossary

Index

Preface

Welcome to the JD Edwards EnterpriseOne Tools Development Tools: Data Dictionary Guide.

Audience

This guide is intended for developers and technical consultants who are responsible for customizing and creating data dictionary items for JD Edwards EnterpriseOne.

This guide assumes you have a working knowledge of the following:

• The principles and customary practices of your business area.

• Computer desktop application usage and terminology.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/us/corporate/accessibility/index.html.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/support/contact.html or visit http://www.oracle.com/accessibility/support.html if you are hearing impaired.

Related Documents

You can access related documents from the JD Edwards EnterpriseOne Release Documentation Overview pages on My Oracle Support. Access the main documentation overview page by searching for the document ID, which is 876932.1, or by using this link:

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=876932.1

To navigate to this page from the My Oracle Support home page, click the Knowledge tab, and then click the Tools and Training menu, JD Edwards EnterpriseOne, Welcome Center, Release Information Overview.

This guide contains references to server configuration settings that JD Edwards EnterpriseOne stores in configuration files (such as jde.ini, jas.ini, jdbj.ini, jdelog.properties, and so on). Beginning with the JD Edwards EnterpriseOne Tools Release 8.97, it is highly recommended that you only access and manage these settings for the supported server types using the Server Manager program. See the Server Manager Guide on My Oracle Support.

Conventions

The following text conventions are used in this document:

Convention

Meaning

Bold

Indicates field values.

Italics

Indicates emphasis and JD Edwards EnterpriseOne or other book-length publication titles.

Monospace

Indicates a JD Edwards EnterpriseOne program, other code example, or URL.

1 Introduction to JD Edwards EnterpriseOne Data Dictionary

This chapter contains the following topics:

- Section 1.1, "Data Dictionary Overview"

- Section 1.2, "Data Dictionary Implementation"

1.1 Data Dictionary Overview

The Data Dictionary in Oracle JD Edwards EnterpriseOne Tools is used to create or modify Data Dictionary items for use in JD Edwards EnterpriseOne applications. Data Dictionary items not only define and describe data, but they also can trigger the runtime engine to react or process in certain ways by nature of their types. Furthermore, online help, error messages, term substitutions for different industries, and translations are all tied to Data Dictionary items.

1.2 Data Dictionary Implementation

The following implementation steps need to be performed before working with the Data Dictionary:

1. Configure Object Management Workbench.
See "Configuring JD Edwards EnterpriseOne OMW" in the JD Edwards EnterpriseOne Tools Object Management Workbench Guide.

2. Configure Object Management Workbench user roles and allowed actions.
See "Configuring User Roles and Allowed Actions" in the JD Edwards EnterpriseOne Tools Object Management Workbench Guide.

3. Configure Object Management Workbench functions.
See "Configuring JD Edwards EnterpriseOne OMW Functions" in the JD Edwards EnterpriseOne Tools Object Management Workbench Guide.

4. Configure Object Management Workbench activity rules.
See "Configuring Activity Rules" in the JD Edwards EnterpriseOne Tools Object Management Workbench Guide.

5. Configure Object Management Workbench save locations.
See "Configuring Object Save Locations" in the JD Edwards EnterpriseOne Tools Object Management Workbench Guide.

6. Set up default location and printers.
See JD Edwards EnterpriseOne Tools Development Tools: Report Printing Administration Technologies Guide.

2 Understanding the Data Dictionary

This chapter contains the following topics:

- Section 2.1, "Data Dictionary Concepts"

- Section 2.2, "Data Dictionary and Data Dictionary Item Storage"

- Section 2.3, "Data Dictionary Triggers"

This chapter discusses Oracle's JD Edwards EnterpriseOne Data Dictionary (DD) concepts, where data dictionary items are stored, and the different types of DD triggers.

2.1 Data Dictionary Concepts

A data dictionary item identifies a unit of information. The DD item definition defines how the item can be used and includes information such as the type of item and its length. Most of the fields in JD Edwards EnterpriseOne applications are actually DD items. At runtime, JD Edwards EnterpriseOne applications (such as those in Accounts Payable or Sales Order Management) access the DD and reflect the assigned attributes in any of these fields:

Just as a dictionary contains word definitions, the JD Edwards EnterpriseOne DD is a central repository that contains all of the database data items that are used in all of the JD Edwards EnterpriseOne applications. Each data item in the dictionary is defined by a number of attributes that describe parameters such as the data type, data length, and so forth. The system performs automatic error checking against these parameters when users enter values during runtime.

Additionally, DD item attributes define how the DD item should appear when placed on a form or report, including its title and whether to display default values. Also, all DD items have an associated glossary in which you can enter text. If the DD item is included on a form, this text appears when the user presses F1, and so is sometimes referred to as F1 Help. The system also displays the glossary text under certain circumstances, such as for the content of an error message.

DD items are the foundation of JD Edwards EnterpriseOne objects. You create DD items for use as fields on a form, columns in a table, fields in a business view (BV), members of a data structure, and fields on a report. When you access applications from a fat client, the applications access the DD at runtime and immediately reflect modifications to DD item attributes such as field descriptions, column headings, decimals, and edit rules. Once accessed the DD items are stored on the workstation in a permanent cache. This is done for performance, to decrease the traffic to the server for the DD information. On the HTML client the DD is stored as serialized objects with the rest of the application specification information. DD items must be regenerated if changed for the applications to know about the modification.

This is a list of the parameters that define DD items:

- Display Decimals

- File Decimals

- Alpha Description

- Data Type

- Size

- Glossary

- Allow Blank Entry *

- Upper Case Only *

- All Triggers *

- Row and Column Headings *

The application retrieves field information from the DD. Fields marked with an asterisk (*) can be overridden in Form Design Aid (FDA) and Report Design Aid (RDA). In these instances, the application retrieves the overrides, if any exist.

Create new DD items and view existing ones with the Object Management Workbench (OMW) or the Data Dictionary Application program (P92001). After you create a DD item, use the Data Dictionary Application program to define jargon and language translations for it.

Use the Data Dictionary Application to create, view, and update attributes for DD items. You can copy a DD item with similar attributes and modify it for your specific needs. This method can be quicker and easier than creating a new DD item, but if you use this method you must distinguish between the original and the copy. You distinguish between them by modifying the alias.

Changing the type and attributes of a DD item might affect how the data is stored and cause discrepancies among records.

Note:
The DD does not verify whether a DD item is used by an application when you delete it. If you delete a DD item that an application uses, that application will fail.

Glossary items are items that cannot be attributes in tables. Glossary items are typically used as information messages.

Error messages used in JD Edwards EnterpriseOne are stored as DD items. Error messages do not use all the fields that are required for regular DD items, so you need to use the DD glossary item application to display error messages.

2.2 Data Dictionary and Data Dictionary Item Storage

This section discusses data dictionary and data dictionary item storage.

DD items reside on enterprise (logic) servers in relational database tables. Workstations retrieve from the publisher DD (the relational database tables) only those DD items that are necessary for the applications being used. This occurs when you use an application for the first time after installing JD Edwards EnterpriseOne. The DD information is stored on each workstation in a permanent cache under the same local path code and spec directory as these global tables:

- glbltbl.xdb (references for the data)

- glbltbl.ddb (the DD items)

See Also:

- "Administering the Data Dictionary" in the JD Edwards EnterpriseOne Tools System Administration Guide.

2.3 Data Dictionary Triggers

This section discusses:

- Data Dictionary triggers overview.

- Default value triggers.

- Visual assist triggers.

- Edit rule triggers.

- Display rule triggers.

- Next number triggers.

- Smart field triggers.

2.3.1 Data Dictionary Triggers Overview

A trigger is an editing or display routine that is attached at the dictionary level and initiated at runtime. Triggers are reusable objects and, therefore, automatically associated with each application that uses the DD item. Triggers save time and increase the usefulness of the code because you can create the business logic only once and then use it within multiple applications. Triggers ensure accuracy and integrity of data across all applications.

Use triggers to perform these tasks:

- Establish field default values.

- Link DD items to a user-defined code (UDC) table of values.

- Activate a visual assist search program when a user positions the cursor in a field.

- Establish rules and procedures that are embedded in the editing and formatting of the data for a field.

- Determine a next number scheme that developers should use when assigning a number to data.

Although you can override any of these triggers in Form Design Aid (FDA), you should anticipate how the DD item will most often be used to reduce the need for overrides.

2.3.2 Default Value Triggers

A default value trigger is the value assigned to the object based on that DD item when the object is blank.

2.3.3 Visual Assist Triggers

A DD item with an associated visual assist trigger displays the visual assist button at runtime. These types of visual assist triggers are available:

- Search form
This visual assist loads the selected search & select form to assist users in selecting values. The search & select form must exist before you attach a search form trigger. Also, the form must display table values only; it cannot display UDC values.

- Calculator
This visual assist provides an on-screen calculator to assist users in deriving mathematical values.

- Calendar
This visual assist provides an on-screen calendar to assist users in selecting dates.

- Universal time
This visual assist provides an on-screen clock and calendar to assist users in selecting times and dates.

2.3.4 Edit Rule Triggers

Use edit rule triggers to validate field values that are based on business functions or rules (logic that you write yourself). For example, you can define an edit rule trigger that performs these functions:

- Validates and compares a field with a particular value.

- Ensures that a field value is within a specified range of values.

- Links a field to a specific UDC search & select form.

- Checks for Y and N values.

To base the trigger on a business function, then the business function must already exist. To base the trigger on a rule, build the validation logic at the time that you define the trigger. These rules can include UDCs such as:

- EQ: Equal

- GE: Greater or Equal

- GT: Greater

- HNDL: Table Handle

- LE: Less Than or Equal

- LT: Less Than

- NE: Not Equal

- NRANGE: Not Between

- RANGE: Between

- UDC: User-Defined Code

- VALUE: In a List

- ZLNGTH: Allocated Length (VARLEN flds)

2.3.5 Display Rule Triggers

Use a display rule trigger to format data. You attach a display rule trigger based on either a business function or a UDC. To base the trigger on a business function, the business function must already exist. To base the trigger on a rule, indicate the formatting at the time that you define the trigger with one of these codes:

- *RAB
Right-adjusts the value and precedes it with blanks. DD items that define business units use this rule.

- *RABN
Right-adjusts the value and precedes it with blanks. DD items that do not define business units use this rule.

- *RAZ
Right-adjusts the value and precedes it with zeroes. For example, Company appears as 00001.

- CODE
Uses the specified edit codes to format numeric fields. See UDC 98/EC for a list of valid codes. The code should be entered into the parameter field.

- MASK
No longer supported.

- LMASK
Embeds leading masks (*'s) within the data when it appears in the web client and UBE reports. For example, to display a credit card number with embedded asterisks, the mask parameter would appear as in this example:

********1234, where the number 4 in the parameter setting corresponds to the number of trailing digits that are unmasked. Make sure that this number is lower than the length of this data item.

Mask can be used only with string DD item types.

2.3.6 Next Number Triggers

The next number trigger controls the automatic numbering for such items as new general ledger account numbers, voucher numbers, and address numbers. It enables you to specify the numbering system code to use and automatically increments numbers to reduce transpositions and keying errors.

Use the next number trigger to enter a default value in a numeric DD item if the user does not enter a number. Next numbers are assigned from an array. The combination of system code and index defines how the next number will be assigned.

F0002 has this logic:

- One record per system and 10-element array.
The key to F0002 is system code. The table includes 10 columns for individual next number elements. The system uses each of these elements for a specific hard code within the applications for that system code.

For example, if you specify system code 09 in the next numbers trigger, six rows are populated and four are blank. The system uses each of these coded, populated rows as hard code. The first row defines New Account ID. Within JD Edwards EnterpriseOne applications that create new accounts, the system retrieves the account number from system 09, row 1 of the F0002 table. Row 2 contains Journal Entries. In a master business function that creates journal entry documents, the system retrieves the document number from system 09, row 2 of the F0002 table.

If you specify system 04 in the Next Numbers trigger, the system uses a separate set of rows that have hard codes for use within system 04.

- Check digits.
Check digits (sometimes called a Modulus 11 check) enable you to specify whether the system adds a number to the end of each next number that it assigns.

For example, if you are using check digits and the next number is 2, the system adds a check digit such as 7, making the last two numbers 27. Check digits provide a method of randomly incrementing numbers to prevent the assignment of transposed numbers. In the algorithm in this topic, the system would never assign next number 72 while the check digits feature is activated.

2.3.6.1 IBM Modulus 11 Self-Check Algorithm

Each position in the base number has a weight factor. Modulus 11 counts positions from the right-most digit (not including the check digit).

The Modulus 11 weight factors are 2, 3, 4, 5, 6, 7, 2, 3, 4, 5, 6, 7, 2, 3, 4, 5, 6, 7, 2 for positions 1 to 31, respectively.

After you set next numbers, do not change them. If you change next numbers, these issues might occur:

- System performance will be affected.

- Next numbers functionality will not duplicate numbers; when it reaches the maximum, it will start over.

- You will not be able to change position or add a new entry without modifying the program.

Next numbers connect to the DD. A DD item in the DD points to the next numbers system which you can manipulate with the Next Numbers application (P0002).

2.3.7 Smart Field Triggers

Smart fields are DD items with attached business functions. The business functions include named mappings, which simplify the process of choosing a DD item with particular functionality. End-users do not need to know which business function to use and what parameters to pass; instead, the user simply selects a DD item that has this information. Smart fields can be used in all section types in Report Design Aid (RDA). For example, you can use smart fields to derive a column heading or an object value in a tabular section. Smart fields are always in glossary group K.

3 Defining a Data Dictionary Item

This chapter contains the following topics:

- Section 3.2, "Creating a Data Dictionary Item"

- Section 3.3, "Adding Glossary Text for Languages"

- Section 3.4, "Defining Jargon and Alternate Language Terms"

3.1 Common Fields Used in This Chapter

Column Title

Enter text to display on the first line of descriptions that are used in column headings on a report or form. This description is for the base language only, unless you update the description for another language.

This description should be no larger than the DD item size, if possible. If the column heading is only one line, it should be placed in this column. Use the second line of the Column Title when one row is insufficient.

Row Description

Use row description in a manner similar to the column description in the query facility. The row description identifies fields on forms and reports. This description is for the base language only, unless you update the description for another language. It should be less than 35 characters. Use abbreviations whenever possible. Common abbreviations are:

- U/M: Units of measure

- YTD: Year-to-date

- MTD: Month-to-date

- PYE: Prior year end

- QTY: Quantity

- G/L: General ledger

- A/P: Accounts payable

- DEPR: Depreciation

3.2 Creating a Data Dictionary Item

This section lists the forms used to create a DD item, and discusses how to create a DD item.

When you create a new DD item, the system prompts you to indicate whether the DD item will be a glossary DD item.

3.2.1 Forms Used to Create a Data Dictionary Item

Form Name

FormID

Navigation

Usage

Add EnterpriseOne Object to the Project

W98220C

Click the Add button on the Object Management Workbench form.

Create a DD item.

Data Item Specifications

W92001C

Select Data Item on the Add EnterpriseOne Object to the Project form.
When prompted, indicate the DD item type you want to create.

Define the DD item specifications. Attach default triggers, if needed. If creating a glossary DD item, write the glossary.

Smart Field Criteria

W9212A

Enter K in the Glossary Group field on the Data Item Specifications form.
Select Smart Fields from the Form menu.

Select the business function that was created for the smart field. Select the event in which the smart field should be triggered. Select the named mapping that is associated with the business function data structure.

3.2.2 Creating a Data Dictionary Item

Access the Data Item Specifications form.

Alias

Enter a code that identifies and defines a unit of information. It is an alphanumeric code up to eight characters long that does not allow blanks or special characters such as %, &, or +. You create new DD items using system codes 55-59. You cannot change the alias.

Within the DD, all DD items are referenced by this four-byte data name. As they are used in database tables, a two-character prefix is added to create unique data names in each table specification (DDS). If you are adding an error message, this field must be left blank. The system assigns the error message number using next numbers. The name appears on a successful add. You should assign error message numbers greater than 5000. Special characters are not allowed as part of the DD item name, with the exception of #, @, $.

Allow Blank Entry

Set this flag to indicate whether blank values can be written to the database. Select this option to allow blank entry under these conditions:

- If the field is edited against a user-defined code (UDC) table, a blank value will be allowed regardless of whether a blank value is valid for the table.

- If the field is specified to be a mandatory entry, a blank value will be allowed as a valid entry.

Auto Include

Set this flag to indicate whether this column should be automatically included in all database fetches to tables that contain this item. This option should only be selected for items that are essential for certain database trigger processes or security validation.

Class

Enter a code that defines the DD item class. The class defines the essential attributes and characteristics of a DD item and is informational only.

Control Type

Enter a code that defines the type of graphical user control that is associated with the DD item. For example, a DD item can appear as a push button, check box, and so on.

Control type is used by Form Design Aid (FDA) to automatically add the correct control to a form for a specific DD item. For example, if a DD item will normally be used as a check box, then the DD control type should be a check box. When you use Quick Form, the DD item will appear as a check box control instead of a generic edit on the form.

You can override this setting in FDA; however, you should anticipate how it will most commonly be used to reduce the need for overrides.

Data Item

Enter a text string used to identify the DD item. The text string can be up to 32 characters long. Blanks and the characters %, & , and + are not allowed. The field cannot be changed after you save the DD item.

Data Type

Enter an identifier of the style or classification of data, such as numeric, alphabetic, and date. Do not change the DD item data type if it is used within an existing application. Data types include these:

- Character: A single letter, always the size of one.

- Date: A date.

- Integer: An integer.

- Character (Blob): An item that can be translated from EBCDIC (8-bit character code commonly used on IBM mainframes) to ASCII (7-bit character code).

- Binary (Blob): An item that cannot be translated, appears in machine code, and is found as an executable file under Win.help.

- Binary: An option that represents two choices.
It is usually a combination of the digits 1 and 0 to represent on and off or true and false.

- String: An item that is always the same size or length.

- Variable String: An item of variable size.

- UTime: An item that allows business processes to span several time zones by coordinating workstations to Universal Coordinated Time.

- Identifier (ID): An item that is used within the program logic for controls.
An ID is used to write a C program and reference third-party software that returns a pointer. An API then saves the pointer that references the ID. The parameter that the system passes to the C program is the ID.

- Numeric: A long integer.

Description

Enter a case-sensitive description for the DD items. The system uses this name to search for similar DD items. To enter an alpha description, follow these conventions:

- Dates: Begin all date fields with the word "Date".

- Amounts: Begin all amount fields with the word "Amount".

- Units: Begin all unit, quantity, and volume fields with the word "Units".

- Name: Begin all 30-byte description fields with the word "Name".

- Prompt: Begin any Y/N prompting field with the word "Prompt".

- Address Number: Begin all address numbers (employee, customer, owner) with the words "Address Number".

Display Decimals

Enter a value that designates the number of decimals in the currency, amount, or quantity fields the system displays. For example, U.S. Dollars would be two decimals, Japanese Yen would be no decimals, and Cameroon Francs would be three decimals.

Do Not Total

Enter a value that identifies DD items that are applicable to one of the development platforms only. Valid values are:

1 – Non-AS/400 system only.

2 – AS/400 only.

Blank – DD item is valid for both platforms.

The system makes this flag available for entry if the DD item is of type numeric. When you select this option, the DD item is marked Not to total. When this item is used in a report, the item property, Suppress At Total, is marked.

File Decimals

Enter a value that indicates number of stored positions to the right of the decimal of the DD item.

Glossary Group

Enter a code that indicates the type of DD item. It is validated against UDC H98/DI. Items in glossary group D or S can be included in database tables. Items in other glossary groups (for example, error messages) cannot be added to a table.

The DD item names for error messages are assigned automatically. If you need to assign your own error message numbers, use 4 digit numbers greater than 5000.

The DD item name for a non-database field (used on a form or report but not in a file - glossary group U) must begin with a #, $ or @. For help text (glossary group H), the DD Inquiry/Revision Program field may be used to specify the name of a follow-on item. To create messages for the IBM message file (glossary group J), begin the DD item name with your own three characters (for example, CLT0001).

Item Occurrences

Enter a value that indicates the number of array elements to create, which in turn will create child items (one child per array element).

Item occurrences allows you to create an item as a child of another item. The DD verifies that attributes are consistent between the parent and the child. If you change the parent item, the changes are duplicated in the child items. The DD item names use the parent DD item name and a number, such as a parent item ABC and child items ABC1, ABC2, and so on.

The array DD item names are restricted to certain lengths depending on the number of array elements:

- 3 bytes - 1 to 9 elements

- 2 bytes - 10 to 99 elements

- 1 byte - 100 to 999 elements

Row Security

Set this flag to indicate whether the field can be used in setting up row security.

You can create protected data names by using $xxx and @xxx, where you define xxx.

The alias cannot be changed.

Size

Enter a value that indicates the field size of the DD item.

All amount fields should be entered as 15 bytes, 0 decimals, and the DD item type should be P (packed).

System Code

Enter a value that designates the system number for the Next Number retrieval. See UDC 98/SY.

Upper Case Only

Set this flag to indicate whether the DD item will accept lowercase text. If the value of this field is a Y, the user cannot enter lowercase characters into a control based on this DD item.

3.3 Adding Glossary Text for Languages

This section lists the forms used to add glossary text for languages, and discusses how to add glossary text for languages.

For any DD item, you can add glossary text for different languages. For example, you can create glossary text for the base English language item and also add glossary text for French, Spanish, and German. Glossary text for languages must be added after the DD item has been created.

3.3.1 Form Used to Add Glossary Text for Languages

Form Name

FormID

Navigation

Usage

Work with Data Items

W92001B

Data Dictionary Design (GH951), Work with Data Dictionary Items

Choose a DD item for which to supply a non-English glossary.

3.3.2 Adding Glossary Text for Languages

To add glossary text for languages:

1. Access Work with Data Items.

2. Select the DD item that you want to change.

3. From the Row menu, select Glossary Overrides.

4. On Work With Data Item Glossary Overrides, click the Add button.

5. On Data Item Glossary Header, complete these fields:

- Language

- Form
Enter a form name if you want the glossary to apply to a specific form only.

If you do not enter a form name, the glossary applies to all forms that use this item.

6. On Work with Data Item Glossary Overrides, select the row that you just added.

7. From the Row menu, select Glossary.

8. On Data Item Glossary, enter the glossary text that you want to appear.

3.4 Defining Jargon and Alternate Language Terms

This section provides an overview of jargon and alternate language terms and discusses how to:

- Change row and column text for all applications.

- Define jargon.

- Update a data item for languages.

3.4.1 Understanding Jargon and Alternate Language Terms

When you create a DD item, you assign descriptions to the row, column, and glossary. Because these descriptions might not offer the flexible terminology that you need, you can assign alternate jargon or language descriptions to each item. Alternate descriptions enable the same DD item to appear with different row, columns, and glossaries for different users, depending on the system (product) code of the object that they are using.

For example, the cost center field MCU is widely used throughout the system. Its row description is Business Unit, which is a term used by financial applications. However, in distribution applications, this DD item appears as Branch/Plant. Likewise, in warehousing applications, the DD item appears as Warehouse.

In addition to any alternate terms that you define, users can implement their own language overrides at the application level. The system checks for and resolves overrides in this order:

1. If a user applies a language override in the application (such as FDA or Report Design Aid (RDA)), the system uses the term indicated by the language override, if one exists.

2. If the user did not specify a language override in the application, then the system determines at runtime whether a system code has been attached to the menu selection.
If the menu selection has an attached system code, then the system displays the alternate term dictated by the system code, if one exists.

3. If no alternate term has been indicated for the menu selection, the system determines at runtime whether a system code has been attached to the application.
If the application has an attached system code, then the system displays the alternate term that is dictated by the system code, if one exists.

4. If no alternate term has been indicated for the application, then the DD text appears.

In all cases, the system first checks the user's preferred language for an alternate term before checking without language. Language and language overrides always take precedence over non-language overrides. For example, assume that, in an environment in which English is the base language, all the forms have French translations that a user can view by selecting the French override. A form might contain a DD item that in English has an alternate term; in this example, however, the French version of the DD item does not have an alternate term. When it appears in English, the form displays either the main term or the alternate term, as appropriate. When it appears in French, however, the form displays only the main term, even when an alternate term is called for, because the language override takes precedence over displaying the alternate term.

Jargon and alternate language terms must be added after the DD item has been created.

3.4.2 Forms Used to Define Jargon and Alternate Language Terms

Form Name

FormID

Navigation

Usage

Work with Data Items

W92001B

Data Dictionary Design (GH951), Work with Data Dictionary Items

Choose a DD item for which to define jargon and alternate language terms.

Work with Data Item Descriptions

W92001S

On Work with Data Items, select a DD item.
From the Row menu, select Descript. Overrides.

Modify language jargon codes.

Data Item Descriptions

W92001Q

On Work with Data Item Descriptions, click the Add button.

Apply a language and jargon code to the DD item.

3.4.3 Changing Row and Column Text for All Applications

Click the Glossary Overrides to change the alpha description and create a record. You then use the Glossary form to change the description.

Changes to row and column descriptions are not replicated through data replication. To deploy row and column changes to workstations, you must deliver a new full or partial package, or an update package that includes the affected applications. The new or update package deletes the existing row and columns that are stored in a cache on the workstation.

To change row and column text for all applications:

Access Work with Data Item Descriptions.

Jargon Code

Enter a UDC (98/SY) value that specifies the system number for reporting and jargon purposes.

3.4.4 Defining Jargon

Access Data Item Descriptions.

Jargon Code

Enter a UDC (98/SY) value that specifies the system number for reporting and jargon purposes.

3.4.5 Updating a Data Item for Languages

Access Data Item Descriptions.

Language

Enter a UDC (01/LP) that specifies the language to use on forms and printed reports. Before you specify a language, a code for that language must exist at either the system level or in the user's preferences.

4 Adding Tips of the Day

This chapter contains the following topics:

- Section 4.1, "Understanding Tips of the Day"

- Section 4.2, "Working with Tips of the Day"

4.1 Understanding Tips of the Day

Many JD Edwards EnterpriseOne applications provide tips of the day, which are sets of short informational text that appear each time you launch an application or access a form. You can change these tip sets or create your own. Tips of the day appear sequentially, so you can browse through the tips. When you close the tip form, the system records where in the tip sequence you are and displays the next tip when you launch the object again.

4.1.1 Prerequisite

Create a data dictionary item with glossary text for each tip of the day.

4.2 Working with Tips of the Day

In JD Edwards EnterpriseOne, tips of the day are the glossary texts of data dictionary items. You create one data dictionary item for each tip. Since you can translate data dictionary glossaries, tips of the day can appear in different languages.

You can associate tips with an application, a form, or an application version. The tips appear in the order that you specify, and you can override a user's option to clear the tip of the day feature for the tip set.

After you have associated tips with an object, you can rearrange the tip order, add new tips, or delete existing ones from the tip set.

4.2.1 Forms Used to Work with Tips of the Day

Form Name

FormID

Navigation

Usage

Work With Tips of the Day

W91500B

System Administration Tools (GH9011), Object Management Administration, Object Management Administration Advanced and Technical Operations, Tip of the Day

View and select a tip of the day.

Tips of the Day Revisions

W91500C

Work With Tips of the Day, click Add

Add a tip of the day to an object.

4.2.2 Adding Tips of the Day to an Object

You can add tips to an application, form, or application version that does not already have tips associated with it. To add tips to an existing tip set, double-click one of the existing tips on the Work With Tips of the Day form, or by selecting Add, to access the Tips of the Day Revisions form.

Access Tips of the Day Revisions.

EnterpriseOne Tool

If you selected Add enter the system application to which you are attaching the tip set. If you selected an existing tip, this field is unavailable for input.

Description

Enter a description of the system application, if one does not already exist.

Force tip to all users

Select this option to end the user's ability to disable Tip of the Day. This option applies to the current tip set only.

Tip Sequence

Select the order in which the tips in the tip set appear.

Data Item

Select the alias of the data dictionary item.

Description

The DD description of the tip is displayed.

Glossary

Accessor Methods/Assessors

Java methods to “get” and “set” the elements of a value object or other source file.

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.

Advanced Planning Agent (APAg)

A JD Edwards EnterpriseOne tool that can be used to extract, transform, and load enterprise data. APAg supports access to data sources in the form of rational databases, flat file format, and other data or message encoding, such as XML.

application server

Software that provides the business logic for an application program in a distributed environment. The servers can be Oracle Application Server (OAS) or WebSphere Application Server (WAS).

Auto Commit Transaction

A database connection through which all database operations are immediately written to the database.

batch processing

A process of transferring records from a third-party system to JD Edwards EnterpriseOne.

In JD Edwards EnterpriseOne Financial Management, batch processing enables you to transfer invoices and vouchers that are entered in a system other than JD Edwards EnterpriseOne to JD Edwards EnterpriseOne Accounts Receivable and JD Edwards EnterpriseOne Accounts Payable, respectively. In addition, you can transfer address book information, including customer and supplier records, to JD Edwards EnterpriseOne.

batch server

A server that is designated for running batch processing requests. A batch server typically does not contain a database nor does it run interactive applications.

batch-of-one

A transaction method that enables a client application to perform work on a client workstation, then submit the work all at once to a server application for further processing. As a batch process is running on the server, the client application can continue performing other tasks.

best practices

Non-mandatory guidelines that help the developer make better design decisions.

BPEL

Abbreviation for Business Process Execution Language, a standard web services orchestration language, which enables you to assemble discrete services into an end-to-end process flow.

BPEL PM

Abbreviation for Business Process Execution Language Process Manager, a comprehensive infrastructure for creating, deploying, and managing BPEL business processes.

Build Configuration File

Configurable settings in a text file that are used by a build program to generate ANT scripts. ANT is a software tool used for automating build processes. These scripts build published business services.

build engineer

An actor that is responsible for building, mastering, and packaging artifacts. Some build engineers are responsible for building application artifacts, and some are responsible for building foundation artifacts.

Build Program

A WIN32 executable that reads build configuration files and generates an ANT script for building published business services.

business analyst

An actor that determines if and why an EnterpriseOne business service needs to be developed.

business function

A named set of user-created, reusable business rules and logs that can be called through event rules. Business functions can run a transaction or a subset of a transaction (check inventory, issue work orders, and so on). Business functions also contain the application programming interfaces (APIs) that enable them to be called from a form, a database trigger, or a non-JD Edwards EnterpriseOne application. Business functions can be combined with other business functions, forms, event rules, and other components to make up an application. Business functions can be created through event rules or third-generation languages, such as C. Examples of business functions include Credit Check and Item Availability.

business function event rule

See named event rule (NER).

business service

EnterpriseOne business logic written in Java. A business service is a collection of one or more artifacts. Unless specified otherwise, a business service implies both a published business service and business service.

business service artifacts

Source files, descriptors, and so on that are managed for business service development and are needed for the business service build process.

business service class method

A method that accesses resources provided by the business service framework.

business service configuration files

Configuration files include, but are not limited to, interop.ini, JDBj.ini, and jdelog.properties.

business service cross reference

A key and value data pair used during orchestration. Collectively refers to both the code and the key cross reference in the WSG/XPI based system.

business service cross-reference utilities

Utility services installed in a BPEL/ESB environment that are used to access JD Edwards EnterpriseOne orchestration cross-reference data.

business service development environment

A framework needed by an integration developer to develop and manage business services.

business services development tool

Otherwise known as JDeveloper.

business service EnterpriseOne object

A collection of artifacts managed by EnterpriseOne LCM tools. Named and represented within EnterpriseOne LCM similarly to other EnterpriseOne objects like tables, views, forms, and so on.

business service framework

Parts of the business service foundation that are specifically for supporting business service development.

business service payload

An object that is passed between an enterprise server and a business services server. The business service payload contains the input to the business service when passed to the business services server. The business service payload contains the results from the business service when passed to the Enterprise Server. In the case of notifications, the return business service payload contains the acknowledgement.

business service property

Key value data pairs used to control the behavior or functionality of business services.

Business Service Property Admin Tool

An EnterpriseOne application for developers and administrators to manage business service property records.

business service property business service group

A classification for business service property at the business service level. This is generally a business service name. A business service level contains one or more business service property groups. Each business service property group may contain zero or more business service property records.

business service property key

A unique name that identifies the business service property globally in the system.

business service property utilities

A utility API used in business service development to access EnterpriseOne business service property data.

business service property value

A value for a business service property.

business service repository

A source management system, for example ClearCase, where business service artifacts and build files are stored. Or, a physical directory in network.

business services server

The physical machine where the business services are located. Business services are run on an application server instance.

business services source file or business service class

One type of business service artifact. A text file with the .java file type written to be compiled by a Java compiler.

business service value object template

The structural representation of a business service value object used in a C-business function.

Business Service Value Object Template Utility

A utility used to create a business service value object template from a business service value object.

business services server artifact

The object to be deployed to the business services server.

business view

A means for selecting specific columns from one or more JD Edwards EnterpriseOne application tables whose data is used in an application or report. A business view does not select specific rows, nor does it contain any actual data. It is strictly a view through which you can manipulate data.

central objects merge

A process that blends a customer's modifications to the objects in a current release with objects in a new release.

central server

A server that has been designated to contain the originally installed version of the software (central objects) for deployment to client computers. In a typical JD Edwards EnterpriseOne installation, the software is loaded on to one machine—the central server. Then, copies of the software are pushed out or downloaded to various workstations attached to it. That way, if the software is altered or corrupted through its use on workstations, an original set of objects (central objects) is always available on the central server.

charts

Tables of information in JD Edwards EnterpriseOne that appear on forms in the software.

check-in repository

A repository for developers to check in and check out business service artifacts. There are multiple check-in repositories. Each can be used for a different purpose (for example, development, production, testing, and so on).

checksum

A fixed-size datum computed from an arbitrary block of digital data for the purpose of detecting accidental errors that may have been introduced during its transmission or storage. JD Edwards EnterpriseOne uses the checksum to verify the integrity of packages that have been downloaded by recomputing the checksum of the downloaded package and comparing it with the checksum of the original package. The procedure that yields the checksum from the data is called a checksum function or checksum algorithm. JD Edwards EnterpriseOne uses the MD5 and STA-1 checksum algorithms.

connector

Component-based interoperability model that enables third-party applications and JD Edwards EnterpriseOne to share logic and data. The JD Edwards EnterpriseOne connector architecture includes Java and COM connectors.

Control Table Workbench

An application that, during the Installation Workbench processing, runs the batch applications for the planned merges that update the data dictionary, user-defined codes, menus, and user override tables.

control tables merge

A process that blends a customer's modifications to the control tables with the data that accompanies a new release.

correlation data

The data used to tie HTTP responses with requests that consist of business service name and method.

credentials

A valid set of JD Edwards EnterpriseOne username/password/environment/role, EnterpriseOne session, or EnterpriseOne token.

cross-reference utility services

Utility services installed in a BPEL/ESB environment that access EnterpriseOne cross-reference data.

database credentials

A valid database username/password.

database server

A server in a local area network that maintains a database and performs searches for client computers.

Data Source Workbench

An application that, during the Installation Workbench process, copies all data sources that are defined in the installation plan from the Data Source Master and Table and Data Source Sizing tables in the Planner data source to the system-release number data source. It also updates the Data Source Plan detail record to reflect completion.

deployment artifacts

Artifacts that are needed for the deployment process, such as servers, ports, and such.

deployment server

A server that is used to install, maintain, and distribute software to one or more enterprise servers and client workstations.

direct connect

A transaction method in which a client application communicates interactively and directly with a server application.

See also batch-of-one and store-and-forward.

Do Not Translate (DNT)

A type of data source that must exist on the iSeries because of BLOB restrictions.

embedded application server instance

An OC4J instance started by and running wholly within JDeveloper.

edit code

A code that indicates how a specific value for a report or a form should appear or be formatted. The default edit codes that pertain to reporting require particular attention because they account for a substantial amount of information.

edit mode

A condition of a form that enables users to change data.

edit rule

A method used for formatting and validating user entries against a predefined rule or set of rules.

Electronic Data Interchange (EDI)

An interoperability model that enables paperless computer-to-computer exchange of business transactions between JD Edwards EnterpriseOne and third-party systems. Companies that use EDI must have translator software to convert data from the EDI standard format to the formats of their computer systems.

embedded event rule

An event rule that is specific to a particular table or application. Examples include form-to-form calls, hiding a field based on a processing option value, and calling a business function. Contrast with the business function event rule.

Employee Work Center

A central location for sending and receiving all JD Edwards EnterpriseOne messages (system and user generated), regardless of the originating application or user. Each user has a mailbox that contains workflow and other messages, including Active Messages.

enterprise server

A server that contains the database and the logic for JD Edwards EnterpriseOne.

Enterprise Service Bus (ESB)

Middleware infrastructure products or technologies based on web services standards that enable a service-oriented architecture using an event-driven and XML-based messaging framework (the bus).

EnterpriseOne administrator

An actor responsible for the EnterpriseOne administration system.

EnterpriseOne credentials

A user ID, password, environment, and role used to validate a user of EnterpriseOne.

EnterpriseOne development client

Historically called “fat client,” a collection of installed EnterpriseOne components required to develop EnterpriseOne artifacts, including the Microsoft Windows client and design tools.

EnterpriseOne extension

A JDeveloper component (plug-in) specific to EnterpriseOne. A JDeveloper wizard

is a specific example of an extension.

EnterpriseOne object

A reusable piece of code that is used to build applications. Object types include tables, forms, business functions, data dictionary items, batch processes, business views, event rules, versions, data structures, and media objects.

EnterpriseOne process

A software process that enables JD Edwards EnterpriseOne clients and servers to handle processing requests and run transactions. A client runs one process, and servers can have multiple instances of a process. JD Edwards EnterpriseOne processes can also be dedicated to specific tasks (for example, workflow messages and data replication) to ensure that critical processes don't have to wait if the server is particularly busy.

EnterpriseOne resource

Any EnterpriseOne table, metadata, business function, dictionary information, or other information restricted to authorized users.

Environment Workbench

An application that, during the Installation Workbench process, copies the environment information and Object Configuration Manager tables for each environment from the Planner data source to the system-release number data source. It also updates the Environment Plan detail record to reflect completion.

escalation monitor

A batch process that monitors pending requests or activities and restarts or forwards them to the next step or user after they have been inactive for a specified amount of time.

event rule

A logic statement that instructs the system to perform one or more operations based on an activity that can occur in a specific application, such as entering a form or exiting a field.

explicit transaction

Transaction used by a business service developer to explicitly control the type (auto or manual) and the scope of transaction boundaries within a business service.

exposed method or value object

Published business service source files or parts of published business service source files that are part of the published interface. These are part of the contract with the customer.

fast path

A command prompt that enables the user to move quickly among menus and applications by using specific commands.

file server

A server that stores files to be accessed by other computers on the network. Unlike a disk server, which appears to the user as a remote disk drive, a file server is a sophisticated device that not only stores files, but also manages them and maintains order as network users request files and make changes to these files.

final mode

The report processing mode of a processing mode of a program that updates or creates data records.

foundation

A framework that must be accessible for execution of business services at runtime. This includes, but is not limited to, the Java Connector and JDBj.

FTP server

A server that responds to requests for files via file transfer protocol.

HTTP Adapter

A generic set of services that are used to do the basic HTTP operations, such as GET, POST, PUT, DELETE, TRACE, HEAD, and OPTIONS with the provided URL.

instantiate

A Java term meaning “to create.” When a class is instantiated, a new instance

is created.

integration developer

The user of the system who develops, runs, and debugs the EnterpriseOne business services. The integration developer uses the EnterpriseOne business services to develop these components.

integration point (IP)

The business logic in previous implementations of EnterpriseOne that exposes a document level interface. This type of logic used to be called XBPs. In EnterpriseOne 8.11, IPs are implemented in Web Services Gateway powered by webMethods.

integration server

A server that facilitates interaction between diverse operating systems and applications across internal and external networked computer systems.

integrity test

A process used to supplement a company's internal balancing procedures by locating and reporting balancing problems and data inconsistencies.

interface table

See Z table.

internal method or value object

Business service source files or parts of business service source files that are not part of the published interface. These could be private or protected methods. These could be value objects not used in published methods.

interoperability model

A method for third-party systems to connect to or access JD Edwards EnterpriseOne.

in-your-face error

In JD Edwards EnterpriseOne, a form-level property which, when enabled, causes the text of application errors to appear on the form.

jargon

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

Java application server

A component-based server that resides in the middle-tier of a server-centric architecture. This server provides middleware services for security and state maintenance, along with data access and persistence.

JDBNET

A database driver that enables heterogeneous servers to access each other's data.

JDEBASE Database Middleware

A JD Edwards EnterpriseOne proprietary database middleware package that provides platform-independent APIs, along with client-to-server access.

JDECallObject

An API used by business functions to invoke other business functions.

jde.ini

A JD Edwards EnterpriseOne file (or member for iSeries) that provides the runtime settings required for JD Edwards EnterpriseOne initialization. Specific versions of the file or member must reside on every machine running JD Edwards EnterpriseOne. This includes workstations and servers.

JDEIPC

Communications programming tools used by server code to regulate access to the same data in multiprocess environments, communicate and coordinate between processes, and create new processes.

jde.log

The main diagnostic log file of JD Edwards EnterpriseOne. This file is always located in the root directory on the primary drive and contains status and error messages from the startup and operation of JD Edwards EnterpriseOne.

JDENET

A JD Edwards EnterpriseOne proprietary communications middleware package. This package is a peer-to-peer, message-based, socket-based, multiprocess communications middleware solution. It handles client-to-server and server-to-server communications for all JD Edwards EnterpriseOne supported platforms.

JDeveloper Project

An artifact that JDeveloper uses to categorize and compile source files.

JDeveloper Workspace

An artifact that JDeveloper uses to organize project files. It contains one or more project files.

JMS Queue

A Java Messaging service queue used for point-to-point messaging.

listener service

A listener that listens for XML messages over HTTP.

local repository

A developer's local development environment that is used to store business service artifacts.

Location Workbench

An application that, during the Installation Workbench process, copies all locations that are defined in the installation plan from the Location Master table in the Planner data source to the system data source.

logic server

A server in a distributed network that provides the business logic for an application program. In a typical configuration, pristine objects are replicated on to the logic server from the central server. The logic server, in conjunction with workstations, actually performs the processing required when JD Edwards EnterpriseOne software runs.

MailMerge Workbench

An application that merges Microsoft Word 6.0 (or higher) word-processing documents with JD Edwards EnterpriseOne records to automatically print business documents. You can use MailMerge Workbench to print documents, such as form letters about verification of employment.

Manual Commit transaction

A database connection where all database operations delay writing to the database until a call to commit is made.

master business function (MBF)

An interactive master file that serves as a central location for adding, changing, and updating information in a database. Master business functions pass information between data entry forms and the appropriate tables. These master functions provide a common set of functions that contain all of the necessary default and editing rules for related programs. MBFs contain logic that ensures the integrity of adding, updating, and deleting information from databases.

master table

See published table.

media storage object

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

message center

A central location for sending and receiving all JD Edwards EnterpriseOne messages (system and user generated), regardless of the originating application or user.

messaging adapter

An interoperability model that enables third-party systems to connect to JD Edwards EnterpriseOne to exchange information through the use of messaging queues.

messaging server

A server that handles messages that are sent for use by other programs using a messaging API. Messaging servers typically employ a middleware program to perform their functions.

Monitoring Application

An EnterpriseOne tool provided for an administrator to get statistical information for various EnterpriseOne servers, reset statistics, and set notifications.

named event rule (NER)

Encapsulated, reusable business logic created using event rules, rather that C programming. NERs are also called business function event rules. NERs can be reused in multiple places by multiple programs. This modularity lends itself to streamlining, reusability of code, and less work.

Object Configuration Manager (OCM)

In JD Edwards EnterpriseOne, the object request broker and control center for the runtime environment. OCM keeps track of the runtime locations for business functions, data, and batch applications. When one of these objects is called, OCM directs access to it using defaults and overrides for a given environment and user.

Object Librarian

A repository of all versions, applications, and business functions reusable in building applications. Object Librarian provides check-out and check-incapabilities for developers, and it controls the creation, modification, and use of JD Edwards EnterpriseOne objects. Object Librarian supports multiple environments (such as production and development) and enables objects to be easily moved from one environment to another.

Object Librarian merge

A process that blends any modifications to the Object Librarian in a previous release into the Object Librarian in a new release.

Open Data Access (ODA)

An interoperability model that enables you to use SQL statements to extract JD Edwards EnterpriseOne data for summarization and report generation.

Output Stream Access (OSA)

An interoperability model that enables you to set up an interface for JD Edwards EnterpriseOne to pass data to another software package, such as Microsoft Excel, for processing.

package

JD Edwards EnterpriseOne objects are installed to workstations in packages from the deployment server. A package can be compared to a bill of material or kit that indicates the necessary objects for that workstation and where on the deployment server the installation program can find them. It is point-in-time snapshot of the central objects on the deployment server.

package build

A software application that facilitates the deployment of software changes and new applications to existing users. Additionally, in JD Edwards EnterpriseOne, a package build can be a compiled version of the software. When you upgrade your version of the ERP software, for example, you are said to take a package build.

Consider the following context: “Also, do not transfer business functions into the production path code until you are ready to deploy, because a global build of business functions done during a package build will automatically include the new functions.” The process of creating a package build is often referred to, as it is in this example, simply as “a package build.”

package location

The directory structure location for the package and its set of replicated objects. This is usually \\deployment server\release\path_code\package\package name. The subdirectories under this path are where the replicated objects for the package are placed. This is also referred to as where the package is built or stored.

Package Workbench

An application that, during the Installation Workbench process, transfers the package information tables from the Planner data source to the system-release number data source. It also updates the Package Plan detail record to reflect completion.

Pathcode Directory

The specific portion of the file system on the EnterpriseOne development client where EnterpriseOne development artifacts are stored.

patterns

General repeatable solutions to a commonly occurring problem in software design. For business service development, the focus is on the object relationships and interactions. For orchestrations, the focus is on the integration patterns (for example, synchronous and asynchronous request/response, publish, notify, and receive/reply).

print server

The interface between a printer and a network that enables network clients to connect to the printer and send their print jobs to it. A print server can be a computer, separate hardware device, or even hardware that resides inside of the printer itself.

pristine environment

A JD Edwards EnterpriseOne environment used to test unaltered objects with JD Edwards EnterpriseOne demonstration data or for training classes. You must have this environment so that you can compare pristine objects that you modify.

processing option

A data structure that enables users to supply parameters that regulate the running of a batch program or report. For example, you can use processing options to specify default values for certain fields, to determine how information appears or is printed, to specify date ranges, to supply runtime values that regulate program execution, and so on.

production environment

A JD Edwards EnterpriseOne environment in which users operate EnterpriseOne software.

Production Published Business Services Web Service

Published business services web service deployed to a production application server.

program temporary fix (PTF)

A representation of changes to JD Edwards EnterpriseOne software that your organization receives on magnetic tapes or disks.

project

In JD Edwards EnterpriseOne, a virtual container for objects being developed in Object Management Workbench.

promotion path

The designated path for advancing objects or projects in a workflow. The following is the normal promotion cycle (path):

11>21>26>28>38>01

In this path, 11 equals new project pending review, 21 equals programming, 26 equals QA test/review, 28 equals QA test/review complete, 38 equals in production, 01 equals complete. During the normal project promotion cycle, developers check objects out of and into the development path code and then promote them to the prototype path code. The objects are then moved to the productions path code before declaring them complete.

proxy server

A server that acts as a barrier between a workstation and the internet so that the enterprise can ensure security, administrative control, and caching service.

published business service

EnterpriseOne service level logic and interface. A classification of a published business service indicating the intention to be exposed to external (non-EnterpriseOne) systems.

published business service identification information

Information about a published business service used to determine relevant authorization records. Published business services + method name, published business services, or *ALL.

published business service web service

Published business services components packaged as J2EE Web Service (namely, a J2EE EAR file that contains business service classes, business service foundation, configuration files, and web service artifacts).

published table

Also called a master table, this is the central copy to be replicated to other machines. Residing on the publisher machine, the F98DRPUB table identifies all of the published tables and their associated publishers in the enterprise.

publisher

The server that is responsible for the published table. The F98DRPUB table identifies all of the published tables and their associated publishers in the enterprise.

QBE

An abbreviation for query by example. In JD Edwards EnterpriseOne, the QBE line is the top line on a detail area that is used for filtering data.

real-time event

A message triggered from EnterpriseOne application logic that is intended for external systems to consume.

refresh

A function used to modify JD Edwards EnterpriseOne software, or subset of it, such as a table or business data, so that it functions at a new release or cumulative update level.

replication server

A server that is responsible for replicating central objects to client machines.

rules

Mandatory guidelines that are not enforced by tooling, but must be followed in order to accomplish the desired results and to meet specified standards.

secure by default

A security model that assumes that a user does not have permission to execute an object unless there is a specific record indicating such permissions.

Secure Socket Layer (SSL)

A security protocol that provides communication privacy. SSL enables client and server applications to communicate in a way that is designed to prevent eavesdropping, tampering, and message forgery.

selection

Found on JD Edwards EnterpriseOne menus, a selection represents functions that you can access from a menu. To make a selection, type the associated number in the Selection field and press Enter.

serialize

The process of converting an object or data into a format for storage or transmission across a network connection link with the ability to reconstruct the original data or objects when needed.

Server Workbench

An application that, during the Installation Workbench process, copies the server configuration files from the Planner data source to the system-release number data source. The application also updates the Server Plan detail record to reflect completion.

SOA

Abbreviation for Service Oriented Architecture.

softcoding

A coding technique that enables an administrator to manipulate site-specific variables that affect the execution of a given process.

source repository

A repository for HTTP adapter and listener service development environment artifacts.

Specification merge

A merge that comprises three merges: Object Librarian merge, Versions List merge, and Central Objects merge. The merges blend customer modifications with data that accompanies a new release.

specification

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

Specification Table Merge Workbench

An application that, during the Installation Workbench process, runs the batch applications that update the specification tables.

SSL Certificate

A special message signed by a certificate authority that contains the name of a user and that user's public key in such a way that anyone can "verify" that the message was signed by no one other than the certification authority and thereby develop trust in the user's public key.

store-and-forward

The mode of processing that enables users who are disconnected from a server to enter transactions and then later connect to the server to upload those transactions.

subscriber table

Table F98DRSUB, which is stored on the publisher server with the F98DRPUB table and identifies all of the subscriber machines for each published table.

super class

An inheritance concept of the Java language where a class is an instance of something, but is also more specific. “Tree” might be the super class of “Oak” and “Elm,” for example.

table access management (TAM)

The JD Edwards EnterpriseOne component that handles the storage and retrieval of use-defined data. TAM stores information, such as data dictionary definitions; application and report specifications; event rules; table definitions; business function input parameters and library information; and data structure definitions for running applications, reports, and business functions.

Table Conversion Workbench

An interoperability model that enables the exchange of information between JD Edwards EnterpriseOne and third-party systems using non-JD Edwards EnterpriseOne tables.

table conversion

An interoperability model that enables the exchange of information between JD Edwards EnterpriseOne and third-party systems using non-JD Edwards EnterpriseOne tables.

table event rules

Logic that is attached to database triggers that runs whenever the action specified by the trigger occurs against the table. Although JD Edwards EnterpriseOne enables event rules to be attached to application events, this functionality is application specific. Table event rules provide embedded logic at the table level.

terminal server

A server that enables terminals, microcomputers, and other devices to connect to a network or host computer or to devices attached to that particular computer.

transaction processing (TP) monitor

A monitor that controls data transfer between local and remote terminals and the applications that originated them. TP monitors also protect data integrity in the distributed environment and may include programs that validate data and format terminal screens.

transaction processing method

A method related to the management of a manual commit transaction boundary (for example, start, commit, rollback, and cancel).

transaction set

An electronic business transaction (electronic data interchange standard document) made up of segments.

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.

triggering event

A specific workflow event that requires special action or has defined consequences or resulting actions.

user identification information

User ID, role, or *public.

User Overrides merge

Adds new user override records into a customer's user override table.

value object

A specific type of source file that holds input or output data, much like a data structure passes data. Value objects can be exposed (used in a published business service) or internal, and input or output. They are comprised of simple and complex elements and accessories to those elements.

versioning a published business service

Adding additional functionality/interfaces to the published business services without modifying the existing functionality/interfaces.

Versions List merge

The Versions List merge preserves any non-XJDE and non-ZJDE version specifications for objects that are valid in the new release, as well as their processing options data.

visual assist

Forms that can be invoked from a control via a trigger to assist the user in determining what data belongs in the control.

vocabulary override

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

web application server

A web server that enables web applications to exchange data with the back-end systems and databases used in eBusiness transactions.

web server

A server that sends information as requested by a browser, using the TCP/IP set of protocols. A web server can do more than just coordination of requests from browsers; it can do anything a normal server can do, such as house applications or data. Any computer can be turned into a web server by installing server software and connecting the machine to the internet.

Web Service Description Language (WSDL)

An XML format for describing network services.

Web Service Inspection Language (WSIL)

An XML format for assisting in the inspection of a site for available services and a set of rules for how inspection-related information should be made.

web service softcoding record

An XML document that contains values that are used to configure a web service proxy. This document identifies the endpoint and conditionally includes security information.

web service softcoding template

An XML document that provides the structure for a soft coded record.

Where clause

The portion of a database operation that specifies which records the database operation will affect.

Windows terminal server

A multiuser server that enables terminals and minimally configured computers to display Windows applications even if they are not capable of running Windows software themselves. All client processing is performed centrally at the Windows terminal server and only display, keystroke, and mouse commands are transmitted over the network to the client terminal device.

wizard

A type of JDeveloper extension used to walk the user through a series of steps.

workbench

A program that enables users to access a group of related programs from a single entry point. Typically, the programs that you access from a workbench are used to complete a large business process. For example, you use the JD Edwards EnterpriseOne Payroll Cycle Workbench (P07210) to access all of the programs that the system uses to process payroll, print payments, create payroll reports, create journal entries, and update payroll history. Examples of JD Edwards EnterpriseOne workbenches include Service Management Workbench (P90CD020), Line Scheduling Workbench (P3153), Planning Workbench (P13700), Auditor's Workbench (P09E115), and Payroll Cycle Workbench.

workflow

The automation of a business process, in whole or in part, during which documents, information, or tasks are passed from one participant to another for action, according to a set of procedural rules.

workgroup server

A server that usually contains subsets of data replicated from a master network server. A workgroup server does not perform application or batch processing.

XAPI events

A service that uses system calls to capture JD Edwards EnterpriseOne transactions as they occur and then calls third-party software, end users, and other JD Edwards EnterpriseOne systems that have requested notification when the specified transactions occur to return a response.

XML CallObject

An interoperability capability that enables you to call business functions.

XML Dispatch

An interoperability capability that provides a single point of entry for all XML documents coming into JD Edwards EnterpriseOne for responses.

XML List

An interoperability capability that enables you to request and receive JD Edwards EnterpriseOne database information in chunks.

XML Service

An interoperability capability that enables you to request events from one JD Edwards EnterpriseOne system and receive a response from another JD Edwards EnterpriseOne system.

XML Transaction

An interoperability capability that enables you to use a predefined transaction type to send information to or request information from JD Edwards EnterpriseOne. XML transaction uses interface table functionality.

XML Transaction Service (XTS)

Transforms an XML document that is not in the JD Edwards EnterpriseOne format into an XML document that can be processed by JD Edwards EnterpriseOne. XTS then transforms the response back to the request originator XML format.

Z event

A service that uses interface table functionality to capture JD Edwards EnterpriseOne transactions and provide notification to third-party software, end users, and other JD Edwards EnterpriseOne systems that have requested to be notified when certain transactions occur.

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.

Z transaction

Third-party data that is properly formatted in interface tables for updating to the JD Edwards EnterpriseOne database.

Index
D  E  F  G  J  N  T  V  W

D

data dictionary items

changing, 2.1

creating, 2.1

defining jargon for, 3.4.1

deleting, 2.1

translating, 3.3, 3.4.5

data dictionary overrides, 3.4.1 default values, 2.3.2

E

error messages, 2.1

F

F1 Help, 2.1

fields

changing the description of, 3.4.3

formatting, 2.3.5

validating, 2.3.4

forms

Tips of the Day Revisions, 4.2.1, 4.2.2

Work With Tips of the Day, 4.2.1

G

glossary items, 2.1

grid columns, 3.4.3

J

jargon, 3.4.1, 3.4.4

N

next numbers, 2.3.6

numbering, automatic, 2.3.6

T

tips of the day, 4.2

Tips of the Day Revisions form, 4.2.1, 4.2.2

V

validation of data, 2.3.4

visual assists, 2.3.3

W

Work With Tips of the Day form, 4.2.1

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2014, Oracle and/or its affiliates. All rights reserved.

Trademark Notice

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

Intel and Intel Xeon 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, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

License Restrictions Warranty/Consequential Damages Disclaimer

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.

Warranty Disclaimer

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.

Restricted Rights Notice

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, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

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.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information on 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. 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.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.