Results for “op_frgt_mth”

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

Overview

OP_FRGT_MTH is a reference (lookup) table owned by the GML schema within the Oracle Process Manufacturing Logistics module (GML) of Oracle E-Business Suite 12.1.1 and 12.2.2. It stores freight bill method codes — the user-definable identifiers that determine how freight charges are billed, settled, or accrued against orders, receipts, transfers, and vendor records throughout the OPM supply chain. Because freight billing rules differ between customers, vendors, and internal movements, this table acts as a controlled vocabulary that standardizes freight handling across order, pricing, procurement, and receiving transactions.

From a Data Vault modeling perspective, the mined metadata classifies OP_FRGT_MTH heuristically as a hub. This is consistent with its structure: a stable, unique business key surrounded by descriptive attributes and referenced by numerous transactional tables. Modelers should treat the table as a business key hub with descriptive satellite attributes, while noting that the classification is heuristic and derived from FK topology rather than an explicit design declaration.

Key Information Stored

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

• FRTBILL_MTHD — the freight bill method code, the primary business identifier. It is enforced by unique index OP_FRGT_MTH_PK (and appears as FRTBILL_MTHD).
• OF_FRTBILL_MTHD — an additional identifier column enforced by unique index OP_FRGT_MTH01, which the metadata documents as the table's primary key.
• FRTBILL_DESC — the descriptive name of the freight bill method, used in list-of-values and reports.
• TEXT_CODE — a foreign key into OP_TEXT_HDR, linking the method to extended descriptive text maintained in the text repository.
• DELETE_MARK — the soft-delete flag; rows are logically deactivated rather than physically removed.
• TRANS_CNT — a transaction counter used by OPM concurrency and audit logic.

The remaining audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — record who created and last modified each method code and through which login session.

Common Use Cases and Queries

Freight method codes surface in pricing setup, order entry, and freight reconciliation. Typical validation query:

• SELECT FRTBILL_MTHD, FRTBILL_DESC FROM OP_FRGT_MTH WHERE DELETE_MARK = 0 ORDER BY FRTBILL_MTHD;
• Join to the text repository for the long description: SELECT m.FRTBILL_MTHD, m.FRTBILL_DESC, t.TEXT FROM OP_FRGT_MTH m, OP_TEXT_HDR t WHERE m.TEXT_CODE = t.TEXT_CODE;
• Count usage across order headers to find unused methods: join OP_ORDR_HDR on FRTBILL_MTHD and GROUP BY the method code.

Reconciliation reporting often aggregates freight amounts by method code across PO_RECV_DTL and PO_VEND_MST to validate accruals, while order-to-cash reporting joins OP_ORDR_HDR to display the freight method on customer-facing documents.

Related Objects

OP_FRGT_MTH is referenced by fourteen foreign keys, indicating wide reuse across OPM order, pricing, procurement, and receiving entities:

• OP_TEXT_HDR — referenced by OP_FRGT_MTH.TEXT_CODE for extended text.
• OP_ORDR_HDR / OP_ORDR_DTL — sales order headers and lines carrying FRTBILL_MTHD.
• PO_ORDR_HDR / PO_ORDR_DTL — purchase order headers and lines with the same freight method code.
• PO_RECV_DTL — receiving transactions referencing FRTBILL_MTHD.
• OP_PRCE_ITM — pricing items where freight method influences charge calculation.
• OP_PRSL_HDR / OP_PRSL_DTL — proposal headers and details.
• OP_CUST_MST / OP_CUST_MST_OPM — customer master defaults for freight billing.
• PO_VEND_MST — vendor master freight method default.
• OP_CNTR_DTL and PO_BPOS_HDR / PO_BPOS_DTL — contract details and blanket purchase order headers and lines.

Because these relationships are enforced through FRTBILL_MTHD, changes to method codes should be validated against all dependent tables before deactivation.