Results for “batch_source”

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

Overview

PA_BATCH_SOURCES is a system-defined reference table in the Oracle Projects (PA) product schema. Its documented purpose is to hold the set of valid sources for expense report expenditure batches. Each row identifies a distinct batch source that Oracle EBS recognizes when expenditure batches are created and processed, providing the controlled vocabulary that governs how batches originate (for example, batch creation originating from expense report processing versus other batch-generation mechanisms).

The table is owned by the PA schema and is marked VALID in the documented release metadata, covering Oracle EBS 12.1.1 and 12.2.2. Because it is a system-seeded reference table rather than a transactional table, its row population is typically small and stable, and it changes only through Oracle-supplied seed data or controlled maintenance.

The relationship metadata classifies PA_BATCH_SOURCES as hub-leaning under a heuristic Data Vault model. As a modeling suggestion, this positions the table as a hub: a durable, business-keyed set of distinct batch source identities, referenced by satellite-like transactional detail in the expenditure batch tables. The classification is heuristic and is derived from the foreign-key structure rather than from an explicit Data Vault declaration.

Key Information Stored

The documented physical schema contains nine columns. The most significant are:

• BATCH_SOURCE — the single-column primary key component of PA_BATCH_SOURCES_PK, and the value carried into expenditure batches as a foreign key. This is the business identifier of the batch source.
• MEANING — the user-facing display name for the batch source, and a business-key candidate via the unique index PA_BATCH_SOURCES_U2 (MEANING, ZD_EDITION_NAME).
• DESCRIPTION — a longer explanatory text for the batch source.
• ZD_EDITION_NAME — the edition discriminator used by Oracle's edition-based redefinition and by the zed-enabled lookup infrastructure. It participates in both unique indexes and therefore forms part of the effective business key in an editioned environment.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard Oracle EBS audit columns recording who created and last modified each row and when.

The two documented unique indexes, PA_BATCH_SOURCES_U1 (BATCH_SOURCE, ZD_EDITION_NAME) and PA_BATCH_SOURCES_U2 (MEANING, ZD_EDITION_NAME), constitute the business-key candidates. The primary key PA_BATCH_SOURCES_PK on BATCH_SOURCE is the surrogate-style row identifier used for referential integrity, while the U1 and U2 indexes enforce uniqueness of source code and display meaning respectively within an edition.

Common Use Cases and Queries

The predominant use of PA_BATCH_SOURCES is as a lookup when interpreting or validating the BATCH_SOURCE value stored on expenditure batches. A typical validation query joins the batch table to the source table to resolve the code into a readable meaning:

• Resolve batch source meaning. SELECT b.batch_source, s.meaning, s.description, COUNT(*) FROM pa.pa_expenditure_batches_all b JOIN pa.pa_batch_sources s ON s.batch_source = b.batch_source GROUP BY b.batch_source, s.meaning, s.description;
• Validate orphaned or unrecognized source codes. Use an outer join from PA_EXPENDITURE_BATCHES_ALL to PA_BATCH_SOURCES to detect any batch whose BATCH_SOURCE has no corresponding reference row.
• List available sources. SELECT batch_source, meaning, description FROM pa.pa_batch_sources ORDER BY meaning; This supports configuration review and reporting parameter lists.
• Audit reference-data changes. Query the audit columns (LAST_UPDATED_BY, LAST_UPDATE_DATE) to determine whether the seeded reference data has been modified from Oracle's delivered values.

Because the row count is small, reporting solutions frequently cache this table and use it in the conformed dimension of an expenditure data mart, joining on BATCH_SOURCE to label fact rows.

Related Objects

The documented foreign-key relationship establishes PA_EXPENDITURE_BATCHES_ALL as the principal dependent object. The relevant join column in each case is BATCH_SOURCE.

• PA_EXPENDITURE_BATCHES_ALL — the primary referencing table; its BATCH_SOURCE column points to PA_BATCH_SOURCES. This is the transactional table of expenditure batches and the main consumer of the reference data.
• PA_BATCH_SOURCES_PK — the primary-key constraint or index on BATCH_SOURCE that enforces uniqueness for the referencing foreign key.
• PA_BATCH_SOURCES_U1 — unique index on BATCH_SOURCE and ZD_EDITION_NAME, a business-key candidate enforcing unique source codes per edition.
• PA_BATCH_SOURCES_U2 — unique index on MEANING and ZD_EDITION_NAME, a business-key candidate enforcing unique display names per edition.
• PA_EXPENDITURE_ITEMS and related expenditure distribution tables — indirectly dependent, since expenditure items ultimately roll up into expenditure batches whose source is resolved through this lookup.

In summary, PA_BATCH_SOURCES functions as a compact, seeded hub of batch source identities that anchors the BATCH_SOURCE foreign key on PA_EXPENDITURE_BATCHES_ALL, with the PA_BATCH_SOURCES_PK primary key and the U1/U2 unique indexes supplying its key and business-key definitions.