Results for “ce_fc_pab_disc_v”

26 results




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

Overview

The CE_FC_PAB_DISC_V view is a Cash Management (CE) reporting object shipped in the APPS schema of Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes billing event and invoice distribution data flowing from Oracle Projects and Oracle Receivables into Cash Management, presenting one row per billable event line together with its invoice line type. The view is read-only and carries a VALID status in the ETRM repository; it is intended for inquiry and integration rather than direct DML.

The name elements indicate its purpose: "CE" denotes Cash Management, "FC" denotes forecast, "PAB" references the Project Accounting Billing (PA/CE billing events) source, and "DISC" indicates a discovery or distribution view. Functionally, CE_FC_PAB_DISC_V is a security-filtered, denormalized projection of billing event rows that supports cash forecasting and reconciliation of invoiced project activity against expected receipts. The object was originally catalogued in the ETRM documentation with the note that the user search term "invoice_line_type" maps directly to its INVOICE_LINE_TYPE column, which is derived from the FND_LOOKUP_VALUES lookup type 'INVOICE LINE TYPE'.

Underlying Base Objects

The documented base and referenced objects for CE_FC_PAB_DISC_V are:

The view text builds a synthetic REFERENCE_ID by concatenating PROJECT_ID with the literal 'X' and EVENT_NUM, then exposes the event number, amount, transaction number, and line number alongside the lookup-derived meaning and organization name. The WHERE clause enforces security by requiring either a NULL ORG_ID or an EXISTS match against CE_SECURITY_PROFILES_V for the row's ORG_ID with ORGANIZATION_TYPE = 'OPERATING_UNIT'.

Key Columns

  • REFERENCE_ID — synthetic key: PROJECT_ID || 'X' || EVENT_NUM.
  • EVENT_NUM — billing event number from the Projects/Receivables billing stream.
  • TRX_AMOUNT — monetary amount associated with the billing event or distribution line.
  • TRX_NUMBER — transaction number of the related invoice or transaction.
  • LINE_NUM — line number within the transaction.
  • INVOICE_LINE_TYPE — the lookup meaning of the source INVOICE_LINE_TYPE code (the searched term), resolved from FND_LOOKUP_VALUES.
  • ORGANIZATION — operating unit name from HR_OPERATING_UNITS, populated where ORG_ID matches.

Common Use Cases and Queries

Typical uses include cash forecasting by invoice line type, reconciliation of billed project events to receipts, and security-scoped reporting of billing distributions for a given operating unit.

  • List distributions for an operating unit: SELECT REFERENCE_ID, EVENT_NUM, TRX_NUMBER, LINE_NUM, INVOICE_LINE_TYPE, TRX_AMOUNT, ORGANIZATION FROM APPS.CE_FC_PAB_DISC_V WHERE ORGANIZATION = :org;
  • Filter by the searched attribute: WHERE INVOICE_LINE_TYPE = 'Line' to isolate a specific invoice line type.
  • Aggregate amounts by line type for forecasting: SELECT INVOICE_LINE_TYPE, SUM(TRX_AMOUNT) FROM APPS.CE_FC_PAB_DISC_V GROUP BY INVOICE_LINE_TYPE;
  • Join to Receivables or Projects tables on TRX_NUMBER or EVENT_NUM for drill-down reconciliation.

Because security is embedded in the view's WHERE clause, callers may query it directly without re-implementing organization access restrictions.