Results for “op_term_mst”

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

Overview

OP_TERM_MST is the payment terms master table within the Process Manufacturing Logistics (GML) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the payment terms codes used to define the discount, due-date, and settlement conditions applied to orders, proposals, customers, vendors, and business processes managed by the Oracle Process Manufacturing (OPM) applications. Because it is owned by the GML schema and serves as the authoritative source of payment terms definitions, it functions as a shared reference table consumed by both the order management and procurement flows within process manufacturing.

From a Data Vault modeling perspective, the metadata classifies OP_TERM_MST heuristically as a hub. This classification reflects the table's central role: it holds the enduring business keys (terms codes) that downstream transactional and master tables reference through foreign keys, making it a natural anchor for a hub entity in a dimensional or Data Vault representation.

Key Information Stored

The table contains 19 documented columns. The most significant for functional and integration purposes are:

• TERMS_CODE — the primary business identifier for a payment terms definition, and the column targeted by the OP_TERM_MST_PK unique index.
• OF_TERMS_CODE — a secondary business-key candidate, enforced by the OP_TERM_MST01 unique index, commonly used for cross-referencing Oracle Financials or legacy terms codes.
• TERMS_DESC — the descriptive name of the payment terms, used in list-of-values displays and reports.
• DISCOUNT_RATE — the discount percentage granted if payment is made within the discount window.
• DISCOUNT_DAYS — the number of days within which payment must be received to qualify for the discount.
• NET_DAYS — the number of days from invoice date until the net amount becomes due.
• RA_TERMS_CODE — a terms code link typically associated with Receivables-style terms mapping.
• TEXT_CODE — a foreign key to OP_TEXT_HDR, allowing free-form terms text or legal wording to be attached.
• DELETE_MARK — the logical deletion flag; records with a non-zero value should be excluded from active lookups.
• TRANS_CNT — a concurrency/transaction counter used by OPM forms for optimistic locking.
• CREATION_DATE, LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit and WHO columns.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — concurrent program context columns identifying the process that last touched the record.

Two unique indexes are documented: OP_TERM_MST01 on OF_TERMS_CODE and OP_TERM_MST_PK on TERMS_CODE. The distinction between the surrogate-style key (OP_TERM_MST01) and the business-key candidate (OP_TERM_MST_PK) matters when designing joins and entity resolution logic.

Common Use Cases and Queries

Typical use cases center on resolving a terms code into its discount and net-due parameters at the time an order, proposal, or vendor record is processed or reported. A common query pattern joins a transactional table to OP_TERM_MST on TERMS_CODE to retrieve discount and due-date attributes:

• Listing active payment terms for a value set or LOV: SELECT TERMS_CODE, TERMS_DESC FROM GML.OP_TERM_MST WHERE NVL(DELETE_MARK,0) = 0 ORDER BY TERMS_DESC;
• Resolving terms for order headers: SELECT h.ORDER_NO, t.TERMS_DESC, t.DISCOUNT_RATE, t.DISCOUNT_DAYS, t.NET_DAYS FROM GML.OP_ORDR_HDR h, GML.OP_TERM_MST t WHERE h.TERMS_CODE = t.TERMS_CODE;
• Identifying vendors or customers assigned to a given terms definition using PO_VEND_MST or OP_CUST_MST.
• Auditing which concurrent program loaded or last modified a terms definition via PROGRAM_ID and REQUEST_ID.
• Extracting terms reference data for a data warehouse hub load, keyed on TERMS_CODE or OF_TERMS_CODE.

Related Objects

OP_TERM_MST is referenced by a broad set of order, proposal, customer, vendor, and business-process tables. The most significant include:

• OP_ORDR_HDR and OP_ORDR_DTL — join on TERMS_CODE to inherit payment terms on sales/order headers and lines.
• OP_PRSL_HDR and OP_PRSL_DTL — proposal headers and lines referencing terms via TERMS_CODE.
• OP_CUST_MST and OP_CUST_MST_OPM — customer master records whose default terms are defined by TERMS_CODE.
• PO_VEND_MST — vendor master, linking vendors to their default payment terms.
• PO_ORDR_HDR and PO_ORDR_DTL — purchase order headers and lines applying the terms code.
• PO_BPOS_HDR and PO_BPOS_DTL — business process order headers and details referencing terms.
• OP_TEXT_HDR — referenced by OP_TERM_MST.TEXT_CODE to supply descriptive or legal text associated with a terms definition.

These relationships confirm OP_TERM_MST as a central reference hub whose business keys propagate throughout the OPM order-to-cash and procure-to-pay flows.