Search Results pa_map_value_sets_u1

Overview

PA.PA_MAP_VALUE_SETS is a reference and configuration table in the Oracle EBS Projects (PA) schema. It stores the source or destination information used by the Projects mapping framework, where each row describes either a source or a destination value set that participates in a mapping. The table is classified as FND Design Data (PA.PA_MAP_VALUE_SETS), and its contents are intended to be seeded by developers rather than maintained by end users through standard application screens. This seeded nature reflects its role as metadata that drives the rendering and resolution of mapping columns at runtime.

From a Data Vault modeling perspective, the mined relationship structure classifies this object as standalone. This is a heuristic suggestion: the table has no downstream dependents in the documented FK graph and only a single documented outbound reference. In practice it functions as a reference or lookup-style entity rather than a transactional hub, link, or satellite. Its stable, low-volume, developer-seeded content is consistent with a reference data set that supports the Projects mapping engine.

Key Information Stored

Each row in PA_MAP_VALUE_SETS is uniquely identified by VALUE_SET_ID, a NUMBER(15) surrogate primary key enforced by the unique index PA_MAP_VALUE_SETS_U1. This index is the documented business-key candidate and the primary access path for lookups by identifier.

• VALUE_SET_ID — Surrogate unique identifier for the value set record; the single column of the unique index.
• VALUE_SET_CODE — Lookup code for the value set. The meaning associated with this lookup code is used to render the source or destination column label in the mapping UI.
• OBJECT_NAME — Name of the source or destination object for the mapping; possible objects are database tables or views.
• VALUE_COLUMN_NAME — Column holding the actual value used for mapping.
• DISPLAY_COLUMN_NAME — Column holding the value used for display purposes.
• PK1_COLUMN_NAME through PK5_COLUMN_NAME — Up to five columns that together provide the primary key of the mapping value, supporting composite-key source and destination objects.
• SOURCE_TYPE — Lookup code identifying the mapping source.
• APPLICATION_ID — Unique identifier of the owning application, scoping the value set to a specific EBS application.
• Standard WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide audit and ownership tracking.

Common Use Cases and Queries

Typical usage centers on resolving the physical column mapping for a given value set so that the mapping engine can construct the correct SQL against the source or destination object. A common query pattern retrieves the column configuration for a value set code:

• Join PA_MAP_VALUE_SETS to its lookup definitions via VALUE_SET_CODE or SOURCE_TYPE to obtain the rendered labels.
• Filter by APPLICATION_ID to isolate value sets belonging to a specific application, which is essential in multi-application EBS instances.
• Retrieve OBJECT_NAME together with VALUE_COLUMN_NAME and the PK1–PK5 columns to build dynamic SQL for a mapping source or destination.
• Audit queries that inspect CREATED_BY, CREATION_DATE, and LAST_UPDATE_DATE to identify when a developer-seeded value set was introduced or changed.

Reporting on this table is primarily diagnostic and administrative, since the content is seeded rather than user-maintained. Reconciliation reports can compare expected seeded rows against actual rows to detect missing or altered value set definitions after patching or upgrades.

Related Objects

The documented FK relationship links this table to the broader mapping value set framework:

• PA.FRM_PART_VALUE_SETS — Referenced through the FK PA_MAP_VALUE_SETS.VALUE_SET_ID → FRM_PART_VALUE_SETS, tying each mapping value set record to its parent value set definition. This is the principal documented inbound/outbound relationship.
• FND lookup tables — VALUE_SET_CODE and SOURCE_TYPE resolve against Oracle Application Object Library lookup definitions, which supply the display meanings for column labels.
• PA mapping engine objects — Runtime mapping components consume PA_MAP_VALUE_SETS rows to resolve OBJECT_NAME, VALUE_COLUMN_NAME, DISPLAY_COLUMN_NAME, and the PK1–PK5 columns when executing source and destination mappings.
• FND_APPLICATION — APPLICATION_ID resolves to the application registry, scoping value sets to their owning application.

Because the table is developer-seeded and referenced by the mapping framework, changes to its content should be treated as configuration changes subject to standard migration and patching controls across Oracle EBS 12.1.1 and 12.2.2.