4 Understanding and Setting Up Data Sources

This chapter contains the following topics:

4.1 Data Sources

The data sources define where the database tables reside and where the software runs logic objects for the enterprise. Data sources can point to:

  • A database in a specific location (for example, a local database, such as E1Local located in \E910\data, or an IBM i data library, such as PRODDATA).

  • A specific machine in the enterprise that processes logic.

Data source definitions are stored in the Data Source Master table (F98611). Workstations use a Common table F98611, which generally resides in the system data source on the enterprise server. EnterpriseOne servers that process logic and request data require their own unique definitions for data sources; therefore, they have their own table F98611 in the server map data source.

A least two sets of table F98611 exist. They reside in a centralized system data source normally kept on an enterprise server which is accessed by workstations, and in a server map data source, which each logic server requires.

4.1.1 Data Source Types

Data sources are the building blocks that you use to set up an enterprise configuration. Data sources define all the databases and logic machines required by the EnterpriseOne configuration. Each database and machine in the enterprise must be defined as a data source for EnterpriseOne to recognize it.

There are two types of data sources:

Database Data Sources

A database is a grouping of tables in a database management system. You must identify databases to the applications that access them. You can distribute databases across a network and involve various servers and database management systems. A database data source identifies the database information that the software needs to connect to a database.

Logic Machine Data Sources

A logic machine is the machine on which batch applications and master business functions run. You must identify logic machines using a data source definition. The data source definition must include the network information about the machine, such as a server name - HP9000, for example.

When mapping logic objects for distributed processing, the software uses the machine data source (distributed processing data source) as the target location for processing logic objects.

4.1.2 Data Source Names

Data source names that you define are names used to identify the data source. You should use a meaningful name for the data sources. For example, to indicate that you are storing business data for production users, the data source name could be Business Data - Prod.

EnterpriseOne provides demonstration data source names at installation; you can use these for your own data sources.

See JD Edwards EnterpriseOne Applications Release 9.2 Upgrade Guide (for your database and platform).

4.1.3 Data Source Definitions

The data source definition must contain information about the database and the server in which it is located. Different database management systems identify the databases in different ways. For example, you must identify Oracle databases by the Oracle SQL*Net V.2 connect string. You must identify databases that you access through ODBC by the ODBC data source name.

4.1.4 Network Machine/Server Names

Database management systems reside on a machine/server. You must identify this machine/server to the network so that other computers can access its resources. You must provide to EnterpriseOne (in the data source definition) the machine/server name for the machine/server that hosts the database management system in which the database resides.

4.2 Required Data Source Types

You must set up a minimum number of data sources for EnterpriseOne to run. Two of the required data sources define machines that process logic in the enterprise. The other data sources define various databases used in the enterprise.

The installation software provides samples of these required data sources to build your system configuration:

Object Librarian

This data source points to the Object Librarian tables you use for custom development. You should have only one set of Object Librarian tables for each software release, regardless of how many path codes (sets of central objects) you maintain. This data source can reside on any supported platform. The Object Librarian data source is named by base release number; for example, Object Librarian - 910.

System

This data source consists of the technical tables you use to run all EnterpriseOne applications. You must set up one system data source per release.

All workstations use a central set of system tables usually stored on the enterprise server but not on the deployment server. Each logic server requires its own subset of system tables. These server system tables are stored in the server map data source.

When running applications, the system tables provide:

  • Object mappings (location of tables, batch processes, and business functions)

  • Data source definitions

  • EnterpriseOne security

  • Next IDs (used for development only)

Data Dictionary by Release

This data source enables you to store data dictionary master tables in a central location to enable easier administration of changes. Group these master tables together to form a data dictionary database. You should share one data dictionary between the production (such as PD910) and development (such as DV910) path codes. The software allows one data dictionary per path code, but multiple data dictionaries are not recommended or supported. The Data Dictionary data source is named by base release number-for example, Data Dictionary - 910, Data Dictionary - B7334, or Data Dictionary - B732.

Local

This data source defines the EnterpriseOne workstation. Use this data source to override the process location of a batch application that you mapped in the Object Configuration Manager to run on the server.

Business Data

This data source is used when you divide the business data into multiple owners or libraries, which can reside on the same enterprise server or on different ones. Each group of data requires a separate data source. The installation software provides demonstration data that you can copy to supported host databases. The data source name is Business Data - PS910.

