Results for “applied_ind”

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

Overview

GMF_XLA_LOTCOST_ADJS_V is an APPS-owned view in Oracle E-Business Suite Process Manufacturing Financials (GMF). It exposes Subledger Accounting (SLA) Accounting Data Repository (ADR) source data originating from lot cost adjustments. The view is a reporting and integration artifact: it joins subledger extraction header records to the underlying lot cost adjustment transactions, then decorates those rows with descriptive attributes drawn from inventory and legal entity reference data. The event class filter restricts the result set to LOTCOSTADJ, so every row returned represents a lot cost adjustment event eligible for SLA processing and eventual transfer to the General Ledger.

Because the view is keyed off GMF_XLA_EXTRACT_HEADERS, it is typically consumed by SLA transaction and accounting programs, reconciliation reports, and custom reporting queries that need to determine whether a given lot cost adjustment has been applied and posted to the general ledger.

Underlying Base Objects

The view is defined over five documented base objects:

• GMF_XLA_EXTRACT_HEADERS (synonym) — alias EH, supplies the SLA extraction header context: reference number, ledger, transaction, event class, operating unit, quantities, source document identifiers, and valuation cost type.
• GMF_LOT_COST_ADJUSTMENTS (synonym) — alias LCA, the transaction source table holding adjustment identifiers, dates, lot number, inventory item, legal entity, organization, reason code, and the APPLIED_IND and GL_POSTED_IND status flags.
• MTL_SYSTEM_ITEMS_B_KFV (view) — alias MSI, the key flexfield concatenated view supplying item number, description, and primary/secondary UOM codes.
• MTL_PARAMETERS (synonym) — alias MP, resolves the organization code for the adjustment’s inventory organization.
• XLE_ENTITY_PROFILES (synonym) — alias LE, provides the legal entity name.

Joins predicate on legal entity, transaction/adjustment ID, source document and line, inventory item, and organization, ensuring a single consolidated row per matching lot cost adjustment event.

Key Columns

• REFERENCE_NO, TRANSACTION_ID, EVENT_CLASS_CODE, OPERATING_UNIT — SLA extraction identification and event classification.
• LEDGER_ID — ledger associated with the extracted event.
• ADJUSTMENT_ID, ADJUSTMENT_DATE, REASON_CODE — the lot cost adjustment transaction identity and reason.
• PRIMARY_QUANTITY, PRIMARY_UOM_CODE, SECONDARY_UOM_CODE, TRANSACTION_UOM — quantity expressed as transaction quantity concatenated with the primary UOM, plus the associated unit-of-measure codes.
• SOURCE_DOCUMENT_ID, SOURCE_LINE_ID — originating document references.
• LOT_NUMBER, INVENTORY_ITEM_ID, ITEM_NUMBER, ITEM_DESCRIPTION — lot and item identification, with the item number resolved from the concatenated segments view.
• LEGAL_ENTITY_ID, LEGAL_ENTITY_NAME, ORGANIZATION_ID, ORGANIZATION_CODE — legal entity and inventory organization context.
• VALUATION_COST_TYPE_ID, VALUATION_COST_TYPE — costing valuation classification.
• APPLIED_IND — decoded via DECODE(LCA.APPLIED_IND,'Y','APPLIED','NOT APPLIED').
• GL_POSTED_IND — decoded via DECODE(LCA.GL_POSTED_IND,1,'POSTED TO GL','NOT POSTED TO GL'). This is the column most commonly searched by users, since it answers whether the adjustment has been transferred to the General Ledger.

Common Use Cases and Queries

Typical uses include reconciling lot cost adjustments against SLA events, identifying adjustments not yet transferred to GL, and diagnosing postings for a specific ledger, legal entity, or organization.

To list adjustments awaiting GL transfer:

SELECT ADJUSTMENT_ID, LOT_NUMBER, ITEM_NUMBER, ORGANIZATION_CODE,
       ADJUSTMENT_DATE, APPLIED_IND, GL_POSTED_IND
  FROM APPS.GMF_XLA_LOTCOST_ADJS_V
 WHERE GL_POSTED_IND = 'NOT POSTED TO GL';

To summarize posting status by ledger and legal entity:

SELECT LEDGER_ID, LEGAL_ENTITY_NAME, GL_POSTED_IND, COUNT(*)
  FROM APPS.GMF_XLA_LOTCOST_ADJS_V
 GROUP BY LEDGER_ID, LEGAL_ENTITY_NAME, GL_POSTED_IND;

To inspect adjustments for a specific item and lot:

SELECT ADJUSTMENT_ID, ADJUSTMENT_DATE, REASON_CODE, PRIMARY_QUANTITY,
       VALUATION_COST_TYPE, GL_POSTED_IND
  FROM APPS.GMF_XLA_LOTCOST_ADJS_V
 WHERE INVENTORY_ITEM_ID = :item_id
   AND LOT_NUMBER = :lot_number;

Because the view already joins inventory and legal entity descriptors, it is well suited to ad hoc reporting without additional lookup joins. Access is governed by APPS schema privileges and underlying SLA and GMF security.