Search Results gl_rx_trial_balance_itf




Overview
Explore in AI Chat

Overview

GL_RX_TRIAL_BALANCE_ITF is an interface table owned by the GL schema in Oracle E-Business Suite General Ledger. Its documented purpose is to serve as the staging interface for country-specific trial balance reports delivered through the GL (General Ledger) "RX" reporting framework. Rather than storing live subledger or journal activity directly, the table is populated by a concurrent program and consumed by report-generation logic that formats the balances according to localized statutory requirements.

From a Data Vault modeling perspective (heuristic, derived from the foreign-key structure), this table is best classified as a link object. It does not carry the enduring, slowly-changing descriptive attributes of a hub, nor the type-2 historical tracking of a satellite; instead it records the association between a concurrent-request execution, an accounting ledger, a chart of accounts, and a reporting currency, together with the resolved period balances for a single run.

Key Information Stored

The table contains 25 documented columns. The most significant are as follows:

The metadata does not document a dedicated surrogate primary key or a unique index; the table is effectively keyed by the combination of REQUEST_ID, PERIOD_NAME, LEDGER_ID, CURRENCY_CODE, and the balancing/account segment pair for a given run.

Common Use Cases and Queries

The principal use case is post-run inspection and reconciliation of a country-specific trial balance report. A typical query retrieves all lines for the latest request run:

SELECT request_id, period_name, ledger_id, currency_code,
       balancing_segment, account_segment,
       period_net_dr, period_net_cr,
       year_to_date_balance_dr, year_to_date_balance_cr
FROM   gl.gl_rx_trial_balance_itf
WHERE  request_id = :p_request_id
ORDER  BY balancing_segment, account_segment;

Supporting scenarios include verifying that debit and credit totals tie out by period, comparing YTD balances across ledgers, extracting a run's data into a spreadsheet for statutory filing, and diagnosing why a report produced no output (an empty REQUEST_ID indicates the concurrent program failed to populate the interface).

Related Objects

The following objects are directly referenced through the documented foreign keys:

  • FND_CONCURRENT_REQUESTS — joined on GL_RX_TRIAL_BALANCE_ITF.REQUEST_ID; provides run timing, status, and parameters.
  • GL_SETS_OF_BOOKS_11I — joined on LEDGER_ID; supplies ledger and accounting-period-setup context.
  • FND_CURRENCIES — joined on CURRENCY_CODE; supplies currency name and precision.
  • GL_MGT_SEG_UPGRADE_H — joined on CHART_OF_ACCOUNTS_ID; relates the row to the management segment upgrade history.

The concurrent program that loads the table, together with the reporting template that consumes it, are the primary functional dependencies and should be reviewed alongside the table when troubleshooting country-specific trial balance output.