Results for “okx_usage”

46 results




Overview
Explore in AI Chat

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

Overview

APPS.MTL_AGREEMENT_DETAILS_V is a reporting and integration view in Oracle E-Business Suite that exposes the intersection of inventory item master data and Oracle Contracts (OKC) service agreement records. It is defined specifically for the OKX_USAGE object type, the Operational Key/Contract item classification used to bind inventory items to usage-based or service-level contract lines. The view presents a denormalized result set combining contract headers, contract lines, contract items, inventory item descriptions, and client parameters, allowing consumers to resolve which service agreement governs a given inventory item at a given organization.

The column naming in the view (for example CONTRACT_NUMBER, SEGMENT1, SERVICE_LINE_START_DATE) indicates the view is intended for external reporting, extracts, or downstream integrations rather than for transactional form logic. It is owned by APPS, meaning it is available to any concurrent program, report, or interface running with APPS privileges. The view does not perform any filtering by operating unit, ledger, or date, so consumers must apply their own predicates for multi-org or date-effective restrictions.

Underlying Base Objects

The view is defined over five documented base objects, joined entirely by inner joins:

Because every join is an equi-join with no outer clauses, any item or contract line missing a valid counterpart is excluded from the results. This makes the view a reliable source of fully resolved usage agreements, but a poor source for identifying orphaned or incomplete contracts.

Key Columns

  • CONTRACT_NUMBER — the contract header number from OKC_K_HEADERS_ALL_B, the primary business identifier of the agreement.
  • CLIENT_CODE, CLIENT_ID, CLIENT_NUMBER — client parameter identifiers from MTL_CLIENT_PARAMETERS, matching the contract customer account.
  • SEGMENT1 — the concatenated item flexfield segments from MTL_SYSTEM_ITEMS_B_KFV, the human-readable item description.
  • PRIMARY_UOM_CODE — the primary unit of measure for the item.
  • SERVICE_LINE_START_DATE and SERVICE_LINE_END_DATE — the effective window of the contract line, sourced from OKC_K_LINES_B.START_DATE and END_DATE.
  • INVENTORY_ITEM_ID — the internal inventory item key, used for joins to other inventory or transaction tables.
  • CLE_ID — the contract line item identifier from OKC_K_ITEMS.
  • DNZ_CHR_ID — the contract header identifier associated with the line item.
  • CUST_ACCT_ID — the customer account on the contract line.
  • ID — the contract header primary key from OKC_K_HEADERS_ALL_B.

Common Use Cases and Queries

The view is most commonly queried to determine which service agreement covers a specific item, to validate that a contract line is active within a date range, or to feed an interface that must reconcile inventory items to contracts. A typical query resolving all usage agreements for a single item follows:

SELECT contract_number, segment1, service_line_start_date, service_line_end_date, client_code FROM apps.mtl_agreement_details_v WHERE inventory_item_id = :p_item_id ORDER BY service_line_start_date;

For reporting agreements active as of a reporting date, the service line date columns are filtered directly:

SELECT contract_number, segment1, primary_uom_code, client_number FROM apps.mtl_agreement_details_v WHERE TRUNC(SYSDATE) BETWEEN service_line_start_date AND service_line_end_date;

For integration extracts keyed by client, the client parameter columns provide the join point:

SELECT client_id, contract_number, inventory_item_id, cle_id, dnz_chr_id FROM apps.mtl_agreement_details_v WHERE client_code = :p_client_code;

Because the view performs no organization filtering beyond the join condition on OBJECT1_ID2, callers should always constrain by organization or item identifier where multi-org data is present, and should bound results by date to avoid retrieving expired service lines.