Results for “base_contract_amount”

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

Overview

OKI_YOY_RENEWAL_AMT_V is a reporting view owned by the APPS schema within the Oracle Contracts Intelligence (OKI) product family. It is documented as VALID and is designed to expose information about the value of renewed contracts on a historical, year-over-year (YOY) basis. Contracts Intelligence provides analytical insight into contract portfolios, including renewal behaviour, and this view supplies the amount-oriented subset of that analysis. The view presents a period-oriented, organization-aware projection of renewal value, allowing reporting tools and downstream integrations to trend the base contract amount of renewed agreements across periods without querying the underlying staging or summary table directly. Because it is a simple projection view — exposed as APPS.OKI_YOY_RENEWAL_AMT_V and visible in ETRM for both 12.1.1 and 12.2.2 — it participates in the same security and synonym conventions as other APPS-owned Contracts Intelligence objects, meaning consumers typically reference it through the APPS synonym or an APPS-backed custom report.

Underlying Base Objects

The ETRM metadata documents no referenced base objects for this view beyond the fact that the view text selects from OKI_YOY_RENEWAL_AMT. It is therefore a thin projection: the view definition aliases the base table as YOY and selects every column it exposes directly from that table, with no joins, aggregations, or filters in the view text itself. All filtering, grouping, and period comparison logic is expected to be applied by the consuming report or query. The base table OKI_YOY_RENEWAL_AMT carries the concurrent program bookkeeping columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE), which indicates that it is populated by a concurrent program — typically a Contracts Intelligence data collection or summarization routine. The view inherits that populate/refresh behaviour and should be treated as a read-only reporting surface that reflects the most recent successful program run.

Key Columns

• ID — Primary identifier of the renewal amount record.
• PERIOD_NAME, PERIOD_SET_NAME, PERIOD_TYPE — Accounting period context for the renewal value, consistent with the EBS accounting calendar model.
• AUTHORING_ORG_ID / AUTHORING_ORG_NAME — The operating unit or authoring organization that owns the renewed contract; enables organization-level reporting.
• YEAR and MONTH — Explicit year and month attributes supporting year-over-year comparison without relying solely on period name parsing.
• SCS_CODE — Contracts Intelligence classification/concept code used to segment renewal values.
• BASE_CONTRACT_AMOUNT — The monetary value of the renewed base contract, the principal measure the view is intended to report.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program audit columns identifying the run that produced the row and when it was last updated.

Common Use Cases and Queries

Typical uses include year-over-year renewal value trend reports, organization-level renewal dashboards, and feeds into custom analytics or data warehouse extracts. Because the audit columns are exposed, reports can also validate data currency by checking PROGRAM_UPDATE_DATE.

Sample query returning renewal value by year and organization:

• SELECT year, authoring_org_name, scs_code, SUM(base_contract_amount) renewal_amt FROM oki_yoy_renewal_amt_v WHERE period_type = 'MONTH' GROUP BY year, authoring_org_name, scs_code ORDER BY year, authoring_org_name;

Sample query isolating the latest concurrent program run for a given organization:

• SELECT id, period_name, year, month, base_contract_amount FROM oki_yoy_renewal_amt_v WHERE authoring_org_id = :org_id AND program_update_date = (SELECT MAX(program_update_date) FROM oki_yoy_renewal_amt_v WHERE authoring_org_id = :org_id);

Both patterns rely on the view remaining a direct projection of OKI_YOY_RENEWAL_AMT, so any future change to the underlying table's population program should be reviewed before these queries are relied upon for period-close reporting.