Results for “pn_set_milestones_vl”

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

Overview

PN_SET_MILESTONES_VL is an APPS-owned view within the PN (Property Manager) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It is documented in ETRM as a validation view intended to serve as the base table for the Milestones Types region of the Milestones_Notification Set form. The view joins milestone notification set definitions to lookup meanings for milestone types and to FND_USER records for the responsible party, providing a denormalized, presentation-ready result set that simplifies form and report development.

The "_VL" suffix indicates the view carries a validation (value/lookup) layer, which in this case is implemented through FND_LOOKUPS on lookup type PN_MILESTONES_TYPE. Rather than exposing the raw MILESTONE_TYPE_CODE alone, the view resolves that code into a user-facing MILESTONE_TYPE meaning. This makes the view well suited to reporting, value-list population, and integration extracts where human-readable milestone type descriptions are required.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over the following referenced objects:

• PN_SET_MILESTONES (synonym) — the primary transactional base that supplies all milestone set attributes including NOTIFICATION_DATE, LEAD_DAYS, FREQUENCY, audit columns, and the ATTRIBUTE1–15 flexfield columns. The view selects MST.ROWID as ROW_ID to preserve row identity.
• FND_LOOKUPS (view) — joined on LOOKUP_TYPE = 'PN_MILESTONES_TYPE' and LOOKUP_CODE = MILESTONE_TYPE_CODE to derive the MILESTONE_TYPE meaning.
• FND_USER (synonym) — joined on USER_ID to resolve the RESPONSIBLE_USER name.
• FND_GLOBAL (package) — referenced for session-level context (e.g., USER_ID/ORG_ID handling) as documented in the referenced objects list.

The joins are inner joins, so records with an unmatched milestone type code or a missing user will be excluded from the result set.

Key Columns

• MILESTONES_SET_ID / SET_ID — Primary identifying keys for the notification set definition.
• MILESTONE_TYPE_CODE / MILESTONE_TYPE — The stored lookup code and its resolved meaning from FND_LOOKUPS.
• USER_ID / RESPONSIBLE_USER — The responsible user's identifier and user name.
• NOTIFICATION_DATE — The date reference used for milestone notification scheduling; central to the user's search.
• LEAD_DAYS / FREQUENCY — Notification lead time and recurrence frequency.
• ATTRIBUTE_CATEGORY / ATTRIBUTE1–15 — Descriptive flexfield segments.
• ROW_ID — Row identifier derived from PN_SET_MILESTONES.ROWID.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical scenarios include reporting upcoming or configured notifications by milestone type and responsible user, populating value lists in custom forms, and feeding notice-scheduling logic. Because NOTIFICATION_DATE is exposed directly, it is a frequent filter and ordering column.

Sample query listing active notification definitions with their resolved type and responsible user:

SELECT p.MILESTONES_SET_ID, p.SET_ID, p.MILESTONE_TYPE, p.NOTIFICATION_DATE, p.LEAD_DAYS, p.FREQUENCY, p.RESPONSIBLE_USER FROM APPS.PN_SET_MILESTONES_VL p WHERE p.NOTIFICATION_DATE >= TRUNC(SYSDATE) ORDER BY p.NOTIFICATION_DATE, p.MILESTONE_TYPE;

Sample query for a specific milestone type and owner:

SELECT p.MILESTONES_SET_ID, p.NOTIFICATION_DATE, p.RESPONSIBLE_USER FROM APPS.PN_SET_MILESTONES_VL p WHERE p.MILESTONE_TYPE_CODE = :type_code AND p.RESPONSIBLE_USER = :user_name;

Because the view resolves lookup meanings and user names, it eliminates the need for developers to join FND_LOOKUPS and FND_USER manually when building milestone notification reports or customizations.