Results for “assignment_id”

50+ results




Overview
Explore in AI Chat

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

Overview

PA_ADVERTISED_OPEN_REQ_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the Projects (PA) product family. It exposes the identifiers of open assignment requirements that have been advertised to the enterprise, functioning as a filtered projection over the action set infrastructure used by Oracle Project Resource Management. The view returns a single column, OBJECT_ID, representing the unique identifier of an advertised open assignment requirement. Its principal value lies in identifying which open requirements are currently eligible for advertisement display based on their action set status, the activation state of the associated advertisement action lines, and the assignment attributes of the currently logged-in user.

The view is particularly relevant to searches involving the "not_started" status. Its WHERE clause explicitly includes NOT_STARTED among the accepted STATUS_CODE values, alongside RESUMED, PAUSED, and STARTED. This means the view surfaces advertised requirements that exist in any of these lifecycle states, including those that have been configured but not yet initiated, allowing resource managers to see the full pipeline of advertised demand.

Underlying Base Objects

The view is defined over five documented base objects. PA_ACTION_SETS and PA_ACTION_SET_LINE_AUD are referenced as synonyms and hold the core action set definitions and their audited action lines respectively. PER_ALL_ASSIGNMENTS_F, referenced as a synonym, supplies assignment-level attributes for the current user. FND_USER supplies the user record linked to the session. FND_GLOBAL is referenced as a package and provides the USER_ID of the active session through FND_GLOBAL.USER_ID.

The SQL joins PA_ACTION_SETS to PA_ACTION_SET_LINE_AUD on the shared OBJECT_ID, OBJECT_TYPE, and ACTION_SET_TYPE_CODE where the action set type is ADVERTISEMENT. The existence subquery further constrains results by joining authorized advertisement lines to the current user's primary assignment, restricting output to requirements the logged-in user is entitled to see based on publication scope.

Key Columns

The view exposes a single documented column, ASSIGNMENT_ID, though the underlying view text aliases it as OBJECT_ID (ASETS.OBJECT_ID). In the context of the Projects module, this value represents the identifier of the open assignment requirement that the advertisement targets.

  • OBJECT_ID / ASSIGNMENT_ID: The primary identifier returned. It correlates to the open assignment record whose requirement has an active advertisement action set in a resolvable status.

Common Use Cases and Queries

This view is typically consumed by resource management dashboards and integration routines that must determine which advertised open requirements should be visible to a given user. It supports row-level visibility filtering driven by the session's FND_GLOBAL.USER_ID, making it unsuitable for cross-user bulk reporting without appropriate context.

A representative query listing all currently visible advertised requirements:

  • SELECT assignment_id FROM apps.pa_advertised_open_req_v;

To join the view to the open requirement entity for descriptive detail:

  • SELECT v.assignment_id, r.* FROM apps.pa_advertised_open_req_v v, apps.pa_open_assignments r WHERE v.assignment_id = r.assignment_id;

Because the view relies on FND_GLOBAL.USER_ID, it should be queried in an environment where the application session context is properly initialized, ensuring the public-to-organization and public-to-self-manager advertisement scopes resolve correctly.