Results for “invoice_format_type”
39 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
PA_INVOICE_GROUPS is a Projects (PA) module reference table that stores system-defined configurations of invoice line groupings. Each row defines a named grouping rule that determines how invoice lines are aggregated and ordered when project invoices, intercompany invoices, or customer invoices are generated and formatted. The table acts as a configuration catalog consumed by the Oracle Projects invoicing engine and by invoice format definitions, allowing organizations to control the presentation of billing detail (for example, grouping by project, task, employee, or expenditure category) without altering core invoice extraction logic.
The ETRM metadata classifies this object heuristically as hub-leaning within a Data Vault model. Under that interpretation, PA_INVOICE_GROUPS would be modeled as a hub, since INVOICE_GROUP_ID is a stable surrogate business key referenced by dependent objects. In practice, the table behaves as a parent configuration entity with two direct child dependencies, PA_INVOICE_FORMATS and PA_INVOICE_GROUP_COLUMNS, both joined on INVOICE_GROUP_ID.
Key Information Stored
The table consists of 12 documented columns. The most significant are listed below.
- INVOICE_GROUP_ID — Surrogate primary key, defined by PA_INVOICE_GROUPS_PK. This is the value propagated to child tables via foreign keys and is the column used in all joins.
- NAME — User-facing name of the grouping configuration.
- INVOICE_FORMAT_TYPE — Identifies the invoice format context in which the grouping applies. Part of the PA_INVOICE_GROUPS_U2 business-key candidate.
- GROUP_TYPE_CODE — Classifies the grouping behavior or category used by the invoice generation logic.
- INTERCOMPANY_INVOICE_FLAG — Indicates whether the grouping is available for intercompany invoicing.
- CUSTOMER_INVOICE_FLAG — Indicates whether the grouping applies to customer invoicing.
- ZD_EDITION_NAME — Editioning column supporting online patching; participates in both unique indexes (PA_INVOICE_GROUPS_U1, PA_INVOICE_GROUPS_U2).
- LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard audit columns recording creation and modification metadata.
The two documented unique indexes define the business-key candidates: PA_INVOICE_GROUPS_U1 on (INVOICE_GROUP_ID, ZD_EDITION_NAME) and PA_INVOICE_GROUPS_U2 on (NAME, INVOICE_FORMAT_TYPE, ZD_EDITION_NAME). The latter enforces uniqueness of grouping name within an invoice format type, confirming NAME and INVOICE_FORMAT_TYPE as the natural composite business key.
Common Use Cases and Queries
Typical usage centers on resolving invoice group configuration for reporting, validating invoice format setup, and auditing which groupings are enabled for customer or intercompany transactions.
- List active customer invoice groupings: SELECT INVOICE_GROUP_ID, NAME, INVOICE_FORMAT_TYPE FROM PA.PA_INVOICE_GROUPS WHERE CUSTOMER_INVOICE_FLAG = 'Y';
- Join groupings to their column definitions: SELECT g.NAME, c.* FROM PA.PA_INVOICE_GROUPS g, PA.PA_INVOICE_GROUP_COLUMNS c WHERE g.INVOICE_GROUP_ID = c.INVOICE_GROUP_ID;
- Identify formats referencing each grouping: SELECT f.* FROM PA.PA_INVOICE_FORMATS f, PA.PA_INVOICE_GROUPS g WHERE f.INVOICE_GROUP_ID = g.INVOICE_GROUP_ID;
- Audit recent configuration changes using LAST_UPDATE_DATE and LAST_UPDATED_BY.
As this is configuration rather than transactional data, reporting is generally small in volume and well suited to joining directly against PA_INVOICE_FORMATS and PA_INVOICE_GROUP_COLUMNS.
Related Objects
- PA_INVOICE_FORMATS — References PA_INVOICE_GROUPS via INVOICE_FORMATS.INVOICE_GROUP_ID; defines the invoice formats that consume each grouping.
- PA_INVOICE_GROUP_COLUMNS — References PA_INVOICE_GROUPS via INVOICE_GROUP_COLUMNS.INVOICE_GROUP_ID; stores the individual columns that compose each grouping definition.
- PA_INVOICE_GROUPS_PK — Primary key constraint on INVOICE_GROUP_ID.
- PA_INVOICE_GROUPS_U1 / PA_INVOICE_GROUPS_U2 — Unique indexes defining the surrogate and composite business-key candidates respectively.
These relationships confirm PA_INVOICE_GROUPS as the hub of an invoice-grouping configuration cluster, with formatting and column composition dependents keyed on INVOICE_GROUP_ID.
-
System-defined configurations of invoice line groupings
-
System-defined configurations of invoice line groupings
-
View: OKL_TXD_AR_LN_DTLS_V 12.1.1
Transaction line details to be included into Receivables invoices
APPS.OKL_TXD_AR_LN_DTLS_V·↳ OKL_TXD_AR_LN_DTLS_B·↳ OKL_TXD_AR_LN_DTLS_TL·Explore OKL module →
-
Transaction line details to be included into Receivables invoices
-
View: OKL_TXD_AR_LN_DTLS_V 12.2.2
Transaction line details to be included into Receivables invoices
APPS.OKL_TXD_AR_LN_DTLS_V·↳ OKL_TXD_AR_LN_DTLS_B·↳ OKL_TXD_AR_LN_DTLS_TL·Explore OKL module →
-
Transaction line details to be included into Receivables invoices
-
VIEW: PA.PA_INVOICE_GROUPS# 12.2.2
-
TABLE: PA.PA_INVOICE_GROUPS 12.1.1
-
TABLE: PA.PA_INVOICE_GROUPS 12.2.2
-
VIEW: PA.PA_INVOICE_GROUPS# 12.2.2
-
PACKAGE: APPS.OKL_TLD_PVT 12.1.1
-
PACKAGE: APPS.OKL_TLD_PVT 12.2.2
-
PACKAGE: APPS.OKL_ARINTF_PVT 12.1.1
-
PACKAGE: APPS.OKL_ARINTF_PVT 12.2.2
-
eTRM - OKL Tables and Views 12.1.1
Translatable columns from OKL_XTL_SELL_INVS_B, per MLS standards
-
eTRM - OKL Tables and Views 12.2.2
Translatable columns from OKL_XTL_SELL_INVS_B, per MLS standards
-
eTRM - PA Tables and Views 12.1.1
-
eTRM - PA Tables and Views 12.2.2