Results for “pa_invoice_format_details”

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

Overview

PA_INVOICE_FORMAT_DETAILS is a Projects (PA) module table that stores the implementation-defined detail lines that make up an Oracle Projects invoice format configuration. Each row represents one positioning instruction within a parent invoice format, defining where a specific data element begins and ends on the formatted invoice output, whether that element is right-justified, and, where applicable, which invoice group column supplies the value. In Oracle EBS 12.1.1 and 12.2.2, the table supports the configurable invoice generation used by Project Billing and Oracle Projects invoicing, allowing customers to tailor the layout of printed or exported invoices without code changes.

The ETRM relationship metadata classifies this object, on a heuristic Data Vault modeling basis, as a link. This reflects its role as an associative structure connecting PA_INVOICE_FORMATS to PA_INVOICE_GROUP_COLUMNS, with a dependent-type relationship to its parent format. In practice it behaves as a detail or child entity of the invoice format, so a satellite classification for its descriptive attributes would be equally defensible in a dimensional model.

Key Information Stored

The table is documented with 12 columns. The most significant are:

• INVOICE_FORMAT_DETAIL_ID — the surrogate primary key, enforced through PA_INVOICE_FORMAT_DETAILS_PK and additionally protected by unique index PA_INVOICE_FORMAT_DETAILS_U1. This is the column most commonly referenced when users search on the term "invoice_format_detail_id".
• INVOICE_FORMAT_ID — foreign key to PA_INVOICE_FORMATS, identifying the parent format configuration to which the detail line belongs.
• INVOICE_GROUP_COLUMN_ID — foreign key to PA_INVOICE_GROUP_COLUMNS, linking the detail line to the invoice group column that supplies its value.
• START_POSITION and END_POSITION — the character offsets defining where the element is placed within the formatted output line. START_POSITION participates with INVOICE_FORMAT_ID in unique index PA_INVOICE_FORMAT_DETAILS_U2, making the pair (INVOICE_FORMAT_ID, START_POSITION) a documented business-key candidate.
• RIGHT_JUSTIFY_FLAG — controls whether the value is right-justified when written to the output.
• TEXT — literal text associated with the detail line, used for static labels or separators.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard Oracle EBS WHO columns capturing audit and concurrency information.

Common Use Cases and Queries

Typical scenarios include diagnosing invoice layout problems, migrating format definitions between environments, and reporting on configured format details for a given format or invoice group column.

• Retrieve all detail lines for a specific format:

SELECT d.invoice_format_detail_id, d.start_position, d.end_position, d.right_justify_flag, d.text FROM pa.pa_invoice_format_details d WHERE d.invoice_format_id = :p_format_id ORDER BY d.start_position;

• Find details that reference a particular group column: join INVOICE_GROUP_COLUMN_ID to PA_INVOICE_GROUP_COLUMNS.
• Validate positioning by checking for overlap, since the unique index guarantees only that no two rows share the same INVOICE_FORMAT_ID and START_POSITION.
• Detect stale or unused format details by comparing against the invoice formats currently in use.

Related Objects

The following objects are the most significant dependencies based on the documented foreign keys and primary key relationships:

• PA_INVOICE_FORMATS — parent table joined on PA_INVOICE_FORMAT_DETAILS.INVOICE_FORMAT_ID = PA_INVOICE_FORMATS.INVOICE_FORMAT_ID.
• PA_INVOICE_GROUP_COLUMNS — referenced table joined on PA_INVOICE_FORMAT_DETAILS.INVOICE_GROUP_COLUMN_ID = PA_INVOICE_GROUP_COLUMNS.INVOICE_GROUP_COLUMN_ID.
• PA_INVOICE_FORMAT_DETAILS_PK / _U1 / _U2 — the primary key and unique indexes that enforce row identity and the (INVOICE_FORMAT_ID, START_POSITION) business key.

Because the metadata documents only these two foreign-key relationships, other dependencies should be confirmed against the specific 12.1.1 or 12.2.2 instance before being relied upon in custom integrations.