Results for “ahl_mc_rules_vl”

34 results




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

Overview

In Oracle E-Business Suite 12.1.1 and 12.2.2, AHL_MC_RULES_VL is a seed data (non-key flexfield) view owned by the APPS schema within the AHL – Complex Maintenance Repair and Overhaul product family. It is a translated ("_VL") view whose purpose is to expose Maintenance Coordination rule header information in a language-aware manner. Specifically, it presents both translation-independent columns (the mandatory, language-neutral attributes of a rule) and translatable columns (the descriptive text that varies by installed language). The view is documented with a status of VALID and is catalogued in ETRM as a reporting and integration access point over the MC rule definition tables.

Because rule descriptions must be presented to users in their own session language, Oracle stores the core rule record separately from its translation. This view joins the two together and filters the translation to the language of the current database session via USERENV('LANG'), so that consumers of the view see only the row that matches their environment. This makes AHL_MC_RULES_VL a convenient single-source object for reports, concurrent programs, and integrations that need rule header details without having to write explicit language-join logic.

Underlying Base Objects

The view is defined over two documented base objects, both referenced in the ETRM metadata as synonyms:

  • AHL_MC_RULES_B – the translation-independent ("base") table holding the rule header record.
  • AHL_MC_RULES_TL – the translation table holding language-specific descriptive text.

The definition joins the two on RULE_ID and restricts the translation with the condition TL.LANGUAGE = USERENV('LANG'). This is the standard Oracle multi-language ("_VL") pattern: the _B table supplies the primary key, DFF attributes, and control columns, while the _TL table supplies the description for the session language. The view text selects B.ROWID as ROW_ID from the base table, which is a common convention for VL views. No other base objects are referenced in the documented definition.

Key Columns

Common Use Cases and Queries

The view is typically used to list or validate maintenance coordination rules for a given header or date range, and to retrieve rule descriptions in the session language. A basic query is:

  • SELECT RULE_ID, RULE_NAME, RULE_TYPE_CODE, DESCRIPTION FROM AHL_MC_RULES_VL WHERE MC_HEADER_ID = :p_header_id;
  • SELECT RULE_ID, RULE_NAME, ACTIVE_START_DATE, ACTIVE_END_DATE FROM AHL_MC_RULES_VL WHERE SYSDATE BETWEEN ACTIVE_START_DATE AND ACTIVE_END_DATE;
  • SELECT RULE_ID, ATTRIBUTE1, ATTRIBUTE2 FROM AHL_MC_RULES_VL WHERE ATTRIBUTE_CATEGORY = :p_category;

Typical scenarios include generating rule listings for CMMS/reporting extracts, populating LOVs or forms that need language-correct descriptions, and integration interfaces that must reconcile rule headers by RULE_ID. Because the view already enforces the session-language join, reports built on it automatically display translated descriptions without additional language handling.