Overview

This section shows the available API objects and provides more information on executing SQL to JD Edwards data.

Key Features

• The connector models JD Edwards tables and business views as relational views, allowing you to write SQL to query JD Edwards data.
• Stored procedures allow you to execute operations against JD Edwards, such as retrieving contact data.
• Live connectivity to these objects means any changes in your JD Edwards environment are immediately reflected when using the connector.

Schema Organization

JD Edwards organizes its tables and business views into System Codes (also called Product Codes) — for example, 04 (AccountsPayable), 08B (BenefitsAdministration), or 52 (ContractBilling). The connector exposes each System Code as its own SQL schema, so a table's fully qualified name reflects the schema it belongs to, e.g. AccountsPayable.AccountLedger or ContractBilling.ContractRevenueSummary.

You can control which system codes are exposed as schemas using these connection properties:

• DataModel: Selects one or more ERP modules (each a bundle of System Codes) to expose as schemas, or All to expose every System Code available in the connected JD Edwards instance.
• SystemCodes: Adds specific System Codes as schemas in addition to whatever DataModel selects, for cases where you need a table that isn't part of the selected module(s).

To list the schemas available on the current connection, query the sys_schemas system table:

SELECT * FROM sys_schemas

Example Schemas

The example schemas below represent only a small subset of the available schemas and include example views and stored procedures to demonstrate the structure of the Data Model. Many more schemas and System Codes are available live via a connection — see the Schemas section above.

• See AccountsPayable for accounts payable examples.
• See ContractBilling for contract billing examples.
• See BenefitsAdministration for benefits administration examples.
• See RealEstateManagement for real estate management examples.
• See AddressBook for address book examples.

To explore the full Data Model, query the sys_tables and sys_procedures system tables, which list all available views and stored procedures exposed by the connector.