Search Results oe_price_lists




Overview
Explore in AI Chat

Overview

OE_PRICE_LISTS is a pricing-related data object surfaced in the Oracle E-Business Suite 12.1.1 and 12.2.2 documentation under the QP (Advanced Pricing) product, despite the "OE_" prefix that historically associates it with the Order Entry module. In the ETRM repository the object is catalogued as a table with the primary key constraint OE_PRICE_LISTS_PK, defined on the single column PRICE_LIST_ID. The ETRM excerpt explicitly records the implementation status as "Not implemented in this database," indicating that within the sampled environment the object is not instantiated as a physical database segment and is likely a legacy, obsolete, or reserved definition retained in the application metadata layer.

From a modeling perspective, the supplied relationship metadata classifies the object as standalone, derived heuristically from the absence of foreign key participation in the mined FK structure. Interpreted through Data Vault conventions, this suggests treating OE_PRICE_LISTS as a hub candidate, with PRICE_LIST_ID functioning as the business key that would anchor the hub. No link relationships are documented, which is consistent with the standalone classification: the object neither references nor is referenced by other keys in the captured schema.

Key Information Stored

The documented metadata for OE_PRICE_LISTS is deliberately sparse. The only column explicitly identified is PRICE_LIST_ID, which participates in the primary key constraint OE_PRICE_LISTS_PK. In the ETRM record this serves as both the surrogate identifier for the row and the sole documented business-key candidate, since no additional unique indexes are enumerated in the provided metadata.

Beyond PRICE_LIST_ID, the ETRM excerpt does not disclose column-level definitions. Consequently, no further columns should be asserted as documented facts. In functional terms, a price list identifier of this nature conventionally keys attributes such as price list name, currency, rounding rules, effective dates, and active status flags; however, the supplied metadata does not confirm the presence of any of these attributes in OE_PRICE_LISTS. Consumers of this reference should regard the column inventory as limited to PRICE_LIST_ID unless verified against the live data dictionary in a specific environment.

Common Use Cases and Queries

Because the object is recorded as "Not implemented in this database," the principal practical use case is diagnostic and inventory-oriented. Technical teams performing upgrade assessments between 12.1.1 and 12.2.2 can use the ETRM entry to confirm whether OE_PRICE_LISTS exists as a physical segment, whether it is a synonym or view alias, and whether legacy customizations or interfaces still reference it. The following patterns reflect typical verification queries:

  • Confirming physical presence: SELECT table_name, tablespace_name, num_rows FROM dba_tables WHERE table_name = 'OE_PRICE_LISTS';
  • Validating the documented primary key: SELECT constraint_name, constraint_type, column_name FROM dba_cons_columns WHERE table_name = 'OE_PRICE_LISTS' AND constraint_name = 'OE_PRICE_LISTS_PK';
  • Checking dependency usage by stored code: SELECT name, type, referenced_name FROM dba_dependencies WHERE referenced_name = 'OE_PRICE_LISTS';
  • Detecting synonyms created by customizations: SELECT owner, synonym_name, table_name FROM dba_synonyms WHERE table_name = 'OE_PRICE_LISTS';

For reporting, where the object is instantiated, price list identifiers are commonly joined to pricing qualifier and list-line tables to build price list matrices and effective-dating reconciliations. In the absence of confirmed column definitions, such reports should be validated against the actual dictionary before publication.

Related Objects

The provided metadata documents no foreign key relationships for OE_PRICE_LISTS, and the heuristic relationship classification is standalone. Accordingly, no join partners can be asserted from documented facts. In practice, where a physical price list structure exists in an Advanced Pricing implementation, the objects most frequently examined alongside a price list header are:

These references are contextual only; the ETRM record does not document key relationships to OE_PRICE_LISTS, and any integration model should rely on verified constraints from the target database instance rather than assumption.