Search Results get_user_status_name

Overview

The APPS.OZF_PRICE_LIST_PVT package is a private PL/SQL API within the Oracle E-Business Suite Trade Management (formerly Oracle Traders/Advanced Pricing) product family. It encapsulates the core business logic used to maintain price list records held in the OZF_PRICE_LIST_ATTRIBUTES entity. In Oracle EBS 12.1.1 and 12.2.2, price lists represent the foundational pricing structures that drive list prices, discounts, promotions, and qualification rules consumed by the Oracle Advanced Pricing and Order Management modules. The _PVT suffix indicates that this is a private package: it is intended for internal invocation by other public APIs and product code rather than for direct customer extension. The package operates with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema, which is consistent with EBS standards for packages that are invoked from within the APPS schema context on behalf of forms, concurrent programs, and other PL/SQL APIs. The package also declares a record type (OZF_PRICE_LIST_Rec_Type) mirroring the columns of the price list attribute table, along with a corresponding PL/SQL table type and a default fetch size constant, reflecting the standard Oracle Forms-based design pattern of bulk record handling.

Key Procedures and Functions

The ETRM metadata documents four public subprograms exposed by this package:

• CREATE_PRICE_LIST — Inserts a new price list attribute record, initializing the identifying, status, ownership, and audit columns defined in the OZF_PRICE_LIST_Rec_Type record structure. It centralizes the creation logic so that dependent APIs and forms apply consistent defaults and validation.
• UPDATE_PRICE_LIST — Modifies an existing price list attribute record. It supports controlled updates to attributes such as status, owner, and the associated QP list header, while maintaining the object version number for optimistic locking and updating the standard audit columns.
• DELETE_PRICE_LIST — Removes a price list attribute record, providing a managed deletion path that respects referential and status considerations rather than allowing direct DML against the underlying table.
• GET_USER_STATUS_NAME — Returns the display name associated with a price list's user-defined status identifier, enabling callers to translate internal status codes into user-facing labels without querying the status lookup tables directly.

Together these routines form a complete lifecycle API for price list attribute maintenance. Parameter detail is intentionally not reproduced here; callers should reference the package specification in the EBS instance for exact signatures.

Tables Accessed

The package reads and writes two documented tables, accessed through APPS synonyms:

• OZF_PRICE_LIST_ATTRIBUTES — The primary operational table storing price list attribute rows. CREATE, UPDATE, and DELETE operations act directly on this table.
• OZF_PRICE_LIST_ATTRIBUTES_S — The supplemental or translated table associated with the attributes entity. It is accessed in conjunction with the base table, typically to resolve user status names and to keep related descriptive or language-dependent data synchronized.

Both tables reside in the Trade Management schema and are exposed to APPS callers via synonyms, which is the standard EBS deployment model.

Usage Notes

OZF_PRICE_LIST_PVT is not normally invoked directly by end users or by custom code. The ETRM metadata records that it is referenced by seven other packages, confirming its role as an internal building block within the pricing API stack. Typical invocation patterns include:

• Oracle Forms — The Price List setup forms in Advanced Pricing call the private APIs through surrounding public wrapper packages to persist user actions.
• Concurrent Programs — Batch processes that generate, copy, or refresh price lists use these APIs to maintain data integrity across large volumes of price list records.
• Other PL/SQL APIs — Higher-level public packages within the OZF and QP schemas delegate create, update, and delete operations to this private layer.

Because the package is private and its comments date from the 12.0 release, its interface is considered stable but unsupported for direct customer use. Developers extending pricing functionality should call the supported public APIs instead, allowing Oracle to evolve the private implementation without breaking customizations. Any direct dependency on OZF_PRICE_LIST_PVT should be treated as a risk during upgrade from 12.1.1 to 12.2.2 or later releases.