VIDEO: JDE Sevice Oriented Architecture (SOA)

VIDEO: Creating a Business View

VIDEO: Creating a Interactive Application

VIDEO: Creating a Simple Batch Application (Report)

VIDEO: Creating a OMW project

Project and its attributes

• A Project is made up of Objects and Owners.
• A Project consists of OneWorld objects that have been modified or created by a developer.
• A Project includes Owners who play different roles in the development process.
• All development of OneWorld Objects will be done in the context of a Project.
Default Project
• The first time a developer uses OMW a Default Project is created.
• The Default Project is named after the user’s ID.
• All development done outside of OMW is stored in the Default Project.
• Default Projects cannot be advanced to another status code.
User Roles
• User Roles define the allowed actions a specific user can perform on a project.
• The administrator assigns allowed actions to each User Role.
• You may add as many people to each User Role in a project as necessary.
Object
• Traditionally a OneWorld Object was defined as any object created in Object Librarian. : Applications, Business Functions, Business Views, UBEs, Data Structures, Tables, Media Objects
• The definition has now been expanded to include non-Object Librarian Objects: Data Dictionary Items, User Defined Codes, Workflow Items, Menus, Versions
Token
• A Token has a One-to-One relationship with the following objects: Applications, Business Functions, Business Views, UBEs, Data Structures, Tables, Media Objects and Batch Versions
• The Token is used to minimize the possibility of one user overriding another user’s changes to an object.
• When an object is checked out and is not already checked out by another user, the project receives a Token.
• A Token can be released, switched or inherited.
• The Token is released by the project when the project reaches the status designated by the administrator for release.
• A Token is not released by the project when the object is checked back in.


Queue up for token
This option is available to the developer upon realizing another project holds the token.


Inherit token
This option is also available to the developer upon realizing another project holds the token.

Release token
This option must be performed by an owner of the project that currently holds the token.

Switch token
This action can only be performed by an owner defined in the Object Management Configuration program. The recommendation is for a manager to be allowed to perform this action.

Constants
Enables the administrator to set the following general constants pertaining to OMW Projects:
• Project Status for Users' Personal Default Projects
• Project Status for All New Projects
• User Role to be Assigned to the Project's Originator
SAR System Integration
• For J.D Edwards internal development and clients using the SAR system.
• Integrates all development with the SAR System.
Logging System
• Tracks information about projects and objects.
• All actions are logged by OneWorld User ID.
• Administrators can reduce logging detail.
• A major log is created whenever:
o A project is created, copied, or deleted
o The project status is changed
o A new or existing object is added to or removed from a project
Object Action Notification
• Enables you to activate or deactivate object action notification.
• Sends you an e-mail each time an event occurs to one of your objects, such as check in or check out.
• Object action notification is enabled by default.

Notification Setup
• Sends e-mail messages to users regarding changes to objects in the system, such as when an object is checked in or checked out.
• Allows you to add, delete, and modify notification subscriptions, as well as to sort notification subscription records by criteria you select.

Activity Rules
• Object Transfer Activity Rules
• Define FROM and TO locations for each object type at each project status transition
• Define get locations for all object types
• Define check out and check in locations for Object Librarian objects

User Roles
• User Roles define the user's function within the project organization.
• When defining user roles, you specify a User Defined Code value or job title for roles that can be performed on a project.
Example:
o 01 Originator
o 02 Developer
o 03 Manager
o 04 Quality Assurance
o 05 PVC Administrator
Allowed Actions

• Rules that define the actions that may be performed by a project owner who has been assigned a certain user role.
• Rules are set up for each user role, object type, and project status
Example:
o 02 Check in
o 03 Check out
o 04 Delete
o 05 Add
o 10 Design

Save Locations
o Indicates the save-off location for Object Librarian (OL) Objects.
o The save location must be different than the check in location.
o Save-off work in development that is not ready to be checked in.

ONE WORLD EVENTS

Events

Events are points in the normal execution or flow of an interactive or batch program. In Event Rules Design, you can specify the particular event to which you want to attach an API. Examples of events are: Entering a Form, Exiting a Field using the Tab key. Events are predefined in the OneWorld toolset and cannot be changed.

Batch Application Events

