Results for “oe_blanket_headers”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OE_BLANKET_UTIL_MISC is a utility package body in the APPS schema that supports the Oracle Order Management blanket sales agreement functionality. Blanket sales agreements in Oracle EBS represent long-term commitments between a customer and a supplier, capturing negotiated pricing, item lists, and quantity thresholds that govern subsequent release orders. The package provides supplementary utility logic used by the blanket agreement processing flow rather than serving as a public application programming interface. Its API classification is documented as OTHER, indicating that it is an internal helper package rather than a formal, externally supported interface.

In Oracle EBS 12.1.1 and 12.2.2, this package is registered as VALID within the ETRM repository. It depends on core Order Management infrastructure packages, including FND_API for the standard API return status conventions, OE_MSG_PUB for message stack handling, and OE_DEBUG_PUB for debug logging and diagnostics. It also references the STANDARD package owned by SYS, which supplies standard PL/SQL constructs and assertion utilities.

Key Procedures and Functions

The ETRM metadata documents a single procedure or function on this package:

• GET_BLANKETAGRNAME — Retrieves the blanket agreement name associated with a blanket agreement record. This routine resolves the descriptive name of a blanket agreement from its identifying information, enabling callers to present or log the agreement name rather than its internal identifier. It is consistent with the package's role as a lookup and formatting helper for blanket header data.

No parameter lists are documented for this routine, and none should be assumed. Additional private or undocumented helpers may exist in the package body, but the ETRM repository records only GET_BLANKETAGRNAME as the documented entry point.

Tables Accessed

The package accesses one documented table through APPS synonyms:

• OE_BLANKET_HEADERS — The header table for blanket sales agreements. It stores the agreement-level attributes, including the agreement number, name, customer, currency, pricing and shipping terms, and status. GET_BLANKETAGRNAME reads from this table to resolve the agreement name for a given blanket agreement. This is the same base table exposed by the user-facing oe_blanket_headers search term, which is why queries on that name commonly surface this package as a dependent object.

The package does not appear to write to OE_BLANKET_HEADERS; its documented behavior is read-oriented name resolution.

Usage Notes

OE_BLANKET_UTIL_MISC is not referenced by any other database object in the ETRM dependency listing, but it is recorded as referenced by four other packages. This means it is consumed as a utility by peer packages in the Order Management suite rather than being called directly from forms or concurrent programs.

Typical invocation occurs within the blanket agreement processing flow — for example, when an internal routine needs the printable or displayable name of a blanket agreement while validating or constructing release orders. Because it is an internal utility with an OTHER classification, it is not a supported integration point. Custom code should not bind directly to it; instead, customizations should use supported Order Management APIs or query OE_BLANKET_HEADERS directly for read-only reporting. On upgrades from 12.1.1 to 12.2.2, the package remains VALID and retains the same dependency profile, so no remediation is normally required.