Results for “no_trans”

33 results




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

Overview

IC_ADJS_JNL is the inventory adjustment detail table within the GMI (Process Manufacturing Inventory) product family in Oracle EBS 12.1.1 and 12.2.2. It resides in the GMI schema and stores the individual line-level detail of inventory adjustment transactions processed by the Process Manufacturing inventory engine. Where the journal header table (IC_JRNL_MST) captures the transaction envelope, IC_ADJS_JNL records each adjustment line with its item, lot, warehouse, quantity, unit of measure, and quality attributes. The table therefore serves as the authoritative source for historical inventory adjustment activity and is central to reconciliation, audit, and valuation reporting.

Based on the foreign key topology documented in the ETRM metadata, IC_ADJS_JNL is best characterized as a link in Data Vault modeling terms: it resolves relationships among items, lots, warehouses, journals, organizations, and reason codes rather than behaving as a standalone hub or a pure descriptive satellite. This is a heuristic classification derived from the FK structure and should be treated as a modeling suggestion rather than a normative statement.

Key Information Stored

The primary key IC_ADJS_JNL_PK is a composite business key composed of TRANS_TYPE, TRANS_FLAG, DOC_ID, and DOC_LINE. This combination uniquely identifies each adjustment line. TRANS_TYPE and TRANS_FLAG distinguish the adjustment transaction category, DOC_ID identifies the source document, and DOC_LINE provides the line sequence within that document.

The most significant columns include:

Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, PROGRAM_APPLICATION_ID, PROGRAM_ID, REQUEST_ID) support traceability back to the originating concurrent program request.

Common Use Cases and Queries

Typical reporting scenarios include adjustment history by item, lot, or warehouse; variance analysis by reason code; and reconciliation of posted adjustments against the general ledger. A representative query pattern joins the detail to its journal header and item master:

  • SELECT a.DOC_ID, a.DOC_LINE, a.ITEM_ID, a.LOT_ID, a.WHSE_CODE, a.QTY, a.REASON_CODE, a.DOC_DATE FROM GMI.IC_ADJS_JNL a WHERE a.JOURNAL_ID = :journal_id ORDER BY a.DOC_LINE;
  • Adjustment volume by reason: aggregate QTY grouped by REASON_CODE and DOC_DATE range, joined to SY_REAS_CDS for descriptions.
  • Lot-level audit: join to IC_LOTS_MST on ITEM_ID and LOT_ID to trace an adjustment back to its receiving or production lineage.
  • Accounting reconciliation: join ACCTG_UNIT_ID to GL_ACCU_MST and compare adjustment quantities to downstream GL entries.

Because the primary key is composite, joins to header tables should be driven through JOURNAL_ID, and care should be taken to filter on COMPLETED_IND where only finalized adjustments are required.

Related Objects

The most significant related objects, based on the documented foreign key relationships, are:

  • IC_JRNL_MST (via JOURNAL_ID) — the journal header providing the transaction envelope.
  • IC_ITEM_MST_B and IC_ITEM_MST (via ITEM_ID) — item definitions.
  • IC_LOTS_MST (via ITEM_ID and LOT_ID) — lot master data.
  • IC_LOTS_STS (via LOT_STATUS) — lot status codes.
  • IC_WHSE_MST (via WHSE_CODE) — warehouse definitions.
  • SY_ORGN_MST_B and SY_ORGN_MST (via CO_CODE and ORGN_CODE) — organization and company context.
  • SY_REAS_CDS_B and SY_REAS_CDS (via REASON_CODE) — adjustment reason codes.
  • SY_UOMS_MST (via ITEM_UM and ITEM_UM2) — unit of measure definitions.
  • SY_DOCS_MST (via TRANS_TYPE) — document type definitions.
  • GMD_GRADES_B and QC_GRAD_MST (via QC_GRADE) — quality grade master data.
  • GL_ACCU_MST (via ACCTG_UNIT_ID) — accounting unit master supporting financial integration.