Search Results age_group4

Overview

The OKI_RENEWAL_AGING_V view is a reporting object within the Oracle E-Business Suite Contracts Intelligence (OKI) module. It is owned by the APPS schema and holds valid status in both Oracle EBS 12.1.1 and 12.2.2 environments. The view is a pass-through or "synonym-style" view that exposes all columns from the underlying OKI_RENEWAL_AGING table without any filtering, joining, or transformation logic. Its explicit business purpose, as documented in the ETRM metadata, is to hold values for the aging of renewals by time period.

The view is designed to support aging analysis of contract renewals, categorizing renewal activity across multiple discrete aging buckets. These buckets are represented by the AGE_GROUP1 through AGE_GROUP4 columns, which allow users and reports to classify renewals by how far they fall into the future or past relative to a given accounting or calendar period. Within the Contracts Intelligence module, this view serves as the reporting and integration layer through which downstream analytics, dashboards, and custom reports consume renewal aging data without querying the base table directly.

Underlying Base Objects

The view is defined over the single base object OKI_RENEWAL_AGING. The defining query is a straightforward projection:

• SELECT from OKI_RENEWAL_AGING ORA (aliased as ORA)
• All 17 documented columns are selected explicitly
• No WHERE, GROUP BY, JOIN, or function-based transformations are applied

This structure indicates that OKI_RENEWAL_AGING is populated by a concurrent program or load process that computes aging values, and the view exists primarily as a stable, named access point for that data. The presence of REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE columns confirms the base table is populated by a concurrent manager request, allowing consumers to trace the run that produced each set of aging records. The view adds no derived columns and preserves the one-to-one row relationship with the base table.

Key Columns

• ID: Primary identifier for each aging record.
• PERIOD_NAME, PERIOD_SET_NAME, PERIOD_TYPE: Define the accounting period context against which aging is calculated, consistent with the GL period model.
• AUTHORING_ORG_ID / AUTHORING_ORG_NAME: The operating unit or organization that authored the renewal, enabling organizational filtering and reporting.
• CUSTOMER_PARTY_ID / CUSTOMER_NAME: The customer associated with the renewal, supporting customer-level aging analysis.
• SCS_CODE: A Contracts Intelligence service or classification code used to segment renewal records.
• AGE_GROUP1, AGE_GROUP2, AGE_GROUP3, AGE_GROUP4: The core aging metrics. Each column represents a defined aging bucket (for example, days or periods) into which renewal values are grouped, permitting stacked or comparative aging reports.
• REQUEST_ID: Identifies the concurrent request that generated the record.
• PROGRAM_APPLICATION_ID, PROGRAM_ID: Identify the concurrent program and its application.
• PROGRAM_UPDATE_DATE: Timestamp of the program update.

Common Use Cases and Queries

The most common use case is aging analysis of renewal pipelines, typically filtered by period, organization, or customer. Example queries include:

• Retrieve all aging buckets for a period: SELECT period_name, customer_name, age_group1, age_group2, age_group3, age_group4 FROM apps.oki_renewal_aging_v WHERE period_name = :period_name;
• Aggregate aging by organization: SELECT authoring_org_name, SUM(age_group1), SUM(age_group2), SUM(age_group3), SUM(age_group4) FROM apps.oki_renewal_aging_v GROUP BY authoring_org_name;
• Trace the source of data: SELECT id, request_id, program_update_date FROM apps.oki_renewal_aging_v WHERE request_id = :request_id;

Users searching for "age_group1" are typically building or troubleshooting aging reports and should confirm the bucket definition used by the concurrent program that populates OKI_RENEWAL_AGING, since the view itself does not document the numeric boundaries of each age group.