Search Results bis_txn_complexity_low

Overview

ASO.ASO_BI_QUOTE_IDS is a table in the ASO (Order Capture / Quoting) schema of Oracle E-Business Suite, present and valid in both 12.1.1 and 12.2.2. Its documented purpose is narrow and mechanical: it divides quotes into batches so that the incremental collection and extraction of quote data into the Business Intelligence / data warehouse layer proceeds in controlled units. The size of each batch is governed by the profile option BIS_TXN_COMPLEXITY_LOW, which the collection program reads to determine how many quotes are grouped into a single BATCH_ID. In this sense the table functions as a staging or work table within the ASO Business Intelligence extraction flow rather than as a transactional quoting entity.

The ETRM metadata classifies the object heuristically as standalone. Following Data Vault modeling conventions, this suggests ASO_BI_QUOTE_IDS is best treated as a standalone reference or staging structure rather than as a true hub, link, or satellite. It carries one foreign-key-style relationship — QUOTE_HEADER_ID pointing to ASO_QUOTE_HEADERS_ALL — but the documentation describes it as referencing the quote header only for identification of the highest quote version, not as an enforced DDL foreign key. It resides in the APPS_TS_INTERFACE tablespace with PCTFREE 10, consistent with its transient, batch-oriented role.

Key Information Stored

The table contains six documented columns. The most significant are:

• QUOTE_HEADER_ID (NUMBER) — Unique identifier for the highest version of a quote. This is the operative join key to the quote header, and the first column of the non-unique index.
• BATCH_ID (NUMBER) — Unique identifier of the batch used in incremental collection of quotes. This is the grouping column that drives the batching logic and is the other indexed column.
• QUOTE_NUMBER (NUMBER) — The business-facing quote number, useful as a human-readable business key candidate.
• MAX_QUOTE_VERSION (NUMBER) — The highest version reached by the quote, used to ensure only the latest version is propagated.
• QUOTE_CREATION_DATE (DATE) — Creation date of the first version of the quote; supports incremental date-range selection.
• QUOTE_AMOUNT_FIRST (NUMBER) — Quote amount on the first version of the quote, retained as the original baseline value.

No surrogate single-column primary key is documented. The only index is ASO_BI_QUOTE_IDS_N1, a NONUNIQUE normal index on (BATCH_ID, QUOTE_HEADER_ID); there is no documented unique index, so QUOTE_HEADER_ID and QUOTE_NUMBER are business-key candidates rather than enforced unique constraints.

Common Use Cases and Queries

Typical usage centers on driving and monitoring the incremental quote collection program. A batch listing identifies which quotes are assigned to a given collection run:

• SELECT QUOTE_HEADER_ID, QUOTE_NUMBER, MAX_QUOTE_VERSION, BATCH_ID FROM ASO.ASO_BI_QUOTE_IDS WHERE BATCH_ID = :batch_id;
• Counting quotes per batch to verify the BIS_TXN_COMPLEXITY_LOW batch size: SELECT BATCH_ID, COUNT(*) FROM ASO.ASO_BI_QUOTE_IDS GROUP BY BATCH_ID;
• Date-filtered extraction to find newly created quotes: SELECT QUOTE_HEADER_ID, QUOTE_NUMBER, QUOTE_CREATION_DATE FROM ASO.ASO_BI_QUOTE_IDS WHERE QUOTE_CREATION_DATE >= :start_date;
• Joining to the header to resolve full quote detail: SELECT q.QUOTE_NUMBER, qi.BATCH_ID, q.QUOTE_AMOUNT FROM ASO.ASO_BI_QUOTE_IDS qi, ASO.ASO_QUOTE_HEADERS_ALL q WHERE qi.QUOTE_HEADER_ID = q.QUOTE_HEADER_ID;

Reporting scenarios include verifying batch sizing against the profile setting, reconciling collected quote counts versus source, and auditing the first-version quote amount against current amounts.

Related Objects

• ASO.ASO_QUOTE_HEADERS_ALL — The primary referenced object; joined on QUOTE_HEADER_ID.
• APPS.ASO_BI_QUOTE_IDS — The APPS synonym/interface layer for this table as exposed to concurrent programs.
• ASO_BI_QUOTE_IDS_N1 — The non-unique index on (BATCH_ID, QUOTE_HEADER_ID) supporting batch and header lookups.
• FND Design Data ASO.ASO_BI_QUOTE_IDS — The registered design data entry governing the table.
• Profile option BIS_TXN_COMPLEXITY_LOW — Controls the batch size used when populating BATCH_ID.

Note that the metadata states the table does not reference any database object via enforced constraints; the ASO_QUOTE_HEADERS_ALL link is a documented logical relationship rather than a physical foreign key.