Some examples of business data include:

  • Production data (non technical data, such as financial and manufacturing data)

  • Test data

  • Demo data (demonstration or training data)

  • Conference Room Pilot (CRP) data

Distributed Processing

This data source definition contains information that the software uses to identify the logic machine in the network. You need to define each logic machine as a data source.

Server Map

This data source enables you to create for each logic server its own subset of system tables, which are called server map tables. Server map tables are required for each logic server. You must maintain these tables to ensure integrity with the workstation's system tables.

Use Server Map data sources to establish unique object mappings for logic servers. When batch jobs and business functions running on the server request data, they look to the Object Configuration Master and the Data Source Master tables in the server map data source; this is necessary because the mappings are different.

For example, suppose a user logs on to an environment that maps static local data on the workstation, dynamic transaction data to the server, and the master business functions and batch processes to the server. The user enters a sales order and clicks OK to enter the order, which runs the Sales Order Entry master business function on the server. It does not make sense for the master business function to go back to the workstation to retrieve user defined codes and tax information; therefore, the server map Object Configuration Manager table maps all data to the appropriate server data source.

These tables in the Server Map database are unique to a server's perspective of processing:

  • Object Configuration Master (F986101): Provides logic objects processing on a server request data and perhaps other logic objects. When these requests are made to EnterpriseOne running on a server, Object Configuration Master must be accessed to find the correct mappings for the data and logic objects. Servers might have different mapping requirements than workstations.

    For example, you should map all user defined codes locally to the workstation for performance during interactive processing. Server processing would require you to map these files locally to a server database to enhance server processing performance.

  • Job Control Status Master (F986110): Records information about batch jobs launched on a server.

  • Job Number Master File (F986111): Records next numbers for batch jobs launched on a server.

Central Objects

This data source points to the source objects (central objects specifications), as well as the User Overrides table (F98950). Central Objects data sources are databases.

If you have multiple path codes, each must have a separate Central Objects data source. Developers check objects out of a Central Objects data source for modification. When the developer checks in the objects, the system copies the objects from the developer's workstation to the relational database tables in the Central Objects data source. You must set up one Central Objects data source for every path code needed in the configuration, for example, Central Objects - PD910 or Central Objects - DV910.

You must have a Central Objects data source for:

  • Pristine objects

  • Production objects

  • Development objects

You connect each Central Objects data source to a path code used by the environments that you created for the configuration.

Control Table

This data source consists of user defined codes, menus, and next numbers.

Versions

This data source corresponds to the path code, as in Versions - PD910. It stores versions and processing option information. It includes these tables:

  • Versions List (F983051)

  • Processing Option Text (F98306)

Alternate Data Source (Release 9.2.1.2)

EnterpriseOne Search execution can be performed on an alternate data source. An alternate data source is a source other than the primary data source that is used for EnterpriseOne operations. If you have a data source with a similar data schema, you can define the search execution to access it instead.

The alternate data source must contain the same data structure, including column names and data types, as the primary data source. On the search result window, the system displays the data retrieved directly from alternate data sources.

See Defining an Alternate Data Source for EnterpriseOne Search (Release 9.2.1.2) for more information.

4.3 Database Structures for EnterpriseOne

All supported database platforms have a similar configuration of tables and data sources.

This diagram illustrates owners and databases for four different platforms:

Figure 4-1 Example of owners and databases structure

Description of Figure 4-1 follows
Description of ''Figure 4-1 Example of owners and databases structure''

4.3.1 Oracle

The basic architecture of an Oracle database includes many different logical and physical storage structures.

Typically, an Oracle database is divided into one or more logical storage structures. The highest-level structures are table spaces and user schema. These structures provide two categories that data may be logically grouped. Data belonging to one table space may belong to different schema, and data for one schema may belong to different table spaces.

Table Spaces

The physical database storage units, data files, are associated with table spaces according to the logical structure of the database. For example, table spaces may be created to separate different categories of data. Table spaces are divided into smaller logical divisions called segments, which are divided further into extents and data blocks. These levels of data storage allow control over how the data files are allocated for physical storage.

User Schema

A schema is a set of objects associated with a user. Schema objects include tables and other data structures used by the database. These objects do not directly correspond to data files stored on the server. Each object's data is stored in one or more data files within a table space. You can specify the space allocated for tables and a few other objects.

