Results for “pa_draft_invoice_items_u1”

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

Overview

PA.PA_DRAFT_INVOICE_ITEMS is a transactional table in the Oracle E-Business Suite Projects (PA) schema that stores the individual lines of a draft invoice. When the Generate Draft Invoice process executes, it creates one invoice line for each billing event and one line for each grouping of expenditure items, with the groupings determined by the invoice formats defined on the project. Each row therefore represents a billable line item awaiting transfer to Oracle Receivables.

The table is owned by the PA schema and resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. Its primary key is PA_DRAFT_INVOICE_ITEMS_PK, defined on the composite of PROJECT_ID, DRAFT_INVOICE_NUM, and LINE_NUM. Under the heuristic Data Vault classification mined from the foreign key structure, this object is best modeled as a satellite: it carries descriptive, non-key attributes (amounts, tax attributes, retention details, currency conversion columns, and who-columns) that hang off the transactional parent PA_DRAFT_INVOICES_ALL rather than acting as a pure hub or link.

Key Information Stored

The physical schema documents 98 columns. The most significant are:

• PROJECT_ID + DRAFT_INVOICE_NUM + LINE_NUM — the composite primary key and the unique business-key candidate, coinciding with unique index PA_DRAFT_INVOICE_ITEMS_U1 (the object referenced in the user's search). Together these identify a single draft invoice line for a project.
• AMOUNT — the amount to be billed for the line, the primary transactional value.
• TEXT — the invoice line description; for event lines this is the event description, while for expenditure lines it is formatted per the project invoice formats.
• INVOICE_LINE_TYPE — classifies the kind of draft invoice line (for example, event versus expenditure-based).
• TASK_ID and EVENT_TASK_ID — identify the task against which the billable activity occurred.
• EVENT_NUM — links the line back to the originating billing event.
• INV_AMOUNT — the invoiced amount for the line, distinct from the raw AMOUNT.
• OUTPUT_VAT_TAX_ID, OUTPUT_TAX_EXEMPT_FLAG, OUTPUT_TAX_CLASSIFICATION_CODE — output tax determination and tax exemption attributes.
• RETN_* columns (RETN_BILLING_METHOD, RETN_PERCENT_COMPLETE, RETN_TOTAL_RETENTION, RETN_BILLING_AMOUNT, RETAINED_AMOUNT, etc.) — retention billing configuration and computed retention values per line.
• PROJECT_BILL_AMOUNT / PROJECT_CURRENCY_CODE, FUNDING_BILL_AMOUNT / FUNDING_CURRENCY_CODE, BILL_TRANS_BILL_AMOUNT / BILL_TRANS_CURRENCY_CODE — the same bill amount expressed in project, funding, and transactional currencies.
• Standard Who columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY) plus the concurrent request audit columns REQUEST_ID, PROGRAM_ID, and PROGRAM_APPLICATION_ID.

Common Use Cases and Queries

Typical reporting and reconciliation scenarios include reviewing all lines attached to a draft invoice before it is released to Receivables, tracing a line back to its originating event or task, and auditing retention and multi-currency bill amounts. A representative query joining the invoice header to its lines is:

SELECT i.draft_invoice_num, it.line_num, it.invoice_line_type,
       it.task_id, it.event_num, it.amount, it.inv_amount
FROM   pa.pa_draft_invoices_all i,
       pa.pa_draft_invoice_items it
WHERE  it.project_id = i.project_id
AND    it.draft_invoice_num = i.draft_invoice_num
AND    it.project_id = :project_id
ORDER BY it.line_num;

Because the concurrent request columns are present, a frequent diagnostic pattern filters on REQUEST_ID and PROGRAM_ID to isolate the rows produced by a specific Generate Draft Invoice run, which is useful when a billing run must be explained or reprocessed. Index PA_DRAFT_INVOICE_ITEMS_N3 (PROJECT_ID, REQUEST_ID) supports this access path directly.

Related Objects

The table participates in a dense network of foreign keys. The most operationally significant relationships are:

• PA_DRAFT_INVOICES_ALL — the header table; joined via PROJECT_ID and DRAFT_INVOICE_NUM. PA_DRAFT_INVOICE_ITEMS is a child of this invoice.
• PA_DRAFT_INVOICE_DETAILS_ALL — holds the expenditure-level detail beneath each draft invoice line.
• PA_PROJECTS_ALL and PA_TASKS — provide the project and task context referenced by PROJECT_ID, CC_PROJECT_ID, TASK_ID, EVENT_TASK_ID, and CC_TAX_TASK_ID.
• PA_BILLING_CYCLES — referenced through RETN_BILLING_CYCLE_ID for retention billing cycle definition.
• GL_CODE_COMBINATIONS — referenced via CC_REV_CODE_COMBINATION_ID for the revenue distribution account.
• AR_VAT_TAX_ALL_B — referenced through OUTPUT_VAT_TAX_ID for output tax determination.
• HZ_CUST_ACCT_SITES_ALL and RA_ADDRESSES_ALL — provide the ship-to address referenced by SHIP_TO_ADDRESS_ID.
• FND_LOOKUP_VALUES — supplies the lookup meanings for the FLE_LOOKUP_TYPE columns.
• PA_CUST_REV_DIST_LINES_ALL and PA_CUST_EVENT_RDL_ALL — downstream revenue distribution tables that reference this table's key.

These relationships make PA_DRAFT_INVOICE_ITEMS the central line-level record bridging project billing activity to the invoice generation and revenue distribution processes.