6 Understanding and Working with Object Configuration Manager

This chapter contains the following topics:

6.1 Object Configuration Manager Overview

This section provides and overview of Object Configuration Manager functionality and discusses:

  • OCM Characteristics

  • OCM Information Requests

  • Object Mappings

6.1.1 OCM Functionality

The OCM provides the flexibility to map data, batch applications, and business functions to a data source, which enables you to coordinate the distributed processing. For example, you would map table objects to database data sources and logic objects to machine data sources

This table describes the minimum of two sets of the Object Configuration Master (F986101) and Data Source Master (F98611) tables that you must have:

One for All Workstations

The Object Configuration Master and Data Source Master tables that the software uses for workstation processing are stored in the centralized system data source normally kept on an enterprise server. If the system data source is not available, the software looks to the workstation's jde.ini file for a secondary location.

One per Logic Server

The Object Configuration Master and Data Source Master tables that the logic server uses are stored on that server in the server map data source. Each logic server type requires its own server map data source.

6.1.2 OCM Characteristics

OCM contains a large number of mappings that define where individual tables exist when looking for data. OCM also contains mappings that define where particular types of logic, specifically business functions or UBEs, will be processed. When a request for data or logic processing occurs, OCM directs it to the appropriate database or machine.

OCM has these characteristics:

  • Data and logic resources can be located on any machine, and EnterpriseOne must know where each resource is located.

  • OCM is the method of managing distributed data and distributed logic processing in an EnterpriseOne architecture configuration.

  • OCM is a collection of data sources, or pointers, to databases and logic processing machines.

6.1.3 OCM Information Requests

When an application requests data from a table or a logic object for processing, OCM points to the appropriate database data source.

This diagram illustrates an information request from OCM.

Figure 6-1 OCM Information Requests

Description of Figure 6-1 follows
Description of ''Figure 6-1 OCM Information Requests''

6.1.4 Object Mappings

In EnterpriseOne, business objects are used to configure distributed processing and distributed data at runtime. The Object Configuration Master table defines this configuration. You can work with the server object map to modify the entries in this table.

Workstation mappings are stored in a centralized system data source. The F986101 table used by the enterprise server is stored on that server in the server map data source. Each enterprise server requires a separate server map data source.

Compared to a workstation, an enterprise server processing a logic object has a different perspective of where data should be retrieved. For a workstation that is requesting user defined codes, its F986101 table (in the system data source) points to the local database.

When an enterprise server requests user defined codes, it makes no sense for the enterprise server to look to a workstation for this information; therefore, the enterprise server should have unique mappings for user defined codes. These mappings are set up in the Object Configuration Master table (F986101) in the server map data source.

If you have changed table F986101 for the workstation, you should check it in the server maps to see if they should also be changed. For example, if you have new environments with unique mappings for the workstation, you should check to see if changes are required in the corresponding mappings for the enterprise server.

The Object Configuration Manager also provides batch processes to help with the administration of the object mappings. These processes perform such tasks as comparing, updating, copying, and deleting Object Configuration Manager records.

6.1.4.1 Mapping Alternatives

You map objects by environment. You select an environment that you have already created and map that environment's objects to the data sources you want those objects to use. You can set default mappings for all instances of an object type to one data source, and you can map individual objects to data sources.

Mapping Object Types: Default Maps

To create a default map for an object type, create a mapping whose object name is the literal value: DEFAULT. Then enter an object type (such as TBLE) and a data source. By creating a default map for the object type TBLE, any table objects not mapped individually point to the default data source.

Mapping Individual Objects

You can map individual objects within an environment. For example, you can map a specific table, such as the Security Workbench Table (F00950), to a data source other than the default, such as to the system data source.

If you do not explicitly map an object by name in the Object Configuration Manager, the software uses the default map for that object's type.

Important:

Each environment must have a default map for TBLE (table) objects for the *PUBLIC user profile because there is no inherent default location for table objects. If table objects do not have a default map and are not explicitly mapped by name, the software produces a Select/Failed error message.

6.2 Distributed Architecture

The software enables you to distribute data and logic in a manner that optimizes both the power of the workstation and the data integrity of the server. This optimization provides you with:

Flexibility in determining your own partitioning schemes.

As requirements change, you can repartition the system quickly and easily to meet new needs.

Independence in using the data and logic objects that you need.

For example, if you are a salesperson on the road, you can download only the data and logic you need to quote prices and availability. Later, you can connect to the server and place the orders in a batch process.

Growth for your enterprise systems.

The system can be as large as you need because the software enables you to move objects around the system in practically endless combinations.

To keep track of where data resides and where logic processing occurs, the software uses a tool called the Object Configuration Manager. This tool enables users to specify data and logic processing locations.

6.3 Partitioning Application Logic on Servers

The logic for EnterpriseOne applications can be partitioned to run remotely by mapping individual or specified groups of business function components to run on an application server or enterprise server instead of on a workstation.

It has been found that redeploying certain business function components (including master business functions and business functions) can significantly increase the performance of a distributed EnterpriseOne workstation while simultaneously decreasing network traffic. This redeployment involves remapping objects using the EnterpriseOne standard Object Configuration Manager methodology.

Examples of such configurations are illustrated by the Windows light client/heavy server and the Java light client/heavy server models. Both models have applications specifications on the client and business function components on the server. The main difference is that the Windows model uses JDENet communication middleware, while the Java model uses JDENet/CORBA middleware.

While the software design enables you to partition all business function components, the biggest benefit is derived from partitioning Master Business Functions (MBFs).

EnterpriseOne transaction-oriented applications are built around the concept of MBFs, which are typically responsible for transaction edits and for committing transactions to the database. Most of the I/O services for transaction-oriented applications are performed by MBFs. By localizing the majority of business logic for transactions in MBFs and partitioning the MBFs to run on application servers, network traffic can be minimized, thus dramatically improving the performance of the application in distributed and WAN environments.

In a two-tier setup where MBFs are processed on the client, a lot of interaction occurs across the WAN between client and server. In a three-tier setup consisting of a client, a data server, and an application or enterprise server, transaction processing can occur across a LAN between the two servers. Interaction across the WAN between the client and server is thus reduced to entering input on the client and sending back results from the server. This three-tier configuration can result in a significant reduction in traffic across the WAN.

