Search Results released_by_person_name




Overview

APPS.PAFV_CUSTOMER_INVOICES is a Business Intelligence System (BIS) view in the Oracle E-Business Suite APPS schema, catalogued under FND Design Data as PA.PAFV_CUSTOMER_INVOICES. It presents information about draft invoices generated for a project, consolidating project billing data with the associated receivables transactions, agreement information, and the personnel records for the users who approved or released each draft invoice. Because it is a BIS view rather than a transactional table, it is intended for read-only reporting, extraction, and analytical workloads; Oracle explicitly marks it as internal use only and does not support direct DML or ad-hoc application access outside of standard Oracle Applications programs.

The view is central to project billing reporting in ETRM releases 12.1.1 and 12.2.2, where users commonly join draft invoice, receivables, and HR person data to answer questions such as who approved a given invoice, when it was released to Oracle Receivables, and how it transferred to the general ledger. The presence of the APPROVED_BY_PERSON_NAME and RELEASED_BY_PERSON_NAME columns makes the view particularly relevant to audit-oriented searches.

Underlying Base Objects

The documented metadata identifies the following referenced base objects, and the view derives directly from them:

The view therefore functions as a pre-joined reporting layer over the project billing and receivables subledgers, with the HR person and organization joins being the reason that name-based columns are available without the user having to write the joins manually.

Key Columns

Common Use Cases and Queries

A frequent requirement is reporting approver and releaser names for audit or workflow review, which maps directly to the search term approved_by_person_name. For example:

  • List all draft invoices approved by a named person: SELECT project_id, draft_invoice_num, approved_by_person_name, approved_date FROM apps.pafv_customer_invoices WHERE approved_by_person_name = :name;
  • Report invoices released but not yet transferred, using RELEASED_DATE populated and TRANSFERRED_DATE null.
  • Reconcile project draft invoices to receivables by joining on TRX_NUMBER or CUSTOMER_TRX_ID.
  • Produce an instructional report of transfer rejections grouped by TRANSFER_REJECTION_REASON.

All queries should constrain by ORG_ID where operating unit security applies, and because the object is a BIS view marked internal use only, it should be consumed through supported reporting tools rather than treated as a general-purpose application interface.