Tables

A schema is a set of objects associated with a user. Schema objects include tables and other data structures used by the database. These objects do not directly correspond to data files stored on the server. Each object's data is stored in one or more data files within a table space. You can specify the space allocated for tables and a few other objects.

This diagram illustrates the Oracle structure with EnterpriseOne:

Figure 4-2 Oracle Structure and EnterpriseOne

Description of Figure 4-2 follows
Description of ''Figure 4-2 Oracle Structure and EnterpriseOne''

4.3.2 SQL Server

SQL Server provides a comprehensive platform that makes it easy to design, build, manage, and use data warehousing solutions which enable your organization to make effective business decisions based on timely and accurate information. SQL Server delivers nine separate databases with EnterpriseOne during an installation.

This diagram illustrates the SQL structure with EnterpriseOne:

Figure 4-3 SQL structure with EnterpriseOne

Description of Figure 4-3 follows
Description of ''Figure 4-3 SQL structure with EnterpriseOne''

4.3.3 DB2 for i Server

DB2 for i is the relational database manager that is fully integrated and provides numerous functions and features such as triggers, stored procedures, and dynamic bitmapped indexing that serve a wide variety of application types. These applications range from traditional host-based applications to client/server solutions to business intelligence applications.

In the IBM i system, each file (also called a file object) has a description that describes the file characteristics and how the data associated with the file is organized into records and the fields in the records. The operating system uses this description whenever a file is processed.

DB2 for i installations store all tables in their respective data sources in a single database.

This diagram illustrates the DB2 for i structure with EnterpriseOne:

Figure 4-4 DB2 for i structure with EnterpriseOne

Description of Figure 4-4 follows
Description of ''Figure 4-4 DB2 for i structure with EnterpriseOne''

4.3.4 DB2 for Linux, UNIX, and Windows

Every data element in a database is stored in a column of a table, and each column is defined to have a data type. The data type places limits on the types of values you can put into the column and the operations you can perform on them. DB2 for i includes a set of built-in data types with defined characteristics and behaviors: character strings, numerics, datetime values, large objects, nulls, graphic strings, binary strings, and datalinks.

When organizing the data into tables, it is beneficial to group tables and other related objects together. This is done by defining a schema. Information about the schema is kept in the system catalog tables of the database to which you are connected. As other objects are created, they can be placed within this schema.

Each schema has a set of four dedicated tablespaces in which the data is physically stored. IBM recommends that each tablespace be stored on a separate disk drive.

This diagram illustrates the DB2 for Linux, UNIX, and Windows 8.1.4 structure with EnterpriseOne:

Figure 4-5 Schemas and tablespaces for DB2 for Linux, UNIX, and Windows

Description of Figure 4-5 follows
Description of ''Figure 4-5 Schemas and tablespaces for DB2 for Linux, UNIX, and Windows''

Figure 4-6 Schemas and tablespaces for DB2 for Linux, UNIX, and Windows

Description of Figure 4-6 follows
Description of ''Figure 4-6 Schemas and tablespaces for DB2 for Linux, UNIX, and Windows''

4.4 System Data Source Connections

When EnterpriseOne starts on a workstation, the software attempts to connect to the base data source found in the workstation jde.ini file. If this data source is unavailable, the software attempts to connect to a secondary data source for system information. It is important to have processes for ensuring that the alternate system data source location contains current information. You can maintain an alternate data source's information using table conversion or data replication.

The jde.ini file should look like the example for the primary system data source connection:

[DB SYSTEM SETTINGS]

.

.

Default Env=DEMO910A

Default PathCode=DEMO

Base Datasource=System 910

Database=System 910

.

.

.

Secondary System Data Source connection

[DB SYSTEM SETTINGS - SECONDARY]

Base Datasource=Access32

Object Owner=

Server=

Database=Access32

During installation, the Release Master application relates the system data source to a release. Configuring the release updates the setup.inf file used during the workstation install to create the jde.ini file.

See Also:

  • Major Technical Tables in the JD EdProduct Title/BookTitle as a Variablewards EnterpriseOne Applications Installation Guide.

4.5 System Table Caching

