# Oracle JD Edwards EnterpriseOne

## Overview

The Veza integration for Oracle JD Edwards Enterprise One (JDE) discovers users and roles assigned in JDE. Veza uses a database account to connect to the JDE database and execute queries to gather user metadata and role assignments.

The integration supports both Oracle and Microsoft SQL Server database backends.

## Prerequisites

Before configuring the integration, ensure you have:

* Administrative access to your JDE database (Oracle or MSSQL)
* Necessary permissions to create database users and grant permissions
* Database connection details (hostname, port, database name)

## Database Configuration

### Oracle Database

1. Connect to a common user with the `CREATE USER` privilege.
2. If the JDE is installed on an Oracle 12c pluggable DB (pdb), switch to the proper pluggable DB.

   ```sql
   ALTER SESSION SET CONTAINER=<pdb_name>;
   ```
3. Create the integration user:

   ```sql
   CREATE USER <username> IDENTIFIED by <strong_password>;
   GRANT SELECT on sy920.f95921 to <username>;
   GRANT SELECT on sy920.f0092 to <username>;
   GRANT SELECT on sy920.f550092t to <username>;
   GRANT SELECT on sy920.f98Owsec to <username>;
   GRANT SELECT on sy920.f0092l to <username>;
   GRANT SELECT on sy920.f9312 to <username>;
   ```

### Microsoft SQL Server

1. Connect to SQL Server Management Studio as a sysadmin.
2. Create the integration login and user:

   ```sql
   -- Create a SQL Server login
   USE [master];
   CREATE LOGIN [veza_jde] WITH PASSWORD = '<strong_password>';

   -- Switch to the JDE database and create a user for the login
   USE JDE_PD920;
   CREATE USER [veza_jde] FOR LOGIN [veza_jde];

   -- Grant SELECT permissions on required JDE tables
   GRANT SELECT ON JDE.f550092t TO [veza_jde];
   GRANT SELECT ON JDE.f0092 TO [veza_jde];
   GRANT SELECT ON JDE.f95921 TO [veza_jde];
   GRANT SELECT ON JDE.F98OWSEC TO [veza_jde];
   GRANT SELECT ON JDE.F0092L TO [veza_jde];
   GRANT SELECT ON JDE.F9312 TO [veza_jde];
   ```

Save the username and password created above for configuration on the Veza platform.

### Enable the Oracle JDE Integration in Veza

1. In Veza, go to the **Integrations** page.
2. Click **Add Integration**.
3. Search for **Oracle JDE**. Select it and click **Next**.
4. Configure the integration:
   * **Insight Point**: Select an Insight Point or choose to use the default internal Insight Point for the connection.
   * **Name**: Enter a display name to identify the provider.
   * **DB FQDN**: The Fully Qualified Domain Name of the Oracle Database instance, e.g., `myoracleserver.domain.com` or `192.168.1.100`.
   * **DB Instance Name**: The optional instance name if connecting to a named Microsoft SQL Server instance (mssql only).
   * **DB Name**: Database name, e.g., `SYS`. You can retrieve this with the SQL command `select * from global_name;`.
   * **DB Port**: Port for the connection, e.g., `1521`.
   * **DB Schema Name**: The schema name for the Oracle JDE connection, e.g. `SY920` (mssql only).
   * **DB Type**: The type of database backend used for the Oracle JDE installation. Valid options are `oracle` or `mssql`.
   * **Username**: Name of the user created in the steps above, e.g., `exampleuser`.
   * **Password**: Password of the integration user.
5. Click **Save** to test the connection and save the configuration.
6. Validate the integration was successful by checking the integration status on the **Integrations** page. Click the integration name to view detailed status and events for each data source.

## Notes and Supported Entities

The integration discovers the following entities, along with attributes for filtering queries and fine-tuning the scope of access review.

### Oracle JDE User

Represents an Oracle JDE user.

| Attribute   | Description        |
| ----------- | ------------------ |
| ID          | User login name    |
| Email       | User email address |
| Employee ID | User employee ID   |

### Oracle JDE Role

Represents an Oracle JDE role.

| Attribute | Description |
| --------- | ----------- |
| Name      | Role name   |

## Troubleshooting

* For Oracle connections, verify the database service name using `tnsping`.
* For MSSQL connections, ensure the SQL Server Browser service is running if using named instances.
* Check database firewall rules allow connections from the Insight Point IP address.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.veza.com/4yItIzMvkpAvMVFAamTf/integrations/integrations/oracle-jde.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.