Search Results project_ou

Overview

PA_PO_PROJECTS_EXPEND_V is a Projects (PA) module view owned by the APPS schema in Oracle E-Business Suite. Its documented purpose is to show the projects included in the list of values for expenditure entry originating from Purchasing (PO). The view is the access-controlled layer that drives the project selection list of values (LOV) presented to users when they enter project-related expenditures sourced from PO transactions. It is registered as VALID in both Oracle EBS 12.1.1 and 12.2.2.

Functionally, the view provides a filtered and security-scoped projection of project attributes. Rather than exposing every project in the operating unit, it restricts the returned rows to those the current user is entitled to access for PO expenditure entry, based on the PA_PO_INTEGRATION_UTILS.PA_USER_PO_ACCESS_PROJ function. This makes the view a targeted integration component between the Projects and Purchasing applications rather than a general-purpose project listing.

Underlying Base Objects

The view is defined over PA_PROJECTS_EXPEND_V, aliased as P in the view text. All columns exposed by PA_PO_PROJECTS_EXPEND_V are drawn directly from that underlying view, and the row set is further constrained by a predicate that calls the PA_PO_INTEGRATION_UTILS package function. The documented referenced objects are:

• PA_PROJECTS_EXPEND_V (VIEW) — the primary source of all selected columns.
• PA_PO_INTEGRATION_UTILS (PACKAGE) — supplies PA_USER_PO_ACCESS_PROJ(PROJECT_ID, FND_GLOBAL.USER_ID), the per-project access check that filters rows.
• FND_GLOBAL (PACKAGE) — provides USER_ID for the current session, which is passed into the access function.
• PA_PROJECT_UTILS, PA_CROSS_BUSINESS_GRP, and FND_PROFILE (PACKAGES) — referenced indirectly through the underlying view and the access/security logic.

The effective predicate is conceptually: rows are returned only where PA_PO_INTEGRATION_UTILS.PA_USER_PO_ACCESS_PROJ(PROJECT_ID, FND_GLOBAL.USER_ID) is not equal to 'N'. This row-level security logic ties project visibility to both the specific project and the authenticated user.

Key Columns

The view exposes twenty-one columns inherited from PA_PROJECTS_EXPEND_V. The most significant for reporting and integration are:

• PROJECT_ID — primary identifier used for joins and the access-check call.
• PROJECT_NUMBER and PROJECT_NAME — the user-facing identifiers shown in the LOV; PROJECT_NUMBER_SORT_ORDER supports ordering.
• PROJECT_DESCRIPTION, START_DATE, and COMPLETION_DATE — descriptive and date-range attributes.
• PROJECT_TYPE and PROJECT_TYPE_CLASS_CODE — classification of the project.
• PROJECT_STATUS_CODE — lifecycle status of the project.
• ALLOW_CROSS_CHARGE_FLAG — indicates whether cross-charge transactions are permitted.
• PROJECT_CURRENCY_CODE, PROJFUNC_CURRENCY_CODE, PROJECT_RATE_DATE, PROJECT_RATE_TYPE, PROJFUNC_COST_RATE_DATE, and PROJFUNC_COST_RATE_TYPE — currency and rate context for costing.
• CARRYING_OUT_ORGANIZATION_ID, PROJECT_OU, EXPENDITURE_OU, and OPERATING_UNIT — organizational context used for access control and cross-business-group logic.

Common Use Cases and Queries

Typical uses include validating which projects a user may select for PO expenditure entry, driving custom LOVs, and auditing project access scope. A representative query is:

• SELECT PROJECT_ID, PROJECT_NUMBER, PROJECT_NAME, PROJECT_STATUS_CODE FROM APPS.PA_PO_PROJECTS_EXPEND_V;
• SELECT PROJECT_NUMBER, EXPENDITURE_OU, ALLOW_CROSS_CHARGE_FLAG FROM APPS.PA_PO_PROJECTS_EXPEND_V WHERE PROJECT_STATUS_CODE = 'APPROVED';
• SELECT PROJECT_ID, PROJECT_NUMBER FROM APPS.PA_PO_PROJECTS_EXPEND_V WHERE PROJECT_ID = :project_id;

Because the view applies USER_ID-based security, results differ by session; in testing, FND_GLOBAL.USER_ID determines the visible project set. Oracle Proprietary, Confidential Information — Legal Notices apply.