Batch Application Events give you flexibility and control over how your reports are processed. For example, you can hide or show an object, hide or show a section, or generate a message.

Batch Application Events consist of the following Categories:

·        Section Level Events

·        Page Footer Section Level Events

·        Page Header Section Level Events

·        Report Footer Section Level Events

·        Report Header Section Level Events

·        Variable Events

Section Level Events consist of the following:

·        AdvanceSection

·        AfterLastObjectPrinted

·        BeforeLevelBreak

·        DoBalanceAuditor

·        DoColumnHeading

·        DoSection

·        DoTabularBreak

·        EndBrkSection

·        EndLvlBrkFooterSection

·        EndLvlBrkHeaderSection

·        EndOfReport

·        EndSection

·        EndVariable

·        InitLvlBrkFooterSection

·        InitLvlBrkHeaderSection

·        InitializeSection

·        RefreshSection

·        SupendSection

AdvanceSection: Advance Section should be used if you need to perform processing on object before a fetch. This occurs each time you do a fetch from the database. If this section does not have a business view attached, then this event is processed once.

AfterLastObjectPrinted: AfterLastObjectPrinted should be used to process information after a row has been output. This occurs after a row is printed to an output file.

BeforeLevelBreak: BeforeLevelBreak should be used to do processing after a fetch, but before any level breaks are checked.

DoBalanceAuditor: Event Rules for this event process form interconnect information and generate the Balance Auditor link information to be displayed in the PDF file.

DoColumnHeadin: DoColumnHeading event will happen once for every column header that is printed on a report. This applies to both columnar and tabular style sections. This also applies to when column headers are reprinted after a page break has occurred. Regardless of why the column headings are printing, this event will be executed.

DoSection: DoSection occurs after Advance Section after values have been assigned to print out to a printer or an output file. This event occurs before any information for the current record is written to the PDF file. This event occurs before DoCell (if Tabular cells exist) and before DoVariable/DoConstant.

DoTabularBreak: DoTabularBreak occurs when any of the business view fields set as level breaks change. This is only valid for tabular sections. Use this to do processing that requires a change of values in any of the level break fields.

EndBrkSection: Event Rules attached to this event occur after a Level Break finishes. After the event has terminated, the Level Break Header begins processing.

EndLvlBrkFooterSection: EndLvlBrkFooterSection should be used to do processing immediately after a level break footer.

EndLvlBrkHeaderSection: EndLvlBrkHeaderSection should be used to do processing immediately after a level break header.

EndOfReport: EndOfReport sends INIT_PAGE_FOOTER and INIT_REPORT_FOOTER messages.

EndSection:  EndSection occurs after a batch process has completed processing the last set of section values. Use this to do processing immediately after a section ends. This event is useful for last record and end of file procedures.

EndVariable: EndVariable occurs immediately after the object has been processed, even if the object is invisible or suppressed.

InitLvlBrkFooterSection: InitLvlBrkFooterSection is to be used to do processing immediately before a level break footer.

InitLvlBrkHeaderSection: InitLvlBrkHeaderSection should be used to do processing immediately before a level break header.

InitializeSection: InitializeSection occurs when a batch process encounters a section for the first time. Use this to do processing immediately before a section begins. This is useful for working with global variables or performing other preparatory procedures. For conditional sections, this event will be processed each time the section is called.

Refresh Section: The first time the UBE encounters a child section; it issues an initialize section event. Each subsequent time the child section is to be processed, the batch process uses Refresh Section. At this point, the internal structures and pointers for the child section have been established and the UBE is about to select a new group of records for the child section. This logic also works for the level break sections. use this to set the object values of level two sections based on the parent section. You can also use this event to reset or modify data selection and sequencing of the child section.

SuspendSection: SuspendSection processes when an overflow page break occurs. For example, if the information printed does not fit in the space available on a page. This temporarily stops the section processing. Use this to do processing when a page break occurs

Page Footer Section Level Events

InitializePageFooter: InitializePageFooter occurs at the beginning of the report after any report header logic and before the page header section processes for the first time. Use this to initialize values to be printed in the current page footer section. These assignments typically depend on information processed so far on that page.

Page Header Section Level Events

EndPageHeader : EndPageHeader after the page header finishes processing. Use this to do processing immediately after a page header.

