Search Results qp_interface_list_headers




Overview

The QP_INTERFACE_LIST_HEADERS table is a transient staging table residing in the QP schema of Oracle Advanced Pricing. It serves as the inbound conduit through which external sources — legacy systems, third-party pricing engines, or bulk data-load routines — deposit price list, discount list, and promotion header records before they are validated and merged into the base pricing tables. The product documentation describes the base entity, QP_LIST_HEADERS_B, as the store for header information across all list types, including Price Lists, Discount Lists, and Promotions; the interface table mirrors that structure while adding a control block of columns that govern how each row is processed.

Because the interface table's purpose is to feed the base list header entity, the interface rows carry the same business attributes as the transactional parent record. From a Data Vault modeling perspective, the mined FK structure classifies this object as a standalone table; no downstream foreign keys were identified in the documented relationship data. The single documented foreign key points inward, from CURRENCY_HEADER_ID to QP_CURRENCY_LISTS_B, indicating that a list header may be associated with a currency list definition rather than only a transactional currency code. The table is populated with 73 columns in the 12.2.2 documented schema, combining pricing attributes with WHO-style audit columns and interface processing controls.

Key Information Stored

The surrogate primary key is LIST_HEADER_ID, which links interface rows back to the base list header during the concurrent merge process. Business attributes that drive pricing behavior include LIST_TYPE_CODE, which classifies the record as a price list, discount list, or promotion; NAME and DESCRIPTION for identification; CURRENCY_CODE; SOURCE_LANG; VERSION_NO; and the activation window columns START_DATE_ACTIVE and END_DATE_ACTIVE. Behavioral flags such as AUTOMATIC_FLAG, ACTIVE_FLAG, ASK_FOR_FLAG, GSA_INDICATOR, DISCOUNT_LINES_FLAG, PRORATE_FLAG, and MOBILE_DOWNLOAD control how the resulting list is presented and applied.

Interface processing is governed by PROCESS_ID, PROCESS_TYPE, INTERFACE_ACTION_CODE, LOCK_FLAG, PROCESS_FLAG, DELETE_FLAG, and PROCESS_STATUS_FLAG, which the concurrent manager interprets to insert, update, or delete the corresponding base record. External lineage is preserved through ORIG_SYS_HEADER_REF, ORIG_ORG_ID, and LIST_SOURCE_CODE, while SOURCE_SYSTEM_CODE identifies the originating application. Additional pricing context is held in SHIP_METHOD_CODE, SHIP_METHOD, FREIGHT_TERMS_CODE, FREIGHT_TERMS, TERMS_ID, TERMS, PTE_CODE, GLOBAL_FLAG, and CURRENCY_HEADER_ID. The fifteen ATTRIBUTE columns and CONTEXT provide flexfield extensibility, and LANGUAGE supports multi-language deployments. Audit columns include CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, PROGRAM_ID, REQUEST_ID, and PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

The principal use case is bulk import of pricing list headers through the Advanced Pricing import concurrent program. Technicians commonly query the table to diagnose stalled or rejected imports:

  • SELECT LIST_HEADER_ID, NAME, LIST_TYPE_CODE, PROCESS_STATUS_FLAG FROM QP.QP_INTERFACE_LIST_HEADERS WHERE PROCESS_STATUS_FLAG IS NULL;
  • Filtering by REQUEST_ID and INTERFACE_ACTION_CODE to trace a specific batch and its intended operation.
  • Joining to QP_CURRENCY_LISTS_B on CURRENCY_HEADER_ID to validate currency list references before the merge.
  • Auditing ORIG_SYS_HEADER_REF and ORIG_ORG_ID to reconcile records received from an external source system.

Reporting use cases include tracking throughput of pricing conversions, identifying rows with DELETE_FLAG set prior to purge, and confirming that ACTIVE_FLAG and start/end dates are consistent before activation.

Related Objects

The base transactional counterpart is QP_LIST_HEADERS_B, which receives merged rows keyed by LIST_HEADER_ID. The documented foreign key references QP_CURRENCY_LISTS_B via CURRENCY_HEADER_ID. The Advanced Pricing import API and the pricing list import concurrent program read this table and drive the merge into the base schema. Related processing tables in the same interface family include list line and adjustment interface structures that pair with these headers during a complete load. Standard EBS WHO audit conventions link CREATED_BY, LAST_UPDATED_BY, PROGRAM_ID, and REQUEST_ID to FND_USER, FND_CONCURRENT_PROGRAMS, and FND_CONCURRENT_REQUESTS for operational tracing.