Results for “projfunc_currency”

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

Overview

APPS.PA_DRAFT_INVOICE_LINES_ALL_V is a reporting and integration view in Oracle EBS Projects (PA) that exposes draft invoice line details used during the billing cycle prior to invoice generation. Unlike released invoice interfaces, this view surfaces draft lines retained in the PA_DRAFT_INVOICES_ALL / PA_DRAFT_INVOICE_ITEMS tables and enriches them with task, event, tax, and currency context. In Oracle EBS 12.1.1 and 12.2.2 the view is a key source for reports, extensions, and interfaces that must reflect provisional billing data before the draft is finalized and transferred to Oracle Receivables.

The view is particularly relevant to currency handling. The user search term "project_currency" maps directly to the view's currency derivation logic, which resolves the invoicing currency according to the invoice processing currency type (PROJFUNC_CURRENCY, PROJECT_CURRENCY, or funding currency) and joins conversion types from PA_CONVERSION_TYPES_V.

Underlying Base Objects

The view is defined over the following documented objects:

• PA_DRAFT_INVOICES_ALL and PA_DRAFT_INVOICE_ITEMS — the primary draft invoice and line records (aliased I).
• PA_EVENTS — provides event-level attributes such as EVENT_ID, COMPLETION_DATE, and billing transaction currency (EV).
• PA_TASKS — supplies TASK_NUMBER, TASK_NAME, and event task identifiers.
• PA_PROJECTS_ALL — the driving project record (PR), used to evaluate INVPROC_CURRENCY_TYPE.
• PA_CONVERSION_TYPES_V — joins to resolve user_conversion_type for the applicable currency conversion.
• AR_VAT_TAX_ALL — tax code lookup for output VAT lines.
• AR_LOOKUPS — meaning values for tax classification and related codes.
• HZ_CUST_ACCT_SITES_ALL, HZ_PARTY_SITES, and HZ_LOCATIONS — assemble the formatted WORK_SITE address (city, state, postal code).

Because the FROM clause includes these objects, the view is a denormalized projection spanning billing, event, task, tax, and party/location data.

Key Columns

• ROW_ID, PROJECT_ID, DRAFT_INVOICE_NUM, LINE_NUM, DRAFT_INV_LINE_NUM_CREDITED — line identity and credit linkage.
• AMOUNT, INV_AMOUNT, ACCT_AMOUNT, ROUNDING_AMOUNT — bill and accounting amounts.
• PROJECT_CURRENCY_CODE and PROJFUNC_CURRENCY_CODE — project functional and project currency codes carried on the line.
• INVPROC_CURRENCY_CODE — the invoice processing currency.
• TRANSLATED_TEXT — invoice line description text.
• EVENT_ID, EVENT_NUM, EVENT_TASK_NUMBER, TASK_NUMBER, TASK_NAME, COMPLETION_DATE — event and task context.
• WORK_SITE — formatted ship-to location derived from HZ tables.
• TAXABLE_FLAG, OUTPUT_VAT_TAX_ID, OUTPUT_TAX_EXEMPT_FLAG, TAX_CODE, and lookup MEANING columns — tax attributes.
• Currency rate columns (rate dates and exchange rates resolved via DECODE on INVPROC_CURRENCY_TYPE) — including PROJECT_INV_RATE_DATE, PROJECT_INV_EXCHANGE_RATE, PROJFUNC_INV_RATE_DATE, and PROJFUNC_INV_EXCHANGE_RATE.
• Standard WHO columns such as LAST_UPDATE_DATE, CREATED_BY, and PROGRAM_ID.

Common Use Cases and Queries

Typical uses include draft billing review reports, reconciliation of project currency versus invoice processing currency, and pre-transfer validation of tax and rounding amounts. A representative query filtering by project currency follows:

SELECT dil.PROJECT_ID, dil.DRAFT_INVOICE_NUM, dil.LINE_NUM, dil.PROJECT_CURRENCY_CODE, dil.INVPROC_CURRENCY_CODE, dil.AMOUNT, dil.PROJFUNC_BILL_AMOUNT, dil.TASK_NUMBER, dil.WORK_SITE FROM APPS.PA_DRAFT_INVOICE_LINES_ALL_V dil WHERE dil.PROJECT_CURRENCY_CODE = :project_currency AND dil.PROJECT_ID = :project_id ORDER BY dil.DRAFT_INVOICE_NUM, dil.LINE_NUM;

The view is read-only and is suited to reporting rather than DML; updates to draft lines must be performed against the underlying PA_DRAFT_INVOICE_ITEMS table.