Results for “user_sourcing_type”

28 results




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

Overview

QP_ATTRIBUTE_SOURCING is a table in the QP (Advanced Pricing) product schema of Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. It stores attribute mapping rules defined for a pricing attribute, for each Pricing Transaction entity to which that attribute is linked. In effect, the table answers the question: "When Oracle Pricing needs a value for a given attribute in a given pricing context (a request type and a sourcing level), where should that value come from?" The rules captured here drive how pricing attributes are sourced from the transaction, from the item, from a qualifier, or from user-defined logic before list prices, modifiers, and qualifiers are evaluated.

The table is documented in ETRM with 36 columns and is owned by the QP schema. The metadata's Data Vault classification is heuristic and identifies the object as standalone, meaning it is not modeled by the miner as a hub, link, or satellite of another entity. From a modeling standpoint, this suggests treating QP_ATTRIBUTE_SOURCING as an independent configuration/reference table keyed on its own identifier, with the segment it references acting as a descriptive attribute rather than a parent hub.

Key Information Stored

The most significant columns are:

Two unique indexes represent the business-key candidates: QP_ATTRIBUTE_SOURCING_U1 on (ATTRIBUTE_SOURCING_ID, ZD_EDITION_NAME) and QP_ATTRIBUTE_SOURCING_U2 on (SEGMENT_ID, REQUEST_TYPE_CODE, ATTRIBUTE_SOURCING_LEVEL, ZD_EDITION_NAME). The second index confirms that, per edition, a segment may hold only one sourcing rule for a given request type and level.

Common Use Cases and Queries

Typical scenarios include diagnosing why a pricing attribute is not receiving an expected value, auditing which attributes are sourced from a given request type, and reporting on customer-defined versus seeded sourcing rules.

To list all active sourcing rules for a segment:

SELECT attribute_sourcing_id, segment_id, request_type_code,
       attribute_sourcing_level, seeded_flag, enabled_flag,
       seeded_sourcing_type, user_sourcing_type
FROM   qp.qp_attribute_sourcing
WHERE  segment_id = :segment_id
AND    enabled_flag = 'Y';

To find every rule for a Pricing Transaction entity:

SELECT segment_id, attribute_sourcing_level,
       seeded_value_string, user_value_string
FROM   qp.qp_attribute_sourcing
WHERE  request_type_code = :request_type
ORDER  BY segment_id, attribute_sourcing_level;

To identify customer-defined overrides that shadow seeded behavior:

SELECT segment_id, request_type_code, user_sourcing_type
FROM   qp.qp_attribute_sourcing
WHERE  seeded_flag = 'N'
AND    enabled_flag = 'Y';

These queries are useful during implementation reviews of an attribute mapping, and when preparing pricing setup documentation or migration scripts between environments.

Related Objects

  • CSF_TDS_SEGMENTS — referenced by the foreign key QP_ATTRIBUTE_SOURCING.SEGMENT_ID → CSF_TDS_SEGMENTS.SEGMENT_ID; the join returns descriptive attribute information for each sourcing rule.
  • QP_ATTRIBUTES / QP_ATTR_DEFINITIONS — define the pricing attributes and their segment metadata that QP_ATTRIBUTE_SOURCING rules resolve against.
  • QP_REQUEST_TYPES / QP_PRICING_ENTITY_* — define the Pricing Transaction entities referenced by REQUEST_TYPE_CODE.
  • QP_QUALIFIERS and QP_LIST_HEADERS / QP_LIST_LINES — the pricing entities whose evaluation consumes sourced attribute values at runtime.
  • QP_FORMULA_* and QP_PRICE_FORMULAS — consume the sourced attribute values where formulas are defined.
  • QP_PREQ_REQUEST_TYPES and the Pricing Request APIs (QP_PREQ_GRP, QP_PREQ_PUB) — orchestrate the pricing request at runtime, executing the mapping rules stored in this table.