Search Results pdf_description

Overview

OKR_K_HDR_DV is a database view belonging to the OKR — Contracts for Rights module, a component of Oracle E-Business Suite (EBS) that is documented as obsolete in releases 12.1.1 and 12.2.2. The view presents a denormalized, reporting-oriented projection of contract header information, combining the base contract header record with related descriptive, checklist, process, and PDF usage data. Its name follows the EBS convention of a "_DV" suffix, indicating a "Document/Descriptive View" intended for read-only querying rather than transactional integrity.

The ETRM metadata explicitly records that the view is not implemented in the current database, meaning it exists in the application dictionary as a legacy or reference object but is not physically present in the runtime schema. The view text is nevertheless preserved, offering insight into the OKR data model. The presence of the column PDF_USAGE indicates that the view surfaces document/process usage metadata associated with a contract, distinguishing PDF-driven workflow usage from the contract header itself. Because OKR — Contracts for Rights is obsolete, this view has no active role in current reporting or integration; it is relevant primarily to historical data reconstruction, upgrade analysis, and data model archaeology.

Underlying Base Objects

The view text joins five base tables. These are the documented base objects, though the ETRM metadata lists none separately, and the view is not implemented in the target database.

• OKC_K_HEADERS_B — the primary contract header base table (alias CHRB), supplying contract identity, dates, amounts, status, and audit columns.
• OKC_K_HEADERS_TL — the translated header table (alias CHRT), supplying short description, description, and comments in the session language.
• OKC_PROCESS_DEFS_B and OKC_PROCESS_DEFS_TL — the process definition base and translated tables (aliases CPDB, CPDT), supplying PDF name, description, workflow process name, and PDF usage.
• OKC_K_PROCESSES — links contracts to process definitions (alias CPSB), via CHR_ID and PDF_ID.
• OKC_QA_CHECK_LISTS_TL — the checklist translated table (alias CQLT), supplying quality assurance checklist name and description.

The join predicates restrict the view to contracts where SCS_CODE = 'TDE_RIGHT', and the language is filtered using USERENV('LANG'). The process, PDF, and checklist joins are outer joins, so contracts without associated processes or checklists are retained.

Key Columns

• CHR_ID / CONTRACT_NUMBER — the contract header identifier and human-readable contract number.
• VERSION — derived via OKR_UTIL_PUB.GET_VERSION_NUMBER, returning the version string.
• START_DATE, END_DATE, PERIOD_DURATION — contract validity window and its derived duration.
• ESTIMATED_AMOUNT, CURRENCY_CODE — financial value and currency of the contract.
• STS_CODE and STATUS_MEANING — the status code and its translated meaning via OKR_UTIL_PUB.GET_K_STATUS_MEANING.
• PDF_ID, PDF_NAME, PDF_DESCRIPTION, PDF_USAGE — the process/document definition identifier, name, description, and the PDF_USAGE attribute that annotates how the associated document process is used. This is the column most directly relevant to the user's "pdf_usage" search.
• WF_PROCESS_NAME — the workflow process associated with the document process.
• QCL_CHECKLIST_NAME, QCL_DESCRIPTION — the quality checklist attached to the contract.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, OBJECT_VERSION_NUMBER.

Common Use Cases and Queries

The predominant use case is identifying the document/process usage (PDF_USAGE) linked to Contracts-for-Rights headers. A representative query follows.

• List contracts and their PDF usage:

  SELECT contract_number, version, start_date, end_date,
         pdf_name, pdf_usage, wf_process_name
  FROM   okr_k_hdr_dv
  WHERE  pdf_usage IS NOT NULL;

• Contracts with status and checklist:

  SELECT contract_number, status_meaning, qcl_checklist_name
  FROM   okr_k_hdr_dv
  WHERE  sts_code = 'ACTIVE';

• Audit of process usage by contract number:

  SELECT contract_number, pdf_usage, last_updated_by, last_update_date
  FROM   okr_k_hdr_dv
  ORDER BY contract_number;

Because the view is not implemented in the database and the OKR module is obsolete, these queries should be treated as reference patterns. Equivalent data in supported releases must be sourced from the underlying OKC_* base tables directly or from the corresponding current Contracts views.