Results for “odm_primary_quantity”

24 results




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

Overview

The table GMI.GMI_DISCRETE_TRANSFER_LOTS is a Process Manufacturing Inventory (GMI) object in Oracle E-Business Suite, present and valid in both 12.1.1 and 12.2.2. It stores the transfer-lot details belonging to transfer lines for inventory movements that cross the boundary between Process (OPM) inventory and Discrete (ODM) inventory. In other words, it records the lot-level information that must be carried across the process-to-discrete or discrete-to-process transfer, so that lot identity, grade, status, and quantity remain traceable on both sides of the handoff.

From a dimensional-modeling perspective, the mined metadata classifies this table heuristically as standalone, meaning it does not resolve to a classic hub, link, or satellite pattern through foreign-key analysis. This classification is a modeling suggestion rather than a definitional statement. Operationally, the table behaves as a child detail table: its primary key is composite, extending the transfer-header/line structure down to a line-detail grain.

Key Information Stored

The row is uniquely identified by the composite primary key GMI_DISCRETE_TRANSFER_LOTS_PK, defined on the three columns TRANSFER_ID, LINE_ID, and LINE_DETAIL_ID. Because this same index is the only documented unique index, there is no distinct surrogate key separate from the business-key candidate; the transfer/line/detail triplet serves as both. These three columns anchor the row to a transfer header, a transfer line, and a specific line detail respectively.

The most significant remaining columns fall into two groups — Process (OPM) lot attributes and Discrete (ODM) lot attributes:

Common Use Cases and Queries

Primary uses are lot traceability, transfer reconciliation, and quantity verification for cross-model inventory movements. A typical reporting query pulls transfer-lot detail for a given transfer or line, filtering out logically deleted rows:

  • Retrieve all lots on a transfer: SELECT * FROM GMI.GMI_DISCRETE_TRANSFER_LOTS WHERE TRANSFER_ID = :p_transfer_id AND NVL(DELETE_MARK,0) = 0;
  • Reconcile OPM versus ODM quantities per line detail: compare OPM_PRIMARY_QUANTITY to ODM_PRIMARY_QUANTITY and flag variances.
  • Expiry/status monitoring: join OPM_LOT_ID and ODM_LOT_NUMBER with OPM_LOT_EXPIRATION_DATE/ODM_LOT_EXPIRATION_DATE to report lots nearing expiry.
  • Grade-based analysis using OPM_GRADE for quality and specification reporting.

Related Objects

The composite key columns imply structural relationships to the transfer header and line objects that carry TRANSFER_ID and LINE_ID; LINE_DETAIL_ID ties the row to the specific transfer line detail. The OPM_LOT_ID column references OPM lot master data, and ODM_LOT_NUMBER correlates to the Discrete lot inventory tables. Because the documented metadata records no enforced foreign keys and classifies the object as standalone, joins to these parent objects should be validated against the customer's specific instance. In practice the principal related objects are the GMI transfer header and transfer line tables, the OPM lot master and lot attribute tables, and the ODM inventory lot tables used to resolve discrete-side lot identity and quantities.