Search Results qp_int_ldets_u1

Overview

QP.QP_INT_LDETS_T is a permanent transactional table in the Oracle E-Business Suite Advanced Pricing (QP) schema that stores line-level detail for the pricing engine's base and adjusted price derivation. Each record corresponds to a single pricing request line detail, representing either a price list line or a modifier list line evaluated during pricing. Because the pricing engine may apply many detail records to a single pricing request, this table serves as the granular audit and working set for how a request line arrived at its final price.

The table resides in the APPS_TS_TX_DATA tablespace, with indexes in APPS_TS_TX_IDX. It is classified as VALID in the ETRM directory for 12.1.1 and 12.2.2. The heuristic Data Vault classification mined from the foreign key structure is standalone; from a modeling perspective, the table behaves less like a hub or link and more like a satellite-style transaction record — a detail captured against an external business process (the pricing request) rather than a shared reference entity. The 81 documented columns reflect the breadth of pricing engine outcomes: precedence, limits, accruals, formulas, currency, and operator-driven adjustments.

Key Information Stored

The surrogate identifier is LINE_DETAIL_INDEX, combined with REQUEST_ID to form the unique business-key candidate enforced by the unique index QP_INT_LDETS_U1 (REQUEST_ID, LINE_DETAIL_INDEX). REQUEST_ID identifies the parent pricing request, while LINE_INDEX links the detail to its priced request line.

• LINE_DETAIL_INDEX / REQUEST_ID / LINE_INDEX — the identity and parentage of each detail record.
• LINE_DETAIL_TYPE_CODE — classifies the nature of the detail (price list versus modifier influences).
• CREATED_FROM_LIST_HEADER_ID / CREATED_FROM_LIST_LINE_ID — the price or modifier list header and line that generated the record.
• CREATED_FROM_LIST_LINE_TYPE — the list line category (e.g., PLL, PBH, DIS, SUR, OID, PRG, TSN).
• PRICING_PHASE_ID — the pricing phase under which the line was evaluated.
• PRICING_STATUS_CODE / PRICING_STATUS_TEXT — whether the line was applied, rejected, or left unprocessed.
• APPLIED_FLAG / OVERRIDE_FLAG / AUTOMATIC_FLAG / ASK_FOR_FLAG — application and interaction indicators for the adjustment.
• OPERAND_VALUE / ADJUSTMENT_AMOUNT / OPERAND_CALCULATION_CODE — the magnitude and calculation basis of the price adjustment.
• PRICE_FORMULA_ID — the formula used, resolving to QP_PRICE_FORMULAS_B.
• CURRENCY_HEADER_ID / CURRENCY_DETAIL_ID / BASE_CURRENCY_CODE / ORDER_CURRENCY — currency context for the applied pricing.
• PRODUCT_PRECEDENCE / INCOMPATABILITY_GRP_CODE / BEST_PERCENT — the precedence and best-price resolution logic.
• PROCESSED_FLAG / UPDATED_FLAG / SELECTED_VOLUME_ATTR / LINE_QUANTITY — engine processing state and quantity basis.
• REQUEST_ID — the primary join back to the originating pricing request.

Common Use Cases and Queries

The most common reporting need is auditing why a given sales order or pricing request line received a particular price. The following query retrieves the applied details for one request line:

SELECT t.line_index, t.line_detail_index, t.created_from_list_line_type,
       t.applied_flag, t.adjustment_amount, t.pricing_status_code
FROM   qp.qp_int_ldets_t t
WHERE  t.request_id = :p_request_id
AND    t.line_index = :p_line_index
ORDER  BY t.product_precedence, t.line_detail_index;

Because the unique key is (REQUEST_ID, LINE_DETAIL_INDEX), lookups driven by both columns are optimal and use QP_INT_LDETS_U1 directly. Reporting on phase and status usage is supported by QP_INT_LDETS_N2, while QP_INT_LDETS_N3 and QP_INT_LDETS_N1 support line and phase aggregations. Typical reports include modifier application by phase, accrual and benefit evaluation, currency conversion effect on adjustments, and list line versus modifier contribution analysis. Because the table is transactional, purge or archive strategies should always be driven by REQUEST_ID.

Related Objects

• QP.QP_PRICING_PHASES — referenced by PRICING_PHASE_ID; defines phase order in which details were evaluated.
• QP.QP_PRICE_FORMULAS_B — referenced by PRICE_FORMULA_ID; the formula behind the adjustment.
• QP.QP_CURRENCY_LISTS_B — referenced by CURRENCY_HEADER_ID; the currency list defining conversion context.
• QP.QP_CURRENCY_DETAILS — referenced by CURRENCY_DETAIL_ID; the specific currency conversion used.
• QP.QP_PRICE_LIST_LINES and QP.QP_MODIFIER_LIST_LINES — logical parents via CREATED_FROM_LIST_LINE_ID where CREATED_FROM_LIST_LINE_TYPE indicates PLL or modifier types.
• QP.QP_INT_HEADERS_T / QP.QP_INT_LINES_T — the pricing request header and line tables joined on REQUEST_ID and LINE_INDEX.

These relationships make QP_INT_LDETS_T the finest-grained factual record of pricing decisions, best consumed alongside its header and line siblings rather than in isolation.