Search Results get_column_label




Overview
Explore in AI Chat

Overview

OE_AUDIT_HISTORY_PVT is a private PL/SQL package in the APPS schema that supports Oracle Order Management's order audit history and descriptive flexfield value resolution within Oracle E-Business Suite 12.1.1 and 12.2.2. Its primary business purpose is to record, retrieve, and interpret historical changes to order header and line attributes, including context-sensitive flexfield segments and payment card attributes, so that users can reconstruct the evolution of an order over time. The package also provides a family of utility functions that translate stored attribute identifiers into human-readable values, display names, column labels, and translated descriptions for the Order Management and Order Capture user interfaces.

The _PVT suffix denotes that the package is private to the application and is not a published, supported public API. It is typically invoked by other Order Management packages, Oracle Forms, and concurrent programs rather than directly by customer extensions. This is consistent with the documented note that it is referenced by two other packages.

Key Procedures and Functions

The package exposes thirteen documented program units. The principal concurrent-program entry points are:

  • SET_ATTRIBUTE_HISTORY — the main audit-history population routine. It accepts retcode and errbuf (standard concurrent program parameters), an operating unit, a date range, an order number range, and an audit duration, and it processes the audited attribute changes for the specified orders.
  • RECORD_SET_HISTORY — added for bug#5631508, records set (configuration) history for a given header, line, and set combination.
  • DELETE_SET_HISTORY — the companion routine, added for the same bug, that removes set history rows for a given line.

Supporting utility functions include:

  • ID_TO_VALUE — converts an attribute ID and stored value into the corresponding display value, optionally scoped by context value and organization.
  • GET_VALUESET_ID_R — retrieves the value set ID, format type, and validation type for a named flexfield segment and context.
  • GET_ATTRIBUTE_VALUE — the function most directly relevant to the search term get_card_attribute_value. It resolves a flexfield attribute value given a flexfield name, context, segment, value, and optional comparison operator.
  • GET_CARD_ATTRIBUTE_VALUE — resolves a stored credit-card-related attribute value, using the payment card infrastructure.
  • COMPARE_CREDIT_CARD — supports comparison of credit card attributes against stored history.
  • VALUE_EXISTS_IN_TABLE — validates whether a supplied value exists in a validation table, returning the associated ID and value.
  • GET_DISPLAY_NAME, GET_COLUMN_LABEL, and GET_TRANSLATED_VALUE — return display names, column labels, and translated flexfield values for presentation.
  • INVENTORY_ITEM — resolves inventory item-related attribute information.

Because only the package specification is documented, parameter lists should be treated as indicative; callers should verify signatures against the deployed source for the specific patch level.

Tables Accessed

The package reads and writes the Order Management audit tables OE_AUDIT_ATTR_HISTORY, OE_ORDER_HEADER_HISTORY, and OE_SETS_HISTORY, with current state from OE_ORDER_HEADERS_ALL and OE_SETS. Flexfield metadata and validation are resolved through FND_FLEX_VALIDATION_TABLES (referenced as fnd_vset.table_r). Party and customer context come from HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES_ALL, HZ_PARTIES, and FND_USER, while IBY_CREDITCARD_H supplies payment card data. Inventory attributes are resolved via MTL_SYSTEM_ITEMS_KFV, and constraint and responsibility data via OE_PC_CONSTRAINTS and FND_RESPONSIBILITY_TL. Dynamic SQL is executed using DBMS_SQL.

Usage Notes

SET_ATTRIBUTE_HISTORY is normally registered as a concurrent program and scheduled to batch-process audit history for a date and order-number range. RECORD_SET_HISTORY and DELETE_SET_HISTORY fire from Order Management set processing. The value-resolution functions are called from Order Management and Order Capture forms and from other private packages that render flexfield, credit card, and item attributes in the UI. Custom code invoking this package should account for its private classification and revalidate signatures after patching, since private packages may change between 12.1.1 and 12.2.2 without a public API compatibility guarantee.