Search Results check_item_effectivity

Overview

OKS_QA_DATA_INTEGRITY is a PL/SQL package owned by the APPS schema within Oracle E-Business Suite Release 12.1.1 and 12.2.2. Its classification in the E-Business Technical Reference Manual (ETRM) is "OTHER," reflecting its role as a centralized validation and data integrity library rather than a formal public business API. The package belongs to the Oracle Knowledge Store / Service Contracts (OKS) module family, which underpins service contract authoring, subscription management, and covered-product entitlement processing.

The primary business function of OKS_QA_DATA_INTEGRITY is to enforce consistency across the many attributes that a service contract or subscription line can reference. Rather than duplicating validation logic in each form or workflow, the OKS module centralizes checks in this package so that credit card data, billing schedules, coverage levels, customer credit holds, item effectivity, and address records are validated against the same rules.

Key Procedures and Functions

The ETRM documents 27 callable units. Representative members include:

• VAL_CREDIT_CARD — validates credit card information used in a subscription or service transaction.
• CHECK_REQUIRED_VALUES / CHECK_REQ_VALUES — verifies that mandatory descriptive or transactional attributes have been populated.
• CHECK_COVERED_LEVELS / CHECK_COVLVL_OVERLAP — ensures covered levels on a service line are valid and do not overlap inconsistently.
• CHECK_COUNTER_BASE_READING — confirms counter-based (meter) readings for service contracts.
• CHECK_TAX_EXEMPTION — determines whether tax exemption applies to the customer or transaction.
• CHECK_CUST_CREDIT_HOLD — detects whether a customer is subject to a credit hold.
• CHECK_ADDRESS — validates the address associated with a customer or party site.
• CHECK_CURR_CONV_DATE — verifies currency conversion dates fall within valid ranges.
• CHECK_ITEM_EFFECTIVITY — confirms that an item is effective for the transaction date.
• CHECK_AUTHORIZE_PAYMENT — supports payment authorization checks.
• CHECK_BILLING_SCHEDULE — validates the billing schedule defined for a contract or subscription.
• CHECK_PRODUCT_AVAILABILITY / CHECK_CUSTOMER_AVAILABILITY — confirms the product or customer is available for the requested service.
• CHECK_PM — validates preventive maintenance eligibility.
• CHECK_ITEM_INSTANCE_VALID — confirms that the referenced item instance exists and is valid.
• CHECK_SUBSCR_ELEMENT_EXIST — verifies subscription elements exist for the requested context.
• CHECK_SUBSCR_IS_SHIPABLE — determines whether a subscription element is shippable.
• CHECK_COVERED_PRODUCT — confirms the covered product is correctly associated with the service.

Tables Accessed

The package reads and, where required, writes to a defined set of APPS synonyms. Customer and party data is drawn from HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_RELATE_ALL, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_PARTIES, and HZ_PARTY_SITES. Installed base and item data come from CSI_ITEM_INSTANCES, CSI_SYSTEMS_B, MTL_SYSTEM_ITEMS, and CS_CUSTOMER_PRODUCT_STATUSES. Receivables and system setup information comes from AR_RECEIPT_METHODS and AR_SYSTEM_PARAMETERS_ALL. Concurrent program and application context is read from FND_APPLICATION, FND_CONCURRENT_PROGRAMS, and FND_CONCURRENT_REQUESTS.

Usage Notes

OKS_QA_DATA_INTEGRITY is typically invoked from the Service Contracts and Subscriptions forms, from workflow or concurrent program validation steps, and from custom PL/SQL that needs to reuse standard OKS integrity rules. Its only documented external dependency is OKC_API (Oracle Knowledge Contracts API), plus SYS.STANDARD. The ETRM records that the package is referenced by zero other packages, indicating it is an internal OKS validation library rather than a widely shared integration point. Custom code should call individual CHECK_* procedures rather than assuming a single entry point.