Results for “secured_data”

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

Overview

PA_PROJECT_FUNDINGS_V is an APPS-owned database view in the Oracle E-Business Suite Projects (PA) module. According to the ETRM metadata it is flagged as "10SC Only," and its status is VALID in both 12.1.1 and 12.2.2. The view consolidates project funding records with descriptive project, task, project type, and currency information, and it applies Oracle Projects security at the row level. For every project row, project number, project name, task number, and task name are returned only when PA_SECURITY.ALLOW_QUERY returns 'Y' for the project; otherwise those four columns are replaced by a masked literal derived from PA_PROJ_ELEMENTS_UTILS.GET_PA_LOOKUP_MEANING('TRANSLATION','SECURED_DATA'). This is the direct connection to the "secured_data" search term: the view deliberately substitutes a generic "Secured Data" label whenever the querying responsibility lacks access to the project. The view therefore functions both as a funding reporting source and as a security-enforcing presentation layer for Oracle Projects funding data.

Underlying Base Objects

The documented base objects underlying the view are:

• PA_PROJECT_FUNDINGS (SYNONYM) — the primary funding table supplying funding ID, project ID, task ID, agreement ID, budget type, allocated amounts, currency and rate attributes, and the descriptive flexfield attribute columns (ATTRIBUTE_CATEGORY and ATTRIBUTE1–10).
• PA_PROJECTS_ALL (SYNONYM) — provides project segment1, name, and billing/currency profile columns such as PROJECT_BIL_RATE_DATE_CODE, PROJFUNC_BIL_RATE_DATE_CODE, and INVPROC_CURRENCY_TYPE.
• PA_TASKS (SYNONYM) — supplies task number and task name.
• PA_PROJECT_TYPES_ALL (SYNONYM) — supplies ALLOWABLE_FUNDING_LEVEL_CODE and PROJECT_TYPE_CLASS_CODE.
• PA_SECURITY (PACKAGE) — the security engine invoked through ALLOW_QUERY to determine whether the current user may see project identifiers.
• PA_PROJ_ELEMENTS_UTILS (PACKAGE) — returns the translated "Secured Data" lookup meaning used as the mask.
• PA_MULTI_CURRENCY (PACKAGE) — via GET_USER_CONVERSION_TYPE, resolves the conversion type name for the project and project functional rate types.

The view is therefore a join of the funding fact table to project and task dimensions, enriched by project type attributes and secured through package calls.

Key Columns

• Identification: PROJECT_FUNDING_ID, PROJECT_ID, TASK_ID, AGREEMENT_ID, ROW_ID.
• Secured descriptors: PROJECT_NUMBER (SEGMENT1), PROJECT_NAME, TASK_NUMBER, TASK_NAME — each conditionally masked with the SECURED_DATA lookup.
• Funding detail: BUDGET_TYPE_CODE, ALLOCATED_AMOUNT, DATE_ALLOCATED, PM_FUNDING_REFERENCE, PM_PRODUCT_CODE.
• Project attributes: ALLOWABLE_FUNDING_LEVEL_CODE, PROJECT_TYPE_CLASS_CODE, PROJECT_BIL_RATE_DATE_CODE, PROJFUNC_BIL_RATE_DATE_CODE, INVPROC_CURRENCY_TYPE.
• Currency and rate: FUNDING_CURRENCY_CODE, PROJECT_CURRENCY_CODE, PROJECT_RATE_TYPE and PROJECT_RATE_TYPE_NAME, PROJECT_EXCHANGE_RATE, PROJECT_ALLOCATED_AMOUNT, and the parallel PROJFUNC_ and INVPROC_ rate/amount sets.
• Audit and DFF: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, ATTRIBUTE_CATEGORY and ATTRIBUTE1–10.

Common Use Cases and Queries

Typical uses include funding status reports, agreement and award funding reconciliation, and currency-basis analysis of allocated amounts. Because masking is applied by the view itself, reports built directly on it inherit Projects security without additional predicates.

List funding for the current user's accessible projects:

• SELECT project_number, project_name, task_number, budget_type_code, allocated_amount FROM apps.pa_project_fundings_v WHERE project_id = :p_project_id;

Summarize funding by project type class and currency:

• SELECT project_type_class_code, project_currency_code, SUM(allocated_amount) FROM apps.pa_project_fundings_v GROUP BY project_type_class_code, project_currency_code;

Detect records where security masking is in effect (project number returned as the secured literal):

• SELECT project_id, project_number FROM apps.pa_project_fundings_v WHERE project_number = (SELECT meaning FROM fnd_lookup_values WHERE lookup_type = 'SECURED_DATA' AND lookup_code = 'TRANSLATION');

Filtering on PROJECT_ID is preferable for large extracts, since ALLOW_QUERY is evaluated per row and can be costly across full-table scans.