Results for “oke_programs”

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

Overview

OKE_PROGRAMS is a transactional table within the OKE (Project Contracts) module of Oracle E-Business Suite, holding in Release 12.1.1 and 12.2.2. It stores master records for "programs," which in the Project Contracts context represent a grouping construct used to organize contract funding and header-level activity. Each row defines a distinct program that can be referenced by downstream contract and funding entities, making the table a central reference point rather than a purely transactional ledger.

The table is owned by the OKE schema and is marked VALID in the data dictionary. Heuristic Data Vault classification mined from the foreign-key structure labels OKE_PROGRAMS as hub-leaning, meaning it functions primarily as a business-key-bearing entity at the center of relationships. In a Data Vault model this would be modeled as a hub, with its descriptive attributes split into satellites and its references to funding and contract headers modeled as links.

Key Information Stored

The documented physical schema contains 28 columns. The most significant are:

• PROGRAM_ID — Surrogate primary key, enforced by OKE_PROGRAMS_PK and mirrored by unique index OKE_PROGRAMS_U1. All foreign-key references from dependent tables point to this column.
• PROGRAM_NUMBER — Business-key candidate, enforced by unique index OKE_PROGRAMS_U2. Typically a user-facing or system-generated identifier.
• PROGRAM_NAME — Business-key candidate, enforced by unique index OKE_PROGRAMS_U3.
• DESCRIPTION — Free-text description of the program.
• START_DATE and END_DATE — Validity window for the program.
• RECORD_VERSION_NUMBER — Optimistic locking / concurrency control column.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — Flexible descriptive flexfield storage for client-specific extensions.

The three unique indexes (OKE_PROGRAMS_U1, U2, U3) confirm that PROGRAM_ID, PROGRAM_NUMBER, and PROGRAM_NAME are each required to be unique.

Common Use Cases and Queries

Typical usage includes resolving program identifiers into names for contract reports, validating that a program is active on a given date before allowing a contract header or funding pool to reference it, and joining programs to their dependent funding and header records. A representative lookup by business key:

• SELECT program_id, program_number, program_name, start_date, end_date FROM oke.oke_programs WHERE program_number = :p_number;
• SELECT p.program_name, h.* FROM oke.oke_programs p JOIN oke.oke_k_headers h ON h.program_id = p.program_id WHERE TRUNC(SYSDATE) BETWEEN p.start_date AND p.end_date;
• SELECT p.program_number, COUNT(fp.funding_pool_id) FROM oke.oke_programs p LEFT JOIN oke.oke_funding_pools fp ON fp.program_id = p.program_id GROUP BY p.program_number;

Reporting scenarios commonly include program-level roll-ups of contract value, program utilization analysis by date range, and data-quality checks for programs with overlapping or missing date windows.

Related Objects

OKE_PROGRAMS participates in the following documented foreign-key relationships:

• OKE_FUNDING_POOLS — references OKE_PROGRAMS via OKE_FUNDING_POOLS.PROGRAM_ID, associating funding pools with their parent program.
• OKE_K_HEADERS — references OKE_PROGRAMS via OKE_K_HEADERS.PROGRAM_ID, linking contract headers to programs.
• OKE_K_HEADERS_H — the history/audit counterpart of OKE_K_HEADERS, referencing OKE_PROGRAMS via OKE_K_HEADERS_H.PROGRAM_ID.

These three dependent tables are the primary consumers of the PROGRAM_ID surrogate key. Because OKE_PROGRAMS is a hub in the derived model, any change to its unique-key values propagates through these dependent foreign keys, so maintenance should be performed with care to preserve referential integrity.