Search Results cst_ap_variance_batches_pk

Overview

CST_AP_VARIANCE_BATCHES is an Oracle E-Business Suite table owned by the BOM schema (Bills of Material) that stores the parameters and control information for each execution of the Invoice Variance Transfer Program. The table functions as the parent or header-level record in the Accounts Payable invoice variance processing framework, capturing the selection criteria and processing options that determine which invoices, items, projects, and adjustments are considered during a given program run. Each row represents one logical batch, identified by the BATCH_ID surrogate primary key, and serves as the anchor point for the detail records created downstream by that run.

From a Data Vault modeling perspective, the heuristic classification for this table is hub-leaning. This classification reflects the fact that CST_AP_VARIANCE_BATCHES acts as a business entity store whose primary key (BATCH_ID) is referenced by multiple dependent tables—namely CST_AP_VARIANCE_HEADERS and CST_AP_VARIANCE_LINES. In a Data Vault or dimensional model, BATCH_ID would typically be treated as a hub key, with the descriptive processing attributes modeled as satellites and the relationships to headers and lines modeled as links.

Key Information Stored

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

• BATCH_ID — The surrogate primary key (enforced via CST_AP_VARIANCE_BATCHES_PK and the unique index CST_AP_VARIANCE_BATCHES_U1). It uniquely identifies each program run and is the foreign key target for downstream detail tables.
• ORGANIZATION_ID — Identifies the inventory organization whose transactions are being processed in the run.
• ITEM_OPTION — Controls whether the run is scoped to all items, a specific item, or a category.
• INVOICE_PROJECT_OPTION — Determines project-related filtering for the variance transfer.
• ADJUSTMENT_ACCOUNT — The account used to record the variance adjustments generated during the run.
• CUTOFF_DATE — The date boundary used to select invoices and transactions eligible for processing.
• TRANSACTION_PROCESS_MODE — Defines how transactions are handled (for example, validation versus posting modes).
• SPECIFIC_ITEM_ID and SPECIFIC_PROJECT_ID — Optional constraints narrowing the run to a single item or project when the corresponding option is selected.
• CATEGORY_ID and CATEGORY_SET_ID — Define the item category and category set used when the item option selects by category.
• WIP_ENTITY_ID — Associates the run with a specific work in process entity when applicable.
• ITEM_TYPE — Indicates the type of item scope applied.
• DESCRIPTION — A descriptive label for the batch, useful in audit and reporting contexts.
• REQUEST_ID, PROGRAM_ID, and PROGRAM_APPLICATION_ID — Standard concurrent program audit columns tying the batch to its originating concurrent request.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — Standard "Who" columns supporting auditing and change tracking.

The surrogate primary key (BATCH_ID) is distinct from any business-key candidates; no separate business key column set is documented beyond the unique index on BATCH_ID itself.

Common Use Cases and Queries

Typical usage centers on auditing, troubleshooting, and reporting on Invoice Variance Transfer Program runs. Consultants often query this table to determine the parameters used by a specific run before investigating the resulting headers and lines. For example:

• Retrieving all batches for an organization: SELECT * FROM CST_AP_VARIANCE_BATCHES WHERE ORGANIZATION_ID = :org_id ORDER BY CREATION_DATE DESC;
• Linking a batch to its concurrent request: SELECT BATCH_ID, REQUEST_ID, PROGRAM_ID, CUTOFF_DATE, TRANSACTION_PROCESS_MODE FROM CST_AP_VARIANCE_BATCHES WHERE REQUEST_ID = :request_id;
• Reporting recent runs and their descriptive labels: SELECT BATCH_ID, DESCRIPTION, ORGANIZATION_ID, CUTOFF_DATE, CREATION_DATE FROM CST_AP_VARIANCE_BATCHES WHERE CREATION_DATE > SYSDATE - 30;

These queries support operational review of variance transfer activity, reconciliation of adjustments posted to the adjustment account, and diagnosis of why particular invoices or items were excluded based on the option columns.

Related Objects

The following objects reference or depend on CST_AP_VARIANCE_BATCHES, based on the documented foreign key relationships:

• CST_AP_VARIANCE_HEADERS — References CST_AP_VARIANCE_BATCHES via CST_AP_VARIANCE_HEADERS.BATCH_ID; stores header-level detail for each batch.
• CST_AP_VARIANCE_LINES — References CST_AP_VARIANCE_BATCHES via CST_AP_VARIANCE_LINES.BATCH_ID; stores line-level variance detail generated by the run.

Joins to these tables are performed on BATCH_ID and are essential for reconstructing the full output of any given Invoice Variance Transfer Program execution. Because the documentation lists only these two dependent tables, they constitute the primary related-object set for this table.