When a user first logs on, the software uses the user ID and environment to retrieve information from the system tables for that user and environment. This information is cached in memory on the workstation. Any time a change is made to the central system tables, dynamic caching of the system information occurs for those workstations with an active EnterpriseOne session.

4.6 Understanding Data Source Set Up

The data sources are the building blocks of your configuration, therefore, the proper identification of all required data sources is critical to having a correct configuration to support your business needs.

The database data sources and logical data sources applications enable you add or modify a database data source or logic data source, respectively. After you add a new data source, you must update the Release/Data Source Map table (F00948) using the Release/Data Source Map application.

4.6.1 Understanding Planning for Data Sources

It is important for you to plan for data sources. The proper identification of all required data sources is critical to having a correct configuration that supports the needs of the business. Be sure to include all machines and all databases in your enterprise.

To plan your data sources:

  1. Evaluate the location of the system data.

  2. Identify all of the enterprise servers in the configuration that will host logic:

    1. Set up one distributed processing data source for each enterprise logic server.

    2. Set up one Server Map data source for each distributed processing data source.

  3. Evaluate how many groups of EnterpriseOne objects you require to support the business environment, such as production, pristine, and development. Set up one Central Objects data source for each group of objects.

  4. Evaluate the various locations of the business data:

    1. Set up one Business Data data source for each database and library that contains Business Data tables that EnterpriseOne applications use.

    2. Set up one Control Table data source for production and one for testing.

4.6.2 Understanding Setting Up Data Source Definitions

These data source types require just one data source definition for each release:

  • Object Librarian

  • System

  • Data Dictionary

  • Local

These data source types might require you to define multiple data sources for each type to support the business requirements:

  • Business Data (production, test, CRP, and PS910 demo data)

  • Distributed Processing (one per logic server)

  • Server Map (one per logic server)

  • Central Objects (one per path code)

  • Control Tables

4.6.3 Understanding Data Source Naming Conventions

When you add data sources, observe these naming conventions:

  • Limit to 30 characters

  • Text is case sensitive

  • Text is space sensitive

Specific exceptions for the Client Access data source are listed in the Client Access Data Source Name section.

4.6.4 Understanding Client Access Data Source Names

The names of Client Access data sources must conform to these standards:

  • Limit to 32 characters

  • Begin with an alphabetic character

  • Do not use these characters: { } [ ] ( ) ? * = ! @ ;

    Note:

    You must type the data source name before you can use the Client Access ODBC driver to access IBM i data.

4.6.5 Understanding Table Owner (Object Owner ID)

Oracle and SQL Server database management systems have unique table owner IDs for each group of tables. For example, the database that contains the system tables might have an owner such as E910SYS. You must identify the table owner ID for Oracle and SQL Server database management systems.

4.7 Adding or Modifying a Database or Logical Data Source

This section lists the prerequisites and discusses how to modify an existing database data source.

4.7.1 Prerequisites

Before you complete the tasks in this section, you should plan for the data sources.

4.7.2 Forms Used to Add or Modify a Database or Logical Data Source

Form Name FormID Navigation Usage
Machine Search & Select W986115E In Solution Explorer, navigate to System Administration Tools, System Administration Tools, Data Source Management, Database Data Sources. Used to display and select a data source.
Work With Data Sources W986115A In the Machine Search & Select form, highlight the machine name and click Select. Used to add a data source or select a data source to modify.
Data Source Revisions W986115O To modify a database data source: In the Work With Data Sources form, click Find, and then highlight the row you want and click Select.

To add a database data source: In the Work With Data Sources form, click Add.

Used to add or modify a data source.

4.7.3 Adding or Modifying a Database Data Source

Access the Data Source Revisions form.

Figure 4-7 Data Source Revisions form

Description of Figure 4-7 follows
Description of ''Figure 4-7 Data Source Revisions form''

4.7.3.1 Data Source Revisions Form Fields

Use these processing options to set up the form fields for your data source.

Data Source Name

Specify the name that identifies the data source.

Data Source Use

Indicate how the data source is to be configured, Servers (SVR) to run UBEs and Business Functions or a Database to access table data.

Data Source Type

Specify the type of database.

Data Class

Future Use.

Platform

Specify the type of physical hardware the database resides on.

Database Server Name

Specify the name of the computer that receives documents form clients.

4.7.3.2 Oracle

Use these processing options to set up parameters for an Oracle database.

