Results for “bill_trans_currency_code”

50+ results




Overview
Explore in AI Chat

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

Overview

PA_CE_BILLING_EVENTS_V is an APPS-owned database view within the Oracle EBS Projects (PA) module. It unifies project billing event data drawn from two distinct contexts: billable events that have not yet been transferred into a draft invoice, and events that already appear as lines on an unreleased draft invoice. This design makes the view a consolidated reporting and integration surface for event-based billing, allowing downstream processes and reports to query billing events and their invoice-side representation through a single definition rather than joining multiple tables independently.

The view is defined as a UNION ALL of two SELECT statements. Because it spans both pre-invoice and draft-invoice states, it is particularly useful to applications that must reason about what has been billed versus what remains to be billed on a given project. It is a read-only construct (a view), so it does not store data and reflects the current state of its underlying base objects at query time.

Underlying Base Objects

The view is defined over the following documented base objects in the APPS schema:

The two branches are combined with UNION ALL, and the column positions are aligned so that the same output structure supports both event-only and draft-invoice rows.

Key Columns

  • PROJECT_ID — the project identifier, common to both branches.
  • AMOUNT / BASE_AMOUNT — in the first branch both map to EV.BILL_AMOUNT; in the second branch AMOUNT maps to ITEM1.INV_AMOUNT and BASE_AMOUNT to ITEM1.AMOUNT, distinguishing invoiced amount from base amount.
  • CURRENCY_CODE / FUNCTIONAL_CURRENCY_CODE — the transaction currency and the functional currency resolved through PA_CURRENCY.GET_CURRENCY_CODE.
  • TRX_DATE — derived from EV.COMPLETION_DATE, the event completion date.
  • ORG_ID — the operating unit identifier from the project or invoice header.
  • TRX_NUMBER / LINE_NUM — populated in the draft-invoice branch from DRAFT_INVOICE_NUM and LINE_NUM; NULL for unconsumed events.
  • INVOICE_LINE_TYPE — the invoice line classification from PA_DRAFT_INVOICE_ITEMS. This is the column associated with the search term "invoice_line_type" and is populated only for rows originating from a draft invoice; it is a TO_CHAR(NULL) placeholder in the event-only branch.
  • EVENT_NUM / TASK_ID — the billing event number and task identifier linking events to project tasks.
  • BILL_TRANS_BILL_AMOUNT / BILL_TRANS_CURRENCY_CODE — the billed transaction amount and its currency.

Common Use Cases and Queries

Typical uses include reconciling billable events against draft invoices, identifying events not yet invoiced, and segmenting billed amounts by invoice line type.

List draft invoice events with their line type:

  • SELECT project_id, event_num, task_id, trx_number, line_num, invoice_line_type, amount FROM pa_ce_billing_events_v WHERE invoice_line_type IS NOT NULL;

Identify uninvoiced events (no invoice line type, no invoice number):

  • SELECT project_id, event_num, bill_trans_bill_amount, trx_date FROM pa_ce_billing_events_v WHERE trx_number IS NULL AND invoice_line_type IS NULL;

Summarize amounts by project and line type:

  • SELECT project_id, invoice_line_type, SUM(amount) FROM pa_ce_billing_events_v GROUP BY project_id, invoice_line_type;

Because the view returns only unreleased draft invoices in its second branch and excludes events already summed into positive invoice amounts in its first branch, queries should account for the possibility that a given event appears in exactly one state. Filtering on INVOICE_LINE_TYPE is the standard way to isolate rows that have entered the invoice pipeline.