Search Results credit_check_processor

Overview

The APPS.OE_CREDIT_CHECK_RPT package is a server-side PL/SQL package within the Oracle E-Business Suite Order Management (OM) module. Its principal business function is to perform credit checking for a batch of sales orders and to support the reporting of customer credit exposure. The package is declared with AUTHID CURRENT_USER, meaning its procedures execute with the privileges of the invoking user and rely on the APPS synonym layer to resolve referenced objects. It is most commonly associated with the Credit Check Processor report, which drives the batch credit verification process against sales orders before fulfillment. The package name surfaces in searches for the term credit_check_processor because its central procedure carries that exact name and serves as the documented entry point for the batch credit check routine. By consolidating credit checking logic, unchecked exposure calculation, and shared reporting utilities, the package provides a reusable foundation for the Order Management credit management workflow.

Key Procedures and Functions

• CREDIT_CHECK_PROCESSOR — The primary public procedure that performs credit checking for a batch of sales orders. According to the embedded comments, it is the server PL/SQL procedure invoked by the Credit Check Processor report. Its parameters support filtering by operating unit (profile org), customer profile class range, party name range, customer account number range, order date range, a specific order header, and an order-by clause, allowing the concurrent report to narrow the population of orders checked.
• GET_UNCHECKED_EXPOSURE — A public procedure that calculates unchecked exposure in the base currency for a given customer. As documented, it accepts parameters identifying the party, the customer, the bill-to site, the operating unit's base currency, and a table of all unchecked currencies, and it returns the computed unchecked exposure. This supports accurate credit limit evaluation where exposure has not yet been fully recognized.
• CREDIT_EXPOSURE_REPORT_UTILS — A documented utility routine supporting credit exposure reporting, providing shared logic used in conjunction with the credit check and exposure reporting processes.

Tables Accessed

The package accesses a broad set of Order Management, Receivables, and Trading Community Architecture tables via APPS synonyms:

• Credit rule and profile tables — OE_CREDIT_CHECK_RULES, HZ_CUSTOMER_PROFILES, HZ_CUST_PROFILE_AMTS, and HZ_CUST_PROFILE_CLASSES supply the credit limits, rules, and profile classifications used to evaluate an order.
• Customer and party tables — HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNTS_ALL, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_HIERARCHY_NODES, and HZ_PARTIES identify the customer, site, and hierarchy relationships relevant to the credit decision.
• Working and temporary tables — OE_CC_PROCESSOR_TEMP and OE_CREDIT_EXPOSURE_TEMP store intermediate results generated during batch processing and exposure calculation.
• Supporting objects — FND_CURRENCIES provides currency information; DBMS_SQL and PLITBLM support dynamic SQL and PL/SQL table manipulation within the package logic.

Usage Notes

The package is typically invoked through the Credit Check Processor concurrent program in Order Management, which calls CREDIT_CHECK_PROCESSOR to evaluate batches of orders against configured credit rules. It is referenced by two other packages, indicating reuse by additional credit or order management components. Custom code should call the documented procedures rather than duplicating credit logic, since the package encapsulates the standard exposure and credit-check calculations. Because the package runs with AUTHID CURRENT_USER, callers must ensure appropriate APPS synonym access and privileges. In Oracle EBS 12.1.1 and 12.2.2 environments, the package is delivered as an APPS-owned object and should be treated as standard, non-modifiable code; extensions are best implemented through supported APIs or by invoking these procedures directly.