Results for “segment_value”

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

Overview

PA_SEGMENT_VALUE_LOOKUPS is an Oracle Projects (PA) implementation table that stores user-defined mappings between AutoAccounting rule intermediate values and Accounting Flexfield segment values. Within the Oracle E-Business Suite 12.1.1 and 12.2.2 environments, AutoAccounting determines how subledgers derive accounting codes for project transactions. When an AutoAccounting rule cannot resolve a segment value directly from source data such as expenditure types, project types, or tasks, the lookup mechanism allows administrators to hard-code a specific segment value. The table records these mappings by associating a named lookup value with a particular lookup set and a specific Accounting Flexfield segment value.

Because the table holds descriptive mappings that extend a parent definition rather than acting as the central identity of a business concept, its documented foreign-key structure is classified heuristically as satellite-leaning from a Data Vault modeling perspective. In this interpretation, PA_SEGMENT_VALUE_LOOKUP_SETS functions as the hub, and PA_SEGMENT_VALUE_LOOKUPS is a satellite capturing the attribute detail (the resolved segment value) attached to that hub over time. This classification is a modeling suggestion rather than a physical constraint.

Key Information Stored

The documented schema contains eight columns. The most important include:

• SEGMENT_VALUE_LOOKUP_SET_ID — Identifies the parent lookup set to which the mapping belongs. This column is both part of the composite primary key and a foreign key to PA_SEGMENT_VALUE_LOOKUP_SETS.
• SEGMENT_VALUE_LOOKUP — The specific lookup value or intermediate value label within the set that is being translated. Together with SEGMENT_VALUE_LOOKUP_SET_ID it forms the composite primary key and business-key candidate.
• SEGMENT_VALUE — The target Accounting Flexfield segment value that AutoAccounting returns when the lookup matches.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS WHO columns capturing audit and concurrency information.

The composite primary key PA_SEGMENT_VALUE_LOOKUPS_PK (SEGMENT_VALUE_LOOKUP_SET_ID, SEGMENT_VALUE_LOOKUP) is the surrogate identifier for each row, while the unique index PA_SEGMENT_VALUE_LOOKUPS_U1 on the same two columns confirms this pair as the genuine business-key candidate. The table has no independent single-column surrogate such as a sequence-generated ID; identity is expressed through the parent set and the lookup value.

Common Use Cases and Queries

Implementation teams use this table to verify how AutoAccounting resolves segments during project setup and troubleshooting. Typical scenarios include validating that every intermediate value in a lookup set maps to a valid segment value, and auditing changes to those mappings. A representative query joins the lookup table to its parent set to present the full picture:

• Listing all mappings in a set: SELECT segment_value_lookup, segment_value FROM pa.pa_segment_value_lookups WHERE segment_value_lookup_set_id = :set_id;
• Auditing recent modifications: filter on LAST_UPDATE_DATE and LAST_UPDATED_BY to trace configuration changes.
• Reporting coverage gaps: comparing the intermediate values expected by an AutoAccounting rule against the rows actually present, to detect missing mappings.

Because the table is implementation-owned, direct DML is discouraged. Corrective actions should flow through the AutoAccounting setup forms, which respect the WHO columns and keep validation consistent.

Related Objects

The most significant related objects include:

• PA_SEGMENT_VALUE_LOOKUP_SETS — The parent table, joined on SEGMENT_VALUE_LOOKUP_SET_ID. It defines the lookup set that groups these mappings.
• AutoAccounting rule tables such as PA_AUTOACCOUNTING_RULES and their components, which determine when a lookup set is consulted during segment derivation.
• FND application and setup views that expose the lookup sets and their values to the application layer.
• GL Accounting Flexfield tables (for example GL_CODE_COMBINATIONS and FND_FLEX_VALUES), referenced indirectly so that SEGMENT_VALUE resolves to a valid segment value.

These relationships make PA_SEGMENT_VALUE_LOOKUPS a supporting configuration table whose integrity depends on the parent lookup set and on the validity of the target Accounting Flexfield values it resolves.