Search Results check_gsa_main

Overview

OE_GSA_UTIL is a utility PL/SQL package in the Oracle E-Business Suite Order Management (OE) module, owned by the APPS schema and classified as a UTIL object. The acronym GSA refers to the General Services Administration schedule, a United States federal procurement vehicle through which government and qualifying commercial customers purchase goods at pre-negotiated contract pricing. In Oracle Order Management, GSA functionality allows organizations to control eligibility for GSA pricing at the order line level, automatically apply the appropriate holds when GSA rules are violated, and release those holds once the line qualifies.

The package encapsulates the decision logic that determines whether a given order line is subject to GSA pricing rules. It evaluates the customer associated with the line, the GSA indicator state on the line, and whether the customer is a designated non-GSA entity. Beyond eligibility checks, the package also performs the operational side of the GSA control mechanism: identifying and applying holds to offending lines and releasing holds when the line becomes compliant. This design isolates GSA-specific business rules from the core order entry logic, allowing the order pricing and validation flow to invoke a small set of well-defined functions.

Key Procedures and Functions

The package exposes ten documented functions, all taking an OE_Order_Pub.Line_Rec_Type record as the primary line context unless otherwise noted.

• CHECK_GSA_MAIN — The primary entry point and orchestration function for GSA validation on an order line. It returns a VARCHAR2 result and accepts an IN OUT NOCOPY result parameter, which the user specifically searched for. It coordinates the subordinate checks and returns the consolidated outcome.
• CHECK_GSA_ENABLED — Determines whether GSA processing is enabled or applicable for the line.
• CHECK_GSA_INDICATOR — Evaluates the GSA indicator value carried on the order line.
• CHECK_GSA_CUSTOMER — Verifies whether the customer on the line qualifies as a GSA customer.
• CHECK_NONGSA_CUSTOMER — Determines whether the customer is a designated non-GSA customer.
• GET_GSA_COUNT — Returns a NUMBER count of GSA-related records associated with the line.
• GET_NONGSA_COUNT — Returns a NUMBER count of non-GSA-related records associated with the line.
• GET_HOLD_ID — Accepts a hold number and returns the corresponding hold identifier for use in hold application.
• GET_SOURCE_ID — Accepts a header identifier and returns the associated source identifier, used in hold source resolution.
• RELEASE_HOLD — Releases the GSA hold on a line, accepting the line record and an IN OUT NOCOPY result parameter and returning a VARCHAR2 status.

Tables Accessed

The package reads and writes the following tables through APPS synonyms. Customer identity and classification data is drawn from HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES_ALL, and HZ_PARTIES, which support the customer eligibility checks. Discount and pricing eligibility information is accessed via OE_DISCOUNTS, OE_DISCOUNT_CUSTOMERS, OE_DISCOUNT_LINES, and OE_PRICE_BREAK_LINES, which underpin the count and adjustment logic. Hold management uses OE_ORDER_HOLDS, OE_HOLD_DEFINITIONS, OE_HOLD_SOURCES, OE_HOLD_RELEASES, and OE_HOLD_RELEASES_S for creating, sourcing, and releasing holds. DUAL is referenced for scalar evaluations.

Usage Notes

OE_GSA_UTIL is invoked indirectly rather than directly by end users. The Order Management order entry forms and the Order Management public APIs call the GSA check functions during line validation, pricing, and save processing, at which point holds may be applied or released automatically. The package is referenced by two other packages, confirming that it is embedded in a broader validation chain rather than called in isolation. Because the functions rely on the OE_Order_Pub.Line_Rec_Type record structure, custom code invoking this package must populate a compatible line record. In Oracle EBS 12.1.1 and 12.2.2, the package remains an internal utility; the header comment indicates a noship designation, and the source carries a 2005 revision. Developers should treat OE_GSA_UTIL as an internal dependency of the Order Management GSA feature and avoid direct invocation unless performing controlled extensions.