Search Results project_description

Overview

AP_WEB_PA_PROJECTS_V is a VALID view owned by the APPS schema and classified under the AP – Payables product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its functional purpose is narrow and well defined: it supplies the Project Number list of values (LOV) used within Oracle Internet Expenses. When an expense report user assigns project-related expenditure in the Internet Expenses user interface, the selectable project numbers are drawn from this view rather than directly from the Projects tables.

The view therefore acts as a security- and organization-aware presentation layer that bridges the Payables/Internet Expenses application with the Oracle Projects data model. By exposing only the subset of projects that are valid for project expenditure entry, and by resolving the carrying-out organization to a human-readable name, it enables the Internet Expenses LOV to present ready-to-use project values without requiring users to understand project structures, organization IDs, or cross-business-group relationships.

Because it is a view rather than a table, AP_WEB_PA_PROJECTS_V holds no data of its own. It is a runtime projection evaluated at query time, which means its results are subject to the profile options, security rules, and business-group context of the querying session. This behavior is central to its design and explains why it is used for interactive LOV selection rather than for bulk extraction or reporting against a fixed snapshot.

Underlying Base Objects

The documented ETRM metadata identifies the following referenced base objects: FND_PROFILE (PACKAGE), HR_GENERAL (PACKAGE), HR_ORGANIZATION_UNITS (VIEW), HR_SECURITY (PACKAGE), PA_CROSS_BUSINESS_GRP (PACKAGE), PA_PROJECTS_EXPEND_V (VIEW), and PA_PROJECT_UTILS (PACKAGE).

The view text itself is a direct join between two objects:

• PA_PROJECTS_EXPEND_V — the primary source of project attributes (alias P), filtered and secured by the supporting packages.
• HR_ORGANIZATION_UNITS — the organization master (alias O), joined on CARRYING_OUT_ORGANIZATION_ID = ORGANIZATION_ID to translate the organization identifier into its name.

The package dependencies explain the view's context sensitivity. HR_SECURITY and HR_GENERAL enforce organization-level access, restricting visible projects according to the responsibility's security profile. PA_CROSS_BUSINESS_GRP resolves the operating/cross-business-group context so that only projects within the accessible business group are returned. PA_PROJECT_UTILS provides standard project utility logic used to determine project validity. FND_PROFILE supplies profile option values, such as the applicable business group or security settings, that govern the filtering applied at runtime. Together these objects make the view both a join and a security gate.

Key Columns

• PROJECT_ID — the unique internal identifier of the project, used as the LOV's hidden return value.
• PROJECT_NUMBER — the user-visible project number displayed in the Internet Expenses project LOV.
• PROJECT_NAME — the descriptive name of the project.
• PROJECT_DESCRIPTION — free-text description of the project.
• START_DATE — the project start date, useful for date-validity filtering.
• COMPLETION_DATE — the project completion date.
• PROJECT_TYPE — the project type classification.
• PROJECT_ORGANIZATION_ID — the carrying-out organization identifier, aliased from CARRYING_OUT_ORGANIZATION_ID.
• PROJECT_ORGANIZATION_NAME — the organization name resolved from HR_ORGANIZATION_UNITS.
• PROJECT_TYPE_CLASS_CODE — the project type class, distinguishing categories of project for expenditure purposes.

Common Use Cases and Queries

The principal use case is the Internet Expenses project number LOV. A representative query reflecting that behavior is:

• SELECT PROJECT_ID, PROJECT_NUMBER, PROJECT_NAME FROM APPS.AP_WEB_PA_PROJECTS_V ORDER BY PROJECT_NUMBER;

To inspect organization and classification context, query additional columns:

• SELECT PROJECT_NUMBER, PROJECT_NAME, PROJECT_ORGANIZATION_NAME, PROJECT_TYPE_CLASS_CODE FROM APPS.AP_WEB_PA_PROJECTS_V WHERE PROJECT_NUMBER = :p_number;

To restrict the LOV to active projects by date, filter on the date columns:

• SELECT PROJECT_ID, PROJECT_NUMBER FROM APPS.AP_WEB_PA_PROJECTS_V WHERE TRUNC(SYSDATE) BETWEEN START_DATE AND NVL(COMPLETION_DATE, SYSDATE + 1);

Because results depend on HR security and profile context, diagnostic queries should be executed under the same responsibility and session context as the original LOV. A project number that appears for one user and not another is typically a security-profile or business-group effect rather than a data discrepancy.