Results for “interface_run_id”

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

Overview

GL_INTERFACE_CONTROL is a General Ledger table in the GL schema that stores journal import execution control information. Its documented role is to govern the execution of the Journal Import program, which loads unposted journal entries from the GL_INTERFACE table into the GL_JE_BATCHES, GL_JE_HEADERS, and GL_JE_LINES tables. Each row in GL_INTERFACE_CONTROL represents a tracked run of Journal Import, identified by an interface run and grouped by source, group identifier, and ledger, allowing the application to process batches of interface rows incrementally and mark them as consumed once imported.

The table behaves as an execution ledger for the import process: it records which groups of GL_INTERFACE rows have been processed, the status of each run, and the concurrent request that performed the work. Because it stores the state and outcome of each import execution, the table is a critical reference point for reconciliation, error diagnosis, and rerun control. The documented foreign key from GL_INTERFACE_CONTROL.SET_OF_BOOKS_ID to GL_LEDGERS ties every control row to a specific ledger, confirming that import execution is scoped at the ledger level.

From a Data Vault modeling perspective, the ETRM relationship metadata classifies this object as satellite-leaning. Rather than acting as a pure hub or link, it functions primarily as a descriptive, time-bound record of the state of an import execution associated with a ledger and an interface run, which supports its treatment as a satellite around the ledger and run identifiers.

Key Information Stored

The documented schema for this table in ETRM 12.2.2 contains nine columns in the GL schema. The most significant of these are summarized below.

• INTERFACE_RUN_ID — the run identifier that ties a control row to a specific execution of Journal Import. This is a primary business-key candidate used to group and retrieve results for a given run.
• SET_OF_BOOKS_ID — the ledger identifier. This is the documented foreign key to GL_LEDGERS and the primary scoping key for the import execution.
• GROUP_ID — identifies the group of interface rows being processed in the run; it links the control record to the corresponding batch of GL_INTERFACE rows.
• JE_SOURCE_NAME — the journal source name (for example, Payables or Manual) whose interface rows are being imported, enabling source-level filtering and reporting.
• INTERFACE_TABLE_NAME — the name of the interface table processed by the run, distinguishing journal import targets.
• PROCESSED_TABLE_CODE — a code indicating the processed table or destination category associated with the run.
• PACKET_ID — an internal packet identifier used to partition and control processing of interface rows.
• STATUS — the execution status of the import run, used to determine whether processing completed successfully or requires attention.
• REQUEST_ID — the concurrent program request identifier, linking the run to its submission in the concurrent manager.

Where a surrogate primary key is present in the Oracle schema, it is an internal identifier rather than a business attribute; the meaningful business keys are the combination of ledger, interface run, group, and source. The documented columns above should be treated as the authoritative set for this object.

Common Use Cases and Queries

The primary use cases center on monitoring and troubleshooting Journal Import. Typical scenarios include identifying the status of a specific import run, finding all groups imported for a ledger, and correlating an import execution to its concurrent request.

To review recent import executions for a ledger:

• Sample pattern: SELECT INTERFACE_RUN_ID, GROUP_ID, JE_SOURCE_NAME, STATUS, REQUEST_ID FROM GL.GL_INTERFACE_CONTROL WHERE SET_OF_BOOKS_ID = :ledger_id ORDER BY INTERFACE_RUN_ID DESC;

To trace a specific interface run and its source:

• Sample pattern: SELECT * FROM GL.GL_INTERFACE_CONTROL WHERE INTERFACE_RUN_ID = :run_id;

To link a control row to its concurrent program output, join on REQUEST_ID to FND_CONCURRENT_REQUESTS. Reporting use cases include dashboards showing import throughput by source and ledger, aging of incomplete runs, and audit evidence that a given group of GL_INTERFACE rows was imported. Because processing is ledger-scoped, reporting should always filter by SET_OF_BOOKS_ID to avoid cross-ledger contamination of results.

Related Objects

The following objects are most significant in relation to GL_INTERFACE_CONTROL, based on documented keys and standard GL integration paths.

• GL_LEDGERS — referenced by the documented foreign key GL_INTERFACE_CONTROL.SET_OF_BOOKS_ID to GL_LEDGERS.SET_OF_BOOKS_ID.
• GL_INTERFACE — the staging table holding the journal rows processed by the run; joined via GROUP_ID, INTERFACE_RUN_ID, and JE_SOURCE_NAME.
• GL_JE_BATCHES — the posted batch destination populated when Journal Import completes successfully for the control row's group.
• GL_JE_HEADERS — journal header destination linked to the import result.
• GL_JE_LINES — journal line destination linked through the resulting headers.
• FND_CONCURRENT_REQUESTS — joined via REQUEST_ID to obtain request status and output.
• FND_CONCURRENT_PROGRAMS — identifies Journal Import and related concurrent programs tied to REQUEST_ID.
• GL_IMPORT_REFERENCES — correlates imported journal lines back to their original interface rows, complementing the control record.

Together these objects complete the chain from staging through import control to posted journals, with GL_INTERFACE_CONTROL providing the execution-level state that binds each run to its ledger and concurrent request.