Results for “invoice_comment”

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

Overview

PAFV_CUSTOMER_INVOICES is a business view owned by the APPS schema in Oracle E-Business Suite, defined within the Projects (PA) module. It presents consolidated information about draft invoices generated by projects, exposing both billing and personnel attributes so that reporting tools and integrations can surface the current state of project-related invoices without joining the underlying transactional tables directly. The view is marked VALID and is available in both Oracle EBS 12.1.1 and 12.2.2, where it is documented in the ETRM repository with its referenced base objects and view text.

The view is particularly relevant to security-conscious reporting: it applies an organization security predicate (_SEC:PDI.ORG_ID) and resolves several descriptive values through lookup translation, including transfer status and generation error meaning. Because the view encapsulates these translations and joins, it functions as a stable, denormalized reporting source for draft invoice status, approval, release, and transfer activity.

Underlying Base Objects

The view is defined over the following documented base objects:

• PA_DRAFT_INVOICES_ALL — the central table supplying draft invoice numbers, dates, amounts, transfer status, and the approved/released person identifiers.
• PA_PROJECTS_ALL — joined on PROJECT_ID to supply the project description and identifier.
• RA_CUSTOMER_TRX_ALL — outer-joined via SYSTEM_REFERENCE to the customer transaction ID, providing TRX_NUMBER and TRX_DATE when the draft invoice has been transferred to Receivables.
• PA_AGREEMENTS_ALL — joined on AGREEMENT_ID to associate the invoice with its project agreement.
• PA_LOOKUPS — a view used to derive the invoice class meaning by evaluating cancellation, write-off, and credit memo flags.
• PER_ALL_PEOPLE_F — joined twice (aliased PAP1 and PAP2) to resolve the full names of the approver and the releaser, with effective-date predicates applied against the current date.
• HR_ALL_ORGANIZATION_UNITS and HR_ALL_ORGANIZATION_UNITS_TL — provide the operating unit identifier and its translated name.

A self-join on PA_DRAFT_INVOICES_ALL (aliased PDIC) links a credit memo back to the draft invoice it credits through DRAFT_INVOICE_NUM_CREDITED.

Key Columns

• DRAFT_INVOICE_NUM, PROJECT_ID, AGREEMENT_ID — core identifiers for the draft invoice and its project/agreement context.
• APPROVED_DATE, RELEASED_DATE, INVOICE_DATE, GL_DATE, BILL_THROUGH_DATE — lifecycle dates tracking approval, release, invoicing, GL accounting, and billing cutoff.
• APPROVED_BY_PERSON_ID / PAP1.FULL_NAME — the approver and resolved name.
• RELEASED_BY_PERSON_ID / PAP2.FULL_NAME — the releaser and resolved name. This pair is the object most frequently sought when users search for released_by_person_name, since the view surfaces the releaser's full name directly.
• TRANSFER_STATUS_CODE, TRANSFERRED_DATE, TRANSFER_REJECTION_REASON, RA_INVOICE_NUMBER, TRX_NUMBER, TRX_DATE — transfer-to-Receivables status and results.
• UNEARNED_REVENUE_CR, UNBILLED_RECEIVABLE_DR — accounting amounts associated with the draft invoice.
• ORG_ID, TL.NAME — operating unit and its translated name, subject to the view's security predicate.

Common Use Cases and Queries

Typical uses include auditing which user released a given draft invoice, reporting invoice generation errors, and reconciling project invoices transferred to Receivables.

SELECT draft_invoice_num, project_id,
       released_by_person_id, full_name AS released_by_person_name,
       released_date, approved_date
FROM   apps.pafv_customer_invoices
WHERE  released_date IS NOT NULL;

To review transfer status and any rejection reasons:

SELECT draft_invoice_num, ra_invoice_number,
       transfer_status_code, transferred_date,
       transfer_rejection_reason
FROM   apps.pafv_customer_invoices
WHERE  transfer_status_code IS NOT NULL;

Because the view enforces the ORG_ID security predicate, queries automatically return only the operating units accessible to the connected responsibility, and effective-dated person joins ensure the approver and releaser names reflect the current person record.