Search Results inv_rate_user_type




Overview
Explore in AI Chat

Overview

APPS.PAFV_INVOICE_LINES is a Business Intelligence System (BIS) view registered in the APPS schema under FND Design Data PA.PAFV_INVOICE_LINES. It is a reporting-oriented view over Oracle Projects draft invoice lines, presenting a denormalized projection of project, task, invoice, currency, and accounting attributes without exposing the underlying primary keys and surrogate columns required for transactional processing. The view is designated VALID in both Oracle EBS 12.1.1 and 12.2.2 and is documented in the ETRM repository with owner APPS.

Because the view consolidates project identification, invoice line detail, and exchange rate information into a single query surface, it is commonly used in custom reports, Oracle Business Intelligence Publisher (BI Publisher) data models, Oracle Discoverer workbooks, and ad hoc SQL where a flattened, read-only representation of draft invoice lines is required. The view carries no DML semantics; it is intended strictly for query access.

Underlying Base Objects

Per the ETRM dependency metadata, PAFV_INVOICE_LINES is defined over the following referenced base objects:

  • PA_DRAFT_INVOICE_ITEMS (synonym) — supplies the draft invoice line detail, including line number, amounts, invoice line type, and text.
  • PA_DRAFT_INVOICES_ALL (synonym) — supplies the draft invoice header context, including the draft invoice number and credited invoice reference.
  • PA_PROJECTS_ALL (synonym) — supplies project identifier, name, and project number.
  • PA_TASKS (synonym) — supplies task identifier, name, and task number used at the line level.
  • PA_CONVERSION_TYPES_V (view) — supplies the conversion type and user-defined rate type descriptions used to resolve the invoice and accounting rate type columns.

The join path follows the natural Projects hierarchy: draft invoice header to draft invoice item, item to project, item to task, and item rate type to conversion type. All joins are performed by the view definition, so consumers need not reconstruct the relationships.

Key Columns

The view exposes four logical column groups. The project and task group includes PROJECT_ID, PROJECT_NAME, PROJECT_NUMBER, TASK_ID, TASK_NAME, and TASK_NUMBER. The invoice identification group includes DRAFT_INVOICE_NUMBER, LINE_NUMBER, DRAFT_INVOICE_NUM_CREDITED, EVENT_NUMBER, EVENT_TASK_ID, and SYSTEM_REFERENCE.

The currency and conversion group is of particular interest to users searching for ACCTD_EXCHG_RATE. It contains PROJECT_CURRENCY_CODE, AMOUNT, INV_CURRENCY_CODE, INV_RATE_TYPE, INV_RATE_USER_TYPE, INV_RATE_DATE, INV_EXCHANGE_RATE, INV_AMOUNT, ACCTD_CURRENCY_CODE, ACCTD_RATE_TYPE, ACCTD_RATE_USER_TYPE, ACCTD_RATE_DATE, ACCTD_EXCHG_RATE, and ACCTD_AMOUNT. ACCTD_EXCHG_RATE holds the exchange rate applied to convert the invoice currency amount into the functional (accounted) currency, while INV_EXCHANGE_RATE holds the rate applied between project and invoice currency. The rate date columns record the effective date for each conversion.

Descriptive and audit columns include INVOICE_LINE_TEXT, the _LA:INVOICE_LINE_TYPE and _LA:TAXABLE_FLAG translated lookup columns, and the standard LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, and CREATED_BY fields.

Common Use Cases and Queries

Typical scenarios include reconciling draft invoice amounts across project, invoice, and functional currencies; auditing exchange rates used on unposted invoice lines; and feeding downstream reporting on unbilled or draft receivables. A representative query filtering on the accounted exchange rate is:

SELECT project_number, project_name, draft_invoice_number, line_number, inv_currency_code, acctd_currency_code, acctd_exchg_rate, acctd_amount FROM apps.pafv_invoice_lines WHERE acctd_exchg_rate IS NOT NULL ORDER BY project_number, draft_invoice_number, line_number;

Additional patterns include aggregating ACCTD_AMOUNT by project and currency, comparing INV_EXCHANGE_RATE with ACCTD_EXCHG_RATE to identify lines converted through differing rate types, and joining EVENT_NUMBER and EVENT_TASK_ID back to Projects expenditure items for drill-down. Because the view is read-only and resolves all lookups, these queries run without additional joins to the Projects base tables.