Search Results curr_sob_contract_amount

Overview

OKI.OKI_SEQ_GROWTH_RATE is a transaction-data table in the Oracle EBS Service Contracts (OKI) schema that stores summarized sequential growth rate metrics for service contract portfolios. It is a denormalized reporting and analytical staging object: rows represent a computed growth rate code (SEQ_GRW_RATE_CODE) for a given contract customer and product category, evaluated across a specific accounting period and summarized on a particular build date. The table resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10 and is marked "Oracle Internal Use Only," meaning Oracle Corporation does not support direct customer access except through standard Oracle Applications programs.

The table has no foreign keys other than SECURITY_GROUP_ID referencing FND_SECURITY_GROUPS, and it references no other application tables directly. Under the heuristic Data Vault classification mined from the FK structure, it is treated as standalone. In modelling terms, this is best read as a satellite-style snapshot: it captures period-keyed, descriptive measures (contract amounts, growth rates) attached to a customer/category business key, refreshed by concurrent programs that populate REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE. It is worth noting that this is a heuristic suggestion rather than a formally declared Data Vault model.

Key Information Stored

The table contains 20 documented columns. Its business-key candidate is the unique index OKI_SEQ_GROWTH_RATE_U1, which spans nine columns: PERIOD_NAME, PERIOD_SET_NAME, PERIOD_TYPE, SUMMARY_BUILD_DATE, AUTHORING_ORG_ID, SEQ_GRW_RATE_CODE, SCS_CODE, CUSTOMER_PARTY_ID, and PRODUCT_CATEGORY_CODE. No separate surrogate primary key column is documented; uniqueness is enforced entirely through this composite business key. The most significant columns are:

• PERIOD_NAME, PERIOD_SET_NAME, PERIOD_TYPE — the accounting period identity, tying each row to a specific calendar or fiscal period definition.
• SUMMARY_BUILD_DATE — the date on which the growth-rate summary was generated, allowing comparison of successive snapshots.
• AUTHORING_ORG_ID, AUTHORING_ORG_NAME — the operating unit or organization that authored the contract data.
• CUSTOMER_PARTY_ID — the internal party identifier of the contract customer; CUSTOMER_NAME carries its denormalized display value.
• SEQ_GRW_RATE_CODE — the growth rate code that categorizes the metric being summarized.
• SCS_CODE — the service contract source or category code associated with the rate.
• PRODUCT_CATEGORY_CODE — the user-requested column, holding the product category against which the growth rate is measured.
• CURR_BASE_CONTRACT_AMOUNT / PREV_BASE_CONTRACT_AMOUNT — current and prior base-currency contract amounts used to derive growth.
• CURR_SOB_CONTRACT_AMOUNT / PREV_SOB_CONTRACT_AMOUNT — current and prior set-of-books currency contract amounts.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — the standard concurrent program audit trail identifying which process built the row.
• SECURITY_GROUP_ID — used for application hosting and multi-tenant data segregation; the only documented FK, to FND_SECURITY_GROUPS.

Common Use Cases and Queries

The primary use case is period-over-period contract growth analysis segmented by customer and product category. A typical query filters on a build date and period to retrieve the latest snapshot and computes growth percentages from the stored amounts:

SELECT customer_name, product_category_code, seq_grw_rate_code,
  CURR_BASE_CONTRACT_AMOUNT, PREV_BASE_CONTRACT_AMOUNT,
  CASE WHEN PREV_BASE_CONTRACT_AMOUNT > 0
    THEN (CURR_BASE_CONTRACT_AMOUNT - PREV_BASE_CONTRACT_AMOUNT) / PREV_BASE_CONTRACT_AMOUNT
  END AS growth_pct
FROM OKI.OKI_SEQ_GROWTH_RATE
WHERE period_name = :period
  AND summary_build_date = (SELECT MAX(summary_build_date) FROM OKI.OKI_SEQ_GROWTH_RATE
    WHERE period_name = :period)
  AND product_category_code = :category
ORDER BY growth_pct DESC;

Because multiple SUMMARY_BUILD_DATE values can exist per period, and multiple SCS_CODE values can exist per customer, reports must use the unique key columns to avoid double counting. Analytical views can join CUSTOMER_PARTY_ID to party tables, while the base/SOB amount pairs support dual-currency and reporting-currency reconciliation.

Related Objects

Documented dependencies for this object are limited, and the table references no other application tables directly. The significant related objects are:

• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID; the sole documented FK and the basis for hosting/security filtering.
• FND_CONCURRENT_REQUESTS — joined via REQUEST_ID to identify the concurrent program run that populated a snapshot.
• FND_APPLICATION / FND_PROGRAM — joined via PROGRAM_APPLICATION_ID and PROGRAM_ID for program metadata.
• HZ_PARTIES — joined via CUSTOMER_PARTY_ID to resolve the internal customer identifier to party details when CUSTOMER_NAME is insufficient.
• FND_PERIODS / accounting calendar tables — resolved through PERIOD_NAME, PERIOD_SET_NAME, and PERIOD_TYPE to relate summary rows to period definitions.
• OKI service contract base tables — the source contract and SCS data from which the growth-rate summary is derived by the building program.