Results for “oki_renew_by_statuses”

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

Overview

OKI_RENEW_BY_STATUSES is a table in the OKI (Contracts Intelligence) module of Oracle E-Business Suite. In ETRM 12.1.1 and 12.2.2, the OKI module is documented as Obsolete and, per the ETRM metadata, the object is not implemented in the reference database. The table is described as holding information about renewal contracts grouped by contract status, implying a pre-aggregated reporting or analytical construct rather than an operational transaction table. It captures periodic snapshots of renewal activity — amounts and contract counts — broken out by the status of the authoring contract and by a secondary classification field, SCS_CODE.

Heuristically, the metadata classifies the object as a Data Vault satellite. This suggests the table behaves as a descriptive, non-historized reference snapshot keyed by a surrogate identifier (ID) and a composite business key, rather than as a hub or link of business entities. Any modelling exercise should treat it as dependent descriptive data whose grain is defined by period, ledger, operating unit, contract status, and SCS classification.

Key Information Stored

The physical schema documents 15 columns. The most significant are:

• ID — the surrogate primary key, constrained by OKI_RENEW_BY_STATUS_PK and the unique index OKI_RENEW_BY_STATUSES_U2.
• PERIOD_NAME, PERIOD_SET_NAME, PERIOD_TYPE — accounting period identifiers that establish the reporting horizon for each aggregate row.
• AUTHORING_ORG_ID, AUTHORING_ORG_NAME — the operating unit or authoring organization owning the renewal contracts, with the ID serving as the join surrogate and the name as a descriptive label.
• STATUS_CODE — the contract status that buckets the renewal records.
• SCS_CODE — an additional classification dimension that participates in the unique business key.
• BASE_AMOUNT — the aggregated monetary value of renewals in the row's bucket.
• CONTRACT_COUNT — the count of contracts represented by the row.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program provenance columns tracing the process that populated the row.
• SECURITY_GROUP_ID — the Multi-Org security grouping used to isolate data by operating unit.

The business-key candidates are defined by OKI_RENEW_BY_STATUSES_U1 over (PERIOD_NAME, PERIOD_SET_NAME, AUTHORING_ORG_ID, STATUS_CODE, SCS_CODE). The surrogate ID is distinct from this composite key and should not be used for reporting-level joins.

Common Use Cases and Queries

Because the table is not implemented, its practical role is confined to migration mapping, historical object inventories, and documentation of legacy Contracts Intelligence reporting. Typical query patterns involve aggregating renewals by period and status:

• Renewal value trend: SELECT period_name, status_code, SUM(base_amount) FROM oki_renew_by_statuses GROUP BY period_name, status_code.
• Operating unit comparison: filtering by authoring_org_id or security_group_id to produce operating-unit-specific renewal counts.
• Contract volume reporting: SELECT status_code, SUM(contract_count) to assess pipeline by status.
• Data lineage auditing: querying request_id, program_id, and program_update_date to identify the concurrent program that loaded a snapshot.

Related Objects

The metadata classifies the table as standalone, with no foreign key relationships to external objects. Consequently, joins are defined logically rather than through enforced constraints. The most significant related objects are OKI_CONTRACTS (or equivalent OKI contract tables) joined on AUTHORING_ORG_ID and STATUS_CODE, the OKI concurrent programs referenced through PROGRAM_ID and PROGRAM_APPLICATION_ID, the FND concurrent request table joined on REQUEST_ID, and the GL or GL period definitions joined through PERIOD_NAME and PERIOD_SET_NAME. Because no FK structure is documented, any such joins must be verified against the local implementation rather than assumed from the ETRM definition.