Search Results ce_fc_pop_disc_v




Overview
Explore in AI Chat

Overview

CE_FC_POP_DISC_V is a VALID database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Cash Management (CE) product family. Its role is to present a consolidated, currency-normalized listing of purchase order related forecast cash flows tied to disbursement activity. The view is principally consumed by the Cash Management forecast engine and by downstream reporting or integration components that need a single, security-filtered projection of expected outflows derived from open purchase orders, PO terms-based orders, and temporary or prospective order records.

The name suffix "_DISC" indicates that the view is designed to feed the Forecast Disbursements framework. The amount column is negated in every UNION ALL branch, meaning disbursements are represented as outflows. Records are only surfaced when they belong to an operating unit accessible to the current user session, making the view intrinsically multi-org aware.

Underlying Base Objects

The view is a UNION ALL of four ordered blocks, each built over a distinct source view, plus common lookup, operating unit, and security objects. ETRM 12.2.2 lists the referenced objects as: CE_PO_FC_ORDERS_V, CE_PO_FC_ORDERS_TERMS_V, CE_PO_FC_ORDERS_TEMP_V, CE_PO_FC_ORDERS_TERMS_TEMP_V, CE_SECURITY_PROFILES_V, FND_LOOKUP_VALUES, HR_OPERATING_UNITS, AP_TERMS, and the packages FND_GLOBAL, FND_PROFILE, FND_ACCESS_CONTROL_UTIL, MO_GLOBAL, and XTR_USER_ACCESS.

The four CE_PO_FC_ORDERS* views supply the core PO rows. FND_LOOKUP_VALUES decodes line-level status against the lookup type 'AUTHORIZATION STATUS', filtered by USERENV('LANG') for language-specific meanings. HR_OPERATING_UNITS is joined with an outer (+) operator on ORGANIZATION_ID = ORG_ID to resolve the operating unit name. AP_TERMS supplies the payment term name only in the terms-based branches. CE_SECURITY_PROFILES_V enforces the organization-level access rule through an EXISTS predicate that requires ORGANIZATION_TYPE = 'OPERATING_UNIT'. This is the direct mechanism by which the "operating_unit" search term applies to the view.

Key Columns

  • REFERENCE_ID (as TO_CHAR): Character conversion of the source reference identifier used to trace the forecast row back to its originating transaction.
  • PO_NUM: The purchase order number associated with the anticipated disbursement.
  • AMOUNT (negated): The forecast amount expressed as a negative value to denote cash outflow; sourced directly from SRC.AMOUNT.
  • LINE_NUMBER: The PO line reference for the cash flow item.
  • STATUS MEANING: The decoded authorization status meaning obtained from FND_LOOKUP_VALUES.
  • PAYMENT_PRIORITY: Priority ranking inherited from the source PO forecast view.
  • VENDOR_TYPE: Classification of the supplier (for example, employee versus external vendor).
  • PAYGROUP: Pay group used for grouping disbursements in forecast and payment processing.
  • TERMS NAME: Payment term description, populated in the second and fourth UNION ALL branches and NULL elsewhere.
  • OPERATING UNIT NAME (HR.NAME): The name of the operating unit resolved from HR_OPERATING_UNITS.

Common Use Cases and Queries

Typical use cases include cash forecasting, operating-unit-level outflow reporting, and reconciliation of forecast disbursement lines against source purchase orders. Because the view enforces organization security internally, callers inherit the same operating unit access as the connected user.

List the anticipated disbursements for the current operating unit context:

SELECT po_num, line_number, amount, meaning, payment_priority, name
FROM apps.ce_fc_pop_disc_v
WHERE name = :operating_unit
ORDER BY po_num, line_number;

Aggregate forecast outflows by operating unit:

SELECT name AS operating_unit, SUM(amount) AS net_forecast
FROM apps.ce_fc_pop_disc_v
GROUP BY name;

Filter rows that carry payment terms versus those that do not:

SELECT po_num, terms_name, amount
FROM apps.ce_fc_pop_disc_v
WHERE terms_name IS NOT NULL;

Consultants customizing Cash Management forecasts should treat this view as read-only and be aware that security filtering depends on CE_SECURITY_PROFILES_V and the Cash Management security profile setup for each operating unit.