Results for “pk5_column_name”

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

Overview

PA_MAP_VALUE_SETS is a reference and configuration table in the Oracle Projects (PA) schema. It stores the source or destination information used by Oracle Projects mapping functionality, where each row represents either a source or a destination definition participating in a mapping. The table acts as a metadata registry that describes value sets and the columns through which mapped values are resolved, rather than holding transactional project data itself.

Under the documented Data Vault classification, this object is identified as standalone. As a modeling suggestion, this implies PA_MAP_VALUE_SETS behaves as a reference or lookup entity without strong upstream dependencies beyond its single foreign key relationship. It is best treated as a descriptive dimension or lookup source rather than a hub, link, or satellite in a strict Data Vault sense. The table is populated through seeding rather than user-driven transaction entry: the ETRM documentation explicitly states that the data in this table should be seeded by developers. Its presence in a 12.1.1 or 12.2.2 instance therefore reflects an implementation or configuration decision, not routine end-user activity.

Key Information Stored

The table contains 17 documented columns. The most operationally significant are:

• VALUE_SET_ID — The surrogate primary key and the single documented unique index (PA_MAP_VALUE_SETS_U1). It is also the column involved in the foreign key relationship to FRM_PART_VALUE_SETS, making it the principal business-key candidate.
• VALUE_SET_CODE — The readable identifier for the value set, typically the value used in setup and diagnostics when the numeric ID is unknown.
• OBJECT_NAME — Identifies the mapped object or entity against which the value set applies.
• VALUE_COLUMN_NAME — The column from which the mapped value is sourced.
• DISPLAY_COLUMN_NAME — The column used to render a human-readable representation of the mapped value.
• PK1_COLUMN_NAME through PK5_COLUMN_NAME — Up to five key columns that define the composite primary key context for lookups, enabling multi-segment value resolution.
• SOURCE_TYPE — Distinguishes whether the record functions as a source or a destination in the mapping.
• APPLICATION_ID — Ties the value set to the owning application, supporting multi-application installations.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN, standard EBS who-columns used for change tracking.

Common Use Cases and Queries

Typical scenarios include validating mapping configuration after an upgrade, tracing why a mapped value fails to resolve, and documenting custom seeding performed during implementation. A simple lookup by value set code is the most frequent diagnostic query:

• SELECT value_set_id, value_set_code, object_name, source_type FROM pa.pa_map_value_sets WHERE value_set_code = :p_code;
• Listing all source definitions: SELECT * FROM pa.pa_map_value_sets WHERE source_type = 'SOURCE';
• Reconciling against the referenced value set table: SELECT m.value_set_code, f.* FROM pa.pa_map_value_sets m, frm_part_value_sets f WHERE m.value_set_id = f.value_set_id;
• Auditing recent changes: filter on LAST_UPDATE_DATE and LAST_UPDATED_BY to identify who reseeded configuration rows.

Because rows are seeded, reporting should generally treat this table as read-only reference data. Any corrective action should be performed through supported setup or patching processes rather than direct DML.

Related Objects

• FRM_PART_VALUE_SETS — Referenced by the documented foreign key PA_MAP_VALUE_SETS.VALUE_SET_ID → FRM_PART_VALUE_SETS. This is the primary dependency and the join target for resolving value set definitions.
• PA_MAP_VALUE_SET_COLS — The companion configuration table typically holding individual column mappings associated with each value set.
• FRM_PART_VALUE_SET_COLS — Provides the column-level detail of the underlying value set, complementing the PK1–PK5 column references in PA_MAP_VALUE_SETS.
• FND_APPLICATION — Joined via APPLICATION_ID to resolve the owning application name for a value set.
• FND_ID_FLEX_STRUCTURES / FND_ID_FLEX_SEGMENTS — Relevant where mapped value sets reference key flexfield segments used in Projects setup.
• PA_LOOKUPS and FND_LOOKUP_VALUES — Useful for decoding SOURCE_TYPE and other coded values present in the table.