Search Results pa_draft_invoice_details_pk

Overview

PA_DRAFT_INVOICE_DETAILS_ALL is a Projects (PA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the line-level details of intercompany draft invoices generated for cross-charged transactions. When expenditures incurred in one operating unit or project are shared with, or charged to, another, Oracle Projects creates a draft intercompany invoice to recover those costs. This table holds the individual detail rows that make up each such draft invoice, binding the billed expenditure item to the invoice, project, tax, and currency context under which the recharge occurs.

The table is owned by the PA schema and is documented as VALID, with 60 columns. Its surrogate primary key is PA_DRAFT_INVOICE_DETAILS_PK, defined on the column DRAFT_INVOICE_DETAIL_ID. From a Data Vault modeling perspective (a heuristic suggestion derived from the foreign-key structure), this object leans toward a satellite: it is keyed by a single surrogate identifier and carries descriptive, transaction-scoped attributes rather than acting as a hub or a many-to-many link.

Key Information Stored

The most operationally significant columns include the following. DRAFT_INVOICE_DETAIL_ID is the surrogate primary key and uniquely identifies each detail line. EXPENDITURE_ITEM_ID references the source expenditure item in PA_EXPENDITURE_ITEMS_ALL that is being cross-charged, while LINE_NUM sequences lines within the detail set. The combination of EXPENDITURE_ITEM_ID and LINE_NUM forms the unique business-key candidate PA_DRAFT_INVOICE_DETAILS_U1/U2, distinguishing it from the surrogate key.

• PROJECT_ID — the project against which the draft invoice detail is recorded.
• CC_PROJECT_ID and CC_TAX_TASK_ID — the cross-charge (charged-to) project and task receiving the cost.
• DRAFT_INVOICE_NUM and DRAFT_INVOICE_LINE_NUM — the parent invoice and line identifiers from PA_DRAFT_INVOICES_ALL and PA_DRAFT_INVOICE_ITEMS.
• DENOM_CURRENCY_CODE, DENOM_BILL_AMOUNT, ACCT_CURRENCY_CODE, BILL_AMOUNT — the denominated and accounted currency amounts billed.
• PROJACCT_CURRENCY_CODE, PROJACCT_COST_AMOUNT, PROJACCT_BILL_AMOUNT — project functional currency cost and bill amounts.
• OUTPUT_VAT_TAX_ID and OUTPUT_TAX_EXEMPT_FLAG — tax identification and exemption status for the cross-charge.
• REVERSED_FLAG, LINE_NUM_REVERSED, DETAIL_ID_REVERSED — reversal tracking for corrected invoices.
• ORG_ID — the operating unit that owns the row.

Common Use Cases and Queries

Analysts typically query this table to reconcile intercompany cross-charge recoveries, to trace which expenditure items were recharged to a partner project, and to report draft invoice amounts by currency, project, and tax status. A representative pattern joins the source expenditure item to the detail line to validate that every cross-charged cost is invoiced exactly once:

SELECT d.DRAFT_INVOICE_NUM, d.PROJECT_ID, d.CC_PROJECT_ID, d.EXPENDITURE_ITEM_ID, d.BILL_AMOUNT, d.DENOM_CURRENCY_CODE, d.REVERSED_FLAG FROM PA.PA_DRAFT_INVOICE_DETAILS_ALL d WHERE d.PROJECT_ID = :project_id AND d.ORG_ID = :org_id;

Reversal auditing uses REVERSED_FLAG and DETAIL_ID_REVERSED to confirm that reversed lines net to zero against their originating details. VAT reporting uses OUTPUT_VAT_TAX_ID to join tax setup tables and verify exemption flags. Because the table is keyed by DRAFT_INVOICE_DETAIL_ID, drill-down reports filter on that column to isolate a single cross-charge transaction.

Related Objects

PA_DRAFT_INVOICE_DETAILS_ALL is tightly coupled to other Projects billing objects. Its parent invoice headers reside in PA_DRAFT_INVOICES_ALL (joined via PROJECT_ID, DRAFT_INVOICE_NUM), and its line-level parent rows reside in PA_DRAFT_INVOICE_ITEMS (joined via PROJECT_ID, DRAFT_INVOICE_NUM, DRAFT_INVOICE_LINE_NUM). Source costs are held in PA_EXPENDITURE_ITEMS_ALL via EXPENDITURE_ITEM_ID. Project and cross-charge project details come from PA_PROJECTS_ALL (PROJECT_ID and CC_PROJECT_ID), while cross-charge tax tasks come from PA_TASKS (CC_TAX_TASK_ID). Tax setup is referenced through AR_VAT_TAX_ALL_B (OUTPUT_VAT_TAX_ID), currency validation through FND_CURRENCIES (DENOM_CURRENCY_CODE, ACCT_CURRENCY_CODE, PROJACCT_CURRENCY_CODE), and accounting code combinations through GL_CODE_COMBINATIONS (REV_CODE_COMBINATION_ID). Downstream, PA_MC_DRAFT_INV_DETAILS_ALL, PA_DRAFT_INV_DETAILS_EFC, PA_MC_DRAFT_INV_DETS_AR, and PA_DRAFT_INV_DETS_AR all reference this table through DRAFT_INVOICE_DETAIL_ID.