Results for “milestone_type_code”

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

Overview

PN_SET_MILESTONES is a Property Manager (PN) module setup table in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the milestone definition records that belong to a milestone set. Where PN_SET_TYPES defines the header or grouping for a set of milestones, PN_SET_MILESTONES holds the individual milestone configuration rows that are associated with that set. This is configuration data rather than transactional data: it drives how the Property Manager application schedules, notifies, and tracks milestone events against leases, properties, and related contracts.

The ETRM metadata classifies this object, on a heuristic basis derived from its foreign key structure, as satellite-leaning. In Data Vault modeling terms this suggests treating PN_SET_MILESTONES as a satellite attached to the PN_SET_TYPES hub, with the SET_ID foreign key providing the link back to the parent set and the descriptive milestone attributes (type, lead time, frequency, notification date, user) representing the satellite's changing descriptive payload.

Key Information Stored

The table contains 28 documented columns. The most significant are:

• MILESTONES_SET_ID — the surrogate primary key, defined by the PN_SET_MILESTONES_PK constraint. It uniquely identifies each milestone setup row.
• SET_ID — foreign key to PN_SET_TYPES. This is the business link that ties each milestone row to its parent milestone set, and is the principal candidate for a business-key relationship.
• MILESTONE_TYPE_CODE — classifies the nature of the milestone (for example, an option, renewal, or notice event) and drives downstream processing logic.
• USER_ID — the application user responsible for or associated with the milestone.
• LEAD_DAYS — the number of days in advance of the milestone date that notification or action should be triggered.
• NOTIFICATION_DATE — the date on which notification is generated for the milestone.
• FREQUENCY — the recurrence interval for recurring milestone events.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle EBS flexfield (descriptive flexfield) columns, providing extensible, customer-defined attributes.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns tracking record creation and modification.

Common Use Cases and Queries

Typical usage centers on reporting and validating milestone configuration. A common pattern retrieves all milestones for a given set:

• SELECT m.milestones_set_id, m.milestone_type_code, m.lead_days, m.frequency, m.notification_date FROM pn_set_milestones m WHERE m.set_id = :set_id;
• Joining to the parent set to describe configuration: SELECT s.set_id, m.milestone_type_code, m.lead_days FROM pn_set_types s, pn_set_milestones m WHERE s.set_id = m.set_id;
• Auditing recently changed setup rows using LAST_UPDATE_DATE to detect configuration drift.
• Reporting on lead-day distributions to validate notification scheduling across milestone sets.

These queries support configuration review, migration validation between environments (12.1.1 to 12.2.2), and reconciliation of milestone definitions tied to specific milestone types or users.

Related Objects

• PN_SET_TYPES — the parent table; joined via PN_SET_MILESTONES.SET_ID = PN_SET_TYPES.SET_ID. This is the primary documented foreign key relationship.
• PN_SET_MILESTONES_PK — the primary key constraint on MILESTONES_SET_ID that enforces uniqueness.
• FND_USER — referenced conceptually through USER_ID, CREATED_BY, and LAST_UPDATED_BY for user attribution.
• FND_FLEX_VALUES / FND_DESCR_FLEX_COL_USAGE_TL — support the ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 descriptive flexfield columns.
• Other PN module setup and transaction tables that consume milestone definitions (leases, options, and property records) depend indirectly on this configuration through the milestone set relationship.

Because the documented relationship data exposes only the single SET_ID foreign key to PN_SET_TYPES, integration and reporting should anchor on that join, treating PN_SET_MILESTONES as a satellite of the milestone set hub for modeling and lineage purposes.