Results for “product_line”

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

Overview

OKE_K_HEADERS_FULL_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the OKE – Project Contracts module. Its documented purpose is to present "contract header extended information," consolidating the core contract header record from the OKC contract tables with the extended attributes maintained in the OKE (Project Contracts) extension tables, and enriching both with descriptive and cross-referential data from lookups, organizations, projects, and type/version utilities. The view status is VALID in both 12.1.1 and 12.2.2.

Because a single contract header is physically split between the base OKC contract tables and the OKE extension table, the view's principal role is to reconstruct a denormalized, end-user-readable row per contract version. It exposes human-meaningful descriptions in place of coded values — for example, type classes, priority names, status meanings, and Yes/No translations of flag columns — making it directly suitable for BI Publisher reports, Oracle Reports, OBIEE extracts, and ad hoc SQL rather than for transactional processing. It is a read-only construct and carries no DML semantics.

Underlying Base Objects

The ETRM metadata documents the following referenced base objects: OKC_K_HEADERS_ALL_B, OKC_K_HEADERS_TL, OKC_STATUSES_TL, and HR_ALL_ORGANIZATION_UNITS_TL (all synonyms), together with OKE_K_HEADERS, OKE_PRIORITY_CODES_TL, OKE_PROGRAMS, and PA_PROJECTS_ALL synonyms, the OKE_K_TYPES_VL and OKE_K_VERS_NUMBERS_V views, the OKE_UTILS package, and FND_LOOKUP_VALUES.

The view is anchored on the OKE extension table OKE_K_HEADERS and joins it to OKC_K_HEADERS_ALL_B on K_HEADER_ID, with OKC_K_HEADERS_TL supplying the translated short description, description, and cognomen. OKE_K_VERS_NUMBERS_V contributes the major and minor version numbers, while OKE_K_TYPES_VL supplies the contract type name and type class code. FND_LOOKUP_VALUES provides lookup meanings such as the product line code. HR_ALL_ORGANIZATION_UNITS_TL resolves the authoring organization and owning organization IDs to names, and PA_PROJECTS_ALL provides the associated project number, name, description, and dates. OKE_UTILS is invoked at the row level to translate flag columns into Yes/No text.

Key Columns

• Identity and versioning: K_HEADER_ID, MAJOR_VERSION, MINOR_VERSION, the concatenated version string, CONTRACT_NUMBER, CONTRACT_NUMBER_MODIFIER, and OBJECT_VERSION_NUMBER.
• Classification: K_TYPE_CODE, K_TYPE_NAME, TYPE_CLASS_CODE, BUY_OR_SELL, CHR_TYPE, and SCS_CODE.
• Status and dates: STS_CODE with its translated MEANING, START_DATE, END_DATE, AWARD_DATE, DATE_ISSUED, DATE_APPROVED, and the customer and contractor signature dates.
• Parties and organizations: AUTHORING_ORG_ID and ORGANIZATION name, OWNING_ORGANIZATION_ID and name, plus PRIME_K_ALIAS and PRIME_K_NUMBER for the prime contract reference.
• Project linkage: PROJECT_ID, project SEGMENT1, NAME, DESCRIPTION, START_DATE, COMPLETION_DATE, and project organization name.
• Flags: CLASSIFIED_FLAG, DCAA_AUDIT_REQ_FLAG, BOOKED_FLAG, OPEN_FLAG, EXPORT_FLAG, HUMAN_SUBJECT_FLAG, PENALTY_CLAUSE_FLAG, SB_PLAN_REQ_FLAG, SB_REPORT_FLAG, and CQA_FLAG, each rendered through OKE_UTILS.YES_NO with NVL defaults.

Common Use Cases and Queries

Typical usage includes contract header reports and extracts, contract dashboards filtered by status or type, award and signature date tracking, and organization- or project-based contract listings.

• Listing active headers for an organization:

  SELECT contract_number, k_type_name, sts_code, start_date, end_date
  FROM   apps.oke_k_headers_full_v
  WHERE  owning_organization_id = :org_id
  AND    sts_code = 'ACTIVE';

• Contracts by project:

  SELECT contract_number, major_version, minor_version, segment1, name
  FROM   apps.oke_k_headers_full_v
  WHERE  project_id = :project_id;

• Flag-based reporting using the translated Yes/No columns:

  SELECT contract_number, booked_flag, classified_flag, cqa_flag
  FROM   apps.oke_k_headers_full_v
  WHERE  NVL(booked_flag,'N') = 'Y';

Because the view joins translation tables and calls OKE_UTILS per row, queries should always be constrained, and appropriate indexes on the base OKC/OKE header keys should be confirmed when the view is used in high-volume extracts.