Search Results sys_il0000396569c00005

Overview

The EDR.EDR_PROCESS_ERECORDS_T table is an Oracle E-Business Suite interface table that serves as the staging and processing repository for electronic records (e-records) managed by the EDR (Electronic Data Records / ERES Manager) subsystem. It is created in the APPS_TS_INTERFACE tablespace, and its status is VALID across EBS 12.1.1 and 12.2.2. The object carries the standard Oracle internal-use restriction: access is supported only through standard Oracle Applications programs, not by direct customer SQL.

The table captures the runtime payload, transaction context, approval status, and parent/child relationships of e-records as they move through ERES (Electronic Records and Electronic Signatures) processing. A heuristic Data Vault classification mined from its foreign key structure places this object as satellite-leaning — a modeling suggestion that reflects its role storing descriptive, transaction-attributable attributes around a driving process entity rather than acting as a pure hub or link.

Key Information Stored

The surrogate primary key is ERECORD_SEQUENCE_ID, enforced by unique index EDR_PROCESS_ERECORDS_T_P. A secondary unique index, SYS_IL0000396569C00005$$, is the LOB index backing the PAYLOAD CLOB column. The documented business-key candidate is the primary key column itself; no separate composite unique business key is documented.

The most significant columns include:

• ERES_PROCESS_ID — the process identifier for the transaction; indexed non-uniquely by EDR_PROCESS_ERECORDS_T_N1 and the principal join to the ERES manager.
• TRANSACTION_NAME and TRANSACTION_KEY — the e-record transaction identity.
• PAYLOAD — a CLOB (4000) holding runtime transaction data.
• REQUESTER — the user requesting the transaction; FK to FND_USER.
• STATUS — the e-record approval status.
• ERECORD_ID — the identifier as stored in the evidence store.
• PARENT_NAME, PARENT_KEY, PARENT_ERECORD_ID, CHILD_ERECORD_IDS — hierarchy linkage.
• DEFERRED_MODE and POST_OP_API — deferred transaction handling.
• USER_KEY_LABEL / USER_KEY_VALUE — user-defined key metadata.
• WF_ITEM_TYPE, WF_ITEM_KEY, WF_PROCESS — Workflow correlation.
• Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE).

Common Use Cases and Queries

Typical scenarios include monitoring pending e-records by status, tracing a transaction to its requesting user, and reconstructing parent/child evidence chains. A representative pattern joins the process manager:

• SELECT p.ERECORD_SEQUENCE_ID, p.TRANSACTION_NAME, p.STATUS, u.USER_NAME FROM EDR.EDR_PROCESS_ERECORDS_T p, FND_USER u WHERE p.REQUESTER = u.USER_ID AND p.STATUS = :status;
• Correlating records to a process: SELECT * FROM EDR.EDR_PROCESS_ERECORDS_T WHERE ERES_PROCESS_ID = :process_id;
• Workflow trace: filter on WF_ITEM_TYPE, WF_ITEM_KEY, WF_PROCESS to reconcile e-records with Workflow activity.

Because PAYLOAD is a CLOB, reports should avoid selecting it unless required. Oracle recommends querying only through supported application APIs.

Related Objects

The most significant related objects, grounded in the documented foreign key relationships, are:

• FND_USER — joined via REQUESTER to resolve the requesting user.
• EDR_ERESMANAGER_T — joined via ERES_PROCESS_ID to the driving ERES process.
• EDR_PROCESS_ERECORDS_T_P — unique primary key index on ERECORD_SEQUENCE_ID.
• EDR_PROCESS_ERECORDS_T_N1 — non-unique index on ERES_PROCESS_ID, supporting process-based lookups.
• SYS_IL0000396569C00005$$ — LOB index for the PAYLOAD column.