Results for “gmi_discrete_transfers”

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

Overview

GMI_DISCRETE_TRANSFERS is a header-level table owned by the GMI schema within the Oracle E-Business Suite Process Manufacturing Inventory module. It stores the header information for inventory transfers that move material between Process Manufacturing (OPM) organizations and Discrete Manufacturing organizations, supporting the integration of the two inventory models within a single EBS instance. Each row in the table represents one transfer transaction header, identified by a surrogate primary key and qualified by a business key based on organization and transfer number.

Based on the heuristic Data Vault classification mined from the foreign key structure, this table is assessed as standalone, meaning no parent-child FK relationships were identified for it. As a modeling suggestion, this classification implies GMI_DISCRETE_TRANSFERS can be treated as an independent component rather than as a link or satellite in a Data Vault derived model, though line-level detail tables that reference it should be evaluated separately to confirm their relationships.

Key Information Stored

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

• TRANSFER_ID — surrogate primary key defined by GMI_DISCRETE_TRANSFERS_PK; uniquely identifies each transfer header.
• ORGN_CODE, TRANSFER_NUMBER — the business-key candidate enforced by unique index GMI_DISCRETE_TRANSFERS_U1; together they identify the transfer within an organization.
• CO_CODE — company code associated with the transfer.
• TRANSFER_TYPE — indicates the direction or nature of the transfer between process and discrete inventory.
• TRANS_DATE — transaction date of the transfer header.
• COMMENTS — free-text description or notes.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE30 — the standard EBS descriptive flexfield (DFF) columns, available for client-specific extensions.
• TEXT_CODE — additional reference or text token associated with the header.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.
• DELETE_MARK — soft-delete indicator; use this column in queries to exclude logically deleted rows.

Common Use Cases and Queries

Typical reporting needs include locating transfers by organization and date range, auditing transfers that have not yet been completed at line level, and reconciling process-to-discrete inventory movements. Example query patterns:

• Header lookup by business key:

  SELECT transfer_id, orgn_code, transfer_number, transfer_type, trans_date
  FROM   gmi.gmi_discrete_transfers
  WHERE  orgn_code = :orgn_code
  AND    transfer_number = :transfer_number
  AND    delete_mark = 0;

• Transfers in a period:

  SELECT transfer_id, orgn_code, transfer_number, transfer_type, trans_date
  FROM   gmi.gmi_discrete_transfers
  WHERE  trans_date BETWEEN :from_date AND :to_date
  AND    delete_mark = 0
  ORDER BY trans_date, transfer_number;

• Flexfield-based reporting on ATTRIBUTE_CATEGORY and specific ATTRIBUTE columns for client-specific fields.

Related Objects

• GMI_DISCRETE_TRANSFERS_PK / GMI_DISCRETE_TRANSFERS_U1 — unique indexes representing primary and business keys.
• The transfer line/detail table (commonly named GMI_DISCRETE_TRANSFERS_L or an equivalent) is expected to join on TRANSFER_ID; verify the exact name in the target instance.
• Process Manufacturing Inventory and Discrete Inventory transaction tables involved in process-to-discrete moves.
• Organization and company reference tables (ORGN_CODE, CO_CODE).

The metadata identifies the table as VALID in the GMI schema for EBS 12.1.1 and 12.2.2.