Search Results mtl_service_contracts_v

Overview

MTL_SERVICE_CONTRACTS_V is a read-only view owned by the APPS schema within the Oracle E-Business Suite Inventory (INV) product family. It exposes a filtered list of service contracts drawn from the Oracle Contracts (OKC) module, specifically those contracts that are currently active and carry a contract classification of "SERVICE". The view is documented as VALID in ETRM for releases 12.1.1 and 12.2.2 and serves as a lightweight integration and reporting surface for downstream Inventory, Service, and Depot Repair processes that require visibility to valid service agreements without querying the full OKC contract model directly.

Because the view joins header data to status data and applies both status and date predicates internally, it presents only contracts that are in force as of the current system date (SYSDATE). This makes it useful as a pre-filtered source in lookups, concurrent programs, and DFF/Value Set definitions where a caller needs to reference a live service contract number rather than the full contract population. Note that no Inventory-specific columns are projected; the view returns contract header attributes only, so its INV membership reflects consumption by Inventory-adjacent flows rather than any dependency on MTL tables.

Underlying Base Objects

The documented view text joins two base objects through their APPS synonyms:

• OKC_K_HEADERS_ALL_B (aliased CONTRACTS) — the contracts header table that supplies ID, CONTRACT_NUMBER, OBJECT_VERSION_NUMBER, AUTHORING_ORG_ID, STS_CODE, SCS_CODE, START_DATE, and END_DATE.
• OKC_STATUSES_B (aliased STATUSES) — the contract status codes table, joined on STATUSES.CODE = CONTRACTS.STS_CODE.

The join is an implicit equi-join in the WHERE clause rather than an ANSI JOIN, and the filters are hard-coded: STATUSES.STE_CODE = 'ACTIVE' (the status is of the "active" status type), CONTRACTS.SCS_CODE = 'SERVICE' (the contract class is Service), and SYSDATE BETWEEN CONTRACTS.START_DATE AND CONTRACTS.END_DATE (the contract is currently effective). Because OKC_STATUSES_B is a base (non-translated) table, the view does not join _TL tables and therefore does not return status descriptions.

Key Columns

• ID — The contract header identifier (OKC_K_HEADERS_ALL_B.ID). This is the primary key value that foreign keys in related OKC line, party, and article tables reference.
• CONTRACT_NUMBER — The user-visible contract number, typically the value displayed to end users and used as the searchable key.
• OBJECT_VERSION_NUMBER — The row version column used by the OKC framework for optimistic locking and change detection. Exposed here for informational and integration purposes only.
• AUTHORING_ORG_ID — The operating unit / authoring organization that owns the contract. Callers running multi-org aware queries must include this column in the WHERE clause to respect MOAC security.

Common Use Cases and Queries

The view is most commonly used to populate value sets, LOVs, and reference fields that must present only currently effective service contracts. A typical query retrieving a contract by number is shown below.

• Simple retrieval: SELECT contract_number, id, authoring_org_id FROM apps.mtl_service_contracts_v WHERE contract_number = :p_contract_number;
• MOAC-safe listing: SELECT contract_number FROM apps.mtl_service_contracts_v WHERE authoring_org_id = :p_org_id ORDER BY contract_number;
• Join to contract lines: SELECT v.contract_number, l.line_number FROM apps.mtl_service_contracts_v v, apps.okc_k_lines_b l WHERE l.chr_id = v.id;
• Count of active service contracts per org: SELECT authoring_org_id, COUNT(*) FROM apps.mtl_service_contracts_v GROUP BY authoring_org_id;

Consultants should remember that the SYSDATE predicate is evaluated at query time, so results change automatically when a contract's start or end date passes. Contracts in draft, terminated, or non-SERVICE classes are excluded and must be queried from OKC_K_HEADERS_ALL_B directly.