InitializePageHeader: InitializePageHeader occurs at the beginning of a report after any report header logic and before the page header section processes for the first time. It also processes every time a page break occurs. Use this to initialize values that cannot be set until after the report header logic executes. This is similar to Init Section for a normal group, columnar, or tabular section, except that it is only processed for a page header section.

Report Footer Section Level Events

EndReportFooter: EndReportFooter occurs after the report footer processes. After processing finishes, the report terminates. Use this to do processing immediately after a report footer.

InitializeReportFooter: InitializeReportFooter occurs once at the very end of a report after everything else processes and before the report footer prints. use this to initialize values to print in the report footer.

Report Header Section Level Events

EndReportHeader: EndReportHeader occurs after the report header processes. Then the report processes the page header for a report. Use this to do processing immediately after a report header.

InitializeReportHeader:  InitializeReportHeader processes once at the very beginning of the report before anything else in the report processes. Use this to initialize values at the beginning of a report. This is similar to Init Section for a normal group, columnar, or tabular section except that it only processes for a report header section.

Variable Events

ClearSpace: ClearSpace occurs when a section reaches its end. If there is a need to process any information at the time a Section is completed, this is the event at which to attach the ER.

ColumnInclusion: ColumnInclusion occurs right after a record is fetched.

DoVariable: DoVariable occurs just before the font and color are selected for the report object and before the value of the object is translated into a printable string of characters and output to the page. This is your last chance to manipulate the value or display attributes of the object before output.

InitializeVariable:  InitializeVariable is invoked each time a report object, or variable, is to be processed.
SkipVariable: If an object will not fit on the current page, the UBE will issue a SkipVariable, which will cause the object to be bypassed until the next page begins processing.

SuspendVariable: If an object requires multiple lines to print, such as a long text string or column heading, and if only part of the object fits onto a page, then the UBE will issue a SuspendVariable, which causes processing of the object to be halted until the next page has been started. The value of the object has already been partially processed when this event happens, so this would be a risky time for Event Rules to manipulate that value.

Table Design (Screen Shots)

Report Director ( Columnar | Group | Tabular Sections)

The Director provides a quick start to designing reports by guiding you through a linear process for setting up the basic elements. As you proceed through the Director, you can select elements to include in the report template, such as:

• Header and footer sections.

• Type of detail section that best meets the business requirement. (you can add more detail sections to the report template after you complete the initial design and quit the Director.)

• Select the appropriate business view to fetch the required data. ie ( Select the Business view fields that you want to include in the detail section layout and how to sort those records based on the elements that you select, the Director creates a report template and opens it in Oracle’s JDE E1 Report Design Aid (RDA). You can then use RDA to format the data, enhance the report, and add additional detail sections.)

• When you create an application report, the Director uses templates to guide you through the design. Director
  

templates define default criteria to meet a specific business requirement, such as:

• Detail section type: Columnar | Group | Tabular Sections
• Business view
• Processing options
• Data selection
• Data sequencing
• Smart fields
• Drill down

On the welcome form of the Report Design Director, you can select from these section options:

• Report header : Creates an empty section that must be completed manually.

• Page header: Creates a section that can be populated automatically by the system or entered manually.

• Columnar :Creates a detail section that provides a columnar format that includes column headings with rows of data.

• Group: Creates a detail section that provides a free-form layout that enables you to place fields exactly where you want them.

• Tabular: Creates a detail section that provides a columnar format with additional features that are unique to the tabular section type.

• Application Reports: Creates a detail section that uses Report Director templates. The system displays Financial Reports as the default template. Use the drop-down list box to select from available Report Director templates.

• Page footer: Creates an empty section that must be completed manually.

• Report footer: Creates an empty section that must be completed manually.
  

Steps to Create a Columnar Report with the Director

The sample columnar report below, used for an annual salary review, was created with the Director. It is based on the business view V060116A - Employee Master, and it uses the following columns from that business view:

• Address Number
• Name - Alpha
• Business Unit - Home
• Pay Class (H/S/P)
• Date - Original Employment
• Rate - Salary, Annual
  

A columnar report format was selected for this report because, being no more than a straightforward listing, the information is best displayed in rows and columns of data. Furthermore, because no columncalculations were required, a tabular report

