Results for “price_book_type_code”

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

Overview

QP_PB_INPUT_HEADERS_B is a table in the QP (Advanced Pricing) schema of Oracle E-Business Suite, holding the header-level input criteria used to generate a Price Book request. Despite the "purchase header" search term that may have surfaced it, this object is not a purchasing table; it stores the parameters a user or concurrent program supplies when requesting price book generation, so the pricing engine knows which customer, currency, product scope, and delivery options to apply. Each row represents one price book request header.

Under a heuristic Data Vault classification, this table is modeled as a standalone object — it functions as a hub-like or reference entity without a parent link enforced through foreign keys on itself, though it is referenced by several child tables.

Key Information Stored

The table contains 40 documented columns. The most significant include:

• PB_INPUT_HEADER_ID — surrogate primary key, enforced by QP_INPUT_HEADERS_B_PK and unique index QP_PB_INPUT_HEADERS_B_U1. Acts as the business-key candidate.
• CUST_ACCOUNT_ID — the customer account driving the price book; foreign key to HZ_CUST_ACCOUNTS.
• CUSTOMER_CONTEXT / CUSTOMER_ATTRIBUTE / CUSTOMER_ATTR_VALUE — context-based flexfield-style qualifiers narrowing the customer population.
• PRODUCT_CONTEXT / PRODUCT_ATTRIBUTE / PRODUCT_ATTR_VALUE — analogous qualifiers for the product dimension.
• CURRENCY_CODE and LIMIT_PRODUCTS_BY — currency and product-limiting criteria for generation.
• EFFECTIVE_DATE and ITEM_QUANTITY — date and quantity basis for pricing.
• PRICE_BOOK_TYPE_CODE and PRICE_BASED_ON — define the type of price book and its pricing source.
• PUB_TEMPLATE_CODE / PUB_LANGUAGE / PUB_TERRITORY / PUB_OUTPUT_DOCUMENT_TYPE — publication formatting and output metadata.
• DLV_XML_FLAG, DLV_EMAIL_FLAG, DLV_PRINTER_FLAG and the associated email/printer fields — delivery routing.
• REQUEST_ID / ORG_ID / REQUEST_TYPE_CODE — links to the concurrent request and operating unit.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical usage centers on reporting and diagnosing price book generation. Analysts join the header to QP_PB_INPUT_LINES to trace which products were requested, and to QP_PRICE_BOOK_MESSAGES to review validation or generation errors.

• Listing recent price book requests with their customer and currency:

  SELECT h.pb_input_header_id, h.cust_account_id, h.currency_code, h.request_id
  FROM qp.qp_pb_input_headers_b h
  WHERE h.creation_date > SYSDATE-30;

• Identifying requests by organization and request type:

  SELECT pb_input_header_id, org_id, request_type_code, price_book_type_code
  FROM qp.qp_pb_input_headers_b
  WHERE org_id = :p_org_id;

• Reviewing affected price books produced from a request via QP_PRICE_BOOK_HEADERS_ALL_B.

Related Objects

Documented relationships include:

• HZ_CUST_ACCOUNTS — referenced through CUST_ACCOUNT_ID.
• QP_PRICE_BOOK_HEADERS_ALL_B — references this table via PB_INPUT_HEADER_ID; holds resulting price book headers.
• QP_PRICE_BOOK_MESSAGES — references via PB_INPUT_HEADER_ID; stores generation messages.
• QP_PB_INPUT_LINES — references via PB_INPUT_HEADER_ID; stores line-level request criteria.

These relationships allow full reconstruction of a price book request from its header inputs through to the generated output and any messages.