Results for “enable_contract_terms_yn”

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

Overview

OKC_BUS_DOC_TYPES_B is a foundational setup table in the Oracle Contracts Core (OKC) module. It stores all business document types and the associated preferences that govern how each document type behaves during Contract authoring. Each product team that integrates with Oracle Contracts—such as Purchasing, Sales, or Project Contracts—seeds rows into this table to register the document types it supports and to control the behavior of those documents within theContracts user interface and processing engine.

The table functions as a reference and configuration hub. It does not store transactional contract data; rather, it defines the metadata that drives contract creation, amendment, attachment handling, approval routing, and UI rendering. The documented physical schema in ETRM 12.2.2 shows 47 columns owned by the OKC schema, and the primary key is OKC_BUS_DOC_TYPES_B_PK on the DOCUMENT_TYPE column. A unique index, OKC_BUS_DOC_TYPES_B_U1, exists on (DOCUMENT_TYPE, ZD_EDITION_NAME). Based on the foreign key relationships mined from the ETRM metadata, this table behaves as a Data Vault hub—a natural modeling suggestion given that it holds the business key (DOCUMENT_TYPE) and is referenced by numerous downstream tables.

Key Information Stored

The table’s most consequential columns fall into several functional groups:

• DOCUMENT_TYPE — The primary key and business identifier for each business document type.
• APPLICATION_ID — Foreign key to FND_APPLICATION, identifying the Oracle application that registered the document type.
• DOCUMENT_TYPE_CLASS — Classifies the document type (for example, contract, template, or quote).
• OBJECT_VERSION_NUMBER — Supports optimistic locking in the Oracle EBS framework.
• PROVISION_ALLOWED_YN — Indicates whether provisioning is permitted for the document type.
• ENABLE_AMEND_SUMMARY_YN / DISABLE_AMEND_YN — Control amendment behavior for contracts of this type.
• ENABLE_DELIVERABLES_YN / ENABLE_CONTROLS_YN / ENABLE_NOTES_YN — Feature toggles that determine which contract components are available.
• ENABLE_PARTIES_YN / ENABLE_RELATIONSHIPS_YN / ENABLE_RISKS_YN — Govern whether parties, relationships, and risks can be associated with the document.
• ENABLE_ATTACHMENTS_YN / ENABLE_ATTACHED_DOC_FLAG — Control attachment and attached-document functionality.
• SHOW_IN_WORKBENCH_FLAG / SHOW_IN_LOV_YN — Determine visibility in the Contracts Workbench and list of values.
• APPROVAL_WORKFLOW_NAME / SIGNATURE_WORKFLOW_NAME — Identify the workflows used for approval and signature.
• DOC_PREVIEW_FUNCTION / DOC_VIEW_DETAILS_FUNCTION / CONTRACT_TERMS_FUNCTION / UI_PERS_FUNCTION — Store function names used to render document previews, view details, contract terms, and personalized UI elements.
• START_DATE / END_DATE — Define the effective date range for the document type configuration.
• CREATED_BY / CREATION_DATE / LAST_UPDATED_BY / LAST_UPDATE_DATE — Standard Oracle EBS audit columns.

The surrogate primary key is DOCUMENT_TYPE, and the unique index OKC_BUS_DOC_TYPES_B_U1 on (DOCUMENT_TYPE, ZD_EDITION_NAME) serves as the business-key candidate.

Common Use Cases and Queries

Typical usage includes identifying which document types are enabled for a given application, determining whether a document type permits amendments or attachments, and retrieving the workflow names associated with a document type. A common query joins this table to FND_APPLICATION to report document types by application:

• SELECT bdt.document_type, bdt.document_type_class, app.application_name FROM okc_bus_doc_types_b bdt, fnd_application app WHERE bdt.application_id = app.application_id;

Another frequent pattern filters by feature flags, for example to list document types where attachments are enabled: WHERE enable_attachments_yn = 'Y'. Reporting on active configurations uses the START_DATE and END_DATE columns to restrict results to the currently effective set of document types.

Related Objects

The ETRM metadata documents the following significant relationships, all keyed on DOCUMENT_TYPE (or its variants):

• OKC_ALLOWED_TMPL_USAGES — References DOCUMENT_TYPE; defines which templates may be used with a document type.
• OKC_K_ARTICLES_B — References DOCUMENT_TYPE; stores contract articles associated with document types.
• OKC_BUS_DOC_EVENTS_B — References BUS_DOC_TYPE; records events tied to business document types.
• OKC_DOC_QA_LISTS — References DOCUMENT_TYPE; holds question-and-answer list definitions for a document type.
• OKC_REP_CONTRACTS_ALL / OKC_REP_CONTRACT_VERS — Reference CONTRACT_TYPE; repository tables for contracts and contract versions.
• OKC_TEMPLATE_USAGES / OKC_TEMPLATE_USAGES_H — Reference DOCUMENT_TYPE; track template usage history.
• OKC_VARIABLE_DOC_TYPES — References DOC_TYPE; maps variables to document types.
• FND_APPLICATION — The referenced parent table for APPLICATION_ID, identifying the owning Oracle application.

These relationships confirm that OKC_BUS_DOC_TYPES_B is a central reference point that many Contract authoring and template features depend upon.