The following contrasts typical network traffic for a two-tier setup where MBFs are processed on the client versus network traffic segmentation for a three-tier setup where MBFs are processed on the server.

6.3.1 Two-Tier: Typical Network Traffic

In a two-tier configuration, the GUI, event rules, and MBFs are typically handled by the client, and data is stored on the server. Typically, this processing occurs across the WAN between client and server:

  • Fetch Record (client to server)

  • Return Record (server to client)

  • Validate Data Format (client to server)

  • Format OK (server to client)

  • Send Record Detail (client to server)

  • Detail OK (server to client)

  • End Transaction (client to server)

6.3.2 Three-Tier: Network Traffic Segmentation

In a three-tier configuration, the GUI and event rules are handled by the client, but an application server or enterprise server handles MBF processing. The database server stores data. This processing occurs across the WAN between client and application or enterprise server:

  • Input Processing Request or Data (client to server)

  • Return Processing Results (server to client)

This processing occurs locally across the LAN between the application or enterprise server and the database server:

  • Fetch Record

  • Return Record

  • Validate Data Format

  • Format OK

  • Send Record Detail

  • Detail OK

  • End Transaction

6.3.3 Master Business Function Operations

This series of events demonstrates how a typical application uses a Master Business Function (MBF). This example uses the Sales Order Entry application.

End of Sales Order Line

The first event occurs when the end of a sales order line is reached, causing the EnterpriseOne client application to call the jdeCallObject API. This command sends a message to the MBF. Included with the message is data (in the form of a data structure) for the line. The application sends the message asynchronously with its associated data; that is, once the message is sent, the client application proceeds to the next line.

MBF Receives Line Message

This event occurs when the MBF receives the JDENet message that includes the data for the line. The line data is cached in the server's shared memory.

MBF Extends and Edits the Line

This event occurs when the MBF extends and edits the sales order line. The data necessary to extend and edit the line is typically accessed locally on a LAN. The data is requested by a database-dependent SQL call and is transported by the applicable Open Database Connectivity (ODBC) or Oracle Call Level Interface (OCI) mechanisms.

MBF Sends a Return Message to the Client Application

This event, the fourth event, occurs after the MBF extends and edits the sales order line and returns the extended line, as well as any error codes, to the client. The return message is sent using JDENet. Events 1 through 4 are then repeated asynchronously for all of the lines associated with the sales order.

End of Sales Order (OK Button)

This event indicates that the user has completed all sales order lines. The user triggers this event by clicking OK after all edited lines have been returned to the client. When the user clicks OK, an end of transaction message is sent to the MBF. The client is immediately released to enter the next transaction.

MBF Processes the Full Transaction

The full transaction is processed when the MBF asynchronously reads the shared memory cache (where all transaction lines are stored) and begins the process of committing the transaction to the database.

Transaction Commitment to the Database and MBF Cleanup

The MBF commits the entire transaction to the database, typically locally through ODBC and OCI, and cleans up the shared memory cache for the completed transaction.

Mapping the MBF to run on the server causes the bulk of the database and logic interaction to occur within a single server machine (enterprise server) or between LAN-attached machines (application server and data server). Thus the transaction has been processed with a minimum of network traffic. This type of application transaction is ideally suited for performance gains in distributed and WAN environments.

6.4 Understanding Object Configuration Manager

The Object Configuration Manager (OCM) program (P986110) has the ability to distribute logic and data provides for flexibility in determining your own partitioning schemes. It also provides independence in using only the data and logic objects that you need and allows for growth within your enterprise systems. You can later add more databases to store data or machines to process logic. You would need to define the data sources for each and create appropriate OCM mappings.

The OCM stores information in tables that tell the software where data resides and where processing occurs. At runtime, the software looks to the OCM to determine these data and processing locations.

OCM configures distributed processing and data dynamically without any programming. Depending on the environment and the user, the OCM points to the correct location for:

  • Data

  • Batch processes

  • Business functions

  • Events

In EnterpriseOne, business data objects (tables) map to database data sources. Batch processes and business functions map to machine data sources. Events map to datasources.

You always need at least two OCM tables:

One table for all workstations.

Store this table in a centralized system data source. Normally, a central data server stores the system data source. If the central server is unavailable, EnterpriseOne looks to the workstation's jde.ini file for a secondary location.

One table for each logic server.

Servers process differently than workstations; for example, the server map data source for each logic server stores separate OCM tables for server processing.

6.4.1 Example: Application Request for Logic

This is an example of how the OCM works with a general logic request.

Step 1:

The request process for application logic is similar to data requests. The OCM controls where all business functions and batch processes are processed.

For example, when you add a purchase order, any event that calls a business function looks to the OCM to determine where to process that business function. After you click OK to complete a purchase order, the software calls a master business function to validate all information and record the transaction. The software can process these business functions locally or on the server.

The primary, unique index to the OCM includes:

  • Environment, such as PD910 or DV910.

  • User, which is either a specific User ID / Role or *PUBLIC.

  • Object name, such as F0101, B401002, or R09801.

  • Database path.

For this example:

  • The environment is PD910 (production).

  • The status is AV (active).

  • The object type can be either a batch process (UBE) or business function (BSFN).

This table describes the search hierarchy that the OCM uses to locate the correct data source for a logic request:

Search Sequence Object Name User or Role Search Criteria
1 B0900049 SI5745669 (user ID) Is there a record for the named environment, status active, type (UBE or BSFN) for the named object, and the specific user?
2 B0900049 OWTOOL (role) Is there a record for the named environment, status active, type (UBE or BSFN) for the named object, and the specific role?
3 B0900049 *PUBLIC Is there a record for the named environment, status active, type (UBE or BSFN) for the named object, and *PUBLIC?
4 DEFAULT SI5745669 (user ID) Is there a record for the named environment, status active, type (UBE or BSFN) with no named object (default), and the specific user?
5 DEFAULT OWTOOL (role) Is there a record for the named environment, status active, type (UBE or BSFN) with no named object (default), and the specific role?
6 DEFAULT *PUBLIC Is there a record for the named environment, status active, type (UBE or BSFN) with no named object (default), and *PUBLIC?
7 NA NA If there is no record for this object type, then the software processes the process on the workstation.

Step 2:

After the data source is determined, the software passes the definition of that data source to JDENet.

Step 3:

JDENet sends a message to the server to begin processing logic. When JDENet on the server receives the message, an EnterpriseOne process on the server responds to the message by processing the requested logic object.

