Search Results ui_pers_function

Overview

OKC_BUS_DOC_TYPES_VL is a view owned by the APPS schema in Oracle E-Business Suite, belonging to the OKC (Contracts Core) product family. It presents the definition of business document types used throughout the Oracle Contracts application. Business document types are the configuration records that govern how a given class of contract document behaves — for example, whether attachments, deliverables, notes, risks, controls, or contract terms are enabled, what workflow drives its approval, and which functions render its preview and detail pages. In 12.1.1 and 12.2.2 this view serves as the canonical read interface for these configuration rows, exposing a translated (VL, "view language") projection that combines the base table with its translations. The view is widely referenced by contracts setup forms, the Contracts Workbench, integration routines, and custom reporting, and it is the object a developer needs when searching for a column such as APPROVAL_WORKFLOW_NAME, which identifies the workflow process initiated when a document of that type is submitted for approval.

Underlying Base Objects

The ETRM metadata documents two referenced base objects, both accessed through synonyms: OKC_BUS_DOC_TYPES_B and OKC_BUS_DOC_TYPES_TL. OKC_BUS_DOC_TYPES_B is the single-language base table holding all non-translatable attributes — workflow names, function references, flags, dates, audit columns, and the primary key DOCUMENT_TYPE with OBJECT_VERSION_NUMBER for optimistic locking. OKC_BUS_DOC_TYPES_TL holds the translatable NAME and DESCRIPTION columns, keyed by DOCUMENT_TYPE plus LANGUAGE and SOURCE_LANG. The view text joins BDTB (the _B synonym) to BDTTL (the _TL synonym) and exposes BDTB.ROWID as ROW_ID, preserving updatability characteristics expected of an MLS view. The _VL suffix indicates the view resolves the session language for NAME and DESCRIPTION while surfacing the remaining columns directly from the base table.

Key Columns

• DOCUMENT_TYPE — primary identifier of the business document type; joins to contract headers and related configuration tables.
• NAME / DESCRIPTION — translatable display values sourced from OKC_BUS_DOC_TYPES_TL.
• APPROVAL_WORKFLOW_NAME — the workflow process used for approval of documents of this type.
• SIGNATURE_WORKFLOW_NAME — workflow used for the signature lifecycle.
• INTENT, DOCUMENT_TYPE_CLASS, PROVISION_ALLOWED_YN — classify the document and control provisioning behavior.
• DOC_PREVIEW_FUNCTION, DOC_VIEW_DETAILS_FUNCTION, CONTRACT_TERMS_FUNCTION, NOTIFICATION_HEADER_FUNCTION, UI_PERS_FUNCTION — entry points invoked by the UI.
• ENABLE_AMEND_SUMMARY_YN, ENABLE_DELIVERABLES_YN, ENABLE_ATTACHMENTS_YN, DISABLE_AMEND_YN, ALLOW_APPROVER_EDIT_YN — amendment and editing controls.
• ENABLE_CONTRACT_TERMS_YN, ENABLE_NOTES_YN, ENABLE_RISKS_YN, ENABLE_CONTROLS_YN, ENABLE_RELATIONSHIPS_YN — feature toggles for related contract components.
• SHOW_IN_WORKBENCH_FLAG, SHOW_IN_LOV_YN, SHOW_PREVIEW_BTN_YN, SHOW_AUTH_PARTY_FLAG, SHOW_EXT_VAR_FLAG — visibility flags.
• START_DATE, END_DATE — effective dating of the configuration row.
• APPLICATION_ID, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard ownership and audit columns.

Common Use Cases and Queries

The most frequent use of this view is identifying which approval workflow governs a document type, or listing all document types and their enabled features. The following query retrieves approval workflow configuration:

SELECT document_type, name, approval_workflow_name, signature_workflow_name, enable_contract_terms_yn, start_date, end_date FROM apps.okc_bus_doc_types_vl WHERE approval_workflow_name IS NOT NULL AND SYSDATE BETWEEN NVL(start_date, SYSDATE) AND NVL(end_date, SYSDATE + 1) ORDER BY name;

Integration and reporting often restrict by document type class or intent, for example: SELECT document_type, name FROM apps.okc_bus_doc_types_vl WHERE document_type_class = :p_class AND show_in_lov_yn = 'Y'; Because the view is an MLS VL view, joins to contract tables on DOCUMENT_TYPE return translated names automatically, making it suitable for concurrent programs, OAF pages, and ad hoc SQL against Contracts configuration.