Results for “source_system_code”

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

Overview

FEM_LD_INTERFACE_DATA_GT is a Global Temporary Table (indicated by the _GT suffix) belonging to the FEM (Enterprise Performance Foundation) product family within Oracle E-Business Suite. In Release 12.1.1 and 12.2.2, the Enterprise Performance Foundation module is classified as obsolete and has been largely superseded by the Enterprise Performance Management (EPM) and Hyperion-based consolidation and profitability components. The ETRM metadata explicitly notes that the object is "Not implemented in this database," meaning the physical segment is either absent from the current installation or has been replaced by a different underlying structure.

This table functions as a staging interface for ledger-derived loader (LD) data. It is populated transiently during the execution of ledger balance loading programs that transfer General Ledger balances, budgets, and encumbrance information into the FEM balances infrastructure. The base table name (FEM_LD_INTERFACE_DATA) with the _GT suffix aligns with Oracle's convention for session-scoped temporary storage, used to isolate intermediate results before final validation and loading into permanent FEM balances tables.

From a Data Vault modeling perspective, the metadata classifies this object as standalone. This heuristic suggests that the table does not behave as a conventional hub, link, or satellite. Rather, it acts as a transient staging structure that holds foreign-key references (such as ENCUMBRANCE_TYPE_ID) and descriptive attributes without forming persistent relationships. The standalone classification is consistent with a temporary interface table whose rows are consumed and discarded within a single program run.

Key Information Stored

The documented physical schema for 12.1.1 contains 22 columns. The most significant are listed below, grouped by function.

• Ledger and dataset identifiers: LEDGER_ID, LEDGER_DISPLAY_CODE, DATASET_CODE, DATASET_DISPLAY_CODE, DIMENSION_GROUP_ID, and SOURCE_SYSTEM_CODE / SOURCE_SYSTEM_DISPLAY_CODE identify the source ledger and dataset configuration that produced the interface row.
• Calendar and time attributes: CALENDAR_ID, CAL_PERIOD, CAL_PERIOD_NUMBER, CAL_PERIOD_LEVEL, CAL_PERIOD_END_DATE, and TIME_DIMENSION_GROUP_KEY establish the accounting period context.
• Budget and balance attributes: BUDGET_ID, BUDGET_DISPLAY_CODE, BALANCE_TYPE_CODE, ENCUMBRANCE_TYPE_ID, and ENCUMBRANCE_TYPE_CODE distinguish actual versus budgeted versus encumbrance amounts.
• Load control: TABLE_NAME, TABLE_ROW, DS_PRODUCTION_VALID_FLAG, and STATUS track the originating source row and the validation state during processing.

No surrogate primary key or unique index is documented in the ETRM metadata, which is consistent with the object's role as a temporary staging table. Column combinations such as (LEDGER_ID, DATASET_CODE, CAL_PERIOD, BUDGET_ID, ENCUMBRANCE_TYPE_ID) serve as logical business-key candidates for row identification and de-duplication.

Common Use Cases and Queries

Because the table is populated only during ledger load execution, typical queries are diagnostic rather than persistent. Common scenarios include validating row counts before and after validation, identifying rows that failed the production-valid check, and reconciling encumbrance balances.

• Counting staged rows per ledger and dataset: SELECT LEDGER_ID, DATASET_CODE, COUNT(*) FROM FEM_LD_INTERFACE_DATA_GT GROUP BY LEDGER_ID, DATASET_CODE;
• Identifying rows pending validation: SELECT * FROM FEM_LD_INTERFACE_DATA_GT WHERE STATUS = 'NEW' OR DS_PRODUCTION_VALID_FLAG = 'N';
• Reconciling encumbrance amounts: SELECT ENCUMBRANCE_TYPE_CODE, CAL_PERIOD, COUNT(*) FROM FEM_LD_INTERFACE_DATA_GT GROUP BY ENCUMBRANCE_TYPE_CODE, CAL_PERIOD;
• Joining to the encumbrance type reference to translate codes: SELECT i.*, t.NAME FROM FEM_LD_INTERFACE_DATA_GT i, GL_ENCUMBRANCE_TYPES t WHERE i.ENCUMBRANCE_TYPE_ID = t.ENCUMBRANCE_TYPE_ID;

These queries are typically run during implementation testing or when diagnosing a stalled ledger load. They are not suitable for production reporting because data is purged at session termination.

Related Objects

The documented foreign-key relationship and the object's role in the FEM loading pipeline define its principal dependencies.

• GL_ENCUMBRANCE_TYPES: Referenced through ENCUMBRANCE_TYPE_ID; provides the encumbrance type name and description for staged rows.
• FEM_LD_INTERFACE_DATA: The base permanent interface table from which the temporary variant is derived.
• FEM_BALANCES / FEM_BALANCES_LEDGER: Target tables populated after successful validation of the interface rows.
• GL_LEDGERS: Supplies ledger attributes joined via LEDGER_ID.
• GL_PERIODS / GL_CALENDARS: Provide calendar and period context aligned through CALENDAR_ID and CAL_PERIOD.
• FEM_DIMENSION_GROUPS: Referenced through DIMENSION_GROUP_ID and TIME_DIMENSION_GROUP_KEY.

Given the product's obsolete status, implementers should confirm whether the actual environment uses a replacement EPM loader before relying on this interface table in any design or custom extension.