6.5 Setting Up Object Configuration Manager

This section discusses how to set up processing option for Object Configuration Manager.

6.5.1 Form Used to Map Objects

Form Name FormID Navigation Usage
Object Configuration Manager W986110D In the Microsoft Windows client, in Solution Explorer, navigate to System Administration Tools, Object Configuration Manager (P986110).

In the web client enter P986110 in the Fast Path.

Determine the location where data is located and logic is run.

6.5.2 Setting Processing Options for Object Configuration Manager

The Object Configuration Manager program (P986110) has one processing option that controls error handling.

6.5.2.1 Process

Although processing options are set up during EnterpriseOne implementation, you can change processing options each time you run a program.

1. Non-existent table error

Specify whether an error or a warning should be issued when a table does not exist in the data source to which it is mapped. Values are:

1 Issue an error

Blank: Issue a warning

6.6 Setting Up Object Mappings for the Object Librarian Table

This section discusses how to set up object mappings for an Object Librarian table.

6.6.1 Forms Used to Set Up Object Mappings for the Object Librarian Table

Form Name FormID Navigation Usage
Machine Search & Select W986110D In Solution Explorer, navigate to System Administration Tools, System Installation Tools, Advanced Operations, Object Configuration Manager (P986110).

In the web client enter P986110 in the Fast Path.

Used to display the data source that stores the Object Configuration Manager table.
Work With Object Mappings W986110B In the Machine Search & Select form, select the data source you want and click Select. Used to display data sources that have the OCM Data Source field checked on the Data Source Revisions form.
Object Mapping Revisions W986110C In the Work With Object Mappings form, click Add. Used to add new object mappings for data sources.

6.6.2 Setting Up Object Mappings for the Object Librarian Table

Batch applications and business functions automatically run locally if there is no default map for that object type.

6.6.2.1 Machine Search & Select

The Machine Search & Select form displays data sources that have the OCM Data Source field checked on the Data Source Revisions form. Workstation use the system data source for their mappings. Each enterprise server has its own server map data source.

Access the Machine Search & Select form.

Figure 6-2 Machine Search & Select form

Description of Figure 6-2 follows
Description of ''Figure 6-2 Machine Search & Select form''

Machine Name

A value that defines the logic host to EnterpriseOne.

Data Source

The name that identifies the data source.

6.6.2.2 Object Mapping Revisions

Object Mapping Revisions is used to add new object mappings for data sources.

Access the Object Mappings Revisions form.

Figure 6-3 Object Mapping Revisions form

Description of Figure 6-3 follows
Description of ''Figure 6-3 Object Mapping Revisions form''

Environment

Specify the environment name is also called the Plan Name and is used to uniquely identify an upgrade environment for Install/Reinstall.

For EnterpriseOne (Environment or Version Applications) this is the path code that identifies the location of the application or version specification data.

Object Name

Specify the name that identifies a system object. EnterpriseOne ERP architecture is object-based. Discrete software objects are the building blocks for all applications. The Object Librarian tracks each object. Examples of system objects include:

  • Batch Applications

  • Interactive Applications

  • Business Functions

  • Business Functions Data Structures

  • Event Rules

  • Media Object Data Structures

Object Type

Specify the type of object with which you are working. For example, if you are working with tables the object type is TBLE, or business functions is BSFN.

BSFN Business Function Modules

GT Generic Text / Media Objects

RTE Real Time Event

TBLE Table Definition

UBE Batch Applications

XAPI Extended Third-Party API Call

Primary Data Source

Specify the name that identifies the data source.

System Role

Specify a profile that you use to classify user into groups for system purposes. You use group profiles to give the members of a group access to specific programs.

Some rules for creating a profile for a user class or group are as follows:

  • The name of the user class or group must begin with and Asterisk (*) so that it does not conflict with any system profiles.

  • The User Class/Group field must be blank when you enter a new group profile.

Object Status

Indicate the data source called by the specifies object.

Secondary Data Source

Use this data source if the primary data source or the data item in the primary data source cannot be located.

Allow OBE

Use this flag to turn On or OFF row-level record locking for the data source.

You should have this flag turned ON to help prevent database integrity issues.

JDEBASE middleware uses this flag to determine whether or not to use row-level record locking.

6.7 Changing Mappings for an Object Librarian Table

This section discusses how to change object mappings for an Object Librarian table.

6.7.1 Forms Used to Change Object Mappings

Form Name FormID Navigation Usage
Machine Search & Select W986115E In Solution Explorer, navigate to System Administration Tools, System Installation Tools, Advanced Operations, Object Configuration Manager (P986110). Used to display the data source that stores the Object Configuration Manager table.
Work With Object Mappings W986110B In Machine Search & Select form, select the data source and click Select. Used to display data sources that have the OCM Data Source field checked on the Data Source Revisions form.
Revise OL Data Source W986110G In the Work With Object Mappings form, click Revise OL DS from the Form menu. Used to map Object Librarian tables to a data source.

6.7.2 Changing Mappings for an Object Librarian Table

When you map any of the Object Librarian tables, the software validates your entries to ensure that all environments based on the same path code have their Object Librarian tables mapped to the same data source. The software alerts you with an error message if you map your Object Librarian tables to different data sources.

6.7.2.1 Work With Object Mappings

The Work With Object Mappings form is used to display data sources that have the OCM Data Source field checked on the Data Source Revisions form.

Access the Work With Object Mappings form.

6.7.2.2 Machine Search & Select

The Machine Search & Select form displays data sources that have the OCM Data Source field checked on the Data Source Revisions form. Workstation use the system data source for their mappings. Each enterprise server has its own server map data source.

Access the Machine Search & Select form.

Figure 6-4 Machine Search & Select form

Description of Figure 6-4 follows
Description of ''Figure 6-4 Machine Search & Select form''

Machine Name

A value that defines the logic host to EnterpriseOne.

Data Source

The name that identifies the data source.

6.7.2.3 Revise OL Data Source

Access the Revise OL Data Source form.

Figure 6-5 Revise OL Data Source form

Description of Figure 6-5 follows
Description of ''Figure 6-5 Revise OL Data Source form''

Path Code

Specify the path code to a set of EnterpriseOne objects that will be used to keep track of sets of objects and their locations within EnterpriseOne.

OL Data Source

Specify the name that identifies the data source.

