Search Results requested_by_name

Overview

PA_LAUNCH_PAGE_ACTIONS_V is a consolidated reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Projects (PA) product family. As its name implies, the view assembles a unified list of actions associated with deliverables in the Project Management and ETRM (Enterprise Track and Resource Management) context. It is valid across both 12.1.1 and 12.2.2 releases and forms part of the "launch page" user interface layer, where project managers and administrators review outstanding actions tied to specific deliverables.

The view is not a base transactional object; it is a denormalized projection whose purpose is to present, in a single row per action, all of the descriptive and relationship data required by the launch page. Because it is a view rather than a table, it inherits the read consistency and security of its underlying objects and is typically the target of reports, OTBI-style extracts, and diagnostic queries rather than DML operations.

Underlying Base Objects

Documented base objects referenced by the view include PA_PROJ_ELEMENTS, PA_PROJ_ELEMENT_VERSIONS, and PA_PROJ_ELEM_VER_SCHEDULE, which supply the action and deliverable identities, their versioning, and the scheduled finish dates. PA_PROJECTS_ALL provides the parent project name and number, while PA_OBJECT_RELATIONSHIPS links deliverables to actions using the DELIVERABLE_TO_ACTION relationship subtype. Party information for requestors and owners is resolved from HZ_PARTIES, with PA_UTILS.GET_PARTY_ID used to map creation users to party records. Lookup meanings are derived via PA_PROJ_ELEMENTS_UTILS.GET_PA_LOOKUP_MEANING and PA_LOOKUPS, and project status comes from PA_PROJECT_STATUSES. Additional synonyms such as PA_CI_ACTIONS, PA_CONTROL_ITEMS, and the PA_CI_TYPES_TL/PA_CI_TYPES_B pair are documented in the dependency list, reflecting the broader action framework the view participates in.

Key Columns

• PROJ_ELEMENT_ID and ELEMENT_VERSION_ID — identify the action and its version.
• LOOKUP_CODE / MEANING — classification of the deliverable action type.
• NAME (project), SEGMENT1, and PROJECT_ID — the owning project.
• REQUESTOR.PARTY_NAME and REQUESTOR.PARTY_ID — the "requested by" party, derived from PPE.CREATED_BY. This is the column returned by the requested_by_name search and is the primary user-facing field on the launch page.
• OWNER.PARTY_NAME / OWNER.PARTY_ID — the deliverable manager, matched via the PER: origin system reference.
• MANAGER_PERSON_ID — the internal person identifier of the manager.
• SCHEDULED_FINISH_DATE and the derived SCHEDULED_FINISH_DATE - TRUNC(SYSDATE) — the due date and days remaining.
• PROJECT_STATUS_NAME, PROJECT_STATUS_CODE, PROJECT_SYSTEM_STATUS_CODE — current deliverable status.

Common Use Cases and Queries

The most common request is to list actions with the name of the person who requested them, which directly explains the requested_by_name search term:

SELECT project_id,
       name,
       requested_by_name,
       scheduled_finish_date,
       scheduled_finish_date - TRUNC(SYSDATE) days_remaining
FROM   apps.pa_launch_page_actions_v
WHERE  requested_by_name IS NOT NULL
ORDER  BY scheduled_finish_date;

Other practical uses include identifying overdue actions by manager, auditing deliverables without a valid requestor party, and building dashboard extracts keyed on project_id and project_status_code. Because the view filters out template projects (TEMPLATE_FLAG <> 'Y') and restricts to PA_ACTIONS and PA_DELIVERABLES object types, queries return only live project actions, making it well suited for operational reporting and integration extracts.