Results for “gl_ledger_set_requests”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GL_LEDGER_SET_REQUESTS is a General Ledger (GL) schema table that records the status of child concurrent requests spawned when a ledger set operation is submitted to the Concurrent Manager. Ledger sets allow multiple ledgers to be grouped and processed together for reporting, consolidation, and period-close activities. When a parent concurrent program is issued against a ledger set, Oracle EBS decomposes the work into one child concurrent request per ledger in the set. GL_LEDGER_SET_REQUESTS is the cross-reference and status-tracking table that links the parent request, each child request, the ledger set, and the individual ledger, so that the aggregate outcome of the set can be monitored and reconciled.

From a heuristic Data Vault modeling perspective, the table is best classified as a link entity. Its primary key is composed entirely of foreign references to FND_CONCURRENT_REQUESTS (parent and child) and GL_LEDGERS (ledger set and ledger), which is characteristic of a link table capturing an association between existing hubs rather than holding descriptive attributes of a single business entity. The status and error columns behave as link-level satellite attributes describing the state of that association.

The table exists in both Oracle EBS 12.1.1 and 12.2.2 with the documented 11-column physical schema owned by the GL schema, and is marked VALID in ETRM metadata for 12.2.2.

Key Information Stored

The table's columns fall into three functional groups: relationship keys, status attributes, and standard audit columns.

• PARENT_REQUEST_ID — Foreign key to FND_CONCURRENT_REQUESTS identifying the top-level concurrent request submitted against the ledger set.
• CHILD_REQUEST_ID — Foreign key to FND_CONCURRENT_REQUESTS identifying the per-ledger child request generated by that parent.
• LEDGER_SET_ID — Foreign key to GL_LEDGERS identifying the ledger set being processed. Despite the _ID suffix, the FK reference is documented against GL_LEDGERS.
• LEDGER_ID — Foreign key to GL_LEDGERS identifying the individual ledger whose child request is tracked in this row.
• STATUS_CODE — The processing status of the child request, allowing the parent's progress to be derived from the combined state of its children.
• ERROR_MESSAGE — Diagnostic text captured when a child request fails, supporting exception reporting and troubleshooting.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, and CREATED_BY provide standard EBS "WHO" auditing of row creation and modification.

The surrogate primary key is GL_LEDGER_SET_REQUESTS_PK, defined over the composite of PARENT_REQUEST_ID, CHILD_REQUEST_ID, LEDGER_SET_ID, and LEDGER_ID. A unique index, GL_LEDGER_SET_REQUESTS_U1, mirrors this same column set, confirming the four-column combination as the business-key candidate that enforces one row per parent/child/ledger-set/ledger combination. No independent surrogate sequence column is documented; the primary key is fully natural and relational.

Common Use Cases and Queries

Primary use cases center on concurrent request monitoring, ledger set diagnostics, and close-process reporting. A typical query retrieves the status of all children under a given parent request:

• SELECT child_request_id, ledger_id, status_code, error_message FROM gl_ledger_set_requests WHERE parent_request_id = :p_request_id;
• Aggregating status to determine whether a ledger set run completed successfully — for example, counting children grouped by STATUS_CODE to detect partial failures.
• Joining to FND_CONCURRENT_REQUESTS to obtain concurrent program names, phase codes, and completion text for both parent and child requests.
• Joining to GL_LEDGERS to resolve ledger names and ledger set names for user-facing reports that show which ledger produced which error.
• Exception reporting: filtering on non-null ERROR_MESSAGE to surface child requests that failed during a ledger set operation.

Related Objects

The following objects are most significant in relation to GL_LEDGER_SET_REQUESTS, based on documented foreign key relationships:

• FND_CONCURRENT_REQUESTS — Referenced twice, via PARENT_REQUEST_ID and CHILD_REQUEST_ID; the principal join target for request-level monitoring.
• GL_LEDGERS — Referenced twice, via LEDGER_SET_ID and LEDGER_ID; supplies ledger and ledger set descriptions.
• FND_CONCURRENT_PROGRAMS — Combined with FND_CONCURRENT_REQUESTS to identify the concurrent program executed for each child request.
• GL_LEDGER_SETS / GL_LEDGER_SET_ASSIGNMENTS — Define which ledgers belong to a set, providing the expected set of child requests against which recorded rows can be validated.
• GL_LEDGER_SET_REQUESTS_PK and GL_LEDGER_SET_REQUESTS_U1 — The primary key constraint and unique index enforcing row uniqueness.