Search Results qp_interface_list_lines




Overview
Explore in AI Chat

Overview

QP_INTERFACE_LIST_LINES is the interface (staging) table for the Advanced Pricing list line entity in Oracle E-Business Suite 12.1.1 and 12.2.2. It is owned by the QP schema and belongs to the QP – Advanced Pricing product family. Where the permanent table QP_LIST_LINES stores all list lines belonging to lists defined in QP_LIST_HEADERS_B, QP_INTERFACE_LIST_LINES holds the same 105-column row shape for inbound/outbound data loading — typically populated by concurrent programs, SQL*Loader scripts, or external pricing integrations before the interface is validated and the rows are transferred into QP_LIST_LINES. In a heuristic Data Vault model the table would most reasonably be classified as a satellite: it is a wide, descriptive, non-keyed-by-integer-business-identity structure anchored to a list line, not a pure hub or a link between two independent business keys. That classification is a modeling suggestion only; the ETRM metadata labels the table as standalone in its FK structure.

Key Information Stored

The physical schema documents 105 columns. The surrogate primary key is LIST_LINE_ID (the FK reference into QP_LIST_LINES). Business keys referenced include LIST_HEADER_ID (the parent list) and LIST_LINE_NO, which together with the header provide the natural identifier of a line. ORIG_SYS_LINE_REF, ORIG_SYS_HEADER_REF, and PRICE_BREAK_HEADER_REF carry the source-system identifiers of the originating external records — candidates for business keys in an integration context.

Common Use Cases and Queries

Typical scenarios include bulk loading of new price list lines during pricing implementations, migrating pricing data between environments, and auditing failed or pending interface rows before they are merged into the live list lines. Monitoring queries usually filter on the process-control columns.

Example — inspect rows awaiting processing for a given request:

SELECT list_line_id, list_header_id, list_line_no,
       inventory_item_id, list_price, interface_action_code,
       process_status_flag, process_flag
  FROM   qp.qp_interface_list_lines
 WHERE  request_id = :p_request_id
   AND  process_status_flag = 'N';

Example — reconciliation against the target pricing table to confirm a successful load:

SELECT i.list_line_id, i.list_header_id, i.orig_sys_line_ref,
       l.list_line_id AS loaded_line_id
  FROM   qp.qp_interface_list_lines i
       LEFT OUTER JOIN qp.qp_list_lines l
         ON l.list_line_id = i.list_line_id
 WHERE  i.program_id = :p_program_id;

Reporting uses the interface table to trace source-system references (ORIG_SYS_LINE_REF, ORIG_SYS_HEADER_REF) back to external systems, and to validate price-break structures before they go live.

Related Objects

  • QP_LIST_LINES — target table; LIST_LINE_ID in the interface table references this object.
  • QP_PRICING_PHASES — PRICING_PHASE_ID references this table, and PRICING_PHASE_NAME is also carried on the interface row.
  • QP_LIST_HEADERS_B — parent of QP_LIST_LINES; LIST_HEADER_ID is populated from the list being loaded.
  • QP_INTERFACE_LIST_HEADERS — the companion header interface table normally populated alongside this line table.
  • QP_PRICE_LIST_LINES (or the associated pricing list-line API) — the pricing engine consumer of loaded list lines.
  • Interface concurrent programs and the standard QP list-line import API — the procedural counterpart that reads from this table and writes to QP_LIST_LINES.