Search Results oke_document_flowdowns




Overview
Explore in AI Chat

Overview

The OKE_DOCUMENT_FLOWDOWNS table is a core data object within the Oracle E-Business Suite (EBS) Project Contracts (OKE) module. Its primary function is to manage the administrative rules governing how document attachments are propagated, or "flowed down," throughout the contract hierarchy. In Project Contracts, documents such as terms and conditions, specifications, or drawings can be attached at various levels, from a master agreement down to individual contract lines. This table stores the configuration that determines whether an attachment made at a higher-level document category should be automatically inherited by lower-level documents, ensuring consistency and compliance across related contractual entities. Its role is integral to the document management and control processes within complex project contracting environments.

Key Information Stored

The table's structure is designed to define flowdown rules per business context and document type. The primary key consists of two critical columns: BUSINESS_AREA_CODE and DOCUMENT_CATEGORY_ID. The BUSINESS_AREA_CODE identifies the specific functional area or transaction type within Project Contracts (e.g., Contract, Deliverable, Funding), enabling different flowdown behaviors across business processes. The DOCUMENT_CATEGORY_ID is a foreign key that links to the FND_DOCUMENT_CATEGORIES table, identifying the specific type of document (e.g., 'Contract Terms', 'Drawings') to which the flowdown rule applies. While the provided metadata does not list all columns, typical supporting columns would include flags or indicators to specify the flowdown behavior (e.g., whether flowdown is mandatory or optional) and who can override the setting.

Common Use Cases and Queries

A primary use case is during the attachment of a document to a contract header. The application queries this table using the current business area and the selected document category to determine if the attachment must be, or can be, flowed down to all associated contract lines and deliverables. Administrators use setups based on this table to enforce organizational policies. A common reporting query would join this table to FND_DOCUMENT_CATEGORIES to produce a list of all configured flowdown rules. A sample SQL pattern to retrieve such a list is:

SELECT fcat.name DOCUMENT_CATEGORY,
       fflow.BUSINESS_AREA_CODE,
       fflow.<flowdown_flag_column>
FROM OKE_DOCUMENT_FLOWDOWNS fflow,
     FND_DOCUMENT_CATEGORIES fcat
WHERE fflow.DOCUMENT_CATEGORY_ID = fcat.id
ORDER BY BUSINESS_AREA_CODE, fcat.name;

Related Objects

  • FND_DOCUMENT_CATEGORIES: This is the primary related table, as defined by the documented foreign key relationship. The OKE_DOCUMENT_FLOWDOWNS.DOCUMENT_CATEGORY_ID column references FND_DOCUMENT_CATEGORIES to obtain the valid document types and their names used across EBS.
  • OKE_DOCUMENT_ATTACHMENTS / OKE_K_ATTACHMENTS: While not listed in the provided metadata, these are key transactional tables that store the actual document attachments for contracts. They rely on the rules defined in OKE_DOCUMENT_FLOWDOWNS to govern attachment inheritance during their creation.
  • OKE_DOCUMENT_FLOWDOWNS_PK: The primary key constraint on the BUSINESS_AREA_CODE and DOCUMENT_CATEGORY_ID columns, ensuring uniqueness of the flowdown rule per business area and document category.