Search Results action_interval

Overview

GMD_ACTIONS_VL is a translated (VL) view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the GMD — Process Manufacturing Product Development module (OPM Quality). The view presents quality action records maintained for Process Manufacturing, exposing action codes and their language-specific descriptions in a single denormalized result set. Because it is a "VL" view, it joins the base entity table to its translation table and restricts rows to the session language via the standard USERENV('LANG') predicate, so a query returns descriptions only in the language of the current session.

The object is classified as VALID in ETRM for both EBS 12.1.1 and 12.2.2, and the documented base objects are identical across those releases: the synonym GMD_ACTIONS_B for the base table and the synonym GMD_ACTIONS_TL for the translation table. In practice, the view serves as the read-only, NLS-aware presentation layer for quality action setup data, and it is the object that forms, reports, and integration queries should target rather than the underlying tables.

Underlying Base Objects

The view text is defined as a join between two documented objects:

• GMD_ACTIONS_TL (alias T) — the translation table holding ACTION_DESC for each language, joined on ACTION_CODE with T.LANGUAGE = USERENV('LANG').
• GMD_ACTIONS_B (alias B) — the base table holding the non-translated attributes, including ACTION_INTERVAL, DELETE_MARK, TEXT_CODE, WHO columns, ATTRIBUTE_CATEGORY, and ATTRIBUTE1 through ATTRIBUTE30. The join key from B to T is ACTION_CODE.

Both underlying objects are referenced through APPS synonyms, so the view always resolves in the APPS schema context. There is no documented additional filter, meaning the view does not itself exclude soft-deleted rows. Consumers must apply their own DELETE_MARK = 2 (the OPM convention for "not deleted") or equivalent filter where active records only are required.

Key Columns

• ROW_ID — the ROWID of the GMD_ACTIONS_B row, included to support updatable/identifiable row semantics and row-level processing.
• ACTION_CODE — the primary business key of the action; the join key between base and translation records.
• ACTION_DESC — the translated description of the action, sourced from GMD_ACTIONS_TL and rendered in the session language.
• ACTION_INTERVAL — the interval associated with the action, defining scheduling/timing behavior in the quality action configuration.
• DELETE_MARK — OPM soft-delete indicator; rows are logically deleted rather than physically removed.
• TEXT_CODE — reference to the OPM text/notes framework used for long descriptions.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns inherited from the base table.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE30 — the standard OPM descriptive flexfield (DFF) columns, exposed without interpretation; the flexfield structure resides in the corresponding application registration.

Common Use Cases and Queries

Typical uses include listing available quality actions in a language-specific pick list, populating custom reports or OBIEE/BI Publisher extracts, reconciling action configuration between environments, and driving integration feeds that require human-readable action descriptions. Because the view hides the translation join, it simplifies reporting code considerably.

Listing all non-deleted actions in the session language:

• SELECT action_code, action_desc, action_interval FROM apps.gmd_actions_vl WHERE delete_mark = 2 ORDER BY action_code;

Retrieving a single action, with WHO audit data:

• SELECT action_code, action_desc, action_interval, creation_date, created_by, last_update_date, last_updated_by FROM apps.gmd_actions_vl WHERE action_code = :p_action_code AND delete_mark = 2;

Reviewing descriptive flexfield content for configured actions:

• SELECT action_code, action_desc, attribute_category, attribute1, attribute2 FROM apps.gmd_actions_vl WHERE attribute_category IS NOT NULL AND delete_mark = 2;

To obtain descriptions in a language other than the session language, the underlying GMD_ACTIONS_TL must be queried directly with an explicit LANGUAGE value; the VL view always filters to USERENV('LANG'). Join the view to quality plan or results tables on ACTION_CODE when action descriptions are needed alongside transactional data. All queries should be executed under a responsibility with access to the Process Manufacturing Product Development data, and read consistency should be considered when the action setup is being maintained concurrently.