Search Results jai_pa_setup_preferences




Overview
Explore in AI Chat

Overview

JA.JAI_PA_SETUP_PREFERENCES is a configuration table within the Asia/Pacific Localizations (JA) product family of Oracle E-Business Suite. Its documented purpose is to store preferences of Context Type based on a distribution rule. In practice, the table acts as the preference-resolution layer that the JA localization engine consults when determining how transactional or setup data should be distributed across contexts defined for a given operating unit or legal entity. The record set is small by design, since preferences are configuration artifacts rather than transactional data, yet the table governs behaviour across downstream processes that rely on context-aware distribution.

The ETRM data-vault classification for this object is satellite-leaning. This is a heuristic modeling suggestion: the table carries a surrogate primary key SETUP_PREFERENCE_ID together with descriptive attributes and an audit trail, and it references a parent via CONTEXT_ID to JAI_PA_SETUP_CONTEXTS. Treated as a Data Vault satellite, it would attach to a context hub (the parent) and hold the descriptive preference payload and its change history. It is not a pure hub, since its grain is not a unique business key, nor a pure link, since it does not resolve a many-to-many relationship between two hubs.

Key Information Stored

The physical schema documented for ETRM 12.2.2 exposes eleven columns. The most significant are:

  • SETUP_PREFERENCE_ID — surrogate primary key, enforced by JAI_PA_SETUP_PREFERENCES_PK. It uniquely identifies each preference row.
  • CONTEXT_ID — foreign key to JAI_PA_SETUP_CONTEXTS. It associates the preference with the context under which it applies, and is the join column used by nearly every query against this table.
  • DISTRIBUTION_RULE — the distribution rule that the preference is scoped to. This, together with the context, determines when a preference takes effect.
  • PREFERENCE — the preference value itself, the payload consumed by the localization logic.
  • ZD_EDITION_NAME — the edition identifier used for edition-based redefinition (EBR) in 12.2.x. Combined with SETUP_PREFERENCE_ID, it forms the unique index JAI_PA_SETUP_PREFERENCES_U1, which is the documented business-key candidate.
  • OBJECT_VERSION_NUMBER — optimistic locking column supporting concurrent update control.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS audit columns, recording who created and last modified each preference row and when.

Note the separation between the surrogate key (SETUP_PREFERENCE_ID) and the business-key candidate declared through the unique index (SETUP_PREFERENCE_ID, ZD_EDITION_NAME). The latter is primarily an EBR construct; the meaningful business identification is the combination of context, distribution rule and preference.

Common Use Cases and Queries

The table is most frequently read during diagnostic investigation of localization behaviour — for example, determining which preference a given context/distribution-rule pair resolves to, or auditing when a preference configuration changed. A typical pattern resolves the context description for each preference:

  • Join JAI_PA_SETUP_PREFERENCES to JAI_PA_SETUP_CONTEXTS on CONTEXT_ID = CONTEXT_ID to report context name alongside preference and distribution rule.
  • Filter by ZD_EDITION_NAME to inspect the currently active edition in a 12.2.x environment.
  • Order or group by LAST_UPDATE_DATE to trace recent configuration changes and identify the LAST_UPDATED_BY user responsible.
  • Compare PREFERENCE values across contexts for the same DISTRIBUTION_RULE to detect inconsistent setup.

A representative query form is: SELECT p.SETUP_PREFERENCE_ID, p.DISTRIBUTION_RULE, p.PREFERENCE, c.CONTEXT_NAME FROM JAI_PA_SETUP_PREFERENCES p, JAI_PA_SETUP_CONTEXTS c WHERE p.CONTEXT_ID = c.CONTEXT_ID AND p.ZD_EDITION_NAME = :edition. In 12.1.1, where EBR is not present, the ZD_EDITION_NAME predicate should be omitted.

Related Objects

  • JAI_PA_SETUP_CONTEXTS — the parent table referenced by CONTEXT_ID; the principal join partner and the object that defines the contexts to which preferences are bound.
  • JAI_PA_SETUP_PREFERENCES_PK — the primary key constraint on SETUP_PREFERENCE_ID.
  • JAI_PA_SETUP_PREFERENCES_U1 — the unique index on SETUP_PREFERENCE_ID, ZD_EDITION_NAME, supporting edition-scoped lookups.
  • JA localization setup and distribution APIs that consume context and preference metadata during configuration and transaction processing.
  • Standard EBS audit and EBR infrastructure referenced by the audit columns and ZD_EDITION_NAME.