6.8 Updating the Object Configuration System Table

This section discusses how to update the object configuration system table.

6.8.1 Forms Used to Run the Object Configuration System Table Update

Form Name FormID Navigation Usage
Work With Batch Versions - Available Versions W98305A In Solution Explorer, navigate to System Administration Tools, System Administration Tools, Data Source Management, Data Source Management Advance and Technical Operations, Object Configuration System Table Update (P98305). Used to add OCM records to the system table.
Versions Prompting W98305D In the Work With Batch Versions-Available Versions form, focus on a versionand select it. Used to change data selection or data sequencing before submitting a report.

6.8.2 Running the Object Configuration System Table Update

This program adds active Object Configuration Manager (OCM) records for a specified table, user ID, and data source for all environments listed in the Environment Detail table (F00941). You can use data selection to filter the environments to which this process adds OCM records.

Access the Work With Batch Versions - Available Versions form.

Figure 6-6 Work With Batch Versions - Available Versions form

Description of Figure 6-6 follows
Description of ''Figure 6-6 Work With Batch Versions - Available Versions form''

Version

A user defined set of specifications that control how applications and reports run. You use versions to group and save a set of user-defined processing option values, data selection and sequencing options. Interactive versions are associated with applications (usually as a menu selection). Batch versions are associated with batch jobs or reports. To run a batch process, you must choose a version.

Version Title

A description of the version that appears next to the version number. The version title is different from the report title.

This field should describe the use of a version. For example, an application for generating pick slips might have a version called Pick Slips - Accounting and another version called Pick Slips - Inventory Management.

User

Identifies the user ID of the user that last modified the application or version.

Last Modified

Indicates the last time the application or version was modified by the specified user.

Security

This field allows you to restrict user access for a report version.

Values are:

0 - No security - Anyone can design, change processing option values, change detail values, check in, check out, install, copy, transfer, delete, or run the version. This is the default when adding a new version.

1 - Medium Security Only the "Last Modified By" user can design, change processing option values, change detail values, check in, check out, or delete the version. Anyone call install, copy, transfer, or run the version. This is how JDE Demo versions are delivered.

2 - Medium to Full Security Only the "Last Modified By" user can design, change processing option values, change detail values, check in, check out, transfer, delete or run the version. Anyone call install or copy the version.

3 - Full Security Only the "Last Modified By" user can design, change processing option values, change detail values, check in, check out, install, copy, transfer, delete, or run the version. This is the default when adding a new version.

Description

A user defined name or remark.

Client Platform

A category code associated with the Versions List table for EnterpriseOne (F983051).

Figure 6-7 Version Prompting form

Description of Figure 6-7 follows
Description of ''Figure 6-7 Version Prompting form''

Data Selection

Turn this option on to change data selection before submitting the report.

Data Sequencing

Turn this option on to change data sequencing before submitting the report.

6.8.3 Setting Processing Options for Object Configuration System Table Update

Processing options enable you to specify the default processing for programs and reports.

6.8.3.1 Process

These processing options enable you to specify the table name, data source, and user ID to use in creating an OCM mapping. You can also specify whether to run the report in proof or final mode.

1. Enter a specific Table Name

Define which mailbox a message is sent to. Values are:

Blank: The field will be not visible when creating a new message.

1 The field will be visible when creating a new message.

2. Enter a specific Data Source

Specify the data source you want to map to each environment. The data source, along with the values you specify for the Table Name and User ID processing options, is used to create a whole OCM Mapping.

3. Enter a specific User ID

Identify the user ID that is mapped to each environment. The user ID, along with the values you specify for the Table Name and Data Source processing options, is used to create an OCM mapping.

4. Proof / Final Mode

Indicate whether records are changed or not changed when the batch application is run. Values are:

Blank: Proof mode

1 Final mode

6.9 Creating OCM Records for Business Functions

This section provides and overview of OCM Business Functions and discusses how to run the Create Server Business Function OCM Records Report.

6.9.1 Understanding Create OCM Records for Business Functions

This batch process (R986140) reads the Object Librarian tables for server business functions, and then creates Object Configuration Manager records for those business functions in the target data source that you specify in processing options. Processing options also enable you to specify the source data source and environment to use when creating these Object Configuration Manager records.

6.9.2 Forms Used to Create OCM Records for Business Functions

Form Name FormID Navigation Usage
Work With Batch Versions - Available Versions W98305A In Solution Explorer, navigate to System Administration Tools, System Administration Tools, Data Source Management, Data Source Management Advance and Technical Operations, Create OCM Records for Business Functions(P98305). Used to create OCM records for business functions.

6.9.3 Creating OCM Records for Business Functions

Access Work With Batch Versions-Available Versions form.

Version

A user defined set of specifications that control how applications and reports run. You use versions to group and save a set of user-defined processing option values, data selection and sequencing options. Interactive versions are associated with applications (usually as a menu selection). Batch versions are associated with batch jobs or reports. To run a batch process, you must choose a version.

Version Title

A description of the version that appears next to the version number. The version title is different from the report title.

This field should describe the use of a version. For example, an application for generating pick slips might have a version called Pick Slips - Accounting and another version called Pick Slips - Inventory Management.

User

Identifies the user ID of the user that last modified the application or version.

Last Modified

Indicates the last time the application or version was modified by the specified user.

Security

This field allows you to restrict user access for a report version.

Values are:

0 - No security - Anyone can design, change processing option values, change detail values, check in, check out, install, copy, transfer, delete, or run the version. This is the default when adding a new version.

1 - Medium Security Only the "Last Modified By" user can design, change processing option values, change detail values, check in, check out, or delete the version. Anyone call install, copy, transfer, or run the version. This is how JDE Demo versions are delivered.

2 - Medium to Full Security Only the "Last Modified By" user can design, change processing option values, change detail values, check in, check out, transfer, delete or run the version. Anyone call install or copy the version.

3 - Full Security Only the "Last Modified By" user can design, change processing option values, change detail values, check in, check out, install, copy, transfer, delete, or run the version. This is the default when adding a new version.

Description

A user defined name or remark.

Client Platform

A category code associated with the Versions List table for EnterpriseOne (F983051).

Figure 6-8 Version Prompting form

Description of Figure 6-8 follows
Description of ''Figure 6-8 Version Prompting form''

Data Selection

Turn this option on to change data selection before submitting the report.

