Results for “ce_fc_por_disc_v”

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

Overview

CE_FC_POR_DISC_V is a Cash Management (CE) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents purchase order and requisition funding data in a form suitable for forecast, reconciliation, and cash positioning workflows. The view name follows the CE naming convention: the "FC" segment denotes forecast, "POR" denotes purchase order requisition, and "DISC" indicates a disclosure or reporting variant of the underlying forecast records.

The view consolidates requisition-sourced commitment records so that treasury users and reporting tools can reconcile forecasted cash outflows attributable to purchase requisitions against source document numbers. Although the view exposes only six columns, it embeds a substantial amount of business logic: it unions committed requisition data with temporary requisition data, decodes authorization status through a lookup, resolves the operating unit name, and applies organization-level security through Cash Management security profiles. In integration scenarios, this view can be queried directly or referenced by custom concurrent programs and BI Publisher data templates rather than reimplementing the join logic.

Underlying Base Objects

The view text shows that CE_FC_POR_DISC_V is defined as a UNION ALL of two nearly identical query blocks. The first block selects from CE_PO_FC_REQUISITIONS_V, and the second from CE_PO_FC_REQUISITIONS_TEMP_V. Both source views are canonical sources of purchase requisition forecast data in Cash Management; the temporary variant accommodates records staged before final commitment.

Each block joins the source view to FND_LOOKUP_VALUES on LOOKUP_TYPE = 'AUTHORIZATION STATUS' and an outer-joined LOOKUP_CODE matching SRC.STATUS, restricted to the user session language via USERENV('LANG'). This resolves the numeric authorization status into a displayable meaning. HR_OPERATING_UNITS is outer-joined on ORGANIZATION_ID = SRC.ORG_ID to return the operating unit name. A security predicate allows rows where ORG_ID is null or where an EXISTS subquery on CE_SECURITY_PROFILES_V confirms the organization is an operating unit accessible to the current security profile. Documented references also list FND_ACCESS_CONTROL_UTIL, FND_GLOBAL, FND_PROFILE, MO_GLOBAL, and XTR_USER_ACCESS, which support the security and language resolution logic applied at runtime.

Key Columns

• REFERENCE_ID — The source reference identifier, converted to character by TO_CHAR. It links the forecast line back to the originating requisition document.
• REQ_NUM — The requisition number from the source view. This is the column most relevant to the "req_num" search, as it exposes the human-readable requisition identifier for drill-down and reconciliation.
• TRX_AMOUNT — The transaction amount, exposed as the negation of SRC.AMOUNT (-SRC.AMOUNT). The negative sign reflects that purchase requisitions represent cash outflows within the forecast.
• LINE_NUMBER — The requisition line number identifying the specific line within the requisition.
• STATUS — The decoded authorization status meaning derived from FND_LOOKUP_VALUES, providing a readable description of the requisition's authorization state.
• ORGANIZATION — The operating unit name resolved from HR_OPERATING_UNITS, subject to the security profile restrictions applied in the WHERE clause.

Common Use Cases and Queries

The view is typically used to list outstanding purchase requisition commitments by requisition number and operating unit, often filtered to a specific organization or status. A representative query is:

SELECT req_num, line_number, trx_amount, status, organization
FROM apps.ce_fc_por_disc_v
WHERE organization = 'Vision Operations';

To locate a specific requisition, users query on the requisition number directly:

SELECT req_num, reference_id, line_number, trx_amount, status
FROM apps.ce_fc_por_disc_v
WHERE req_num = :p_req_num;

Because the view applies Cash Management security profiles, results are automatically limited to operating units the responsibility is authorized to access, making it safe to expose in self-service and treasury reporting. When the same logical requisition appears in both committed and temporary sources, the UNION ALL may return duplicate REQ_NUM values; consumers should aggregate or deduplicate accordingly. For language-sensitive reporting, the decoded STATUS reflects the session language. Users are advised to run such queries with a MO or CE responsibility whose security profile grants access to the target operating unit.