Results for “action_code_id”

32 results




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

Overview

The table XDP_ACTION_CODES_TL resides in the XDP schema (Oracle Provisioning) within Oracle E-Business Suite 12.1.1 and 12.2.2. It is the language-specific translation overlay for the base action code definition held in XDP_ACTION_CODES. The ETRM metadata lists the product description as "Not used," indicating the object is retained for dictionary completeness rather than active functional use, yet its structure follows the standard EBS multilingual pattern (_TL suffix), storing translated display text keyed by language.

Its primary key, XDP_ACTION_CODES_TL_PK, spans ACTION_CODE_ID and LANGUAGE, confirming that a single action code supports multiple language rows. A heuristic Data Vault classification mined from the foreign-key structure identifies this object as satellite-leaning. In Data Vault modeling terms, this positions XDP_ACTION_CODES_TL as a descriptive satellite attached to the XDP_ACTION_CODES hub, carrying language-dependent attributes rather than business relationships.

Key Information Stored

The documented schema contains 12 columns. The most significant are:

  • ACTION_CODE_ID — Surrogate identifier and part of the composite primary key; it is also the foreign key pointing back to XDP_ACTION_CODES.
  • LANGUAGE — The second component of the primary key, designating the translation language of each row.
  • SOURCE_LANG — Indicates the source language from which the translation was derived.
  • DISPLAY_NAME — The translated, user-facing label for the action code.
  • DESCRIPTION — The translated descriptive text for the action code.
  • ZD_EDITION_NAME — Editioning column supporting EBS online patching (notably in 12.2.2).
  • SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting multi-tenant/security-group data isolation.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS WHO columns capturing audit and concurrency information.

Two unique structures are documented: the primary key XDP_ACTION_CODES_TL_PK on (ACTION_CODE_ID, LANGUAGE), and the business-key candidate XDP_ACTION_CODES_TL_U1 on (ACTION_CODE_ID, LANGUAGE, ZD_EDITION_NAME). The latter reflects the editioning requirement where the same logical key may exist across edition versions.

Common Use Cases and Queries

Because the object surfaces translated action code labels, reporting queries typically join it to its base table and constrain by language. A common retrieval pattern resolves the display text for a given installation language:

  • Join XDP_ACTION_CODES to XDP_ACTION_CODES_TL on ACTION_CODE_ID, filtering LANGUAGE = USERENV('LANG') or a fixed language code such as 'US'.
  • Use the unique index XDP_ACTION_CODES_TL_U1 to fetch a specific edition's translation by supplying ZD_EDITION_NAME.
  • Audit translation coverage by comparing row counts across LANGUAGE values to detect missing locales.
  • Security-scoped reporting joins SECURITY_GROUP_ID to FND_SECURITY_GROUPS to restrict results to the caller's group.

A representative query selects DISPLAY_NAME and DESCRIPTION for a known ACTION_CODE_ID, driving picklist and lookup rendering in provisioning screens.

Related Objects

  • XDP_ACTION_CODES — Base (non-translated) parent table; joined on ACTION_CODE_ID.
  • XDP_ACTION_CODES_TL_PK — Primary key constraint on (ACTION_CODE_ID, LANGUAGE).
  • XDP_ACTION_CODES_TL_U1 — Unique business-key index on (ACTION_CODE_ID, LANGUAGE, ZD_EDITION_NAME).
  • FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID for data isolation.
  • FND_LANGUAGES — Consulted to validate LANGUAGE and SOURCE_LANG values.
  • FND_APPLICATION / XDP provisioning forms and concurrent programs — Consume the translated labels at runtime.