Results for “line_item_id”

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

Overview

The FEM_INTG_GL_WRTBK_BAL_GT table is an APPS-owned interface staging object in Oracle EBS 12.1.1 and 12.2.2, registered under the FND – Application Object Library product. Its name follows Oracle's integration naming conventions, indicating that it holds General Ledger write-back balance data bridged into the Enterprise Performance Foundation / Financial Consolidation Hub (FEM) integration layer. Rows are transient in nature: balances are written from a FEM integration process into this table and then consumed or republished into the general ledger or profitability model, typically within a single concurrent program run. The object is therefore best understood as a high-volume, batch-oriented landing table rather than a permanent transaction store.

Applying heuristic Data Vault classification against the mined FK structure, this table shows the profile of a standalone structure rather than a modelled hub, link, or satellite. It carries a single surrogate key column (ROW_ID) and no documented foreign keys to other FEM fact or dimension tables, which suggests it functions as a load buffer whose referential integrity is not enforced at the database layer, but rather by the integration program that populates it.

Key Information Stored

The documented physical schema for 12.1.1 contains 30 columns. The most operationally significant are:

• ROW_ID — surrogate identifier for each staged row; not marked as a primary key in the documented metadata, so uniqueness is generally guaranteed by the loader.
• CODE_COMBINATION_ID — the accounting flexfield combination to which the write-back balance belongs; this is the principal join point back to GL.
• COMPANY_COST_CENTER_ORG_ID — the organization context for the combination, aligning FEM balances with the accounting entity structure.
• CURRENCY_CODE and CURRENCY_TYPE_CODE — the transaction and currency-basis indicators used to separate entered, converted, and reporting balances.
• PTD_DEBIT_BALANCE_E and PTD_CREDIT_BALANCE_E — the period-to-date debit and credit amounts being written back; these are the core measures of the table.
• ACTIVITY_ID, COST_OBJECT_ID, FINANCIAL_ELEM_ID, PRODUCT_ID, NATURAL_ACCOUNT_ID, CHANNEL_ID, LINE_ITEM_ID — dimension foreign-key style references to the FEM profitability model.
• PROJECT_ID, CUSTOMER_ID, ENTITY_ID, INTERCOMPANY_ID, TASK_ID — GL segment references carried through for reconciliation and drill-down.
• USER_DIM1_ID through USER_DIM10_ID — ten configurable user-defined dimension slots, allowing customer-specific extensions without schema change.
• VS_MAPPED_FLAG — indicates whether the row has been mapped through a value-set or validation mapping, supporting exception reporting.

Common Use Cases and Queries

Typical usage centres on balancing, mapping validation, and reconciliation of FEM write-back results before they are committed to GL. A common pattern confirms that all staged rows have been successfully mapped:

• Aggregating PTD debits and credits by CODE_COMBINATION_ID and CURRENCY_CODE to verify that the write-back equals the FEM source balance.
• Filtering on VS_MAPPED_FLAG to report unmapped combinations that must be corrected before posting.
• Joining to FND_DM_PRODUCTS on PRODUCT_ID to obtain product descriptions for profitability and margin reporting.
• Grouping by the user dimensions to trace balances that are driven by custom dimension membership rather than standard GL segments.

Because the table is a staging area, queries should be scoped to a specific run or truncation cycle; historical retention is not guaranteed.

Related Objects

• FND_DM_PRODUCTS — referenced by FEM_INTG_GL_WRTBK_BAL_GT.PRODUCT_ID.
• CS_SYSTEMS_ALL_B_TEMP — referenced by FEM_INTG_GL_WRTBK_BAL_GT.ROW_ID.
• GL_CODE_COMBINATIONS — join target for CODE_COMBINATION_ID to resolve the accounting flexfield.
• GL_JE_HEADERS / GL_JE_LINES — the eventual destination of the write-back balances.
• The FEM integration concurrent programs that populate and drain this table, which enforce the referential rules that the schema itself does not.