Search Results project_ou




Overview
Explore in AI Chat

Overview

APPS.PA_PO_PROJECTS_EXPEND_V is a reporting and integration view in Oracle E-Business Suite that exposes project expenditure attributes specifically for Oracle Purchasing (PO) integration. It is owned by the APPS schema and references PA_PROJECTS_EXPEND_V as its primary source, filtering and enriching the results with a user-level access check. This view is designed so that only projects to which the current user has valid PO access are returned, making it suitable for LOVs, purchasing inquiry forms, and integration interfaces where projects are matched to purchase orders, requisitions, and related expenditure documents.

The view carries a broad column set including project identity, currency, rate information, operating unit, and the critical ALLOW_CROSS_CHARGE_FLAG attribute. Because it is a synonym-style API-facing view, it abstracts the underlying access logic so that consuming forms and reports do not need to implement user-access validation themselves. This is a key element in Oracle EBS 12.1.1 and 12.2.2 for cross-charge and cross-business-group project expenditure handling in Purchasing.

Underlying Base Objects

The view's SELECT statement is defined over a single primary object, PA_PROJECTS_EXPEND_V, aliased as P, with a WHERE clause invoking the package function PA_PO_INTEGRATION_UTILS.PA_USER_PO_ACCESS_PROJ(PROJECT_ID, FND_GLOBAL.USER_ID). Documented referenced objects include FND_GLOBAL (PACKAGE), FND_PROFILE (PACKAGE), PA_CROSS_BUSINESS_GRP (PACKAGE), PA_PO_INTEGRATION_UTILS (PACKAGE), PA_PROJECTS_EXPEND_V (VIEW), and PA_PROJECT_UTILS (PACKAGE).

  • PA_PROJECTS_EXPEND_V provides the base project expenditure and currency derivation logic.
  • PA_PO_INTEGRATION_UTILS supplies PA_USER_PO_ACCESS_PROJ, which determines whether the current user may view a project for PO purposes, returning values evaluated against the literal 'N'.
  • FND_GLOBAL and FND_PROFILE supply session context, user identity, and profile option values used in access and currency derivation.
  • PA_CROSS_BUSINESS_GRP and PA_PROJECT_UTILS support cross-business-group and general project utility logic leveraged by the underlying view and access function.

Key Columns

The view exposes the following columns, as documented in the ETRM metadata. ALLOW_CROSS_CHARGE_FLAG, the search term of interest, indicates whether a project permits cross-charge transactions, which is fundamental in Oracle Purchasing project charging and intercompany/cross-business-group expenditure flows.

Common Use Cases and Queries

Typical usage includes populating project LOVs in Purchasing, validating project chargeability during requisition and PO entry, and feeding interface tables that require user-restricted project expenditure data. A basic query follows:

  • SELECT project_number, project_name, allow_cross_charge_flag, project_currency_code, operating_unit FROM apps.pa_po_projects_expend_v WHERE project_status_code = 'APPROVED';
  • Filtering by cross-charge eligibility: ... WHERE allow_cross_charge_flag = 'Y' AND operating_unit = :p_org_id;
  • Joining to purchasing tables to confirm project-to-PO linkage using project_id or project_number.

Because access is enforced by PA_USER_PO_ACCESS_PROJ, no additional row-level security predicate is required in consuming queries. This makes the view reliable for both 12.1.1 and 12.2.2 reporting and integration development.