Search Results gmf_transaction_valuation_u1

Overview

GMF.GMF_TRANSACTION_VALUATION is a transaction valuation table owned by the GMF (Process Manufacturing) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the cost and accounting valuation details generated for process manufacturing inventory transactions, providing the bridge between inventory movement records and the Subledger Accounting (SLA) engine that produces journal entries. Because process organizations value transactions differently from discrete organizations — factoring in resources, lots, and cost types specific to a ledger — this table captures the raw and computed base values that feed the accounting pre-processor and the SLA extraction process.

From a Data Vault modeling perspective, the metadata heuristic classifies this object as standalone. In practical terms, it functions most like a satellite attached to inventory transaction and accounting event hubs, since it records descriptive valuation context (cost type, ledger, amounts, posting status) keyed by the unique VALUATION_ID. It references FV_LEGAL_ENTITIES and MTL_TXN_SOURCE_TYPES as lookup dependencies rather than owning hub relationships, which reinforces the satellite interpretation.

Key Information Stored

The table contains 46 documented columns. The most significant are:

• VALUATION_ID — the surrogate primary key and the sole column in the unique index GMF_TRANSACTION_VALUATION_U1; the definitive business-key candidate for row identification.
• HEADER_ID and EVENT_ID — the SLA Extract header identifier and SLA Accounting event identifier, linking the valuation to the subledger accounting event.
• LEDGER_ID, LEGAL_ENTITY_ID, and LEDGER_CURRENCY — the accounting ledger, legal entity, and currency context, with LEGAL_ENTITY_ID forming a foreign key to FV_LEGAL_ENTITIES.
• VALUATION_COST_TYPE and VALUATION_COST_TYPE_ID — the cost type applied to valuations within the ledger.
• TRANSACTION_SOURCE, TRANSACTION_ID, TRANSACTION_SOURCE_TYPE, and TRANSACTION_SOURCE_TYPE_ID — the source of the underlying transaction, with TRANSACTION_SOURCE_TYPE_ID referencing MTL_TXN_SOURCE_TYPES.
• ORG_ID and ORGANIZATION_ID — the operating unit and inventory organization identifiers.
• INVENTORY_ITEM_ID, ITEM_NUMBER, LOT_NUMBER, SUBINVENTORY_CODE, and RESOURCES — the item, lot, subinventory, and resource context of the valuation.
• TXN_BASE_VALUE_RAW and TXN_BASE_VALUE — the raw and finalized transaction base values that drive accounting amounts.
• FINAL_POSTING_DATE and ACCOUNTED_FLAG — the posting date and status indicator used to determine whether the valuation has been accounted.
• TRANSACTION_DATE — the date of the underlying transaction, supporting period-based reporting.

Common Use Cases and Queries

Typical scenarios include reconciling inventory transactions to their subledger journal entries, auditing posting status, and reporting transaction values by cost type, organization, or item. The non-unique indexes GMF_TRANSACTION_VALUATION_N2 (FINAL_POSTING_DATE), N3 (ACCOUNTED_FLAG), and N4 (TRANSACTION_SOURCE, TRANSACTION_ID) directly support period-based reconciliation, unaccounted-transaction identification, and source-transaction lookups.

For example, to find unaccounted valuations for a posting period:

SELECT v.valuation_id, v.transaction_source, v.transaction_id,
       v.txn_base_value, v.ledger_currency
  FROM gmf.gmf_transaction_valuation v
 WHERE v.accounted_flag = 'N'
   AND v.final_posting_date BETWEEN :p_start AND :p_end;

To aggregate posted value by organization and cost type:

SELECT v.organization_id, v.valuation_cost_type,
       SUM(v.txn_base_value) total_value
  FROM gmf.gmf_transaction_valuation v
 WHERE v.accounted_flag = 'Y'
 GROUP BY v.organization_id, v.valuation_cost_type;

Related Objects

• FV_LEGAL_ENTITIES — joined on GMF_TRANSACTION_VALUATION.LEGAL_ENTITY_ID = FV_LEGAL_ENTITIES.LEGAL_ENTITY_ID to resolve legal entity details.
• MTL_TXN_SOURCE_TYPES — joined on TRANSACTION_SOURCE_TYPE_ID to resolve the transaction source type name.
• GL_LEDGERS — logically joined on LEDGER_ID for ledger and currency context (not a documented FK, but implied by LEDGER_ID / LEDGER_CURRENCY).
• XLA_EVENTS — referenced via EVENT_ID for the subledger accounting event.
• MTL_TRANSACTIONS / MTL_MATERIAL_TRANSACTIONS — the underlying inventory transactions matched on TRANSACTION_ID and TRANSACTION_SOURCE.
• GMF_COST_TYPES — the cost type referenced through VALUATION_COST_TYPE_ID.
• SLA extract process tables (Header/Extract) referenced via HEADER_ID.