3 JD Edwards EnterpriseOne

This chapter describes how to work with JD Edwards EnterpriseOne Knowledge Modules in Oracle Data Integrator.

This chapter includes the following sections:

Section 3.1, "Introduction"
Section 3.2, "Installation and Configuration"
Section 3.3, "Setting Up the Topology"
Section 3.4, "Setting up an Integration Project"
Section 3.5, "Creating and Reverse-Engineering a Model"
Section 3.6, "Designing an Interface"

3.1 Introduction

JD Edwards (JDE) EnterpriseOne is an integrated applications suite of comprehensive ERP software that combines business value, standards-based technology, and deep industry experience into a business solution with a low total cost of ownership.

3.1.1 Concepts

The JDE Knowledge Modules for Oracle Data Integrator use mature database-level integration methods for JDE EnterpriseOne, in order to:

Reverse-Engineer JDE EnterpriseOne data structures
Read data from JDE EnterpriseOne (Direct Database Integration)
Write data through the Z-tables to an JDE Application (Interface Table Integration)

3.1.2 Knowledge Modules

Oracle Data Integrator provides the Knowledge Modules listed in Table 3-1 for handling JDE EnterpriseOne data. These specific JDE KMs provide connectivity and integration of the JDE EnterpriseOne platform with any database application through Oracle Data Integrator.

Table 3-1 JDE Knowledge Modules

Knowledge Module	Description
RKM JDE Enterprise One Oracle	Reverse-engineers the metadata of the applications' objects such as tables and interface tables from JDE EnterpriseOne installed on an Oracle database.
RKM JDE Enterprise One SQL Server	Reverse-engineers the metadata of the applications' objects such as tables and interface tables from JDE EnterpriseOne installed on SQL Server.
IKM JDE Enterprise One Control Append (UBE)	Integrates data from any source to JDE EnterpriseOne. Integrates data in EnterpriseOne Z-table in control append mode. Data can be controlled: invalid data is isolated in the Error Table and can be recycled The KM performs integration into JDE enterprise One with a RunUBE batch command

Knowledge Module

Description

RKM JDE Enterprise One Oracle

Reverse-engineers the metadata of the applications' objects such as tables and interface tables from JDE EnterpriseOne installed on an Oracle database.

RKM JDE Enterprise One SQL Server

Reverse-engineers the metadata of the applications' objects such as tables and interface tables from JDE EnterpriseOne installed on SQL Server.

IKM JDE Enterprise One Control Append (UBE)

Integrates data from any source to JDE EnterpriseOne. Integrates data in EnterpriseOne Z-table in control append mode.

Data can be controlled: invalid data is isolated in the Error Table and can be recycled
The KM performs integration into JDE enterprise One with a RunUBE batch command

3.2 Installation and Configuration

Make sure you have read the information in this section before you start working with the JDE EnterpriseOne data:

System Requirements and Certifications
Technology Specific Requirements
Connectivity Requirements

3.2.1 System Requirements and Certifications

Before performing any installation you should read the system requirements and certification documentation to ensure that your environment meets the minimum installation requirements for the products you are installing.

The list of supported platforms and versions is available on Oracle Technical Network (OTN):

http://www.oracle.com/technology/products/oracle-data-integrator/index.html.

3.2.2 Technology Specific Requirements

In order to use the IKM JDE Enterprise One Control Append (UBE), the Oracle Data Integrator run-time agent must be installed on the JDE Server where the RunUBE utility is installed.

3.2.3 Connectivity Requirements

Oracle Data Integrator connects to the database hosting the JDE data using JDBC connectivity. For detailed information on JDBC connectivity with Oracle and Microsoft SQL Server databases, see the "Oracle Database Connectivity Requirements" and "Microsoft SQL Server Connectivity Requirements" in the Oracle Fusion Middleware Connectivity and Knowledge Modules Guide for Oracle Data Integrator.

3.3 Setting Up the Topology

This step consists in declaring in Oracle Data Integrator the data server, as well as the physical and logical schemas that will be used to store the JDE data.

3.3.1 Create a Data Server

The JDE tables can be stored in an Oracle schema or a Microsoft SQL Server database.

Create a data server either for the Oracle technology or for the Microsoft SQL Server technology. See "Creating an Oracle Data Server" or "Creating a Microsoft SQL Server Data Server" in the Oracle Fusion Middleware Connectivity and Knowledge Modules Guide for Oracle Data Integrator.

This data server must point to the Oracle database instance or the Microsoft SQL Server that stores the JDE data.

3.3.2 Create a Physical Schema

Create a physical schema under the data server that you have created in Section 3.3.1, "Create a Data Server". Use the standard procedure, as described in "Creating a Physical Schema" of the Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator.

