Search Results pa_draft_invoices_u1

Overview

PA.PA_DRAFT_INVOICES_ALL is the header-level table for draft invoices generated by Oracle Projects (PA) billing before those invoices are transferred to Oracle Receivables as transactions. Each row represents a single draft invoice for a project, keyed by the surrogate primary key PA_PROJECT_ID combined with DRAFT_INVOICE_NUM. The table is a multi-org view over transactional data, meaning queries automatically filter rows to the operating unit of the current session based on ORG_ID. The FND Design Data registration is PA.PA_DRAFT_INVOICES_ALL, and its storage resides in the APPS_TS_TX_DATA tablespace, confirming it as a high-volume transactional object subject to standard partitioning and purge practices.

In Data Vault terms, the mined classification suggests a satellite-leaning object: project and draft invoice number together form the stable business key, while attributes such as status, flags, and amounts behave as descriptive, historically-adjusted satellite attributes. This classification is a modeling heuristic rather than an enforced constraint.

Key Information Stored

The 94 documented columns cover the full lifecycle of a draft invoice. The most operationally significant are:

• PROJECT_ID and DRAFT_INVOICE_NUM — the surrogate primary key pair, also the columns of the unique index PA_DRAFT_INVOICES_U1, which is the business-key candidate returned by the user's search.
• TRANSFER_STATUS_CODE — indicates where the draft sits in the transfer-to-Receivables lifecycle; indexed by PA_DRAFT_INVOICES_N2.
• GENERATION_ERROR_FLAG — records errors raised during invoice generation; combined with REQUEST_ID in index PA_DRAFT_INVOICES_N6.
• AGREEMENT_ID, CUSTOMER_ID, BILL_TO_CUSTOMER_ID, SHIP_TO_CUSTOMER_ID — links to billing agreements and the customer/address hierarchy.
• INVOICE_DATE, GL_DATE, PA_DATE, BILL_THROUGH_DATE — critical accounting and cut-off dates used to derive GL and PA period assignment.
• INVOICE_CURRENCY_CODE, INV_EXCHANGE_RATE, INV_RATE_TYPE, INV_RATE_DATE — currency conversion context for the billed amounts.
• UNEARNED_REVENUE_CR, UNBILLED_RECEIVABLE_DR — the core revenue and receivable figures flowing to Receivables.
• RA_INVOICE_NUMBER, SYSTEM_REFERENCE — Receivables references created after successful transfer, backing index PA_DRAFT_INVOICES_N7.
• APPROVED_BY_PERSON_ID, RELEASED_BY_PERSON_ID — approval and release audit trail, indexed by PA_DRAFT_INVOICES_N3 and N4.
• UBR_SUMMARY_ID, UER_SUMMARY_ID, PJI_SUMMARIZED_FLAG — summarization links to unconverted/unearned revenue balance summaries.
• ORG_ID — the multi-org discriminator enforcing operating-unit security.
• CANCELED_FLAG, WRITE_OFF_FLAG, CONVERTED_FLAG, RECORD_VERSION_NUMBER — operational state flags for cancellation, write-off, and optimistic locking.

Common Use Cases and Queries

Typical usage centers on monitoring draft invoice creation, transfer success, and error resolution. A common pattern filters by project and status to list pending drafts:

• SELECT DRAFT_INVOICE_NUM, INVOICE_DATE, TRANSFER_STATUS_CODE, UNBILLED_RECEIVABLE_DR FROM PA_DRAFT_INVOICES_ALL WHERE PROJECT_ID = :project_id AND TRANSFER_STATUS_CODE IS NULL;
• Reporting drafts stuck in error: SELECT PROJECT_ID, DRAFT_INVOICE_NUM, GENERATION_ERROR_FLAG FROM PA_DRAFT_INVOICES_ALL WHERE REQUEST_ID = :request_id AND GENERATION_ERROR_FLAG = 'Y';
• Reconciliation to Receivables after transfer: join on SYSTEM_REFERENCE = RA_CUSTOMER_TRX_ALL.CUSTOMER_TRX_ID and compare RA_INVOICE_NUMBER.
• Reporting approved-but-unreleased drafts using APPROVED_DATE and RELEASED_DATE with person lookups via PER_ALL_PEOPLE_F.

These queries benefit from the composite indexes on TRANSFER_STATUS_CODE, APPROVED_BY_PERSON_ID, RELEASED_BY_PERSON_ID, and RA_INVOICE_NUMBER.

Related Objects

PA_DRAFT_INVOICES_ALL is the centre of a dense relationship set. The most significant related objects are:

• PA_DRAFT_INVOICE_ITEMS / PA_DRAFT_INVOICE_DETAILS_ALL — line-level children joined on PROJECT_ID and DRAFT_INVOICE_NUM; details carry distribution, funding, and revenue split information.
• PA.PA_PROJECTS_ALL — parent project master via PROJECT_ID.
• PA.PA_AGREEMENTS_ALL — billing agreement via AGREEMENT_ID.
• RA.RA_CUSTOMER_TRX_ALL — the resulting Receivables transaction once transfer completes, referenced through SYSTEM_REFERENCE.
• HZ_CUST_ACCOUNTS and RA_ADDRESSES_ALL / HZ_CUST_ACCT_SITES_ALL — customer and address master rows for CUSTOMER_ID, BILL_TO_CUSTOMER_ID, and SHIP_TO_CUSTOMER_ID.
• GL.GL_CODE_COMBINATIONS — the receivable, rounding, unbilled, unearned, write-off, and retention accounting flexfield references.
• PA.PA_DISTRIBUTION_WARNINGS — warning records that reference the draft invoice and are useful in error triage.
• PA_MC_DRAFT_INV_ITEMS and JAI_PA_DRAFT_INVOICES — secondary children, including multi-currency and India localization extensions.

Because the object is multi-org, all runtime access is filtered through ORG_ID, and any custom reporting must respect that security model to avoid cross-operating-unit leakage.