Search Results gmd_activities_vl




Overview
Explore in AI Chat

Overview

GMD_ACTIVITIES_VL is a multilingual (ML) view owned by the APPS schema within the Oracle E-Business Suite environment. It belongs to the GMD product family, which covers Process Manufacturing Product Development. The view presents activity definitions used by Oracle Process Manufacturing (OPM) quality and product development functionality, exposing translated activity descriptions alongside the transactional and descriptive attributes held in the base tables.

Because the object name carries the "_VL" suffix, it is a "view with language" — the standard Oracle Applications pattern for presenting user-visible descriptive text in the session language while keeping installation-independent data in a base table. The view is documented as VALID in ETRM for both EBS 12.1.1 and 12.2.2, and it is defined as a join of GMD_ACTIVITIES_B and GMD_ACTIVITIES_TL. Its role is primarily read-only: it supports forms, concurrent programs, reports, and ad-hoc SQL that require the activity code together with its translated description.

Underlying Base Objects

The view is defined over two base objects, both registered in the APPS schema as synonyms in the documented metadata:

  • GMD_ACTIVITIES_B — the base (non-translated) table holding the activity code, cost analysis code, text code, translation counter, deletion flag, and the standard WHO audit columns.
  • GMD_ACTIVITIES_TL — the translation table holding language-specific activity descriptions.

The join is performed on the ACTIVITY column: B.ACTIVITY = T.ACTIVITY, with the additional predicate T.LANGUAGE = USERENV('LANG'). The view also exposes B.ROWID as ROW_ID. The translation counter TRANS_CNT is typically incremented whenever a translation row changes, and the language predicate ensures only the row matching the session language is returned. Where no translated row exists for the session language, the view returns no rows for that activity — the standard ML behavior that administrators must account for when validating translations.

Key Columns

  • ROW_ID — the ROWID of the base table row, exposed for tools that require a unique physical row identifier.
  • ACTIVITY — the activity code; the primary business key and the join column between the base and translation tables.
  • ACTIVITY_DESC — the translated description sourced from GMD_ACTIVITIES_TL; the primary user-facing column.
  • COST_ANALYSIS_CODE — the cost analysis code associated with the activity.
  • TEXT_CODE — reference to descriptive text (long description) stored in the standard text tables.
  • TRANS_CNT — translation counter used to track translation modifications.
  • DELETE_MARK — soft-delete indicator; rows with a non-zero value are logically deleted and should normally be filtered out.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns inherited from the base table.

Common Use Cases and Queries

The view is most often used in reports and queries that need the activity code and its translated description without manually joining the ML tables. A typical listing excludes logically deleted activities:

  • Activity LOV and validation — lookup queries for forms and concurrent programs that need only active activities with descriptions.
  • Reporting — joining GMD_ACTIVITIES_VL to quality results, specifications, or product development data by ACTIVITY to present meaningful labels.
  • Translation verification — confirming that a translated description exists for the current session language.

Sample query:

  • SELECT activity, activity_desc, cost_analysis_code
  • FROM apps.gmd_activities_vl
  • WHERE delete_mark = 0
  • ORDER BY activity;

Because the view already enforces LANGUAGE = USERENV('LANG'), no additional language predicate is required; however, queries executed under a language for which no translations exist will return fewer rows than the base table, which is an important consideration when reconciling counts.