Search Results g_rule_dependent_value

Overview

OKC_QA_DATA_INTEGRITY is a validation and diagnostic package belonging to the Oracle Contracts (OKC) module of Oracle E-Business Suite. Its primary purpose is to verify the internal consistency and completeness of contract data stored across the OKC schema. The package name — "QA" for quality assurance and "DATA_INTEGRITY" — signals that it is designed to detect violations of business rules that govern how contract headers, lines, parties, rules, and rule groups relate to one another. Unlike the OKC_API package, which performs transactional operations such as creating and modifying contracts, OKC_QA_DATA_INTEGRITY is a read-oriented inspection utility. It raises descriptive error messages when it encounters structural or referential problems in contract data.

The package declares a comprehensive set of global message constants that map to Oracle Application Object Library (AOL) message names, including tokens such as G_REQUIRED_RULE, G_REQUIRED_RULE_VALUES, G_REQUIRED_RULE_GROUP, G_REQUIRED_RULE_PARTY_ROLE, G_RULE_DEPENDENT_VALUE, G_INVALID_LINE_DATES, G_INVALID_COVERAGELINE_DATES, G_REQUIRED_LINE_VALUE, and G_INVALID_LINE_CURRENCY. These constants reveal the categories of defects the package is built to surface: missing mandatory rules or rule values, orphaned party-role assignments, mismatched dependent values, and invalid or missing date ranges on contract lines and coverage lines. The declarations use AUTHID CURRENT_USER, so the package executes with the privileges of the calling user rather than the package owner.

The package header carries the header string OKCRQADS.pls, revision 120.0, dated 2005/05/25, with the "noship" flag, confirming it is an internal development artifact rather than a customer-facing API.

Key Procedures and Functions

The ETRM metadata documents five procedures and functions within the package. Their purposes, inferred from naming conventions and associated message constants, are as follows:

• CHECK_REQUIRED_VALUES — The procedure most directly associated with the user's search term. It verifies that contractual elements that are mandatory under the configured rule definitions are actually populated. It draws on message constants such as G_REQUIRED_RULE_VALUES and G_REQUIRED_LINE_VALUE to report missing rule values or required line-level fields.
• CHECK_ART_COMPATIBLE — Validates that article combinations and associated rule definitions are compatible, ensuring that articles assigned to a contract do not conflict with one another or with the governing rule set.
• CHECK_RULE_GROUPS — Examines rule groups (OKC_RULE_GROUPS_B) and their member rules to confirm that groups are properly formed, that required rules within a group are present, and that group-level dependencies are satisfied.
• CHECK_RULE_GROUP_PARTIES — Verifies that party roles referenced by rule groups correspond to valid contract party roles, and that party-role assignments required by a rule group have not been deleted or left orphaned.
• CHECK_EFFECTIVITY_DATES — Confirms that start and end dates on headers, lines, and coverage lines form valid ranges, guarding against end dates earlier than start dates or other date inconsistencies.

Tables Accessed

The package reads across the principal OKC contract tables and their supporting setup tables. Contract structure is obtained from OKC_K_HEADERS_B, OKC_K_LINES_B, OKC_K_ARTICLES_B, and OKC_CONTACTS, while party-role information is read from OKC_K_PARTY_ROLES_B. Rule configuration is sourced from OKC_RULES_B, OKC_RULE_DEFS_B, OKC_RULE_GROUPS_B, OKC_RG_DEF_RULES, OKC_RG_PARTY_ROLES, and OKC_RG_ROLE_DEFS. Date and interval validation relies on OKC_COVER_TIMES and OKC_REACT_INTERVALS, with line style and flexfield metadata obtained from OKC_LINE_STYLES_TL and FND_DESCR_FLEX_COLUMN_USAGES. Collectively these tables supply the reference data needed to compare actual contract records against expected rule-driven configuration.

Usage Notes

OKC_QA_DATA_INTEGRITY is typically invoked as a background consistency check rather than as part of normal contract entry. It can be called from concurrent programs, from diagnostic or correction scripts executed in SQL*Plus, or from custom PL/SQL wrappers that scan subsets of contracts before migration, upgrade, or data repair activities. Because the package is not referenced by any other documented package, it is not part of the standard runtime call graph and is not invoked automatically by OKC forms. Its AUTHID CURRENT_USER declaration means the invoking schema must possess appropriate SELECT privileges on the OKC tables. Errors are surfaced through AOL messages declared as constants, allowing callers to trap and report specific integrity failures. Customers upgrading between 12.1.1 and 12.2.2 should treat the package as an internal diagnostic utility; it is not a supported extension point, and custom code invoking it must be validated against each release.