Results for “deviation_type”

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

Overview

OKC_TERMS_DEVIATIONS_T is a table in the OKC (Contracts Core) schema of Oracle E-Business Suite, documented as valid in both release 12.1.1 and 12.2.2. The ETRM metadata describes it as a "temporary table to store Contract Standard Deviations data," positioning it as a transient working store used by the Contracts Core deviation engine rather than as a durable transactional master. Records are typically populated during term and clause comparison processing, consumed by deviation reporting or validation logic, and purged thereafter, which explains the "_T" suffix convention.

The object carries 38 documented columns and one foreign key. Under the heuristic Data Vault classification derived from the mined foreign key structure, the table is characterized as satellite-leaning. In Data Vault terms this suggests the object behaves as a descriptive satellite attached to a parent hub or link — here the referenced rule header — capturing context and qualifier attributes about deviations rather than defining new business entities. Practitioners should treat this classification as a modeling suggestion, not a normative claim, because the table functions as a temporary staging artifact and its persistence semantics differ from a conventional satellite.

Key Information Stored

The column set reflects deviation detection, article comparison, and document context. The most significant columns are:

• DEVIATION_CATEGORY, DEVIATION_CODE and their meaning columns (DEVIATION_CATEGORY_MEANING, DEVIATION_CODE_MEANING) — classify the nature of each detected deviation and supply display text.
• DEVIATION_CATEGORY_PRIORITY — supports ranked ordering of deviation output.
• DEVIATION_TYPE — distinguishes deviation classes produced by the comparison engine.
• RULE_ID — the foreign key to OKC_XPRT_RULE_HDRS_ALL; identifies the rule header under which the deviation was evaluated.
• DOCUMENT_ID, DOCUMENT_TYPE, DOCUMENT_VALUE — identify the contract or document being assessed.
• DOC_ARTICLE_ID, DOC_ARTICLE_VERSION_ID and the reference pair REF_ARTICLE_ID, REF_ARTICLE_VERSION_ID — the compared article and its reference standard.
• ORIG_ARTICLE_ID, ARTICLE_TITLE, ARTICLE_DESCRIPTION, ARTICLE_STATUS, SECTION_HEADING, LABEL, SCN_LABEL — descriptive metadata for the article line.
• MANDATORY_FLAG, COMPARE_TEXT_FLAG, LOCK_TEXT_MOD_FLAG — control flags governing comparison and text modification behavior.
• SEQUENCE_ID, SCN_SEQUENCE, ART_SEQ_ID, DISPLAY_SEQUENCE, LINE_NUMBER — ordering and positional attributes for rendering results.
• SCN_ID, OBJECT_TYPE, OBJECT_CODE, OBJECT_DESCRIPTION, ITEM_NAME, ITEM_DESCRIPTION — association and object identity attributes.
• CONFIG_HEADER_ID, CONFIG_REVISION_NUMBER, CREATION_DATE — configuration linkage and record creation context.

The documented metadata does not name a surrogate primary key column or a unique index. Business-key candidates among the documented columns would likely involve the combination of RULE_ID with DOC_ARTICLE_ID and DOC_ARTICLE_VERSION_ID, or DOCUMENT_ID with LINE_NUMBER, but no unique constraint is confirmed in the supplied ETRM extract.

Common Use Cases and Queries

The table supports deviation reporting on contract terms, clause compliance reviews, and diagnostics of rule evaluation output. Typical access patterns filter by document, rule, or deviation category and order by the sequence columns. A representative query joins the rule header for rule context:

• SELECT d.DEVIA TION_CODE, d.DEVIATION_CATEGORY, d.DOC_ARTICLE_ID, d.LINE_NUMBER FROM OKC.OKC_TERMS_DEVIATIONS_T d WHERE d.DOCUMENT_ID = :doc_id ORDER BY d.DISPLAY_SEQUENCE, d.LINE_NUMBER;
• Joining rules: SELECT r.RULE_ID, d.DEVIATION_TYPE, d.DEVIATION_CODE FROM OKC.OKC_TERMS_DEVIATIONS_T d, OKC.OKC_XPRT_RULE_HDRS_ALL r WHERE d.RULE_ID = r.RULE_ID AND d.MANDATORY_FLAG = 'Y';
• Aggregation for compliance summaries: SELECT DEVIATION_CATEGORY, COUNT(*) FROM OKC.OKC_TERMS_DEVIATIONS_T WHERE DOCUMENT_ID = :doc_id GROUP BY DEVIATION_CATEGORY;

Because the object is temporary, queries should be scoped to the active processing session or document and should not be relied upon for historical trend reporting without persisting results elsewhere.

Related Objects

The following objects are the most significant in relation to this table, based on the documented foreign key and Contracts Core dependencies:

• OKC_XPRT_RULE_HDRS_ALL — referenced via OKC_TERMS_DEVIATIONS_T.RULE_ID; the rule header defining deviation evaluation.
• OKC_TERMS_DEVIATIONS — the non-temporary counterpart commonly used to persist deviation results.
• OKC_XPRT_RULE_LINES / OKC_XPRT_RULE_LINE_VALUES — rule detail lines that drive comparison logic.
• OKC_ARTICLES_ALL / OKC_ARTICLES_TL — article definitions underlying DOC_ARTICLE_ID and REF_ARTICLE_ID.
• OKC_CONTRACT_HEADERS / OKC_K_HEADERS_ALL — contract and document headers referenced by DOCUMENT_ID.
• OKC_TERMS_UTIL and the OKC_TERMS_DEVN_PVT APIs — programmatic entry points that populate and consume this temporary table.

Together these dependencies confirm the table's role as a transient, satellite-leaning staging structure within the Contracts Core deviation lifecycle.