format was not needed.

. To create the example columnar report

1. Launch the Report Design tool.

2. On Report Design, choose New from the Report menu.

3. On Create New Report, fill out the form as illustrated below, and then click OK.

Enterprise Report Writing

Note that the text you enter in the Report Name field appears on the left side of the page header and that the text you enter in the Description field appears in the center of the page header under the company name.

4. On the Director’s Welcome form, choose Page Header and Columnar, and then click Next.

5. On the Page Header Details form, click Next.

6. On the Business View Selection Option form, choose I’ll Find a Business View Myself, and then click Next.

7. On the Director’s Select Business View form, search for and choose the V060116A - Employee Master business view, and then click Next.

8. On the Section Layout form, use the horizontal arrow buttons to select the following columns and move them to the Select Columns column:

•Address Number

•Name - Alpha

•Business Unit - Home

•Pay Class (H/S/P)

•Date - Original Employment

•Rate - Salary, Annual

9. Ensure that the columns are ordered as listed above. Use the vertical buttons to change the order of the selected business columns, if necessary.

Note the correlation between the order of the columns on this form and the order of the columns on the report illustration.

10. Click Next when the selected columns are arranged as shown.

11. On the Section Data Sequencing form, use the horizontal arrow buttons to select and move the Name - Alpha column to the Selected Columns column, and then click Next.

12. On the Define Sort Properties form, ensure the sort arrow points up (to alphabetize the report in ascending order by name), and then click next.

13. On the Section Data Selection form, click Next. (No data selection was defined for this example.)

14. On the Director’s Finish form, click Finish.

Report Design appears, displaying the report you just created.

15. Click Save to save the report.

16. Click the Preview tab to see the report. It should look similar to the sample report illustration at the beginning of this section.

. To save a report

On Report Design, perform one of the following:

•From the Report menu, choose Save

•Click the Save button on the toolbar



Steps to Create a Group Report with the Director

The sample group report below was created with the Director. It is based on the business view V41021E - Item Location, Item Master Join, and it uses the following columns from that business view:

•Location

•Item Number - Short

•Primary Location

•Category G/L

•Quantity on Hand - Primary units

•Quantity on Backorder

•Business Unit

Additionally, the report displays items from Business Unit 27 only.

To create the example group report

1. Launch the Report Design tool.

2. On Report Design, choose New from the Report menu.

3. On Create New Report, fill out the form as illustrated below, and then click

OK.

Note that the text you enter in the Report Name field appears on the left side of the page header and that the text you enter in the Description field appears in the center of the page header under the company name.

4. On the Director’s Welcome form, choose Page Header and Group on the Welcome form, and then click Next.

5. On the Page Header Details form, click Next.

6. On the Business View Selection Option form, choose I’ll Find a Business View Myself, and then click Next.

7. On the Select Business View form, search for and choose the V41021E - Item Location, Item Master Join business view, and then click Next.

The Director’s Section Layout form appears.

8. On the Section Layout form, use the horizontal arrow buttons to select the following columns and move them to the Selected Columns column:

•Location

•Item Number - Short

•Primary Location

•Category G/L

•Quantity on Hand - Primary units

•Quantity on Backorder

•Business Unit

9. Ensure that the columns are ordered as listed above. Use the vertical buttons to change the order of the selected business columns, if necessary.

Note the correlation between the order of the columns on this form and the order of the columns on the report illustration.

10. When the selected columns are arranged as shown, enter a 3 in the Number of Columns field, and then click Next.

11. On the Section Data Sequencing form, use the horizontal arrow buttons to select and move the Location and Item Number - Short columns to the Selected Columns column.

12. Ensure the columns appear in the Selected Columns column as indicated in the figure below. In this way, items on the report will be sorted first by location and then second by item number.

13. Click Next when the selected columns are arranged as shown.

14. On the Define Sort Properties form, ensure the sort arrows point up (to alphabetize the report in ascending order in both categories), and then click next.

The Director’s Section Data Selection form appears.

15. On the Section Data Selection form, fill out the grid fields as follows:

•Left Operand - BC Business Unit (F41021)

•Comparison - is equal to

•Right Operand -

When you double-click , the Single Value form appears.

16. Click the Single Value tab, enter 27 in the Business Unit field, and click OK.

