Connectors → JD Edwards
About Oracle JD Edwards EnterpriseOne
Oracle JD Edwards EnterpriseOne is a versatile ERP software suite with flexible database and deployment options, including on-premises, private, public, or hybrid clouds. This suite features over 80 modules, including general ledger, accounts payable, accounts receivable, fixed assets, and cash management.
About the JD Edwards Connectors
Incorta ingests data from Oracle JD Edwards EnterpriseOne by connecting to its metadata database. It supports both Oracle and SQL Server databases, providing flexibility based on your setup. For SQL Server connections, Incorta can use either the Microsoft JDBC driver or the jTDS JDBC driver.
These connectors are available in the Marketplace for Incorta releases 2024.1.7, 2024.7.x, and later.
To accommodate different metadata database configurations in JD Edwards EnterpriseOne, Incorta offers three distinct connectors:
- JD Edwards (Oracle)
- JD Edwards (SQL Server)
- JD Edwards (SQL Server - jTDS)
These connectors allow you to seamlessly bring JD Edwards EnterpriseOne data into Incorta, enabling the creation of dashboards and insights. This modernized approach to reporting and analytics helps your organization overcome challenges in managing JD Edwards EnterpriseOne data, delivering actionable insights and enhanced decision-making capabilities.
The JD Edwards connectors support the following Incorta-specific functionalities:
| Feature | Supported |
|---|---|
| Chunking | ✔ (JD Edwards (Oracle) |
| Data Agent | ✔ |
| Encryption at Ingest | |
| Incremental Load | ✔ |
| Multi-Source | ✔ |
| OAuth | |
| Performance Optimized | ✔ |
| Remote | |
| Single-Source | ✔ |
| Spark Extraction | |
| Webhook Callbacks | ✔ |
Steps to connect Oracle JDE EnterpriseOne and Incorta
To connect Oracle JDE EnterpriseOne and Incorta, here are the high-level steps, tools, and procedures:
Create an external data source
You can create an external data source via the Data Manager. The JD Edwards connectors exist under the Database connector category.
For the list of properties available when creating a JD Edwards data source, refer to the JD Edwards connector properties.Create a schema table with the Schema Wizard or the Schema Designer
You can create a schema table via the Schema Wizard or the Schema Designer.For the list of properties available when creating a dataset based on a JD Edwards data source, refer to the JD Edwards dataset properties.
NoteWhen creating a schema table via the Schema Designer, you can find the JD Edwards data sources when you select SQL Database for the data source Type.
Load the schema
You can perform a full or incremental load of the schema with the JD Edwards dataset. You can also load a specific table.Explore the schema
After loading data, you can use the Analyzer to explore the physical schema, create your first insight, and save it to a new dashboard tab or an existing dashboard tab.
JD Edwards connector properties
The three connectors share most of the properties in this table. Only a few of them are connector-specific.
| Property | Control | Description |
|---|---|---|
| Data Source Name | text box | Enter the name of the data source |
| Username | text box | Enter the database username |
| Password | text box | Enter the database password |
| Authentication type | dropdown list | This option is available only for JD Edwards (SQL Server - jTDS). Select the authentication type to connect to the SQL server: ● Windows Authentication ● SQL Server Authentication |
| Connection Pool | spin box | Enter the connection pool. The default is 30. |
| Connection String | text box | Enter the connection string depending on the selected connector. ● JD Edwards (Oracle): jdbc:oracle:thin:@<HOST>:<PORT>:<DATABASE_NAME> ● JD Edwards (SQL Server): jdbc:sqlserver://<HOST>:<PORT>;databaseName=<DATABASE_NAME>; ● JD Edwards (SQL Server - jTDS): jdbc:jtds:sqlserver://<HOST>:<PORT>/<DATABASE_NAME>; |
| Set Extraction Timeout | toggle | This option is available only for JD Edwards (Oracle). Turn the toggle on to enable the termination of load jobs for the SQL query if the extraction time exceeds the configured time. |
| Stop after (Minutes) | spin box | This option is available only for JD Edwards (Oracle) when the Set Extraction Timeout is enabled. Enter the maximum time allowed to extract data based on the SQL query. When exceeding this period, Incorta terminates the load job. |
| Connection Properties | text box | Enter a line-separated list of customized properties, as applicable, in the format of propertyName=propertyValue. ● For Oracle connection properties, refer to Oracle JDBC Driver documentation. ● For SQL Server connection properties, refer to Setting the connection properties. ● For jTDS SQL Server connection properties, refer to The JTDS Project FAQ. |
| Show Advanced Options | toggle | Turn on this toggle to show and set the advanced options |
| Show Advanced Options > JDE Business Data Schema | text box | Enter the name of the JDE business schema. The required format varies according to the selected connector. ● For JD Edwards (Oracle), enter the schema name only. The default is PS920DTA. ● For JD Edwards (SQL Server) and (SQL Server - jTDS), enter the database and schema name in the following format [database].[schema_name]. The default is JDE_PRODUCTION.PRODDTA. |
| Show Advanced Options > JDE Data Dictionary Schema | text box | Enter the name of the JDE data dictionary schema. The required format varies according to the selected connector. ● For JD Edwards (Oracle), enter the schema name only. The default is DD920. ● For JD Edwards (SQL Server) and (SQL Server - jTDS), enter the database and schema name in the following format [database].[schema_name]. The default is JDE920.DD920. |
| Show Advanced Options > JDE Central Object Schema | text box | Enter the name of the JDE central object schema. The required format varies according to the selected connector. ● For JD Edwards (Oracle), enter the schema name only. The default is PS920. ● For JD Edwards (SQL Server) and (SQL Server - jTDS), enter the database and schema name in the following format [database].[schema_name]. The default is JDE_PD920.PD920. |
| Show Advanced Options > JDE Object Librarian Schema | text box | Enter the name of the JDE object librarian schema. The required format varies according to the selected connector. ● For JD Edwards (Oracle), enter the schema name only. The default is OL920. ● For JD Edwards (SQL Server) and (SQL Server - jTDS), enter the database and schema name in the following format [database].[schema_name]. The default is JDE920.OL920. |
| Extra Options | text box | Enter supported extra options in the form of key=value. |
| Use Data Agent | toggle | Enable using a data agent to securely ingest data that resides behind a firewall. For more information, please review Tools → Data Agent and Tools → Data Manager. |
| Data Agent | dropdown list | This property is available when Use Data Agent is enabled. Select from the data agents created in the tenant, if any. |
JD Edwards dataset properties
For a schema table in Incorta based on a JD Edwards data source, you can specify the following properties:
| Property | Control | Connector | Description |
|---|---|---|---|
| Incremental | toggle | All | Enable incremental load configuration for the schema table. See Types of Incremental Load. |
| Incremental Extract Using | dropdown list | JD Edwards (Oracle) | This property becomes available when Incremental is enabled. Use the Incremental Extract Using list to specify the incremental load method, choosing either Last Successful Extract Time or Maximum Value of a Column. See Types of Incremental Load. |
| Incremental Column | dropdown list | JD Edwards (Oracle) | This property becomes available when Incremental Load is enabled. Use the Incremental Column dropdown to select the column whose maximum value the Loader will track, using the greatest value or the most recent timestamp for each load operation. |
| Set Extraction Timeout | toggle | JD Edwards (Oracle) | Turn the toggle on to enable the termination of load jobs for the SQL query for this table if the extraction time exceeds the configured time. This setting overrides the similar setting at the data source level. |
| Stop after (Minutes) | spin box | JD Edwards (Oracle) | This property becomes available when Set Extraction Timeout is enabled. Use the Stop after (Minutes) field to specify the maximum extraction time in minutes for this table based on the SQL query. If the extraction exceeds this limit, Incorta will terminate the load job. This setting overrides the similar setting configured at the data source level. |
| Query | text box | All | Enter the SQL query to retrieve data from the data source. |
| Update Query | text box | All | This property becomes available when Incremental Load is enabled. Enter the SQL update query to use during an incremental load. |
| Timestamp Field Type | dropdown list | SQL Server and SQL Server - jTDS | This property becomes available when Incremental Load is enabled. Select the type of the timestamp field used in the update query: ● Timestamp ● Unix Epoch (seconds) ● Unix Epoch (milliseconds) |
| Incremental Field Type | dropdown list | JD Edwards (Oracle) | This property becomes available when Incremental Load is enabled. Select the format of the incremental field type. |
| Fetch Size | text box | All | Specify the number of records that will be retrieved from the database in each batch until all records are retrieved. The default is 5000. |
| Chunking Method | dropdown list | JD Edwards (Oracle) | Chunking methods allow for parallel extraction of large tables. The default is No Chunking. There are two chunking methods: ● By Size of Chunking (Single Table) ● By Timestamp |
| Chunk Size | text box | JD Edwards (Oracle) | This text box becomes available when you set the Chunking Method to By Size of Chunking. Enter the number of records to extract per chunk in relation to the Fetch Size. The default is 3 times the fetch size. |
| Order Column | dropdown list | JD Edwards (Oracle) | This property becomes available when you set the Chunking Method to By Size of Chunking. Select a column in the source table to order by before chunking. It's typically an ID column and it must be numeric. |
| Order Column [Date/Timestamp] | dropdown list | JD Edwards (Oracle) | This property becomes available when you set the Chunking Method to By Timestamp. Select a column in the source table to order by before chunking. It should be a Timestamp column. |
| Chunk Period | dropdown list | JD Edwards (Oracle) | Select the chunk period that will be used in dividing chunks: ● Daily ● Weekly (default) ● Monthly ● Yearly ● Custom |
| Number of days | text box | JD Edwards (Oracle) | This property becomes available when you set the Chunk Period to Custom. Enter the chunking period in days. |
| Upper Bound for Order Column | text box | JD Edwards (Oracle) | Optional. Enter the maximum value for the order column. |
| Lower Bound for Order Column | text box | JD Edwards (Oracle) | Optional. Enter the minimum value for the order column. |
| Callback | toggle | All | Turn this toggle on to enable post-extraction callback |
| Callback URL | text box | All | This property becomes available when the Callback option is enabled, allowing you to specify the callback URL. |
Types of Incremental Load
You can enable incremental load for a JD Edwards table dataset. The options available vary according to the connector you use.
Incremental load types available for JD Edwards (Oracle)
There are two types of incremental extractions available for a table dataset based on the JD Edwards (Oracle) connector:
- Last Successful Extract Time: Fetch updates since the last time the tables were loaded. Determined by the difference between the current time and the database timestamp.
- Maximum Value of a Column: The column-based strategy depends on a column in the table. The connector supports both timestamp and numeric columns. A timestamp column is of the type date or timestamp. A numeric column is of the type int or long.
Changing or disabling the incremental load strategy requires a full load to ensure data integrity.
Incremental load types available for JD Edwards SQL Server
There is only one type of incremental extractions available for a table dataset based on the JD Edwards (SQL Server) and (SQL Server - jTDS) connectors. You can fetch updates based on the value of a timestamp column in the table.