Search Results pa_draft_inv_items_bas

Overview

PA_DRAFT_INVOICES_FORM_MRC_V is a Projects (PA) module view in Oracle EBS 12.1.1 and 12.2.2 that provides a consolidated, multi‑reporting‑currency (MRC) presentation of draft project invoices. It joins the header‑level draft invoice table PA_DRAFT_INVOICES with the line‑level tables PA_DRAFT_INVOICE_ITEMS and PA_MC_DRAFT_INV_ITEMS to expose both transactional and converted currency information in a single row. As its name implies, the view was built primarily to support the Draft Invoice form and related inquiry/reporting pages, but it is fully queryable by custom SQL, BI Publisher reports, and integration extracts. Because it sources fields from the MRC child table, it is particularly useful when Project Billing is configured to hold multiple reporting currencies, allowing reconciliation between the entered invoice currency and the functional/reporting currency amounts. Note that the ETRM implementation metadata for this object indicates it is not implemented in the database in the reference instance, meaning the view text is documented but the object may not exist in every environment; developers should verify existence and validity before referencing it.

Underlying Base Objects

The documented base objects for this view are:

• PA_DRAFT_INVOICES – the invoice header table (aliased I), supplying invoice number, dates, status flags, currency, and DFF attributes.
• PA_DRAFT_INVOICE_ITEMS – the invoice line table, providing line‑level detail for the draft invoice.
• PA_MC_DRAFT_INV_ITEMS – the multi‑currency child table holding converted amounts per reporting currency.

The view text additionally joins several supporting master/reference objects, including PER_ALL_PEOPLE_F (approved by / released by person names and numbers), PA_PROJECTS and PA_PROJECT_STATUSES (project name, number, status), PA_DISTRIBUTION_RULES (distribution rule meaning), HR_ORGANIZATION_UNITS (project organization), HZ_PARTIES and RA_CUSTOMERS (customer), OKC_AGREEMENTS (agreement and terms), FND_LOOKUPS (invoice status and invoice class), and GL_DAILY_CONVERSION_TYPES (rate type meaning). No referenced base objects were otherwise recorded in the ETRM metadata beyond the three primary tables, so the join relationships should be confirmed from the view source in the target instance.

Key Columns

• ROW_ID, PROJECT_ID, PROJECT_NUMBER, PROJECT_NAME – identity of the owning project, sourced from PA_PROJECTS.
• DRAFT_INVOICE_NUM, RA_INVOICE_NUMBER, INVOICE_DATE, GL_DATE, PA_DATE – invoice identification and accounting dates.
• TRANSFER_STATUS_CODE, INVOICE_STATUS_CODE / INVOICE_STATUS_M, CHK_STATUS – status indicators; CHK_STATUS is derived via nested DECODE from the generation error flag, approval date, release date, and transfer status code (values such as ERROR, UNAPPROVED, UNRELEASED, RELEASED, REJECTED, TRANSFERRED, ACCEPTED).
• APPROVED_BY_PERSON_ID / NAME / NUMBER, RELEASED_BY_PERSON_ID / NAME / NUMBER – approver and releaser information from PER_ALL_PEOPLE_F.
• INV_CURRENCY_CODE, INV_RATE_TYPE, INV_RATE_DATE, INV_EXCHANGE_RATE, USER_CONVERSION_TYPE, PROJECT_CURRENCY_CODE – currency and exchange rate details, including the MRC conversion type.
• CUSTOMER_ID, PARTY_NAME, PARTY_NUMBER, AGREEMENT_ID, AGREEMENT_NUM, TERM_ID, TERM_NAME – customer and billing agreement context.
• CANCELED_FLAG, WRITE_OFF_FLAG, CONVERTED_FLAG, EXTRACTED_DATE, RETENTION_PERCENTAGE – billing lifecycle flags.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE10 – descriptive flexfield columns.

Common Use Cases and Queries

Typical usage includes reconciliation of draft invoice headers to their MRC line amounts, reporting on approval/release cycles, and building extracts for downstream invoicing or analytics. A basic query listing unreleased draft invoices is shown below.

SELECT project_number, project_name, draft_invoice_num, invoice_date,
    invoice_status_m, chk_status, inv_currency_code, project_currency_code
  FROM pa_draft_invoices_form_mrc_v
 WHERE chk_status IN ('UNAPPROVED','UNRELEASED')
   AND canceled_flag = 'N';

For MRC reconciliation, join or filter on INV_CURRENCY_CODE and the converted amounts surfaced through PA_MC_DRAFT_INV_ITEMS, and use TRANSFER_STATUS_CODE to isolate transferred or accepted invoices for financial reconciliation. Note that because the view combines header and line sources, row multiplicity may occur; aggregate functions (SUM, COUNT DISTINCT) should be applied carefully. The search term pa_draft_inv_items_bas reflects a closely related base table name; the view is the appropriate consolidated source when users need header, line, and MRC data together rather than querying that base table directly.