Search Results okc_article_flowdowns




Overview

The OKE_ARTICLE_FLOWDOWNS table is a core configuration entity within the Oracle E-Business Suite (EBS) Project Contracts (OKE) module. It serves as a master repository for defining and managing contractual flowdown rules. In the context of project contracts, a flowdown refers to the automatic application of specific contract terms and conditions (articles) from a higher-level contract, such as a master agreement, to its associated lower-level documents, like work orders or purchase orders. This table holds the settings that determine which standard articles are mandated for specific business contexts or article subjects, thereby enforcing compliance and consistency across a contractual hierarchy. Its role is critical in automating the contract creation process and ensuring that all downstream documents inherit the legally and procedurally required clauses.

Key Information Stored

The table's structure is defined by a composite primary key, which dictates the uniqueness of each flowdown rule. Based on the provided metadata, the key columns are:

  • BUSINESS_AREA_CODE: This column identifies the specific business process or functional area within Project Contracts (e.g., Contract, Deliverable, Funding, Billing) to which the flowdown rule applies. It segments rules by operational context.
  • ARTICLE_SUBJECT_CODE: This column stores a code representing a category or subject of contractual articles (e.g., Insurance, Termination, Liability). It links the flowdown rule to a family of standard clauses.

Together, these columns create a rule specifying that for a given BUSINESS_AREA_CODE, articles classified under a particular ARTICLE_SUBJECT_CODE must be flowed down. The table likely contains additional descriptive or control columns (such as ENABLED_FLAG, START_DATE, or CREATED_BY) common to EBS setup tables, though they are not detailed in the excerpt.

Common Use Cases and Queries

A primary use case is during the authoring of a project contract or a downstream document. The application queries this table to determine which standard articles must be automatically included based on the document's business area and the subjects flagged for flowdown from the parent contract. Administrators use interfaces to maintain these rules, ensuring new business areas or regulatory requirements are reflected. For reporting and analysis, queries often join this table to article master data. A sample query to list all active flowdown rules would be:

SELECT BUSINESS_AREA_CODE, ARTICLE_SUBJECT_CODE FROM OKE.OKE_ARTICLE_FLOWDOWNS WHERE SYSDATE BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, SYSDATE);
Another common pattern is to validate or audit setup by joining to the standard article subjects table (OKC_ARTICLE_SUBJECTS_TL) to get the subject name:
SELECT f.BUSINESS_AREA_CODE, t.NAME FROM OKE.OKE_ARTICLE_FLOWDOWNS f, OKC_ARTICLE_SUBJECTS_TL t WHERE f.ARTICLE_SUBJECT_CODE = t.CODE AND t.LANGUAGE = USERENV('LANG');

Related Objects

The table maintains a direct relationship with the standard Oracle Contracts Core (OKC) table for article subjects. As indicated by its primary key name (OKC_ARTICLE_FLOWDOWNS), it is a subtype or extension table within the OKC data model, inheriting its key structure from a parent entity in the OKC schema. The ARTICLE_SUBJECT_CODE column is a foreign key to the OKC_ARTICLE_SUBJECTS_B table (or its translated version, OKC_ARTICLE_SUBJECTS_TL), which holds the definition of all article subject codes. The BUSINESS_AREA_CODE may reference a lookup type (e.g., OKE_BUSINESS_AREA) for validation. This table is fundamentally referenced by the contract generation engine within the OKE module, which applies these rules to populate the OKC_ARTICLE_VERSIONS table for specific contracts.