Results for “qp_price_req_sources_v”

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

Overview

QP_PRICE_REQ_SOURCES_V is a documented Oracle EBS Advanced Pricing (QP) view owned by the APPS schema. It exposes the relationship between pricing request types and the source systems that supply pricing requests to Oracle Advanced Pricing. The view is a thin join layer defined over two PTE (Pricing Transaction Entity) configuration tables and is registered in ETRM with a status of VALID for both 12.1.1 and 12.2.2. Its role is primarily read-only reporting and integration: it allows external pricing engines, custom concurrent programs, and integration middleware to resolve which source system codes are valid for a given pricing request type without querying the underlying base tables directly. Because the view presents the SOURCE_SYSTEM_CODE, which corresponds to the APPLICATIONS_SHORT_NAME of the registered source system, it is a convenient lookup for resolving "source_system_code" queries during price request processing.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through synonyms in the APPS schema:

• QP_PTE_REQUEST_TYPES_B (SYNONYM) — the base table that stores pricing request type definitions, keyed by PTE_CODE and exposing REQUEST_TYPE_CODE.
• QP_PTE_SOURCE_SYSTEMS (SYNONYM) — the base table that enumerates the source systems configured for each PTE, exposing PTE_CODE and APPLICATION_SHORT_NAME.

The defining SQL text is a simple inner join:

SELECT QP_PTE_RT.REQUEST_TYPE_CODE,
       QP_PTE_SS.APPLICATION_SHORT_NAME SOURCE_SYSTEM_CODE
  FROM QP_PTE_REQUEST_TYPES_B QP_PTE_RT,
       QP_PTE_SOURCE_SYSTEMS QP_PTE_SS
 WHERE QP_PTE_RT.PTE_CODE = QP_PTE_SS.PTE_CODE

The join on PTE_CODE means that only request types having at least one configured source system appear in the view. If a request type exists in QP_PTE_REQUEST_TYPES_B but has no corresponding rows in QP_PTE_SOURCE_SYSTEMS, it is excluded. This design intentionally surfaces only valid source system assignments.

Key Columns

The view exposes exactly two columns as documented in ETRM:

• REQUEST_TYPE_CODE — the pricing request type identifier carried from QP_PTE_REQUEST_TYPES_B. It identifies the category or type of pricing request (for example, a specific integration or processing path) that Oracle Advanced Pricing recognizes.
• SOURCE_SYSTEM_CODE — an alias for APPLICATIONS_SHORT_NAME from QP_PTE_SOURCE_SYSTEMS. It identifies the calling or originating application by its Oracle Applications short name (for example, OE, ONT, or another EBS module). This is the value commonly searched as "source_system_code".

There is no PTE_CODE exposed on the view, so consumers must rely on the request type and source system code pairing. Because the view is not key-preserved with respect to a single base table, it is intended for querying only, not for DML.

Common Use Cases and Queries

The view is typically used to validate or enumerate which source systems may submit requests for a given pricing request type. A common pattern is:

SELECT REQUEST_TYPE_CODE, SOURCE_SYSTEM_CODE
  FROM APPS.QP_PRICE_REQ_SOURCES_V
 WHERE SOURCE_SYSTEM_CODE = :p_source_system_code;

Integration teams use it to confirm that a calling application's short name is registered for the expected request type before invoking the pricing engine. Reporting users enumerate all valid request type/source system pairs with a simple SELECT * FROM APPS.QP_PRICE_REQ_SOURCES_V ORDER BY REQUEST_TYPE_CODE. Because the view is a straightforward join with no complex logic, it carries no additional filtering beyond the PTE_CODE equality, making it suitable for lightweight lookups in custom concurrent programs and diagnostic scripts. It should be treated as a read-only reference object.