Steps 15 and 16 limit the report to displaying records associated with Business Unit 27 only.

17. On the Section Data Selection form, click Next.

18. On the Director’s Finish form, click Finish.

Report Design appears, displaying the report you just created.

19. Click Save to save the report.

20. Click the Preview tab to see the report. It should look similar to the sample report illustration at the beginning of this section.

. To save a report

On Report Design, perform one of the following:

•From the Report menu, choose Save

•Click the Save button on the toolbar

Steps to Create a Tabular Report with the Director

The sample tabular report below was created with the Director. It shows the total amount in outstanding purchase orders for each business unit in a company. It is based on the business view V4311A - Purchase Order Detail Browse and it uses the following columns from that business view:

•Business Unit

•Order Type

•Amount Open

The report is organized by Company and displays item names. Also, it is filtered to display only those purchase orders (as opposed to items ordered by other methods such as purchase requisitions) for stocked parts that have a balance and are not yet closed. While this stipulation might seem obvious, you must plan for and define this filter when you set up the report.

A tabular report format was selected for this report because of the automatic totaling and Display Column features of tabular reports.

. To create the example tabular report

1. Launch the Report Design tool.

2. On Report Design, choose New from the Report menu.

3. On Create New Report, fill out the form as illustrated below, and then click

OK.

Note that the text you enter in the Report Name field appears on the left side of the page header and that the text you enter in the Description field appears in the center of the page header under the company name.

4. On the Director’s Welcome form, choose Page Header and Tabular, and then click Next.

5. On the Page Header Details form, click Next.

6. On the Business View Selection Option form, choose I’ll Find a Business View Myself, and then click Next.

7. On the Select Business View form, search for and choose the V4311A - Purchase Order Detail Browse business view, and then click Next.

The Director’s Section Layout form appears. Note that the Director has added a Description column for you already.

8. On the Section Layout form, use the horizontal arrow buttons to select the following columns and move them to the Select Columns column:

•Business Unit

•Order Type

•Amount Open

9. Ensure that the columns are ordered as listed above. Use the vertical buttons to change the order of the selected business columns, if necessary.

Note the correlation between the order of the columns on this form and the

order of the columns on the report illustration.

10. Click Next when the selected columns are arranged as shown.

11. On the Section Data Sequencing form, use the horizontal arrow buttons to select and move the Order Company (from table F4311) and 2nd Item Number columns to the Selected Columns column. Ensure that the columns are ordered as shown below, and then click Next.

Note that this report is sorted on business view columns that are not included for display in the report.

12. On the Define Sort Properties form, ensure the sort arrow points up (to alphabetize the report in ascending order by name) and that Level Break is selected for both business view columns. Then click next. Making these two columns level breaks ensures that the Description Column displays properly and that the system displays totals for open orders each time the system displays a new record.

13. Filter data to appear on the report as follows, and then click Next. Note that each succeeding line of the filter is connected with an And operator. You must use And in this case because every data item must meet all of the criteria to be included in the report.

•To include only purchase orders with a balance:

•Left Operand - Amount - Open (F4311)

Although you select Amount - Open (F4311) from the drop-down list, the item appears as BC Amount - Open (F4311). BC is a code that indicates the item is a business column.

•Comparison - is greater than

•Right Operand -

Note that you cannot enter a value of zero as a literal value.

•To include only purchase order items (purchase orders in the F4311 table are indicated by the code PO):

•Operator - And

•Left Operand - Order Type (F4311)

•Right Operand - OP

OP is a literal value. To insert it, select . The Single value form appears. Click the Single value tab, enter OP in the Order Type field, and click OK.

•To include only open purchase orders (indicated in the F4311 table by

any code except 999):

•Operator - And

•Left Operand - Status Code - Next (F4311)

•Comparison - is not equal to

•Right Operand - 999

999 is a literal value.

•To include only stocked items (indicated in the F4311 table by a code of S):

•Operator - And

•Left Operand - Line Type (F4311)

•Comparison - is equal to

•Right Operand - S

S is a literal value.

14. On the Director’s Finish form, click Finish.

Report Design appears, displaying the report you just created.

15. Click Save to save the report.

