Results for “secured_data”

46 results




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

Overview

APPS.PA_PROJECT_FUNDINGS_V is a secured reporting view over project funding records in Oracle Projects. It exposes the allocation of a funding amount from a funding agreement to a specific project and, optionally, to a specific task, together with the full set of multi-currency amounts maintained by the funding engine. The view's distinguishing characteristic is that it does not expose raw project, task, and task-name values unconditionally. Instead, each of the four descriptive columns (project number, project name, task number, and task name) is wrapped in a DECODE(pa_security.allow_query(P.project_id), 'Y', <real value>, SUBSTR(PA_PROJ_ELEMENTS_UTILS.Get_PA_Lookup_Meaning('TRANSLATION', 'SECURED_DATA'), 1, n)) construct. When the current user is not authorized to query the project, the real value is replaced by a translated lookup meaning for the token SECURED_DATA, truncated to the appropriate column width.

This design is why user searches on the string "secured_data" resolve to this view. The token is not a column or a table; it is a substitution label that masks data the caller may not see. The view therefore serves as the security boundary for funding information consumed by concurrent programs, Oracle Forms, OAF pages, and third-party integrations.

Underlying Base Objects

The documented base objects are:

Key Columns

Common Use Cases and Queries

The view is typically queried to list funding allocated to a project, to reconcile funded amounts by currency, or to detect rows where descriptive values are masked for the current user.

  • List funding for a project with its budget type and allocated amount, ordered by allocation date.
  • Compare ALLOCATED_AMOUNT to the project functional and invoiced amounts to validate exchange rate treatment.
  • Filter on ALLOWABLE_FUNDING_LEVEL_CODE to determine whether task-level funding rows are expected for a project type.
  • Detect security masking by comparing the project number column against PA_PROJECTS_ALL.SEGMENT1 joined on PROJECT_ID.

A representative query:

SELECT project_funding_id, project_id, task_id, budget_type_code, allocated_amount, project_allocated_amount, projfunc_allocated_amount, funding_currency_code, date_allocated FROM apps.pa_project_fundings_v WHERE project_id = :p_project_id ORDER BY date_allocated;

Because the masking logic invokes PA_SECURITY for every row, queries returning large funding populations should constrain PROJECT_ID or AGREEMENT_ID whenever possible to limit the number of security evaluations performed.