Search Results okc_bus_doc_types_b

Overview

The OKC_BUS_DOC_TYPES_B table is a core master data table within the Oracle Contracts Core (OKC) module of Oracle E-Business Suite (EBS). It serves as the central repository for defining and managing all business document types that are contract-enabled. Its primary role is to store the metadata and configuration preferences that govern how different document types, such as Sales Orders, Purchase Agreements, or Service Contracts, are authored and processed within the Oracle Contracts framework. The data in this table is not typically created by end-users but is seeded by product teams during the integration of other EBS modules (e.g., Order Management, Purchasing) with Oracle Contracts, making it fundamental for cross-module contract functionality.

Key Information Stored

The table's primary key is the DOCUMENT_TYPE column, which holds the unique internal code identifying a specific business document type, such as 'OKC_CONTRACT' or 'OKS_CONTRACT'. Other critical columns include APPLICATION_ID, which links to the FND_APPLICATION table to identify the owning EBS product (e.g., OKC, OKS), and various preference columns that control document behavior. These preferences may dictate settings like whether the document type supports deliverables, renewals, or specific approval workflows. The table essentially acts as a control point, defining the contract authoring rules and capabilities for each integrated business document.

Common Use Cases and Queries

This table is central to configuration analysis, integration support, and data validation reports. A common use case is to identify all contract-enabled document types available in the instance and their source application. A typical query would join with FND_APPLICATION to get the application name:

• SELECT bdt.document_type, fa.application_short_name FROM okc_bus_doc_types_b bdt, fnd_application fa WHERE bdt.application_id = fa.application_id;

Another frequent scenario involves troubleshooting template assignments or article usage, requiring a lookup to validate if a specific DOCUMENT_TYPE is correctly seeded and active. Developers and functional consultants reference this table to understand the contract attributes available for a given transaction type when designing extensions or custom reports.

Related Objects

As a key master table, OKC_BUS_DOC_TYPES_B has numerous foreign key relationships within the Contracts schema. Key documented relationships include:

• FND_APPLICATION: Linked via APPLICATION_ID to identify the source EBS product.
• OKC_ALLOWED_TMPL_USAGES: Defines which template usages are permitted for a given DOCUMENT_TYPE.
• OKC_K_ARTICLES_B: Articles are associated with a specific DOCUMENT_TYPE.
• OKC_BUS_DOC_EVENTS_B: Business document events are defined per BUS_DOC_TYPE.
• OKC_DOC_QA_LISTS: Question and Answer lists are linked to a DOCUMENT_TYPE.
• OKC_REP_CONTRACTS_ALL: Reporting views use CONTRACT_TYPE to filter by document type.
• OKC_TEMPLATE_USAGES and OKC_TEMPLATE_USAGES_H: Template assignment history is tied to a DOCUMENT_TYPE.