16. Click the Preview tab to see the report. It should look similar to the sample report illustration at the beginning of this section.

List of Product Codes

12 B = Language Translations

15 E = Industry Developed Prods
21 H = OneWorld Tools
22 S = OS/Server Translations

01 Address Book
02 Electronic Mail

03 Accounts Receivable
03B Enhanced Accounts Receivable
03C Issue Management System

04 Accounts Payable
07 Payroll
08 Human Resources
09 General Accounting
10 Financial Reporting
11 Multi Currency
12 Fixed Assets
16 Profit Management (EPS)
17 Customer Service Management

30 Product Data Management
31 Shop Floor Control
32 Configuration Management
34 Requirements Planning
36 Forecasting
37 Quality Management
39 Advanced Stock Valuation

40 Inventory/OP Base
4010 Advanced Price Adjustments

41 Inventory Management
41B Bulk Stock Management

42 Sales Management
42B Sales Order Entry
42E ECS Sales Management
42S Customer Self Service

43 Procurement
43A Purchase Order Receipt/Routing
43B Voucher Match and Landed Cost
43S Supplier Self Service

44 Subcontract Management
45 Advanced Pricing
46 Warehouse Management
47 Electronic Commerce

48S Service Billing
48 Transportation Management

51 Job Costing
53 Change Management

55,56,57,58,59 Reserved for clients

60,61,62,63,64,65,66,67,68,69 Reserved for JDE custom

70 Multi-National Products obsolete-do not reuse
71 Client Server Applications obsolete-do not reuse

74U United Kingdom Localizations
75A Australia Reporting System Only

75I India
75J Japan Reporting System Only

75S Singapore Reporting System Only
76N Canada Reporting System Only
76U United States Reporting System Only

85 Custom Programming
87 JDE Internal
89 Conversion Programs
91 Documentation
96 Computer Operations
97 Software Installation
98 Technical Tools
98FT Form Type

Data Items

A data item identifies a unit of information. The data item definition defines how the item can be used and Includes information such as the type of item and its length.

For creating a new data item in the data dictionary select the object and click Add

Select the option Data item button in the screen

Click OK

Data Item, Alias, Glossary Group, Description, Product Code, Data type and size are mandatory fields in this screen. After entering the data in the fields click Ok.

ERP Terminology

Application Server – Server where ERP logic is executed. A distributed ERP installation can have more than one Application Server.

Application Developers - Also known as App Developers. These developers use the ERP tools to develop ERP business application packages such as Financials, Manufacturing, Distribution, Human Resources, etc.

ASCII - American Standard Code for Information Interchange - Character set used by UNIX & Windows.

BDA – Business view Design Aid. This is the ERP CASE tool which is used to create and modify business views of data. See also FDA, RDA, and TDA.

Blobs – Binary Large OBjectS. A stream of data. Generally this is used as in reference to data structures put together end to end in a stream of data. Blobs may or may not be stored in database tables. For example, most of the TAM data is stored in blobs.

BSFN – Business Functions C code modules written by application developers. This term is used for both individual functions and for the actual C modules, which may contain multiple functions. For example, both b986150.c (the module) and ServerPackageTransfer (the function) will be referred to as business functions in different contexts.

Call Object – Running a business function. Also can be used to mean running a business function on a server. This is the mechanism which allows applications that are running on a client PC to run some set of logic on an enterprise server.

Client Install – A mechanism which installs an ERP Package from the deployment server to a client PC.

CQP – Customer Quality Program. Basically ERP Beta sites.

CRP – Conference Room Pilot. Part of the REP Methodology for going live with ERP. Involves setting up ERP in a pilot environment with options set up like they will be in the production environment.

Cumulative Release – A release containing changes to both system and application code. These releases are cumulative between base releases, i.e. B73.1.2 contains all changes that were done for B73.1.1. Also known as Cumms.

Data Sources – This is the F98611 table which defines how to access either data or servers. Such information as table owner, the connect string, and server name. This is used in conjunction with the OCM or F986101.

Deployment Server – Basically a file server which contains business function source, header, object, and DLL files; TAM specifications, and packages. This is where Object Librarian takes files when they are checked out, and puts them when they are checked in. Client Install takes a package from the deployment server and deploys it to a client PC.

DBCS - Double Byte Character Set. See Double Byte.

