Results for “date_strategy_executed”

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

Overview

OKL_AM_ASSET_TRACK_UV is a denormalized reporting and integration view owned by the APPS schema within the Oracle Lease and Finance Management (OKL) module. It consolidates asset-tracking information across lease contracts, contract portfolios, and portfolio lines, presenting a single row for each asset-tracking line associated with a contract. In Oracle EBS 12.1.1 and 12.2.2, this view serves as a convenient read interface for extracting contract identifiers, contract dates (including the CONTRACT_END_DATE column that users frequently search on), transaction status, asset-tracking strategy, budget amounts, and execution dates without requiring direct joins across the underlying transactional tables.

The view is defined with status VALID and is typically used for operational reporting, ad hoc queries, and dashboard or extract development where a flattened, human-readable representation of asset-tracking activity is required.

Underlying Base Objects

The view is defined over several documented base objects joined through their key relationships. The documented referenced objects include FND_GLOBAL (PACKAGE), FND_LOOKUPS (VIEW), OKC_STATUSES_V (VIEW), OKC_UTIL (PACKAGE), OKL_AM_PORTFOLIO_TEAMS_UV (VIEW), OKL_K_HEADERS_FULL_V (VIEW), OKL_PRTFL_CNTRCTS_V (VIEW), and OKL_PRTFL_LINES_V (VIEW).

• OKL_K_HEADERS_FULL_V (KHR) — the contract header source, supplying CONTRACT_NUMBER, START_DATE, END_DATE, DESCRIPTION, and STS_CODE.
• OKL_PRTFL_CNTRCTS_V (PFC) — the portfolio-contract association, joined on KHR_ID.
• OKL_PRTFL_LINES_V (PFL) — the portfolio line carrying asset-tracking strategy, status, budget, and execution information, joined on PFC_ID.
• OKC_STATUSES_V (OKS) — the contract status meaning, joined on STS_CODE.
• OKL_AM_PORTFOLIO_TEAMS_UV (JTV) — resolves the assignment group display name, joined on TMB_ID.
• FND_LOOKUPS (FND1, FND2) — lookup meanings for transaction status (OKL_TRANSACTION_STATUS) and asset-tracking strategies (OKL_ASSET_TRACK_STRATEGIES).

OKC_UTIL and FND_GLOBAL are referenced supporting packages used within the OKL and Oracle Contracts infrastructure.

Key Columns

• CONTRACT_NUMBER / CONTRACT_START_DATE / CONTRACT_END_DATE — contract identifier and its validity window; CONTRACT_END_DATE is a common filter for expiry or renewal analysis.
• ID / KHR_ID / PFC_ID / PFL_ID — surrogate identifiers linking back to headers, portfolio contracts, and portfolio lines.
• STS_CODE / CONTRACT_STATUS — coded contract status and its translated meaning.
• TRX_STATUS_CODE / TRANSACTION_STATUS — asset-tracking transaction state and its lookup meaning.
• ASSET_TRACK_STRATEGY_CODE / STRATEGY_DESCRIPTION — the strategy driving the tracking action and its descriptive text.
• DATE_STRATEGY_EXECUTION_DUE / DATE_STRATEGY_EXECUTED — scheduled versus actual execution dates for the strategy.
• BUDGET_AMOUNT, COMMENTS, TMB_ID, FMA_ID, ASSINGMENT_GROUP, OBJECT_VERSION_NUMBER — financial, descriptive, team/assignment, and concurrency metadata.

The column name ASSINGMENT_GROUP is a documented spelling variant preserved in the view definition.

Common Use Cases and Queries

Typical usage includes identifying contracts approaching expiry, reconciling strategy execution against due dates, and reporting asset-tracking activity by assignment group. A representative query filters on the searched column:

• SELECT contract_number, contract_end_date, transaction_status, strategy_description FROM apps.okl_am_asset_track_uv WHERE contract_end_date BETWEEN :p_from AND :p_to;
• SELECT contract_number, asset_track_strategy_code, date_strategy_execution_due, date_strategy_executed FROM apps.okl_am_asset_track_uv WHERE date_strategy_executed IS NULL AND date_strategy_execution_due < SYSDATE;
• SELECT assingment_group, COUNT(*) FROM apps.okl_am_asset_track_uv GROUP BY assingment_group;

Because the view is a non-materialized definition, query performance depends on the predicates pushed to the underlying OKL views; filtering by contract number, contract end date, or status code is recommended to constrain result sets.