Search Results get_credit_check_level

Overview

OE_CREDIT_CHECK_UTIL is a utility package in the Oracle Order Management (OM) credit checking subsystem within Oracle E-Business Suite 12.1.1 and 12.2.2. It resides in the APPS schema and is classified as a UTIL API, meaning it provides shared helper logic rather than a standalone business transaction entry point. Its primary purpose is to centralize the low-level operations that support credit evaluation of sales orders: retrieving credit limits and exposures, resolving usage balances, converting transaction values into the functional currency, evaluating credit check rules, and dispatching credit hold notifications. Because these operations are reused by many components of the credit engine, the package acts as a common substrate beneath the higher-level credit check APIs such as OE_CREDIT_CHECK_ORDER_PVT, OE_CREDIT_CHECK_LINES_PVT, OE_CREDIT_CHECK_PVT, and OE_CREDIT_EXPOSURE_PVT.

For users investigating the search term "oe_holds_pvt", OE_CREDIT_CHECK_UTIL is directly relevant: it references OE_HOLDS_PVT (the hold application utility) to apply or release credit-related order holds, and it is itself referenced by OE_HOLDS_PVT. This bidirectional relationship confirms that credit checking and hold management share utility logic for determining whether a business event should place an order on hold.

Key Procedures and Functions

The documented API surface comprises 23 procedures and functions. The core credit evaluation routines include GET_LIMIT_INFO, which returns credit limit details for a customer or customer site; GET_USAGES, which retrieves current exposure or usage balances; GET_ITEM_LIMIT, which obtains item-level credit limits; and GET_GLOBAL_EXPOSURE_FLAG, which indicates whether global exposure rules apply. GET_SYSTEM_PARAMETERS and GET_CREDIT_CHECK_RULE retrieve the configured credit checking parameters and the applicable credit check rule for a transaction, while GET_CREDIT_CHECK_RULE_ID and GET_CREDIT_CHECK_LEVEL return the rule identifier and the level (order, line, or customer) at which checking occurs.

Amount and currency handling is performed by ROUNDED_AMOUNT, GET_TRANSACTION_AMOUNT, CONVERT_CURRENCY_AMOUNT, GET_GL_CURRENCY, and CURRENCY_LIST. Exposure and aging logic is provided by GET_PAST_DUE_INVOICE, GET_ORDER_EXPOSURE, and GET_EXTERNAL_TRX_AMOUNT, which derives exposure from external (non-order) transactions such as receivables. Notification is handled by SEND_CREDIT_HOLD_NTF, which dispatches the credit hold notification workflow or message. Supporting routines include CHECK_DEBUG_FLAG for diagnostic tracing, CHECK_DRAWEE_EXISTS for validating drawee information, and GET_DRAWEE_SITE_USE_ID for resolving a drawee site use identifier.

Tables Accessed

The package reads and writes a set of operational and setup tables through APPS synonyms. HZ_CREDIT_PROFILES and HZ_CREDIT_PROFILE_AMTS supply credit profile definitions and limit amounts. OE_CREDIT_CHECK_RULES and OE_HOLD_SOURCES provide the credit rule configuration and hold source definitions used in hold application. OE_ORDER_HEADERS and OE_ORDER_LINES_ALL hold the transaction being evaluated. GL_DAILY_CONVERSION_TYPES supports currency conversion rate type lookup. Exposure and receivables data are sourced from AR_CASH_RECEIPTS_ALL, AR_CASH_RECEIPT_HISTORY, AR_CASH_RECEIPT_HISTORY_ALL, AR_PAYMENT_SCHEDULES, AR_PAYMENT_SCHEDULES_ALL, AR_RECEIVABLE_APPLICATIONS, and AR_RECEIVABLE_APPLICATIONS_ALL. FND_USER is referenced for user context, and FND_PROFILE for profile option values.

Usage Notes

OE_CREDIT_CHECK_UTIL is not intended for direct invocation by end users. It is called internally by the Oracle Order Management credit checking engine during order entry and order import processing, and by concurrent programs such as credit exposure and credit check reporting (OE_CREDIT_CHECK_RPT). The documented dependency list shows it is referenced by 15 packages, including OE_CREDIT_CHECK_ORDER_PVT, OE_CREDIT_CHECK_LINES_PVT, OE_CREDIT_EXPOSURE_PVT, OE_CREDIT_INTERFACE_UTIL, OE_HEADER_UTIL, OE_LINE_UTIL, and HZ_CREDIT_REQUEST_PVT. Customizations that require credit limit, exposure, currency conversion, or hold source logic should call the supported higher-level credit check APIs rather than this utility package, since its signatures are not published as a stable public interface. When orders are unexpectedly placed on credit hold, DBAs and developers commonly trace execution through OE_CREDIT_CHECK_UTIL to OE_HOLDS_PVT to identify the rule and hold source applied.