This schema must point to the Oracle schema or Microsoft SQL Server database that contains the JDE tables that you want to reverse-engineer.

Note:

The Oracle schema or the Microsoft SQL Server database storing the JDE tables should never be defined as a work schema in the physical schema definition. Moreover, this schema or database must not be used as staging area of an interface.

Create for this physical schema a logical schema using the standard procedure, as described in "Creating a Logical Schema" of the Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator and associate it in a given context.

3.4 Setting up an Integration Project

Setting up a project using JDE features follows the standard procedure. See "Creating an Integration Project" of the Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator.

Import the following KMs into your Oracle Data Integrator project:

IKM JDE Enterprise One Control Append (UBE)
RKM JDE Enterprise One Oracle or RKM JDE Enterprise One SQL Server

In addition to these specific JDE KMs, import the standard LKMs for the Oracle or Microsoft SQL Server technologies. See Oracle Database "Knowledge Modules" and Microsoft SQL Server "Knowledge Modules" in the Oracle Fusion Middleware Connectivity and Knowledge Modules Guide for Oracle Data Integratorfor a list of available KMs.

3.5 Creating and Reverse-Engineering a Model

This section contains the following topics:

Create a Model
Reverse-Engineer JDE Tables

3.5.1 Create a Model

Create a Model based on the Oracle or Microsoft SQL Server technology and on the logical schema created when configuring the JDE Connection using the standard procedure, as described in "Creating a Model" of the Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator.

3.5.2 Reverse-Engineer JDE Tables

The JDE RKMs are able to reverse-engineer JDE tables. These RKMs retrieve metadata from JDE objects such as tables and interface tables.

To perform a Customized Reverse-Engineering of JDE tables with the JDE RKMs, use the usual procedure, as described in "Reverse-engineering a Model" of the Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator. This section details only the fields specific to JDE tables:

In the Reverse tab of the Model, select the RKM JDE Enterprise One <database>. In this chapter, <database> refers to the technology containing the JDE data.

Set the RKM options as follows:

JDE_CENTRAL_OBJECTS: Specify the Oracle Schema or Microsoft SQL Server Database storing the JDE Central objects
JDE_DATA_DICTIONARY: Specify the Oracle Schema or Microsoft SQL Server Database storing the JDE data dictionary
JDE_OBJECT_LIBRARIAN: Specify the Oracle Schema or Microsoft SQL Server Database storing the JDE Object librarian

JDE_CONTROL_TABLES: Specify the Control Tables schema

Note:

To find the schema required in the options JDE_CENTRAL_OBJECTS, JDE_DATA_DICTIONARY, JDE_OBJECT_LIBRARIAN, and JDE_CONTROL_TABLES you can either ask your application manager or query the table F98611(Data Source Master).

JDE_DATA_TABLES: Set this option to YES to reverse-engineer data tables
JDE_Z_TABLES: Set this option to YES to reverse-engineer interface tables (Z-tables)
JDE_MODULES: Indicate the JDE System Short Name, for example 00 for Foundation Environment, 01 for Address Book, and 02 for Electronic Mail

Note:
You can also specify a list of modules. In the list, the modules must be separated by commas and enclosed within single-quote characters, for example:
'01','02','04'
JDE_LANGUAGE: Indicate the language used for retrieving object descriptions and comments, for example E for English, F for French, and S for Spanish

Specify the reverse mask in the Mask field in order to select the tables to reverse. The Mask field, in the Reverse tab, filters reverse-engineered objects based on their name. The Mask field must not be empty and must contain at least the percentage symbol (%).

The reverse-engineering process returns the datastores grouped per module. You can use these datastores as a source or a target of your integration interfaces.

3.6 Designing an Interface

You can use JDE data tables as a source of an integration interface. JDE Z-tables can be used as the target of an integration interface.

The KM choice for an interface determines the abilities and performance of this interface. The recommendations in this section help in the selection of the KM for different situations concerning loading and integrating JDE data.

3.6.1 Loading Data from JDE

After performing a reverse-engineering using the RKM JDE Enterprise One <database>, you can use JDE data tables as a source of an integration interface to extract data from the JDE application and integrate them into another system (Data warehouse, other database and so forth).

Using JDE as a source in these conditions is the same as using an Oracle or Microsoft SQL Server datastore as a source in an integration interface. The generic SQL, Oracle Database, or Microsoft SQL Server KMs can be used for this purpose. See the following chapters in the Oracle Fusion Middleware Connectivity and Knowledge Modules Guide for Oracle Data Integratorfor more information:

"Oracle Database"
"Generic SQL"
"Microsoft SQL Server"

3.6.2 Integrating Data in JDE

After performing a reverse-engineering using the RKM JDE Enterprise One <database>, you can use JDE Z-tables as a target of an interface to load data from any system to the JDE application with the IKM JDE Enterprise One Control Append (UBE).