Object Owner ID

Specify the database table prefix or owner.

Database Name

Specify the name assigned to the database during installation, such as HPDEVORAP or HP9000.

Depending on the data source type, this field is used differently. If the data source type is Oracle, then this field contains the Oracle connect string. If the data source type is Microsoft Access, SQL*Server or Client Access, then this field contains the Windows ODBC data source name. In order to minimize the number of connections to SQL*Server, it is recommended that the ODBC Data Source name is the machine name where the SQL*Server Database resides and that the Catalog name is set for the individual database name. For example, if you have two databases, DatabaseA and DatabaseB, on a machine called INTELNT, this field would contain INTELNT and the Catalog name would be set to DatabaseA for one data source and DatabaseB for the other data source.

4.7.3.3 SQL ODBC

Use these processing options to set up parameters for a SQL ODBC database.

Object Owner ID

Specify the database table prefix or owner.

Database Name

Specify the name assigned to the database during installation, such as HPDEVORAP or HP9000.

Depending on the data source type, this field is used differently. If the data source type is Oracle, then this field contains the Oracle connect string. If the data source type is Microsoft Access, SQL*Server or Client Access, then this field contains the Windows ODBC data source name. In order to minimize the number of connections to SQL*Server, it is recommended that the ODBC Data Source name is the machine name where the SQL*Server Database resides and that the Catalog name is set for the individual database name. For example, if you have two databases, DatabaseA and DatabaseB, on a machine called INTELNT, this field would contain INTELNT and the Catalog name would be set to DatabaseA for one data source and DatabaseB for the other data source.

ODBC Data Source Name

Specify the name assigned to the database during installation, such as HPDEVORAP or HP9000.

4.7.3.4 SQL OLEDB

Use these processing options to set up parameters for a SQLOLEDB database.

Object Owner ID

Specify the database table prefix or owner.

Database Name

Specify the name assigned to the database during installation, such as HPDEVORAP or HP9000.

Depending on the data source type, this field is used differently. If the data source type is Oracle, then this field contains the Oracle connect string. If the data source type is Microsoft Access, SQL*Server or Client Access, then this field contains the Windows ODBC data source name. In order to minimize the number of connections to SQL*Server, it is recommended that the ODBC Data Source name is the machine name where the SQL*Server Database resides and that the Catalog name is set for the individual database name. For example, if you have two databases, DatabaseA and DatabaseB, on a machine called INTELNT, this field would contain INTELNT and the Catalog name would be set to DatabaseA for one data source and DatabaseB for the other data source.

Database Instance

Specify the name of the server instance. This name is required for SQL Server ODBC and SQL Server OLEDB data sources.

4.7.3.5 DB2 for i

Use these options to set up parameters for a DB2 for i database.

Library name

Specify the name of the SQL Server database name. This name is required for SQL Server ODBC and SQL Server OLEDB data sources.

ODBC Data Source Name

Specify the name assigned to the database during installation, such as HPDEVORAP or HP9000.

4.7.3.6 DB2 for Linux, UNIX, and Windows

Use these options to set up parameters for a DB2 for Linux, UNIX, and Windows database.

Schema

Specify the database table prefix or owner.

Database Alias Name

Specify the name of the SQL Server database. This name is required for SQL Server ODBC and SQL Server OLEDB data sources.

ODBC Data Source Name

Specify the name assigned to the database during installation, such as HPDEVORAP or HP9000.

4.7.3.7 Local Oracle

Use these processing options to set up parameters for a Local Oracle database.

Tablespace

Specify the Tablespace.

4.7.3.8 Access

Use these options to set up parameters for an Access database.

ODBC Data Source Name

Specify the name assigned to the database during installation.

4.7.3.9 Logical

Server Map Data Source Name

Specify the name assigned to the database during installation, such as HPDEVORAP or HP9000.

4.7.4 Setting Processing Options for Database or Logical Data Sources

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

4.7.4.1 Defaults

Use these options to specify a local (database) data source or a server data source and to indicate whether you want to create an ODBC data source when the Workstation Installation program (P986115) runs.

1. Data Source Type

Indicate how the data source is to be configured: Servers (SVR) to run UBEs and Business Functions or a Database (DB) to access table data.

2. ODBC Data Sources

Specify whether to create an ODBC data source during the workstation installation process. Values are:

