Results for “okl_qa_data_integrity”

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

Overview

OKL_QA_DATA_INTEGRITY is an APPS-owned PL/SQL package within the Oracle E-Business Suite Lease Management (OKL) module, part of the Enterprise Territory and Revenue Management (ETRM) family of applications. Its documented API classification is OTHER, indicating that it is an internal data validation and quality assurance utility rather than a public integration API. The package serves as a centralized repository of integrity checks that verify the consistency, completeness, and correctness of lease contract data across the OKL and OKC (Contracts Core) schemas.

The package is marked with a status of VALID in the ETRM 12.2.2 metadata, confirming that it compiles cleanly and is actively deployed. It is referenced by two other packages, OKL_CONTRACT_BOOK_PVT and OKL_LA_SALES_TAX_PVT, which indicates that booking and sales tax processing routines depend on the validation logic exposed here. In the broader architectural context, OKL_QA_DATA_INTEGRITY acts as a gatekeeper that ensures lease contract structures, stream types, asset associations, and financial components conform to expected business rules before downstream processing occurs.

Key Procedures and Functions

The package exposes 45 documented procedures and functions, each targeting a specific validation domain within lease contracts. Representative members include:

• CHECK_VARIABLE_RATE — validates that variable interest rate configurations on lease contracts are properly defined.
• CHECK_PREFUNDING_STATUS — verifies the status of pre-funding arrangements associated with a contract.
• CHECK_ADVANCED_RENTALS — confirms that advanced rental amounts and schedules are consistent.
• CHECK_FEE_LINES — inspects fee lines on the contract for completeness and validity.
• CHECK_RULE_CONSTRAINTS and CHECK_FUNCTIONAL_CONSTRAINTS — enforce rule group and functional constraint definitions attached to lease lines.
• CHECK_ACCEPTANCE_DATE and CHECK_PMNT_START_DT — validate that acceptance and payment start dates fall within permissible bounds.
• CHECK_SRVC_AMNT, CHECK_SERVICE_LINES, CHECK_COV_SERVICE_LINES, and CHECK_SERVICE_LINE_HDR — perform service amount and service line integrity checks, including covered service lines.
• CHECK_FEE_SERVICE_PAYMENT — reconciles fee and service payment relationships.
• CHECK_TAX_BOOK_COST, CHECK_CAPITAL_FEE, and CHECK_ASSET_TAX — validate tax basis, capitalized fee treatment, and asset-level tax attributes.
• CHECK_SUBSIDIES and CHECK_SUBSIDIES_ERRORS — evaluate subsidy eligibility and surface subsidy-related errors.
• CHECK_CREDIT_LINE and CHECK_INVOICE_FORMAT — confirm credit line setup and invoice formatting parameters.

These procedures are designed to be invoked individually or collectively as part of pre-processing validation routines.

Tables Accessed

The package reads from a broad set of OKC and OKL base tables and views through APPS synonyms. From Contracts Core it references OKC_K_HEADERS_B, OKC_K_ITEMS, OKC_K_LINES_B, OKC_K_PARTY_ROLES_B, OKC_LINE_STYLES_B, OKC_RULES_B, OKC_RULE_GROUPS_B, and OKC_STATUSES_B to evaluate contract header, line, party role, rule, and status data. OKL-specific objects include OKL_K_HEADERS, OKL_K_HEADERS_FULL_V, OKL_K_LINES_FULL_V, OKL_INDEX_VALUES, OKL_INDICES, OKL_PRODUCTS, OKL_PRODUCTS_V, OKL_STRM_TYPE_B, OKL_STRM_TYPE_TL, OKL_STRM_TYPE_V, OKL_STRM_TMPT_LINES_UV, OKL_SUPP_INVOICE_DTLS, OKL_TXD_ASSETS_V, and OKL_TXL_ASSETS_B. Supporting reference data comes from CSI_ITEM_INSTANCES, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, FND_LOOKUPS, OKX_VENDORS_V, and DUAL.

Usage Notes

OKL_QA_DATA_INTEGRITY is not intended for direct customer-facing calls. It is typically invoked internally by OKL_CONTRACT_BOOK_PVT during the contract booking process and by OKL_LA_SALES_TAX_PVT during sales tax calculation, ensuring that contract data is consistent before downstream financial or tax processing. Custom development that extends lease contract validation should call these procedures rather than reimplementing equivalent checks, preserving consistency with seeded EBS logic. The package also references OKC_API and OKL_API, indicating that API-layer operations may trigger validation routines.