Results for “pa_invoice_groups_u1”

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

Overview

PA.PA_INVOICE_GROUPS is a seed data table in the Oracle Projects (PA) schema that stores system-defined invoice line groupings. Oracle Projects supplies all invoice groups upon installation; the table is not intended for end-user maintenance, though implementers may review its contents to understand how expenditures are consolidated into invoice lines. Each row represents one invoice group, which defines both the columns used to group expenditure items into invoice lines and the invoice format types for which the group is valid. The table resides in the APPS_TS_SEED tablespace, consistent with its role as shipped reference data rather than transactional data.

From a Data Vault modeling perspective, the mined relationship metadata classifies PA.PA_INVOICE_GROUPS as hub-leaning. This is a modeling suggestion only: the table behaves as a durable business entity keyed by a system-generated identifier, with two dependent child tables acting as satellites or link-bearing structures that extend its attributes. In Oracle EBS 12.1.1 and 12.2.2 the object is VALID, owned by PA, and registered in FND Design Data as PA.PA_INVOICE_GROUPS.

Key Information Stored

The primary key is INVOICE_GROUP_ID, the system-generated number that uniquely identifies each invoice group. Two unique indexes enforce business-key candidates. PA_INVOICE_GROUPS_U1 covers INVOICE_GROUP_ID (with ZD_EDITION_NAME in the 12.2.2 physical schema), and PA_INVOICE_GROUPS_U2 covers NAME together with INVOICE_FORMAT_TYPE. The NAME and INVOICE_FORMAT_TYPE pair therefore constitutes the meaningful business identifier, while INVOICE_GROUP_ID remains the surrogate primary key.

• INVOICE_GROUP_ID – surrogate primary key; system-generated unique identifier.
• NAME – the descriptive name of the invoice group shown to users.
• GROUP_TYPE_CODE – identifies the columns by which expenditure items are grouped into invoice lines when this group is used.
• INVOICE_FORMAT_TYPE – the invoice format type for which the group is applicable; part of the composite unique key.
• INTERCOMPANY_INVOICE_FLAG – indicates whether the group is used for intercompany invoicing.
• CUSTOMER_INVOICE_FLAG – indicates whether the group is used for customer invoicing.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN – standard Who columns tracking insert and update audit information.
• ZD_EDITION_NAME – editioning column present in the 12.2.2 physical schema, supporting online patching and edition-based redefinition.

Common Use Cases and Queries

Typical usage centers on determining valid groupings and format combinations, and on joining invoice groups to their associated formats and grouping columns. A basic lookup query follows:

• SELECT INVOICE_GROUP_ID, NAME, GROUP_TYPE_CODE, INVOICE_FORMAT_TYPE, INTERCOMPANY_INVOICE_FLAG, CUSTOMER_INVOICE_FLAG FROM PA.PA_INVOICE_GROUPS WHERE INVOICE_FORMAT_TYPE = :format_type;
• Join to PA_INVOICE_GROUP_COLUMNS on INVOICE_GROUP_ID to enumerate the columns that make up a given grouping.
• Join to PA_INVOICE_FORMATS on INVOICE_GROUP_ID to identify which formats reference a group.
• Query by NAME and INVOICE_FORMAT_TYPE to resolve the business key to its surrogate INVOICE_GROUP_ID.

Reporting use cases include validating configuration across formats and groupings, auditing intercompany versus customer invoicing coverage, and extracting seed group definitions for comparison between environments during upgrades or clones.

Related Objects

PA.PA_INVOICE_GROUPS references no other database object, but it is referenced by the following tables, which should be joined on INVOICE_GROUP_ID:

• PA.PA_INVOICE_FORMATS – joins on INVOICE_GROUP_ID; defines invoice formats that consume an invoice group.
• PA.PA_INVOICE_GROUP_COLUMNS – joins on INVOICE_GROUP_ID; stores the individual grouping columns belonging to each group.
• APPS.PA_INVOICE_GROUPS – the APPS synonym or view exposing the table to application code.

Collectively these dependencies confirm the hub-leaning classification, placing PA_INVOICE_GROUPS at the center of the invoice grouping and formatting configuration model within Oracle Projects.