Blank: Do not create ODBC data sources.

1 Create Client Access, SQL Server and DB2 for i data sources.

4.8 Defining an Alternate Data Source for EnterpriseOne Search (Release 9.2.1.2)

EnterpriseOne Search can override the primary data source and leverage an alternate data source for search execution. The Alternate Data Sources application (P98611X) enables you to define a data source that is an alternate to a primary data source.

You can designate an alternate data source for a database data source (DB) and not for a server data source (SVR). Each primary data source can only have one alternate data source; however, an alternate data source can have multiple primary data sources pointing to it.

Note:

You are responsible for the processing to keep the alternate data source in synchronization with the actual data and determine the frequency of synchronization so that the results are accurate.

To define an alternate data source:

  1. In JD Edwards EnterpriseOne, navigate to EnterpriseOne Menus, EnterpriseOne Life Cycle Tools, System Administration Tools, System Administration Tools, Data Source Management, Database Data Sources.

  2. In the Machine Search & Select form (W986115E), highlight the machine name and click Select.

  3. In the Work With Data Sources form (W986115A), click Find.

  4. Select the row for which you want to define an alternate data source.

  5. Select Alternate Sources from the Form menu.Alternatively, you can select Alternate Source from the Row exit.

  6. In the Alternate Data Sources form (P98611X), specify the name of the Primary Data Source, and then specify the name that identifies the Alternate Data Source. You can also use the Visual Assist to search and select the database data sources.

    When you use the Row exit to open the Alternate Data Sources form, the Primary Data Source field displays the data source name and is disabled.

  7. Click OK to save and define the alternate data source.

    The Search Data Sources table (F98611X) stores the data source and alternate data source information.

    Note:

    If there is an invalid mapping of data sources, the system displays an error message during search execution.

4.9 Modifying the Release/Data Source Map Table

This sections provides an overview of the Release/Data Source Map table and discusses how to modify the Release/Data Source Map table.

4.9.1 Understanding the Release/Data Source Map Table

The Release/Data Source Map program (P00948) enables you to define the release level for a data source for a data source type. When you add a new data source, you need to update the Release/Data Source Map table (F00948). This table contains entries for the data dictionary, Object Librarian, versions lists, and workflow, and organizes the entries according to release.

When you copy or transfer objects between data sources, the software checks the release of each data source and then determines whether the source data source and the target data source reside in compatible releases. If Unicode conversion is needed (for example, transfer from an Xe version to a EnterpriseOne 8.10 version), the software converts the data for you when you are using a release of EnterpriseOne 8.10 or greater.

The software does not allow you to move or copy objects between data sources with incompatible releases. When you add a data source, if a record is already found in the Release/Data Source Map table for the data structure and data type entered, the system displays an error. You can only have one release level defined for a data source per data type.

4.9.2 Form Used to Modify the Release/Data Source Map Table

Form Name FormID Navigation Usage
Work With Release/Data Source Map W00948A In Solution Explorer, navigate to System Administration Tools, System Administration Tools, Environment Management, Release/Data Source Map (P00948) Used to add database sizing information.
Release/Data Source Map Revisions W00948B In the Work With Release/Data Source Map form, click Add. Used to add database sizing information.

4.9.3 Adding or Modifying the Release/Data Source Map Table

Access the Database Object Sizing form.

Figure 4-8 Release/Data Source Map Revisions form

Description of Figure 4-8 follows
Description of ''Figure 4-8 Release/Data Source Map Revisions form''

Data Source Type

Specify this is the type of object contained in the indicated data source.

Data Source

Specify the name that identifies the data source.

Release

Specify the release number identified in the Release Master.

UserID

Identify the user profile.

WorkstationID

Identify the workstation ID that executed a particular job.

ProgramID

Identify the batch or interactive program (batch or interactive object). For example, the number of the Sales Order Entry interactive program is P4210 and the number of the Print Invoices batch process report is R42565.

The program ID is a variable length value. It is assigned according to structured syntax in the form TSXXX, where:

T = The first character of the number is alphabetic and identifies the type, such as P for Program, R for report, and so on. For example, the value P in the number P4210 indicated that the object is a program.

SS = The second and third characters of the number is numeric and identify the system code. For example, the value 42 in the number P4210 indicates that this program belongs to system 42, which is the Sales Order Processing system.

