Search Results get_pricing_attributes




Overview

OKS_EXTWAR_UTIL_PVT is a private utility package in the Oracle E-Business Suite Service Contracts (OKS) module. The "EXTWAR" naming convention denotes its role as an extended warranty processing utility, providing shared PL/SQL logic consumed by other service contracts packages and APIs rather than being invoked directly by end users. Its documented header carries the revision marker OKSRUTLS.pls 120.10, and the package declares a comprehensive set of global constants and message tokens inherited from OKC_API, including g_required_value, g_invalid_value, g_unexpected_error, and g_uppercase_required, along with a global exception g_exception_halt_validation. Logging constants are drawn from FND_LOG levels, and g_app_id is fixed at 515, the Service Contracts application identifier. Although the user search term was "calculate_rev_rec," no procedure of that name appears in the documented procedure list; revenue recognition calculation in Service Contracts is ordinarily handled through other billing and accounting APIs, and the closest documented capability here is CREATE_BILLING_SCHEDULE.

Key Procedures and Functions

The package exposes approximately 30 documented procedures and functions covering warranty validation, contract retrieval, billing, and sales credit processing:

Tables Accessed

The package reads and writes across several EBS schemas via APPS synonyms. Installation and inventory context come from CSI_ITEM_INSTANCES, MTL_SYSTEM_ITEMS_TL, and HR_ALL_ORGANIZATION_UNITS. Customer and contact data are sourced from HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, and OKC_CONTACTS. Sales representative information is drawn from JTF_RS_SALESREPS and JTF_RS_RESOURCE_EXTNS, with credit records written to OE_SALES_CREDITS. Order and contract linkage relies on OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL, OKC_K_GRPINGS, FND_CURRENCIES, and FND_LOOKUP_VALUES.

Usage Notes

As a PVT-classified package, OKS_EXTWAR_UTIL_PVT is not a public API and Oracle does not guarantee its signature across releases; the revision history confirms signature changes over time. It is referenced by 31 other packages, indicating extensive internal reuse across the Service Contracts code base. It is typically invoked indirectly through Service Contracts forms, concurrent programs, and public APIs such as the OKS contract authoring flows, and through order-to-contract integration for extended warranty lines. Developers should not call private procedures directly in customisations; where a specific capability such as revenue recognition calculation is required, the supported public API for that business function should be identified instead.