Results for “pn_set_types”

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

Overview

PN_SET_TYPES is a Property Manager (PN) module table in Oracle EBS Release 12.1.1 and 12.2.2 that defines the categories, or "types," used to group milestones. Its documented description is "Type of milestones grouping." In practice, the table functions as a reference or lookup master for milestone set definitions, allowing Property Manager users to organize related milestones into logical groupings that can then be assigned to properties, leases, or other PN entities. Because PN milestones underpin lease administration, option tracking, and critical-date management, PN_SET_TYPES provides the classification layer that makes milestone reporting and lifecycle monitoring meaningful.

From a Data Vault modeling perspective, the heuristic classification for this table is hub-leaning. PN_SET_TYPES behaves primarily as a hub: its surrogate key (SET_ID) uniquely identifies each set type, and the table is referenced by foreign keys from dependent tables. Analysts building a Data Vault or dimensional model may therefore treat SET_ID as a hub business key, with descriptive attributes such as SET_NAME and DESCRIPTION modeled as satellites.

Key Information Stored

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

• SET_ID — The surrogate primary key, defined by the constraint PN_SET_TYPES_PK. It uniquely identifies each milestone set type and is the column propagated to child tables as a foreign key.
• SET_NAME — The business-facing name of the milestone grouping. This is the value users select when assigning or filtering milestones.
• DESCRIPTION — Free-text explanation of the set type's purpose, typically displayed in lookup lists and reports to clarify the grouping's intent.
• LANGUAGE — The language code for the row. Combined with SET_ID, this forms the unique index PN_SET_TYPE_U1, making (SET_ID, LANGUAGE) the business-key candidate. This also indicates the table is translatable.
• SOURCE_LANG — The source language of the translation, used by the multilingual translation framework to identify the base row.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — The standard Oracle EBS WHO columns that capture audit and concurrency information for each row.

The distinction between the surrogate key (SET_ID) and the composite unique key (SET_ID, LANGUAGE) is important: a single logical set type may exist as multiple language rows sharing the same SET_ID. Queries that ignore LANGUAGE risk returning duplicate rows.

Common Use Cases and Queries

Typical usage includes populating a milestone-set-type lookup in a Property Manager form, validating a milestone assignment during lease creation, and reporting on milestones grouped by set type. A basic lookup query filters by language to avoid duplication:

• SELECT SET_ID, SET_NAME, DESCRIPTION FROM PN.PN_SET_TYPES WHERE LANGUAGE = USERENV('LANG');
• Joining to milestones: SELECT st.SET_NAME, sm.* FROM PN.PN_SET_TYPES st, PN.PN_SET_MILESTONES sm WHERE st.SET_ID = sm.SET_ID AND st.LANGUAGE = USERENV('LANG');
• Finding unused set types via an outer join against PN_SET_MILESTONES to support cleanup and governance.

Reporting scenarios include milestone dashboards grouped by set type, audit reports on recently created or modified set types, and migration validation scripts confirming that every PN_SET_MILESTONES.SET_ID resolves to a valid parent row.

Related Objects

The principal dependent object is PN_SET_MILESTONES, which references PN_SET_TYPES through the column PN_SET_MILESTONES.SET_ID. This foreign-key relationship is the only documented link and defines the parent-child hierarchy in which set types group their constituent milestones. Because the metadata documents a single referencing table, the relationship graph is intentionally narrow.

In a broader EBS context, integration and reporting objects that surface milestone data — such as Property Manager milestone inquiry forms, concurrent programs, and interface tables — will resolve set-type names through PN_SET_TYPES by joining on SET_ID with a LANGUAGE filter. Any extract, BI Publisher report, or data warehouse load touching PN_SET_MILESTONES should include PN_SET_TYPES to supply the descriptive SET_NAME and DESCRIPTION attributes rather than exposing raw ID values.