XXX = The remaining characters of the number are numeric and identify a unique program or report. For example, the value 10 in the number P4210 indicates that this is the Sales Order Entry Program.

Date Updated

The date that specifies the last update to the file record.

Time Updated

The time the object was last checked in.

Important:

If you want to view the data sources without adding or changing one, ensure that you exit from the Data Source Revisions form and click Cancel instead of OK. When you click OK, the system assumes that you have added or changed a data source, and the existing ODBC drivers might not work correctly. You will have to modify them using the ODBC Data Source Administrator applet accessible from the Control Panel.

4.9.4 Setting Advanced Options for Release/Data Source Map Revisions

The Advanced form displays options that are related to the data source type being configured.

4.9.4.1 Advanced

Use these form exit options to set up additional options.

Unicode

Indicate whether a database supports Unicode. This option is required for all data sources.

Use Decimal Shift

Check this option to automatically shift decimals when retrieving or updating data based on specifications in the data dictionary. This field is for EnterpriseOne tables only. Non-EnterpriseOne tables should be in a separate data source with decimal shift turned off. If you bring in a EnterpriseOne table as non-EnterpriseOne table, the system does not recognize the fields in this table that have been decimal shifted. This is not checked in Table Conversion.

Use this flag to SELECT or CLEAR 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.

Use Julian Dates

Check this option to store dates in a Julian format. Otherwise, dates are stored as defined in the Microsoft Windows Control Panel. The system automatically turns this flag off for non-EnterpriseOne tables.

Support For Updates

Use this flag to SELECT or CLEAR 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.

OCM Data Source

Specify whether the data source will contain an OCM table (F986101). If you enable this flag, the system displays a 1 in the OCM Data Source field on the Work With Data Sources form. You should only set this flag for the system data source and any server map data sources. That is, you should not enable this setting for any database data source or log data sources that are not system or server map data sources.

Use Table Owner

Activate use of the Owner ID field.

LOB Data Type Support

Indicate whether a database supports a LOB data type. This option is required for all IBM i and Oracle data sources.

Note:

If you select I - DB2 for Linux, UNIX, and Windows on IBM i as the data source type, you can select either LOB Data Type Support or IBM i BLOB Support, but not both.
IBM i BLOB Support

The setting for the IBM i Binary Object (BLOB) Data source indicates whether a data source may contain EnterpriseOne BLOB Tables.

4.10 Understanding Data Source Reports

The Data Source Master batch processes enable you to create a report for a data source or a comparison report for two data sources.

The Data Source Master batch processes are called from a report driver (R98611B), although other EnterpriseOne reports do not require a report driver. You use the R98611B report driver to set processing options for each report. Any data selection for a report must be entered for the specific report, not from the driver. When you finish entering processing options and data selection, you run the report from the driver.

4.11 Running the Data Source Master and Data Source Master Compare Reports

This section lists the prerequisites and discusses how to set up and run the Data Source Master and Data Source Master Compare reports.

4.11.1 Prerequisites

Before you run the reports in this section, you should complete these tasks:

  • Use the report driver to enter processing options for the reports.

  • Set up data selection for the reports before running the reports.

4.11.2 Forms Used to Run Data Source Master and Data Source Master Compare Reports

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 Reporting, Data Source Master Report or Data Source Master Comparison (P98305)

In the Work With Batch Versions - Available Versions form, enter R98611 (Data Source Master Report) or R986112 (Data Source Master Comparison) in Batch Application.

Used to run the Data Source Master Report or Data Source Master Comparison report.

4.11.3 Running the Data Source Master or Data Source Master Compare Report

The Data Source Master and Data Source Master Compare reports enable you to create a report for a data source.

Access the Work With Batch Versions - Available Versions form.

Figure 4-9 Work With Batch Versions - Available Versions form

Description of Figure 4-9 follows
Description of ''Figure 4-9 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).

4.11.4 Setting Processing Options for Data Source Master and Data Source Master Compare Report

Processing options are used to select the report and version you wish to run.

4.11.4.1 UBE Driver

Use this processing option to enter the report and version that you wish to run. Then complete the processing options on the corresponding tab.

1. Data Source Master Report Name

Specify the name of the report you want to run.

Values are:

R98611 - Data Source Master Report

R986112 - Data Source Master Compare

