Results for “security_id_char_1”

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

Overview

XLA_EVENTS_INT_GT is a global temporary interface table owned by the XLA schema in Oracle E-Business Suite, serving the Subledger Accounting (XLA) module. Its purpose is to facilitate the bulk creation of accounting events, which are the foundational records that subsequently flow into the accounting engine for journal entry generation. The table functions strictly as a temporary staging area: rows inserted during a session are purged automatically upon COMMIT, meaning the object holds no persistent data and must not be treated as a durable audit or reporting source.

Because the table is transient and standalone in nature, ETRM data vault classification heuristic suggests treating it as a staging or load construct rather than a modeled entity. It does not participate in traditional hub, link, or satellite relationships within the data vault model; instead it acts as a high-volume inbound conveyor for event data that is validated, processed, and then discarded. Its only documented foreign key relationship — LEGAL_ENTITY_ID referencing FV_LEGAL_ENTITIES — reinforces that events are scoped to a specific legal entity during ingestion.

Key Information Stored

The table exposes 43 columns, but its functional core is concentrated in a small set of identifiers and control attributes. The most important are:

• EVENT_ID — The surrogate identifier and the sole documented unique index (XLA_EVENTS_INT_GT_U1), making it the business-key candidate for uniquely identifying each staged event.
• ENTITY_ID, APPLICATION_ID, LEDGER_ID, LEGAL_ENTITY_ID — The primary scoping keys that determine which entity, application, ledger, and legal entity the event belongs to. LEGAL_ENTITY_ID is the only column with a documented foreign key, to FV_LEGAL_ENTITIES.
• ENTITY_CODE, EVENT_CLASS_CODE, EVENT_TYPE_CODE — Classify the event by source entity and event taxonomy, driving how the accounting engine will interpret it.
• EVENT_NUMBER, TRANSACTION_NUMBER, TRANSACTION_DATE — Business-facing references and timing information linking the event to its originating transaction.
• EVENT_DATE, EVENT_STATUS_CODE, PROCESS_STATUS_CODE — Control the event's effective date and its lifecycle state during processing.
• SOURCE_ID_INT_1..4 and SOURCE_ID_CHAR_1..4 — The flexible source identifier slots used to map the event back to its originating subledger transaction.
• REFERENCE_NUM_1..4, REFERENCE_CHAR_1..4, REFERENCE_DATE_1..4 — Generic reference attribute groups for passing supplemental descriptive data into the accounting process.
• ON_HOLD_FLAG, BUDGETARY_CONTROL_FLAG — Operational flags that influence whether the event proceeds through accounting.

Common Use Cases and Queries

The primary use case is bulk event creation. A subledger process or custom concurrent program inserts a batch of events into this table within a single transaction, invokes the Subledger Accounting event API, and relies on COMMIT to clean the staging area. Consequently, queries against this table are almost always executed from within the same session that inserted the data, and any query outside that context will typically return no rows.

Typical diagnostic patterns include verifying staging contents prior to processing:

• SELECT EVENT_ID, EVENT_CLASS_CODE, EVENT_TYPE_CODE, EVENT_STATUS_CODE, PROCESS_STATUS_CODE FROM XLA_EVENTS_INT_GT WHERE LEDGER_ID = :ledger_id;
• Detecting held or blocked events: SELECT * FROM XLA_EVENTS_INT_GT WHERE ON_HOLD_FLAG = 'Y';
• Counting staged volume by class and entity before commit: SELECT ENTITY_CODE, COUNT(*) FROM XLA_EVENTS_INT_GT GROUP BY ENTITY_CODE;
• Joining back to source entities using SOURCE_ID_CHAR_1 or SOURCE_ID_INT_1 when tracing origin transactions.

Because the data is volatile, it is unsuitable for reconciliation or trend reporting; persistent results are found in the permanent XLA_EVENTS and XLA_AE_HEADERS tables once processing completes.

Related Objects

The following objects are most significant in relation to XLA_EVENTS_INT_GT:

• FV_LEGAL_ENTITIES — Referenced via the documented foreign key LEGAL_ENTITY_ID; the only explicit FK relationship in the metadata.
• XLA_EVENTS — The permanent destination where validated events ultimately reside after the temporary interface is processed.
• XLA_AE_HEADERS and XLA_AE_LINES — Downstream accounting entry tables populated once events are accounted.
• XLA_TRANSACTION_ENTITIES — Defines the transaction entity context that the EVENT_CLASS_CODE and ENTITY_CODE values align to.
• XLA_EVENT_CLASSES and XLA_EVENT_TYPES — Reference the classification codes staged in the table.
• XLA_EVENTS_PKG / Subledger Accounting event APIs — The programmatic entry point responsible for consuming rows and generating accounting events.

Together these objects form the ingestion pipeline through which subledger transactions become accounted entries, with XLA_EVENTS_INT_GT serving exclusively as the volatile entry point.