Double Byte – Character sets which require two bytes to describe each character, such as Chinese or Japanese.

EBCDIC - Extended Binary Coded Decimal Interchange Code - Character set used by the AS/400

Enterprise Server – Server where ERP logic is run. This is generally the primary ERP Application Server.

Environment – The set of TAM files, business functions, and data that are used when running ERP. What is in an environment is driven by the path code for the environment, which drives what set of business functions and TAM files are used, and by OCM, which describes where all of the data resides.

ER - Event Rules Specifications that describe what ERP will do when a given event occurs. Stored in the gbrspec TAM file..

Everest – What OneWorld was called internally before the name OneWorld picked. There is code which refers to Everest as well as K2, that other big mountain.

External Service Packs – ERP patches that are delivered to customers.

FDA – Form Design Aid. The ERP CASE tool used to create and modify ERP forms or applications interfaces. See also BDA, RDA, and TDA.

GBR – General Business Rule see Event Rules.

Global Build – The building of all business function objects and DLLs.

Global Table Specs – The specifications ERP needs to access a database table. ERP builds these from a variety of other table specifications as needed. The first time a table is accessed, ERP will build the global table specs for that table.

IFS – Integrated File System on the AS/400. The AS/400 has two types of file systems. The traditional uses a file(member) architecture, while IFS is hierarchical like DOS or Unix.

JDEBASE – The ERP database middleware

JDE – JDEdwards. Named for Jack Thomson, Dan Gregory, and Ed McVaney, the three founders.

JDBNET – The ERP database driver which allows heterogeneous servers to access each other’s data. For example, an AS/400 can access Oracle data on an HP9000 using JDBNET. JDBNET uses JDENET to communicate with other servers.

JDEIPC – This is the interprocess communication APIs within ERP. These functions are platform independent and allow processes to communicate with each other through message queues, shared memory, semaphores, etc.

JDENET – The ERP network middleware. JDENET runs over TCP/IP using sockets.

JITI – Just In Time Install. The retrieval of TAM specifications as they are needed. For example, if a user has installed a partial package and wishes to run an application that was not delivered in the package, ERP will automatically install what it needs to run the application.

JITR – Just In Time Replication. Used primarily for the UDC table. ERP checks to see if a UDC exists in the local Access database, if it is not there, ERP retrieves it from the main database and stores it in the Access database.

kernel – Not an OS kernel, rather the J.D. Edwards ERP foundation code. This is where the database middleware, the caching code, the business function calling mechanism, and other lower level functions are located.

kernel job – One of two types of jdenet processes. Kernel jobs are the processes on an enterprise server that really do the work calling a business function, submitting a UBE, retrieving data, etc. There can be 0 to many kernel jobs running on an enterprise server. The actual executable is jdenet_k.

kernel type – On an ERP application server, kernel jobs of different types can be started. For example, Security Server uses a different kernel type than JDBNET does.

Logic server – This term is often used as a synonym for application server or enterprise server. This phrase would never be used to describe a data-only server.

MBF – Master Business Function. MBFs are large business functions, which are frequently run on application servers.

net job – One of two types of jdenet processes. Net jobs are the processes on the server that handle all of the network communications. There can be 1 to many net jobs running on an enterprise server. The actual executable is jdenet_n.

NLS - National Language Support. ERP supports many national languages and cultural characteristics with a common set of program code. For the user interface, different sets of textual data is used for different languages. For character data sent to and received from different platforms, ERP performs the necessary data conversion to reserve data integrity.

OCM – Object Configuration Manager. This is what drives the “where” of ERP. OCM specifies where database tables are located, where business functions run, and where UBEs run. The OCM table is F986101 and works with the Data Sources table, F98611.

Object Librarian – Also known as OL. The application source code control. Before using any of the design tools, the object that is being worked on must be checked out through Object Librarian. Once the work is completed, the object is checked in through Object Librarian. Object Librarian stores the specifications for the object (TAM) in the relational database tables (RDB). Object Librarian stores business function source, header and object files on the deployment server.

ERP Tools – The ERP CASE tools. See also BDA, FDA, RDA, and TDA. Also can refer to the ERP Tools department, which encompasses much more than just the CASE tools. Basically the ERP Tools group is responsible for all of the “system” code within ERP.