The processing options for the report you are running must be completed. The XJDE0001 version of the actual report is the one that will run. therefore, if Data Selection is necessary, it must be done on the XJDE0001 version of the report.

4.11.4.2 R986112

Use these processing options to specify the parameters for the R986112 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 Only

Specify the type of processing for an event.

Values are:

1 Print exceptions only

Blank: Print all records

4.11.4.3 R98611

Use this processing option to specify the data source to use for the R98611 report.

1. Data Source Name

Use this processing option to specify the Data Source that you want to use to produce the report.

4.11.5 Setting Data Selection for the Data Source Master or Data Source Master Compare Report

Access the Data Source Selection form.

Figure 4-10 Data Selection form

Description of Figure 4-10 follows
Description of ''Figure 4-10 Data Selection form''

Enter a 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.

4.12 Running the Verify Object Configuration Mappings Report

This section provides an overview of the Verify Object Configuration Mappings report, lists the prerequisites, and discusses how to set up and run the Verify Object Configuration Mappings report.

4.12.1 Understanding the Verify Object Configuration Mappings Report

The Verify OCM report (R9861130) is a useful troubleshooting tool that can help you verify that:

  • All Data Source Master definitions have OCM mappings

  • Object Configuration Mappings are consistent for a given user, are not duplicated, and have data source definitions,

  • Appropriate specification files exist on a specific server

  • Business function DLLs exist on a specific server

Run this report to verify the previous items for a workstation or a server. The machine on which you run this report determines which set of Object Configuration Manager and Data Source Master tables will be verified. Consequently, you should run this report on the local machine and on each server that runs EnterpriseOne. You can also run this report on the deployment server.

4.12.2 Prerequisite

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

4.12.3 Forms Used for the Verify Object Configuration Mappings Report

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 Reporting, Verify OCM.(P98305). Used to run the Verify Object Configuration Mappings report.

4.12.4 Running the Verify Object Configuration Mappings Report

Access the Work with Batch Versions - Available Versions form.

Figure 4-11 Work with Batch Versions - Available Versions form

Description of Figure 4-11 follows
Description of ''Figure 4-11 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).

4.12.5 Setting Processing Options for the Verify Object Configuration Mappings Report

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

4.12.5.1 Data Source

Use these processing options to specify whether to perform data source validation for data source master definitions, and to specify an environment.

1. Data Source Mappings

Specify whether to perform data source validation for data source master definitions. Values are:

Blank: Do not verify data source definitions.

1 Verify that each data source has at least one OCM mapping defined.

2. Environment Validation

Specify the environments for which you want to run the validations. Values are:

*All Run the validations for all environments.

Specific environment name: Validate only that environment.

4.12.5.2 Parent DLL

Use this processing option to specify whether each business function has a parent DLL assigned.

1. Business Function Parent DLL

Specify whether each business function has a parent DLL assigned. Values are:

Blank: No verification is done.

1 Verify that each business function has a parent DLL assigned. Also, verify that the DLL name is valid.

4.12.5.3 Specifications

Use this processing option to verify that all required specifications exist for the pathcode.

1. Validate Server Specifications

Verify that all specifications required to run EnterpriseOne exist for the pathcode. This processing option applies only when running against a server. Values are:

Blank: Do not verify specifications

1 Verify whether the required specifications exist

4.12.5.4 OCM

Use these processing options to specify OCM parameters.

1. User ID to Validate

Specify the user ID for which the OCM validations should be run. Values are:

Blank: Run the validations for all users.

*ALL Run the validations for all users.

*PUBLIC Run the validations for only *PUBLIC.

A specific User ID. (Performs validations for only that user.)

2. OCM Mappings

Indicate whether to validate OCM mappings. Values are:

Blank: Do not validate OCM mappings.

1 Validate all active OCM mappings.

2 Validate both the active and inactive OCM mappings.

3. Duplicate OCM Mappings

Specify whether OCM records should be checked for duplicates. Values are:

Blank: Do not check for duplicates.

1 Verify that the active OCM mapping records have no duplicates.

4.12.6 Setting Data Selection for the Verify Object Configuration Mappings Report

Access the Data Selection form.

Figure 4-12 Data Selection form

Description of Figure 4-12 follows
Description of ''Figure 4-12 Data Selection form''

Enter a 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.