Data Sequencing

Turn this option on to change data sequencing before submitting the report.

6.9.4 Setting Processing Options for Create OCM Records for Business Functions

Processing options enable you to specify the default processing for programs and reports.

6.9.4.1 Process

These processing options enable you to specify the run mode, data source, environment and target data source to use in creating OCM records for business functions.

1. Specify proof or final mode.

When you enter 1, the report runs in Final mode, which means that the report will be printed and reports will be updated. When you enter 0 or leave this field blank, the report runs in Proof mode, which means that the report will be printed but not updated.

2. Enter the Data Source Name.

Specify the machine data source that corresponds to the server you wish to run the business function on.

3. Enter the Environment Name.

Specify the environment you wish to use realtime events on.

4. Enter the name of the Target Data Source where the OCM records are to be placed.

Specify the system data source that the client-to-server machines use.

6.10 Updating the Oracle Parameters Table

This section discusses how to update the Oracle parameters table.

6.10.1 Forms Used to Update the Oracle Parameters Table

Form Name FormID Navigation Usage
Work With Oracle Database Object Sizing W9861151A In Solution Explorer, navigate to System Administration Tools, System Administration Tools, Data Source Management, Object Configuration Manager (P986110).

In the Machine Search & Select form, highlight the row you want and click Select.

In the Work With Object Mappings form, highlight the row you want and then select Oracle Parms from the Row menu.

Used to modify the Oracle database object table fields.
Oracle Database Object Sizing W9861151B In the Work With Oracle Database Object Sizing form, click Add. Used to revise and add table and index information for a data source or table.
Revise Database and Data Source Overrides W9861151C In the Work With Oracle Database Object Sizing form, select Overrides from the Form menu. Used to select override information for an Oracle table.

6.10.2 Updating the Oracle Parameters Table

You must update the Oracle parameters table if you use Oracle and do not follow the recommended naming conventions or if you add new Oracle data sources.

6.10.2.1 Machine Search & Select

Machine Search & Select is used to display the data source that stores the Object Configuration Manager table. The data source resides on a machine. Workstations use the system data source for their mappings. Each enterprise server has its own server map data source.

Access the Machine Search & Select form.

Machine Name

A value that defines the logic host to EnterpriseOne.

Data Source

The name that identifies the data source.

6.10.2.2 Work With Oracle Database Object Sizing

Access the Work With Oracle Database Object Sizing form.

Figure 6-9 Work With Oracle Database Object Sizing form

Description of Figure 6-9 follows
Description of ''Figure 6-9 Work With Oracle Database Object Sizing form''

Release Number

Specify the release number as defined in the Release Master.

Depending on whether you select a data source for the DEFAULT map or for a specific object, different fields appear on the Oracle Database Object Sizing form.

For the DEFAULT map, you can define only the name of the Oracle space where tables or indexes reside. However, for a specific object you can define parameters such as the amount of space to use for an Oracle table.

Data Source

Specify the name that identifies the data source.

Object Name

Define parameters for all objects in a data source, type DEFAULT in this field.

Enter the name that identifies a system object. EnterpriseOne architecture is object-based. Discrete software objects are the building blocks for all applications, and developers can reuse the objects in multiple applications. The Object Librarian tracks each object. Examples of system objects include:

  • Batch Applications (such as reports)

  • Interactive Applications

  • Business Views

  • Business Functions

  • Business Functions Data Structures

  • Event Rules

  • Media Object Data Structures

Object Description

Specify a user defined name or remark.

6.10.2.3 Oracle Database Object Sizing

Oracle Database Object Sizing is used to revise and add table and index information for a data source or table.

Access the Oracle Database Sizing form.

Figure 6-10 Oracle Database Object Sizing form

Description of Figure 6-10 follows
Description of ''Figure 6-10 Oracle Database Object Sizing form''

Data Source

Specify the name that identifies data source.

Object Name

Specify the name that identifies a system object. EnterpriseOne architecture is object-based. Discrete software objects are the building blocks for all applications, and developers can reuse the objects in multiple applications. The Object Librarian tracks each object. Examples of system objects include:

  • Batch Applications (such as reports)

  • Interactive Applications

  • Business Views

  • Business Functions

  • Business Functions Data Structures

  • Event Rules

  • Media Object Data Structures

Release

Specify the release number as defined in the Release Master.

Depending on whether you select a data source for the DEFAULT map or for a specific object, different fields appear on the Oracle Database Object Sizing form.

For the DEFAULT map, you can define only the name of the Oracle space where tables or indexes reside. However, for a specific object you can define parameters such as the amount of space to use for an Oracle table.

Table Space Name

Specify the name of an Oracle region of space created to store tables.

Index Space Name

Specify the name of an Oracle region of space created to store indexes.

6.10.2.4 Revise Table and Data Source Overrides

Access the Revise Table and Data Source Overrides form.

Figure 6-11 Revise Table and Data Source Overrides form

Description of Figure 6-11 follows
Description of ''Figure 6-11 Revise Table and Data Source Overrides form''

Copy Data (Y/N)

Indicate if a file and its data are copied into production. A value of N moves the file without data during a file copy. When the system creates a production data library from JDFDATA, this field designates whether the data is included in the copy.

Create Tables (1/0)

Denote whether tables are automatically created for this data source.

See UDC H96/CR.

6.11 Revising the Generic Text Language Status Table

This section discusses how to revise the Generic Text Language Status table.

6.11.1 Understanding Revising the Generic Text Language Status Table

The Generic Text Language Status table (F001651) has more mapping flexibility than other objects because the data stored in this table has different uses. The generic text categories are as follows:

Common data that all environments use.

For example, data dictionary glossaries and business function notes are the same across all environments.

Production data specific to an environment.

For example, inventory item notes and address book supplemental data can be different for a corporation running EnterpriseOne over multiple environments, such as production, test, and demo data.

6.11.1.1 Example: Object Configuration Master Table (F986101)

This table is an example what the Object Configuration Master table (F986101) looks like after installing EnterpriseOne if your business follows the typical configuration: (This example includes only the PD910 (production) and TS910 (test) environments).

