Search Results oe_discount_customers

Overview

OE_GSA_UTIL is a utility package body in the APPS schema that supports the Oracle E-Business Suite Order Management GSA (General Services Administration) compliance feature. GSA processing exists to ensure that orders placed against negotiated federal supply schedules are repriced and validated against the correct contract terms, and that orders which violate those terms are held from further processing. The package encapsulates the reusable validation and hold-management logic on which the GSA pricing engine and the related discount and hold modules depend.

The package is classified as a UTIL API, meaning it is not an externally directed business API but an internal helper invoked by other Order Management code. Its documented dependants confirm this role: OE_ORDER_PUB, OE_DISCOUNTS, OE_HOLD_DEFINITIONS, and OE_MSG_PUB all rely on it for GSA checks, hold lookup, and hold release. Because it references OE_PRICE_BREAK_LINES directly, it is also associated with the price break resolution used when qualifying a GSA order line against the applicable price list. The package body is VALID in the target environment.

Key Procedures and Functions

Ten procedures and functions are documented:

• CHECK_GSA_MAIN — the primary entry point that orchestrates the GSA validation sequence for an order or line, invoking the subordinate checks.
• CHECK_GSA_ENABLED — determines whether GSA processing is active for the current operating context, typically by profile option evaluation.
• CHECK_GSA_INDICATOR — evaluates the GSA-related indicator on the transaction to determine whether GSA rules apply.
• CHECK_GSA_CUSTOMER — verifies whether the customer or ship-to is a GSA-eligible entity.
• GET_NONGSA_COUNT — returns a count of non-GSA lines or entities, used to detect mixed orders.
• CHECK_NONGSA_CUSTOMER — validates the non-GSA customer condition, the complement of CHECK_GSA_CUSTOMER.
• GET_GSA_COUNT — returns a count of GSA-qualifying lines or entities.
• GET_HOLD_ID — resolves the hold definition identifier to be applied to a GSA-violating order.
• GET_SOURCE_ID — resolves the hold source identifier associated with the GSA hold.
• RELEASE_HOLD — removes the GSA hold once the condition is satisfied, writing through the hold release tables.

Tables Accessed

Customer classification reads flow through HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES_ALL, and HZ_PARTIES, supplying the customer and site attributes consumed by CHECK_GSA_CUSTOMER and CHECK_NONGSA_CUSTOMER. Pricing qualification uses OE_PRICE_BREAK_LINES together with OE_DISCOUNTS, OE_DISCOUNT_CUSTOMERS, and OE_DISCOUNT_LINES to resolve eligible price breaks and modifiers. Hold management writes and reads OE_HOLD_DEFINITIONS, OE_HOLD_SOURCES, OE_HOLD_RELEASES, and the OE_HOLD_RELEASES_S sequence, with the applied hold persisted in OE_ORDER_HOLDS. DUAL and the STANDARD package supply scalar evaluation. The package also depends on the FND_API, FND_GLOBAL, FND_MESSAGE, FND_PROFILE, OE_DEBUG_PUB, OE_MSG_PUB, and OE_ORDER_PUB APIs for messaging, environment context, and order-level access.

Usage Notes

OE_GSA_UTIL is invoked internally by Order Management rather than directly by end users. Typical call paths include order entry and order import processing, where OE_ORDER_PUB invokes the GSA checks during pricing and validation, and the pricing engine, where discount and price break logic calls the same routines to confirm GSA eligibility before applying modifiers. The hold-related routines are exercised during order booking and hold release processing, including the Order Management forms where a user releases a GSA hold. Customizations should treat this package as a dependent internal utility: direct invocation is generally unnecessary, and any extension should call the public OE_ORDER_PUB and hold APIs so that GSA validation, messaging, and hold bookkeeping remain consistent with the standard flows in both 12.1.1 and 12.2.2.