Results for “gl_subr_led”

50+ results




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

Overview

GL_SUBR_LED is the Oracle Process Manufacturing (OPM) subsidiary ledger table owned by the GMF schema. It functions as the liaison between OPM subsystem activity and the Oracle General Ledger, storing the booked accounting detail generated from OPM subsystem transactions (documents). In Oracle EBS 12.1.1 and 12.2.2, records are created and refreshed by the OPM Subsidiary Ledger Update process, which translates confirmed subsystem transactions — receipts, deliveries, inventory movements, and related costing events — into entries that can be summarized and transferred to GL through the standard OPM-to-GL transfer and posting programs.

The table is the primary repository of accounting distributions at the OPM subledger level, sitting logically between the operational transaction tables and the GL interface. Each row represents a single subledger accounting entry line, carrying the source document identity, accounting flexfield reference, currency amounts, quantities, tax attributes, and posting status indicators. From a dimensional modeling perspective, the FK structure of GL_SUBR_LED — numerous references to master tables with no dependent child tables — supports a heuristic Data Vault classification as a link entity, connecting document events to accounting, currency, ledger, and unit-of-measure masters.

Key Information Stored

The surrogate primary key is SUBLEDGER_ID, enforced by the GL_SUBR_LED_PK unique index. No other unique index is documented, so additional business-key candidates should be validated against actual data before being treated as guaranteed unique.

Common Use Cases and Queries

Typical reporting includes subledger-to-GL reconciliation, unposted or unexported transaction analysis, period-end close validation, tax detail review, and quantity-versus-value audit. A common pattern filters entries that have not yet been exported:

  • SELECT SUBLEDGER_ID, DOC_TYPE, DOC_ID, ACCT_ID, AMOUNT_BASE, AMOUNT_TRANS FROM GMF.GL_SUBR_LED WHERE EXPORTED_DATE IS NULL;
  • SELECT s.FISCAL_YEAR, s.PERIOD, s.CO_CODE, SUM(s.AMOUNT_BASE) FROM GMF.GL_SUBR_LED s WHERE s.LEDGER_CODE = :ledger GROUP BY s.FISCAL_YEAR, s.PERIOD, s.CO_CODE;
  • Joining to GL_SUBR_STA on REFERENCE_NO to trace control totals or batch status.
  • Joining to GL_ACCT_MST on ACCT_ID to expand account descriptions for financial reporting extracts.
  • Comparing AMOUNT_BASE against AMOUNT_TRANS and EXCHANGE_RATE to validate currency conversion for multi-currency ledgers.

Because the table is maintained by the OPM Subsidiary Ledger Update process, direct DML should be avoided; corrections belong in the originating subsystem transactions followed by a re-run of the update process.

Related Objects

The most significant relationships, based on documented foreign keys, are:

  • GL_ACCT_MST — joined on GL_SUBR_LED.ACCT_ID for account combination detail.
  • GL_ACCU_MST — joined on ACCTG_UNIT_ID for accounting unit attributes.
  • GL_CURR_MST — joined on CURRENCY_BASE and CURRENCY_TRANS for currency definitions.
  • GL_LDGR_MST — joined on LEDGER_CODE for ledger information.
  • GL_PLCY_MST — joined on CO_CODE for company policy context.
  • GL_SEVT_MST — joined on SUB_EVENT_TYPE for accounting event definitions.
  • GL_SRCE_MST — joined on TRANS_SOURCE_TYPE for source classification.
  • GL_SUBR_STA — joined on REFERENCE_NO for subledger control/status records.
  • GL_ACCT_TTL — joined on ACCT_TTL_TYPE for account title information.
  • SY_UOMS_MST — joined on QUANTITY_UM for unit of measure descriptions.

These referenced masters supply the descriptive dimensions that make GL_SUBR_LED usable both for OPM close processing and for downstream GL transfer and reporting.