Environment Object Name Description Data Source Object Type
PD910 F00165 Generic Text Table Business Data - Prod TBLE
PD910 GT92002 Data Dictionary Glossary Data Dictionary GT
PD910 GT9860A Object Librarian Object Librarian GT
PD910 GT9862A Business Function Notes Object Librarian GT
PD910 GT98DSA Data Structure Notes-Structure Object Librarian GT
PD910 GT98DSB Data Structure Notes-Structure and Item Object Librarian GT
PD910 GT98TMPL Media Objects Templates Object Librarian GT
TS910 F00165 Generic Text Table Business Data - Test TBLE
TS910 GT92002 Data Dictionary Glossary Data Dictionary GT
TS910 GT9860A Object Librarian Object Librarian GT
TS910 GT9862A Business Function Notes Object Librarian GT
TS910 GT98DSA Data Structure Notes-Structure Object Librarian GT
TS910 GT98DSB Data Structure Notes-Structure and Item Object Librarian GT
TS910 GT98TMPL Media Objects Templates Object Librarian GT

6.11.2 Forms Used for Revising the Generic Text Language Status Table

Form Name FormID Navigation Usage
Select User Defined Code W0005SB In the Work With Object Mappings form, click Add.

In the Object Type field, click Search and Select.

Used to map specific generic text objects.

6.11.3 Revising the Generic Text Language Status Table

Access the Select User Defined Code form.

Figure 6-12 Select User Defined Code form

Description of Figure 6-12 follows
Description of ''Figure 6-12 Select User Defined Code form''

Code

A list of valid codes for a specific user defined code list.

Description

A user defined name or remark.

6.12 Understanding Object Configuration Management Reports

This section provides an overview of Object Configuration Management reports and discusses how to use a batch application to set processing options for running the reports.

6.12.1 Understanding Object Configuration Management Reports

Batch Versions provide batch processes that produce reports that helps you track your object mappings.

Some of these reports are called when you select that report from the EnterpriseOne menu while other reports are called from a batch application. Although the result is the same, you set processing options and data selection differently for a batch process than for a report called from a batch application.

Any data selection for a report must be entered for the specific report and not from the batch application. When you finish entering processing options and data selection, if any, you can run the report from the batch application.

  • Job Master Deletion By Days Old

  • Object Configuration Mapping Comparison

  • Object Configuration Global Update

  • Object Configuration Delete

  • Object Configuration Copy

  • OCM Category Update/Delete report

6.13 Running Job Master Deletion by Days Old Report

This section lists the prerequisites and discusses how to set up and run the Job Master Deletion by Days Old report.

6.13.1 Understanding the Job Master Deletion by Days Old Report

This batch application lets you produce a report listing obsolete print jobs submitted to servers. You have the option of generating the report only, or generating the report and then deleting obsolete records from the Job Control Status Master table (F986110).

This batch application is launched by a report driver. Enter any data selection from the batch application, but enter processing options from the report driver (R9861101), not from the actual application (R9861102).

6.13.2 Prerequisites

Set up processing options for the report from Batch Versions, not from the actual report.

6.13.3 Forms Used by Job Master Deletion by Days Old Report

Form Name FormID Navigation Usage
Work With Batch Versions - Available Versions W98305A In Solution Explorer, navigate to Report Management, Report Management Advanced and Technical Operations, Job Master Deletion by Days Old Report(P98305). Used to produce a report listing obsolete print jobs submitted to servers.

6.13.4 Running the Job Master Deletion by Days Old Report

Access the Work With Batch Versions - Available Versions form.

Figure 6-13 Work With Batch Versions - Available Versions form

Description of Figure 6-13 follows
Description of ''Figure 6-13 Work With Batch Versions - Available Versions form''

Versions

A user-defined set of specifications that control how applications and reports run. You use versions to group and save a set of user-defined processing option values and data selection and sequencing options. Interactive versions are associated with batch jobs or reports. To run a batch process, you must choose a version.

Version Title

A description of the version that appears next to the version number. The version title is different from the report title.

This field should describe the use of a version. For example, an application for generating pick slips might have a version called Pick Slips - Accounting and another version called Pick Slips - Inventory Management.

User

Identifies the use ID of the user who last modified the application or version.

Last Modified

Indicates the last time an application or version was modified by the specified user.

Security

This field allows you to restrict user access for a report version. Values are:

0 - No security. Anyone can design, change processing values, change detail values, check in, check out, install, transfer, copy, delete, or run the version. This is the default when adding a new version.

1 - Medium security. Only the "Last Modified By" user can design, change processing values, change detail values, check in, check out, install, transfer, copy, delete, or run the version. This is how JDE Demo versions are delivered.

2 - Medium to full security. Only the "Last Modified By" user can design, change processing values, change detail values, check in, check out, transfer, delete, or run the version. Anyone can install or copy the version.

3 - Only the "Last Modified By" user can design, change processing values, change detail values, check in, check out, install, transfer, copy, delete, or run the version.

4 - Medium security-extended. Only the "Last Modified By" user can design, change processing values (including runtime processing options and data selection), change detail values, check in, check out, transfer, delete, or run the version. Anyone can install or copy the version.

Description

A user defined name or remark.

Client Platform

A category code associated with the Versions List table for EnterpriseOne (F983051).

6.13.5 Setting Processing Options for Job Master Deletion by Days Old Report

Use these processing options to set up the defaults and versions for the report.

6.13.5.1 Defaults

Use this processing option to set up the data source, number of days to query for, and the report type.

1. Data Source

Specify the name that identifies the data source.

2. Days Old

Specify the number of days in future to query for responses due.

3. Control Mode

Select an option that specifies the type of processing for an event.

1 = Proof Mode

2 = Final Mode

4. Delete Mode

Specify the records to delete.

1 = Delete both UBE and Report Definition records

2 = Delete UBE records only

3 = Delete Report Definition records only

6.13.5.2 Versions

Use this processing option to specify a specific version.

1. Job Control Status UBE (R9861102)

Select a user defined specification that determines how application and reports run. You use versions to group and save user-defined processing option values and data selection and sequencing options. Interactive versions are associated with applications (usually as a menu selection). Batch versions are associated with batch jobs or reports. To run a batch process, you must choose a version.

XJDE0001 = Jobs With All Status

XJDE0002 = Jobs With Done Status

XJDE0003 = Jobs With Error Status

XJDE0004 = Jobs With Wait Status

6.13.6 Setting Data Selection for the Job Master Deletion by Days Old Report

Access the Data Selection form.

Figure 6-14 Data Selection form

