Search Results oki_renewal_aging_pk

Overview

The OKI_RENEWAL_AGING table resides in the OKI schema, the Contracts Intelligence module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. Contracts Intelligence provides renewal management, service contract analysis, and forecast reporting across the enterprise. OKI_RENEWAL_AGING stores pre-aggregated aging values that classify renewal opportunities by time period, enabling renewal managers and service organizations to segment upcoming contract expirations into aging buckets for pipeline, forecast, and revenue-at-risk analysis.

Each row represents an aging snapshot for a specific combination of accounting period, period set, authoring organization, customer party, and service contract source code (SCS_CODE). Four aging group columns (AGE_GROUP1 through AGE_GROUP4) hold the bucket values that drive renewal risk reporting. The table is populated by concurrent programs identified through REQUEST_ID, PROGRAM_ID, and PROGRAM_APPLICATION_ID, indicating a batch-driven refresh model rather than real-time transactional capture.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure is standalone. The table references only FND_SECURITY_GROUPS and is not itself dependent on a hub or link from a parent domain. It effectively functions as a satellite or snapshot table that records period-scoped measurements (aging buckets) against a compound business key formed by period, organization, customer, and SCS_CODE.

Key Information Stored

The physical schema in 12.1.1 documents 18 columns. The most significant are:

• ID — Surrogate primary key enforced by OKI_RENEWAL_AGING_PK and the unique index OKI_RENEWAL_AGING_U1.
• PERIOD_NAME, PERIOD_SET_NAME, PERIOD_TYPE — Identify the accounting period and calendar set for the aging snapshot.
• AUTHORING_ORG_ID, AUTHORING_ORG_NAME — The operating unit or organization owning the renewal data.
• CUSTOMER_PARTY_ID, CUSTOMER_NAME — Customer party identifier and descriptive name.
• SCS_CODE — Service contract source code, classifying the contract population.
• AGE_GROUP1 through AGE_GROUP4 — The four aging bucket values that quantify renewals falling within each time band.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program audit trail identifying the run that produced the row.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting multi-org security policies.

The unique index OKI_RENEWAL_AGING_U2 defines the compound business key (PERIOD_NAME, PERIOD_SET_NAME, AUTHORING_ORG_ID, CUSTOMER_PARTY_ID, SCS_CODE), ensuring one aging row per period/organization/customer/contract-source combination.

Common Use Cases and Queries

Typical reporting retrieves renewal aging across organizations and customers for a given period. A representative query:

• SELECT customer_name, scs_code, age_group1, age_group2, age_group3, age_group4 FROM oki_renewal_aging WHERE period_name = :period AND authoring_org_id = :org_id ORDER BY customer_name;
• Aggregate aging totals by organization to gauge renewal pipeline health.
• Join to FND_SECURITY_GROUPS on SECURITY_GROUP_ID to enforce data security in custom reports.
• Use PROGRAM_UPDATE_DATE and REQUEST_ID to verify data freshness against the last concurrent request run.

Related Objects

• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID for row-level security.
• FND_CONCURRENT_REQUESTS — joined via REQUEST_ID to trace the populating program.
• FND_CONCURRENT_PROGRAMS — joined via PROGRAM_ID and PROGRAM_APPLICATION_ID.
• OKI_RENEWAL_AGING_PK / U1 / U2 — primary and unique indexes enforcing identity and business keys.
• OKC_SERVICE_CONTRACTS and OKC_CUSTOMER_PARTIES — typical domain joins for renewal context when SCS_CODE and CUSTOMER_PARTY_ID are resolved to source contracts.