Results for “acctd_rate_date”

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

Overview

PA_DRAFT_INVOICES_AR is an archive and purge companion table to PA_DRAFT_INVOICES in the Oracle Projects (PA) module of Oracle E-Business Suite 12.1.1 and 12.2.2. Draft invoices represent billing events that Oracle Projects has generated but not yet transferred to Oracle Receivables. When these invoice records reach the end of their retention lifecycle, the Archive and Purge process migrates them out of the transactional table into this shadow table, preserving the audit trail while keeping the live draft invoice table lean. The table carries 96 documented columns and is owned by the PA schema. It is a standalone object from a referential standpoint: the heuristic Data Vault classification derived from its foreign key structure identifies it as a standalone entity rather than a hub, link, or satellite. From a dimensional modeling perspective, it is best treated as a historical snapshot or archival satellite keyed to the purge batch, since its grain is one archived draft invoice row per purge execution context.

Key Information Stored

PA_DRAFT_INVOICES_AR mirrors the column structure of the live draft invoice table, with ARCHIVE/PURGE control columns added at the front of the physical definition. The purge orchestration columns are the distinguishing feature of this table. PURGE_BATCH_ID is the foreign key to PA_PURGE_BATCHES_ALL and identifies the batch run that archived the row; PURGE_RELEASE, PURGE_PROJECT_ID, and PURGE_FLAG provide release and project scope together with the removal marker. SYSTEM_REFERENCE, DRAFT_INVOICE_NUM, and DRAFT_INVOICE_NUM_CREDITED carry the business identifier of the invoice and any related credit memo, while PROJECT_ID, ORG_ID, and AGREEMENT_ID anchor the billing context. Status and lifecycle columns include TRANSFER_STATUS_CODE, APPROVED_DATE, APPROVED_BY_PERSON_ID, RELEASED_DATE, RELEASED_BY_PERSON_ID, TRANSFERRED_DATE, and TRANSFER_REJECTION_REASON. Financial and accounting columns such as INVOICE_DATE, GL_DATE, PA_DATE, BILL_THROUGH_DATE, INV_CURRENCY_CODE, INV_EXCHANGE_RATE, RECEIVABLE_CODE_COMBINATION_ID, UNBILLED_CODE_COMBINATION_ID, UNEARNED_CODE_COMBINATION_ID, and RETENTION_PERCENTAGE retain the monetary and accounting attributes needed for audit and reconstructing the archived invoice. A RECORD_VERSION_NUMBER column supports optimistic locking. Because the table is an archive target, the metadata does not document a dedicated surrogate primary key or unique business index; identity is effectively established by the combination of PURGE_BATCH_ID and the original draft invoice identifier (DRAFT_INVOICE_NUM), consistent with the archive-by-batch access pattern.

Common Use Cases and Queries

The primary use case is auditing and reconstructing invoice history after the transactional draft invoice has been purged. Reports typically constrain by project, batch, or date. For example, to list all archived invoices for a project within a purge batch:

• SELECT DRAFT_INVOICE_NUM, INVOICE_DATE, TRANSFER_STATUS_CODE, INV_CURRENCY_CODE FROM PA.PA_DRAFT_INVOICES_AR WHERE PURGE_BATCH_ID = :batch_id AND PROJECT_ID = :project_id;
• SELECT PURGE_BATCH_ID, COUNT(*) FROM PA.PA_DRAFT_INVOICES_AR GROUP BY PURGE_BATCH_ID ORDER BY PURGE_BATCH_ID; to reconcile archive volumes per batch.
• SELECT DRAFT_INVOICE_NUM, TRANSFERRED_DATE, RA_INVOICE_NUMBER FROM PA.PA_DRAFT_INVOICES_AR WHERE TRANSFERRED_DATE IS NOT NULL AND PROJECT_ID = :project_id; to trace which archived drafts reached Receivables and under which RA invoice number.

Other scenarios include regulatory retention reporting, historical revenue and unbilled receivable analysis, and troubleshooting transfer rejections recorded in TRANSFER_REJECTION_REASON.

Related Objects

The documented foreign key relationship links PURGE_BATCH_ID to PA_PURGE_BATCHES_ALL, which is the controlling parent for all archived rows and the most significant related object. Other significant dependencies, by column correspondence, include the live PA_DRAFT_INVOICES table (from which rows are archived), the RA interface tables used during transfer to Receivables, and PA_PROJECTS_ALL via PROJECT_ID for project context. The code combination references (RECEIVABLE_CODE_COMBINATION_ID, UNBILLED_CODE_COMBINATION_ID, UNEARNED_CODE_COMBINATION_ID, WOFF_CODE_COMBINATION_ID, RETN_CODE_COMBINATION_ID, UNBILLED_RECEIVABLE_DR, UNEARNED_REVENUE_CR) join to GL_CODE_COMBINATIONS for accounting validation, while ORG_ID and AGREEMENT_ID map to HR_OPERATING_UNITS and PA_AGREEMENTS respectively. The Oracle Projects Archive and Purge concurrent programs, together with the Purge Batches APIs that populate PA_PURGE_BATCHES_ALL, govern the population and cleanup of this table.