Description of Figure 6-14 follows
Description of ''Figure 6-14 Data Selection form''

Enter condition by selecting from the options provided in each cell of the template.

Operator

Where

Left Operand

Select the primary data source from the list.

Comparison

is equal to

is equal to or empty

is greater than

is greater than or equal to

is less than

is less than or equal to

is not equal to

Right Operand

Select the secondary data source from the list.

6.14 Running Object Configuration Interactive and Batch Applications

This section lists the prerequisites and discusses how to set up and run Interactive and Batch Applications.

6.14.1 Understanding Interactive and Batch Applications

These batch applications have processing options that are entered from Batch Applications (R98611A) using the same processing option form:

  • Object Configuration Mapping Comparison (R986101)

  • Object Configuration Global Update (R986110)

  • Object Configuration Delete (R986120)

  • Object Configuration Copy (R986121)

6.14.2 Prerequisites

Set up processing options for the report from Batch Versions, not from the actual report.

6.14.3 Forms Used for Object Configuration Batch Applications

Form Name FormID Navigation Usage
Work With Batch Versions - Available Versions W98305A In Solution Explorer, navigate to Application Development, Object Management, Interactive and Batch Versions, Batch Versions (P98305). Used to set up and run batch applications and reports.

6.14.4 Setting Processing Options for Batch Applications

These processing options enable you set other parameters used by the specific batch application.

6.14.4.1 Driver

Use these processing options to specify which report and version to run.

1. Object Configuration Manager Report Name

Specify the name of the report that you want to run. Values are:

R986101 = OCM Mapping Comparison

R986110 = OCM Global Update

R986120= Object Configuration Delete

R986121 = Object Configuration Copy

2. Version

Specify the version of the report that you want to run.

You must enter report processing options before running the report.

If data selection is necessary, it must be done on the version of the report that you specified on the Driver tab.

6.14.4.2 R986101

Use these processing options to specify parameters when running the R986101 report.

1. Data Source One

Specify the names of the data sources that you want to compare. If necessary, you can use the Visual Assist feature to locate valid data sources. Click the Visual Assist button to display the Data Source Search and Select form.

2. Comparison Data Source Two

Specify the names of the data sources that you want to compare. If necessary, you can use the Visual Assist feature to locate valid data sources. Click the Visual Assist button to display the Data Source Search and Select form.

3. Comparison Method

Specify the comparison method used. Values are:

1 Compare one direction only. Print only the records found in the first data source, but not in the second data source.

Blank: Compare both directions. Print records found in the first data source but not in the second data source, and also the records in the second data source that don't exist in the first data source.

4. Exceptions

Specify whether to print only the report exceptions, or every record from the data selection, noting the differences between the data sources. Values are:

1 Print exceptions only

Blank: Print all records

6.14.4.3 R986110

Use these processing options to specify parameters when running the R986110 report.

1. Process Mode

Specify the mode in which the report processes data. Valid options are:

1 Proof Mode. This mode produces a report that enables you to view the records you want to delete, but no records are deleted.

Blank: Final Mode. This mode produces a report of records you want to delete, and then deletes the records.

2. Data Source name

Specify the name of the data source for the Object Manager Configuration table. Any updates that occur as a result of running this report will be made to the Object Manager Configuration table found in the specified data source.

3. Process Control

Specify whether to create new OCM records or change existing ones. Values are:

1 Create new OCM records from existing ones. The records created will look similar to those selected, except that the new OCM values entered in the processing options will be substituted where appropriate.

Blank: Change selected records with new OCM values. Use data selection to specify which records will be changed with the new OCM values entered into the processing options.

4. Enter the new OCM values:

Use this processing option to enter new OCM values. If you are creating new OCM records from existing ones, any values you enter for this processing option will replace the existing ones. Values are:

  • Environment Name

  • Object Name

  • Primary Data Source

  • User

  • Object Type

  • Data Source Mode

  • Secondary Data Source

  • Allow QBE

6.14.4.4 R986120

Use these processing options to specify parameters when running the R986120 report.

1. Process Mode

Specify the mode in which the report processes data. Valid options are:

1 Proof Mode. This mode produces a report that enables you to view the records you want to delete, but no records are deleted.

Blank: Final Mode. This mode produces a report of records you want to delete, and then deletes the records.

2. Enter Data Source name

Specify the name of the data source for the Object Manager Configuration table. Any updates that occur as a result of running this report will be made to the Object Manager Configuration table found in the specified data source.

3. Object Copy

Specify whether to run the Object Configuration Copy report (R986121) along with the Object Configuration Delete report. Values are:

1 Run the Object Copy (R986121). Creates a copy before deleting records. When you run the Object Copy, remember to enter the processing options under the R986121 tab, and to set up any data selection. Data Selection should be defined on the same version of R986121 that you specified for R986121 (Object Configuration Delete).

Blank: Do not run Object Copy. Deletes the records without first creating a copy.

6.14.4.5 R986121

Use these processing options to specify parameters when running the R986121 report.

1. Process Mode

Specify the mode in which the report processes data. Valid options are:

1 Proof Mode. This mode produces a report that enables you to view the records you want to delete, but no records are deleted.

Blank: Final Mode. This mode produces a report of records you want to delete, and then deletes the records.

2. From Data Source

Specify the name of the data source with the Object Configuration Manager table from which you want to copy records.

3. Target Data Source

Specify the name of the data source with the Object Configuration Manager table to which you want to copy.

6.14.5 Setting Data Selection for Object Configuration Batch Applications

Access the Data Selection form.

Enter condition by selecting from the options provided in each cell of the template.

Operator

Where

Left Operand

Select the primary data source from the list.

Comparison

is equal to

is equal to or empty

is greater than

is greater than or equal to

is less than

is less than or equal to

is not equal to

Right Operand

Select the secondary data source from the list.

6.15 Running the Object Configuration Mapping Comparison Report

This section lists prerequisites and discusses how to set up and run the Object Configuration Mapping Comparison Report.

6.15.1 Understanding the Object Configuration Mapping Comparison Report

Run the Object Configuration Comparison report to compare Object Configuration Master tables (F986101) from two different data sources and display the differences between them. For example, you might compare the F986101 table in the system data source to the F986101 table for a given server map data source.

6.15.2 Prerequisite

Set up processing options for the report from the report driver, not from the actual report.

6.15.3 Forms Used to Run the Object Configuration Mapping Comparison Report

