Search Results okc_bus_doc_types_v




Overview
Explore in AI Chat

Overview

OKC_BUS_DOC_TYPES_V is a seeded, VALID view in the APPS schema that exposes the metadata definitions of business document types used throughout Oracle Contracts Core (OKC). A business document type describes the behavioral template of a contract-related document — for example, a purchase agreement, a sales contract, or a subscription — and controls how that document type is rendered, amended, previewed, and surfaced in the Contracts workbench. The view is not a transactional object; it is a reference and configuration view consumed by the Contracts forms, the Contracts Workbench (OKC), and integrations that need to enumerate the document types available to a responsibility or user.

The view exists primarily to join the base table to its translation table so that the NAME presented to the user is returned in the session language. Because it exposes flags such as SHOW_IN_WORKBENCH_FLAG, it is the canonical source used by the Workbench UI to decide which document types appear as selectable tiles or list entries.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over two base objects, exposed to APPS through synonyms:

The two are joined on DOCUMENT_TYPE, with the TL side additionally restricted by LANGUAGE = USERENV('LANG'), so the view returns exactly one row per document type, translated into the caller's session language.

Key Columns

Common Use Cases and Queries

The most frequent use of this view is to list the document types enabled for the workbench, or to obtain the display name of a given document type for a report or integration.

SELECT document_type, name, intent, document_type_class
  FROM apps.okc_bus_doc_types_v
 WHERE show_in_workbench_flag = 'Y'
 ORDER BY name;

To resolve a single document type's name and preview function in an integration or concurrent program:

SELECT name, doc_preview_function, contract_terms_function
  FROM apps.okc_bus_doc_types_v
 WHERE document_type = :p_document_type
   AND SYSDATE BETWEEN NVL(start_date, SYSDATE)
                   AND NVL(end_date, SYSDATE);

To identify types available for a specific class, such as purchase agreements, use DOCUMENT_TYPE_CLASS and APPLICATION_ID as filters. Because the view is language-aware, its results vary with USERENV('LANG'); reports that must be language-independent should join the base table OKC_BUS_DOC_TYPES_B directly or specify the desired LANGUAGE. Query performance is generally good, as the view is a simple equijoin with no aggregation or union operations.