Results for “segment_value_lookup_set_id”

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

Overview

PA_SEGMENT_VALUE_LOOKUP_SETS is a Projects (PA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores implementation-defined lists of segment value lookups. Each row represents a named lookup set, which acts as a container or grouping header for one or more individual segment value lookup entries maintained in the child table PA_SEGMENT_VALUE_LOOKUPS. Lookup sets allow implementers and administrators to define reusable, controlled collections of segment values that can subsequently be attached to project accounting rules, thereby governing which segment values are valid for a given business context.

Because this table functions as the parent or anchor for dependent detail rows, the heuristic Data Vault classification derived from the foreign key structure is hub-leaning. In a Data Vault modeling sense, PA_SEGMENT_VALUE_LOOKUP_SETS behaves like a hub: it holds a stable business entity (the lookup set), keyed by a surrogate identifier, with descriptive attributes, and it is referenced by multiple dependent and referencing tables. This classification is a modeling suggestion only; the table remains a standard transactional/master-style EBS table with standard WHO audit columns.

Key Information Stored

The table is documented with eight physical columns. The most significant are:

• SEGMENT_VALUE_LOOKUP_SET_ID — The surrogate primary key, backed by the unique index PA_SEGMENT_VALUE_LOOKUP_SET_PK, and also enforced through PA_SEGMENT_VALUE_LOOKUP_SET_U1. This is the value propagated to child and referencing tables.
• SEGMENT_VALUE_LOOKUP_SET_NAME — The user-facing name of the lookup set. It is a business-key candidate, enforced by the unique index PA_SEGMENT_VALUE_LOOKUP_SET_U2, which guarantees uniqueness of the name.
• DESCRIPTION — Free-text description explaining the purpose or scope of the lookup set.
• LAST_UPDATE_DATE — Date the row was most recently modified; used for audit and incremental extraction.
• LAST_UPDATED_BY — The user or process that last modified the row.
• CREATION_DATE — Date the row was originally created.
• CREATED_BY — The user or process that created the row.
• LAST_UPDATE_LOGIN — The login identifier associated with the last update, used for session-level auditing.

The distinction between the surrogate key (SEGMENT_VALUE_LOOKUP_SET_ID) and the natural business key (SEGMENT_VALUE_LOOKUP_SET_NAME) is important for integration and de-duplication logic, since both are protected by unique indexes.

Common Use Cases and Queries

Typical uses include identifying which project accounting rules reference a given lookup set, validating that a lookup set exists before attaching it to a rule, and reporting on the defined lookup sets available in an implementation. A representative query to list all lookup sets is:

• SELECT SEGMENT_VALUE_LOOKUP_SET_ID, SEGMENT_VALUE_LOOKUP_SET_NAME, DESCRIPTION FROM PA.PA_SEGMENT_VALUE_LOOKUP_SETS ORDER BY SEGMENT_VALUE_LOOKUP_SET_NAME;

To find the individual lookup entries within a set, join to the child table on the shared key:

• SELECT s.SEGMENT_VALUE_LOOKUP_SET_NAME, l.* FROM PA.PA_SEGMENT_VALUE_LOOKUP_SETS s, PA.PA_SEGMENT_VALUE_LOOKUPS l WHERE s.SEGMENT_VALUE_LOOKUP_SET_ID = l.SEGMENT_VALUE_LOOKUP_SET_ID;

To determine which rules depend on a specific set, join to PA_RULES:

• SELECT r.* FROM PA.PA_RULES r, PA.PA_SEGMENT_VALUE_LOOKUP_SETS s WHERE r.SEGMENT_VALUE_LOOKUP_SET_ID = s.SEGMENT_VALUE_LOOKUP_SET_ID AND s.SEGMENT_VALUE_LOOKUP_SET_NAME = :name;

Such queries support configuration validation, migration testing, and impact analysis before modifying or removing a lookup set.

Related Objects

The documented foreign key relationships identify the principal objects that reference or depend on this table:

• PA_RULES — References this table through PA_RULES.SEGMENT_VALUE_LOOKUP_SET_ID, linking project accounting rules to their assigned lookup set.
• PA_SEGMENT_VALUE_LOOKUPS — The child detail table, related via PA_SEGMENT_VALUE_LOOKUPS.SEGMENT_VALUE_LOOKUP_SET_ID, holding the individual segment value entries belonging to each set.

Because the ETRM metadata documents only these two referencing objects, they constitute the primary dependency surface. Administrators and developers should treat PA_SEGMENT_VALUE_LOOKUP_SETS as the header/master entity for segment value lookup configuration within the Projects module, with PA_SEGMENT_VALUE_LOOKUPS as its detail and PA_RULES as its principal consumer.