Results for “pn_milestones_type”

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

Overview

APPS.PN_SET_MILESTONES_VL is a validation-level (VL) view in the Oracle E-Business Suite Projects/Property Manager (PN) module. It presents milestone definitions that are configured against milestone sets, enriching the raw transactional rows with human-readable lookup meanings and the responsible user's name. The view is a denormalized, reporting-oriented projection of PN_SET_MILESTONES joined to FND_LOOKUPS and FND_USER, which makes it suitable for concurrent programs, OAF pages, BI Publisher data templates, and inbound/outbound integration extracts that must display milestone types as descriptive text rather than raw codes.

The view is available in both Oracle EBS 12.1.1 and 12.2.2. The "_VL" suffix conventionally signals that the object is intended as a validation view, typically registered as a value set source or used by a descriptive flexfield/LOV mechanism. The user search term "pn_milestones_type" maps directly to the lookup type that the view consumes, which is why this object surfaces in that context.

Underlying Base Objects

The view is owned by APPS and is defined over the following documented base objects:

• PN_SET_MILESTONES (synonym) — the primary table holding milestone set definitions; aliased as MST and supplying the majority of columns.
• FND_LOOKUPS (view) — aliased as MLOOK, filtered on lookup_type = 'PN_MILESTONES_TYPE' and joined on lookup_code = MST.milestone_type_code to derive the descriptive meaning.
• FND_USER (synonym) — aliased as FN, joined on user_id to resolve the user_name of the responsible individual.
• FND_GLOBAL (package) — referenced by the ETRM metadata, generally used elsewhere in the module for session/context resolution but not shown in the documented view text.

The core logic is an inner join across all three sources; a milestone row is only returned when its type code matches an active PN_MILESTONES_TYPE lookup entry and its user_id resolves to a valid FND_USER record.

Key Columns

• ROW_ID — ROWID of the base PN_SET_MILESTONES row, enabling direct updates.
• MILESTONES_SET_ID / SET_ID — identifiers associating a milestone to its parent milestone set.
• MILESTONE_TYPE_CODE — the stored code value from the PN_MILESTONES_TYPE lookup.
• MILESTONE_TYPE — the lookup meaning (descriptive text) for the code; the principal reason for using the VL view.
• USER_ID and RESPONSIBLE_USER — the responsible user's ID and resolved user_name from FND_USER.
• NOTIFICATION_DATE, LEAD_DAYS, FREQUENCY — scheduling attributes controlling when and how often milestone notifications fire.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the standard DFF (descriptive flexfield) columns carried through from the base table.
• WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical scenarios include milestone setup reporting, notification scheduling audits, and LOV/value set population for milestone types.

• List milestones for a set:

  SELECT milestones_set_id, set_id, milestone_type, responsible_user, lead_days, frequency
  FROM   apps.pn_set_milestones_vl
  WHERE  milestones_set_id = :p_set_id;

• Find all milestones of a given type:

  SELECT milestones_set_id, responsible_user, notification_date
  FROM   apps.pn_set_milestones_vl
  WHERE  milestone_type_code = :p_milestone_type_code;

• Audit upcoming notifications:

  SELECT set_id, milestone_type, responsible_user, notification_date
  FROM   apps.pn_set_milestones_vl
  WHERE  notification_date >= TRUNC(SYSDATE)
  ORDER BY notification_date;

Because the view is not itself filtered by set or user, add predicates on MILESTONES_SET_ID or MILESTONE_TYPE_CODE for performance. Supplying the PN_MILESTONES_TYPE lookup codes and joining to this view is the standard way to translate a milestone type code into its display meaning.