Package – A group a TAM specifications, business functions, an Access database, and ERP system code. There are “full” packages, which include everything you need to run ERP on a client. There are “partial” packages, which include a base of ERP and uses JITI to get anything else needed to run ERP. There are “update” packages, which modify an existing package on a client PC.

Package Build – The application which reads the relational database files (RDB) and writes the TAM index and data files.

Paper Fix – Instructions for modifying an application to fix a bug. Generally, these are sent to customers by the application development groups. The tools group will usually have to send an external service pack to customers.

Path Code – The way TAM specifications, business functions, and local data are grouped. Each path code has its own set of RDB tables in a database and business functions on a deployment server.

PVC – Production Version Control. This is the group responsible for maintaining the source code control system, the environments, and for building the code for production.

RDA – Report Design Aid. This is the ERP CASE tool used to design batch processes or reports (UBEs). See also BDA, FDA, and TDA.

RDB Tables – Confusingly, this does not always refer to all tables in a relational database within the contexts of ERP. Rather, it is referring to the central repository for the TAM files. All TAM files are stored centrally in relational database files. TAM is actually built from these RDB tables in the package build process.

Runtime – The application engine. This is the piece of the system code which drives the applications via event rules that are stored in TAM.

SAR – Software Action Request. The bug tracking software we use. This runs only on the AS/400. Often, especially when working on External Service Packs, a SAR will be required to get code checked into Source Safe.

SAW - Server Administration Workbench. An interface allowing Server administrator to work with Server resources and Server environment on different platforms. A client SAW application allows users to get information about a Server running on a remote host.

SBCS - Single Byte Character Set. Text character sets in which each character can be described with a single character.

Security Server – The ERP server performing sign-on security and database access security. If the security server is not up and running nobody can get into ERP.

Server Package Install – The mechanism used to get TAM and business function updates from Object Librarian to enterprise servers.

Server Map – The OCM and data source tables for an enterprise server.

Snapshot – This is a process which stores an existing ERP installation on a client PC so that a user can run another installation. Snapshot allows the user to quickly and easily switch between versions of J.D. Edwards.

SPC – Software Protection Codes. These are authorization codes which are set up at a customer site as part of the initial install of ERP. Without correct codes, the customer will not be able to install ERP.

Spec Files – See TAM.

Spec Install – Transferring the TAM specifications for a version of a report from a client PC to an enterprise server when that version is being run on a server.

TAM – Table Access Manager. TAM is what our binary specifications are called. TAM specifications drive everything within ERP, the applications, the batch reports, access to the database tables, event rules, business function calls, data structures, etc. There are two components to each TAM type, a data file and an index file. TAM files exist both on the client PCs and the enterprise servers, although not all TAM files are put on the servers.

TBLE – Table An ERP object that stores data.

TC – Table Conversion. An ERP mechanism to convert non-ERP or “foreign” tables to ERP and vice-versa.

TDA – Table Design Aid. The ERP CASE tool used to create and modify database table layout and indexes. See also BDA, FDA, and RDA.

Tools Developers – ERP developers who develop the system code for ERP. This includes the design tools, the various engines, the middleware, etc.

UBE – Universal Batch Engine. This is the ERP report engine. UBEs are driven by TAM specs. UBEs can run on client PCs or on enterprise servers. When it a UBE is submitted to run on a server, often it will be referred to as “launching a UBE”.

UDC – User defined code. A set of valid values for a particular field.

E1 Acronyms

• APPL Application
• BDA Business View Design Aid
• BSFN Business Function
• BSVW Business View
• CRP Conference Room Pilot
• DD Data Dictionary
• DLL Dynamic Link Library
• DS or DSTR Data Structure
• ER Event Rules
• FDA Form Design Aid
• NER Named Event Rules
• OCM Object Configuration Manager
• OL Object Librarian
• OMW Object Management Workbench
• QBE Query by Example
• RDA Report Design Aid
• SAR Software Action Request
• Specs Specifications
• TAM Table Access Management
• TBLE Table
• TC Table Conversion
• TDA Table Design Aid
• TER Table Event Rules
• UBE Universal Batch Engine
• UTB Universal Table Browser
• WF Work Flow