Form Name FormID Navigation Usage
Work With Batch Versions - Available Versions W98305A In Solution Explorer, navigate to Application Development, Object Management, Interactive and Batch Versions, Batch Versions (P98305).

In the Batch Application field, enter R986101, then click Find.

Used to compare Object Configuration Master tables (F986101) from two different data sources and display the differences between them.

6.15.4 Running the Object Configuration Mapping Comparison Report

Access the Work With Batch Versions - Available Versions form.

6.16 Running the Object Configuration Global Update Report

This section lists prerequisites and discusses how to set up and run the Object Configuration Global Update Report.

6.16.1 Understanding the Object Configuration Global Update Report

This process performs global updates and global copies of object mappings in the same Object Configuration Master table (F986101). You can use this batch application rather than the interactive application (P986110). This application is useful in updating and copying multiple records.

6.16.2 Prerequisite

Set up processing options for the report from the report driver, not from the actual report.

6.16.3 Forms Used to Object Configuration Global Update Report

Form Name FormID Navigation Usage
Work With Batch Versions - Available Versions W98305A In Solution Explorer, navigate to Application Development, Object Management, Interactive and Batch Versions, Batch Versions (P98305).

In the Batch Application field, enter R986101, then click Find.

Used to performs global updates and global copies of object mappings in the same Object Configuration Master table (F986101).

6.16.4 Running the Object Configuration Global Update Report

Access the Work With Batch Versions - Available Versions form and run the Object Configuration Update Report (R986110).

6.17 Running the Object Configuration Delete Report

This section lists prerequisites and discusses how to set up and run the Object Configuration Delete Report.

6.17.1 Prerequisite

Set up processing options for the report from the report driver, not from the actual report.

6.17.2 Form Used to Run the Object Configuration Delete Report

Form Name FormID Navigation Usage
Work With Batch Versions - Available Versions W98305A In Solution Explorer, navigate to Application Development, Object Management, Interactive and Batch Versions, Batch Versions (P98305).

In the Batch Application field, enter R986120, then click Find.

Used to delete object mappings in the same Object Configuration Master table (F986101).

6.17.3 Running the Object Configuration Delete Report

Access the Work With Batch Versions - Available Versions form and run the Object Configuration Delete Report (R986120).

6.18 Running the Object Configuration Copy Report

This section lists the prerequisites and discusses how to set up and run the Object Configuration Copy Report.

6.18.1 Understanding the Object Configuration Copy Report

This process copies Object Configuration Manager records from one data source to another and automatically deletes any duplicate records. For example, if you create a new environment by copying an existing one, Object Configuration Manager records are created for the new environment in the system data source.

You use the Object Configuration Copy batch process to copy those records to the appropriate server map data source. After copying the records, use the Object Configuration Global Update program (R986110) to change, at the minimum, any mappings for LOCAL to the appropriate server location.

6.18.2 Prerequisite

Set up processing options for the report from the report driver, not from the actual report.

6.18.3 Forms Used for the Object Configuration Copy Report

Form Name FormID Navigation Usage
Work With Batch Versions - Available Versions W98305A In Solution Explorer, navigate to Application Development, Object Management, Interactive and Batch Versions, Batch Versions (P98305).

In the Batch Application field, enter R986121, then click Find.

Used to copy Object Configuration Manager records from one data source to another and automatically deletes any duplicate records.

6.18.4 Running the Object Configuration Copy Report

Access the Work With Batch Versions - Available Versions form and run the Object Configuration Copy Report (R986121).

6.19 Running the OCM Category Update/Delete Report

This section provides an overview of the OCM Category Update/Delete Report and discusses how to set up and run the OCM Category Update/Delete report.

6.19.1 Understanding the OCM Category Update/Delete Report

This batch application (R986101B) lets you add, update, or delete member objects of a specified category from the Object Configuration Master table (F986101).

6.19.2 Prerequisites

Set up processing options for the report from the report driver, not from the actual report.

6.19.3 Forms Used for the OCM Category Add/Update/Delete Report

Form Name FormID Navigation Usage
Work With Batch Versions - Available Versions W98305A In Solution Explorer, navigate to Application Development, Object Management, Interactive and Batch Versions, Batch Versions (P98305).

In the Batch Application field, enter R986101B, then click Find.

Used to add, update, or delete member objects of a specified category from the Object Configuration Master table (F986101).

6.19.4 Running the OCM Category Add/Update/Delete Report

Access the Work With Batch Versions - Available Versions form and run the Add/Update/Delete Report (R986101B).

6.19.5 Setting Processing Options for the OCM Category Add/Update/Delete Report

Processing options for the OCM Category Add/Update/Delete report include:

6.19.5.1 OCM Modes

These processing options let you add or delete OCM mappings for all members in the same category rather than adding or deleting them individually.

Proof or Final Mode

Enter 1 to run the report in Proof mode. The report will print and the Object Configuration Manager table will not be updated. Enter 2 to run the program in Final mode. The report will print and the Object Configuration Manager table will be updated.

Add or Delete Mode

Enter 1 to add OCM mappings for objects in the category or 2 to delete mappings.

Override Mapping

Enter 1 to delete OCM mappings for objects that already have mappings for the environment and user. Enter 2 or leave this field blank to deactivate but not delete mappings for conflicting OCM records.

6.19.5.2 OCM Settings

These processing options enable you to specify whether to add or delete mappings, as well as the appropriate path code, environment, and data source to use.

Path Code to use when adding or deleting OCM mappings

When you enter a path code, mappings are added or deleted for all environments with the path code you enter. You do not need to enter a path code if you entered an environment name in the Environments processing option. If this field is blank, OCM mappings will be added or deleted regardless of the path code.

Environment to use when adding or deleting OCM mappings

If this field is blank, OCM mappings are added or deleted regardless of the environment. If you entered a path code in the Path Code processing option, that path code is used. If both the Environments and Path Code processing option fields are blank, OCM mappings will be added or deleted for all environments in the Environment Detail table (F00941).

User Class/Role

If you are deleting OCM mappings and this field is blank, all OCM records will be deleted regardless of the user class or role. If you are adding OCM mappings, you must enter a value in this field.

Data Source

If you are deleting OCM mappings and this field is blank, all OCM records will be deleted regardless of the data source. If you are adding OCM mappings, you must enter a value in this field.