Results for “qp_number”

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

Overview

QP_NUMBER is a utility package in the Oracle E-Business Suite APPS schema that provides canonical numeric conversion services for the Oracle Advanced Pricing (QP) module. Its central responsibility is to translate between the internal "canonical" representation of a number — a normalized text form used for comparison and storage — and a native Oracle NUMBER value. This canonicalization capability supports pricing, qualifier, and formula processing, where numeric values frequently originate as user-entered or imported character strings that must be validated, normalized, and compared reliably regardless of locale-specific formatting.

The package maintains two session-level configuration variables that govern this conversion: canonical_mask, which defines the expected pattern for canonical strings, and decimal_char and group_separator, which describe the decimal and thousands separators in effect. Together these attributes allow QP_NUMBER to interpret and emit canonical values consistently across environments where NLS numeric formatting may differ.

Key Procedures and Functions

• CANONICAL_TO_NUMBER — Converts a canonical character representation into an Oracle NUMBER. It is the inbound path used when canonical values (for example, from pricing attributes or stored qualifier strings) must be evaluated arithmetically or compared numerically.
• NUMBER_TO_CANONICAL — Performs the inverse operation, rendering an Oracle NUMBER as its canonical character form. This is the outbound path used when numeric results must be stored or compared using the canonical convention.
• INITIALIZE — Establishes the package-level state, resolving the canonical mask and separator characters prior to conversion calls. It is typically invoked once at the start of a session or processing block to ensure the conversion routines operate against the correct NLS context.
• TEST — A diagnostic procedure provided to verify that the conversion logic behaves correctly. It is not part of the production calling contract and is intended for validation and troubleshooting.

Both conversion functions are declared with the RESTRICT_REFS pragma (WNDS, WNPS, RNDS), indicating they do not write database state and are safe for use within SQL and read-consistent contexts.

Tables Accessed

The documented ETRM metadata does not list any base tables referenced through APPS synonyms. QP_NUMBER functions primarily as a computational utility operating on package state and scalar inputs rather than performing direct DML against pricing tables. The absence of documented table references is consistent with a low-level conversion library whose callers supply and consume the values.

Usage Notes

QP_NUMBER is referenced by 25 other packages within the APPS schema, reflecting its role as a shared foundation service for numeric normalization across the pricing stack. It is typically invoked indirectly from advanced pricing APIs, pricing engine routines, and qualifier evaluation logic rather than directly by end users. Custom code that must reproduce Oracle's canonical numeric behavior should call NUMBER_TO_CANONICAL and CANONICAL_TO_NUMBER after first invoking INITIALIZE, ensuring the mask and separator state are established. Because both functions are pragma-restricted, they may be embedded in SQL statements and PL/SQL expressions wherever read-only numeric conversion is required. The API classification of OTHER indicates it is not a published, externally supported interface; consumers should treat it as an internal utility subject to change between releases. The TEST procedure is available for verifying conversion behavior in a given NLS environment.