The integration of data into JDE Enterprise One is performed in two phases:

During the first phase data is integrated into a set of Z-tables using several interfaces, without calling the RunUBE command. These interfaces can use the IKM JDE Enterprise One Control Append (UBE) with the JDE_RUNUBE option set to No.
During the second phase the RunUBE command is launched to integrate the data from these Z-tables into JDE Enterprise One. This is typically done in the interface loading the last required Z-table. This interface also uses the IKM JDE Enterprise One Control Append (UBE) with the JDE_RUNUBE option set to Yes.

These interfaces should be sequenced in a package.

Oracle Data Integrator can automatically call the RunUBE command to write to JDE. The RunUBE call should be activated in the IKM only after loading all the required Z-table for populating JDE. The capability to load the Z-Tables, as well as the call of the RunUBE command is provided by the IKM JDE Enterprise One Control Append (UBE).

To create an interface targeting JDE:

Create an integration interface with Z-tables as target datastores.
Create joins, filters, and mappings as usual.
In the Flow tab select the IKM JDE Enterprise One Control Append (UBE).
Set the standard KM options (INSERT, COMMIT, FLOW_CONTROL).

If this interface launches the RunUBE command, specify the KM options as follows:

Set the JDE_RUNUBE option to Yes.
Specify the JDE_DIRECTORY in which the RunUBE command is executed.

If you want to create a password file, set the password related options as shown in Table 3-2.

Table 3-2 Password Related KM Options

Option	Value	Notes
JDE_CREATE_PWD_FILE	Yes	To enhance RunUBE security in a Unix or iSeries environment, when the RunUBE command is submitted, the system reads the text file specified in the JDE_PWD_FILE option and uses the JD Edwards EnterpriseOne user ID and password as indicated in the text file.
JDE_PWD_FILE	Absolute path of the password security file	This file contains the user id and password specified in the JDE_USER_ID and JDE_PWD options.
JDE_DELETE_PWD_FILE	`E\|D`	Enter `D` to delete the password file. Enter `F` to keep the password file. Note that even if the password file is removed after the execution of the command, the file should be kept in a secure location on the server file system
JDE_USER_ID	JDE EnterpriseOne user ID	The user must have permissions to run the report.
JDE_PWD	JDE EnterpriseOne password	The EnterpriseOne password that corresponds to the user ID.

Set the parameters for the RunUBE command as shown in Table 3-3.

Table 3-3 RunUBE Command related KM Options

Option	Value	Notes
JDE_ENVIRONMENT	The JDE EnterpriseOne environment
JDE_ROLE	The JDE EnterpriseOne role
JDE_REPORT	The system name of the report that you want to process	For example: `APS Outbound Processor (R34A400)` and `APS Inbound Processor (R34A410)` for flat files, and the `APS SCBM 2.0 Outbound Processor (R34A700)` and `APS Master Inbound Processor (R34A820)` for XML files
JDE_VERSION	The name of the version of the report that you want to process	For example: `XJDE0001`. Note that you must enter a version name; you cannot submit the template of a report.
JDE_JOB_QUEUE	The name of the job queue to which the system should route the batch job	For example: `QBATCH`
JDE_PROCESSING_MODE	The processing mode	Enter `B` to use batch processing. In this case, the system uses the Job Control Status Master table (F986110) to assign the report a place in the queue. Enter `I` to use the interactive mode. This mode runs the report immediately outside of the JDE EnterpriseOne queuing mechanism
JDE_HOLD_CODE	The hold code	Enter `P` to send the output to a printer immediately after the job completes. Enter `H` to hold the processed file without printing. You can print the job later using the Work With Servers program (P986116) that is accessible from the System Administration Tools menu (GH9011).
JDE_SAVE_CODE	The save code	Enter `S` to save the file after processing is complete. The delete option (`D`) is reserved for future use. Currently, the delete option is disabled.

Limitations of the IKM JDE Enterprise One Control Append (UBE)

The TRUNCATE option cannot work if the target table is referenced by another table (foreign key).
When using the RECYCLE_ERRORS option, an Update Key must be set for your interface.
When using this module with a journalized source table, data is automatically filtered to not include source deletions.
The FLOW_CONTROL and STATIC_CONTROL options call the Check Knowledge Module to isolate invalid data (if no CKM is set, an error occurs). Both options must be set to No when an integration interface populates a TEMPORARY target datastore.
The RunUBE command must be executed on the JDE server.
The Oracle Data Integrator run-time agent must be installed on this server.
Besides the information whether the RunUBE command has been started or not, the RunUBE command does not give any further details about the execution of the program. To know more about the execution of the program you can either view the log file created by the JDE server or connect to your JDE application and look for the application View Job Status (Application = P986110, Form = W986116A).