Search Results config_status_desc




Overview
Explore in AI Chat

Overview

The AHL_MC_HEADERS_V view is a reporting and integration object within the Oracle E-Business Suite AHL (Complex Maintenance Repair and Overhaul) module. It exposes Master Configuration header information together with the lookup meanings and descriptions that correspond to the configuration status code, so that consumers of the view receive human-readable status text rather than raw lookup codes. In Oracle EBS 12.1.1 and 12.2.2, the object is owned by the APPS schema and carries a VALID status.

The view is built on the base and translation tables of the master configuration entity, combined with the relationship table and the seeded AHL_CONFIG_STATUS lookup. Its principal functional value is the resolution of CONFIG_STATUS_CODE. The view does not simply return the stored code; it applies logic that can substitute the value 'EXPIRED' when the associated active end date has passed, and then joins to FND_LOOKUP_VALUES_VL to obtain the corresponding meaning and description. This makes the view particularly useful for queries and reports that need a current, meaningful configuration status, which is the context in which the search term "config_status_code" arises.

Underlying Base Objects

The documented base objects referenced by AHL_MC_HEADERS_V are AHL_MC_HEADERS_B, AHL_MC_HEADERS_TL, AHL_MC_RELATIONSHIPS, and FND_LOOKUP_VALUES_VL. All of the AHL objects are exposed to the view as synonyms within the APPS schema.

  • AHL_MC_HEADERS_VL — the view-level source that combines the base table AHL_MC_HEADERS_B and the translation table AHL_MC_HEADERS_TL; supplies identifiers, name, version, revision, description, audit columns, and the attribute columns.
  • AHL_MC_RELATIONSHIPS — supplies the relationship rows used to determine the active end date that drives the expiration logic; the join restricts to the top-level relationship (PARENT_RELATIONSHIP_ID IS NULL).
  • FND_LOOKUP_VALUES_VL — supplies the meaning and description for the resolved status, filtered on LOOKUP_TYPE = 'AHL_CONFIG_STATUS'. The join to this lookup is an outer join, so rows are not lost when a lookup value is missing.

The join between AHL_MC_HEADERS_VL and AHL_MC_RELATIONSHIPS is on MC_HEADER_ID, and the deterministic relationship selection ensures a single corresponding relationship row per configuration header.

Key Columns

The view exposes the following principal columns:

  • ROW_ID — the ROWID of the underlying header row, useful for direct row addressing.
  • MC_HEADER_ID — the primary identifier of the master configuration header.
  • NAME, MC_ID, VERSION_NUMBER, REVISION — identifying and versioning attributes of the configuration.
  • CONFIG_STATUS_CODE — the resolved status code. If the stored code is 'CLOSED' it is returned unchanged; otherwise, if the active end date is in the past, the value 'EXPIRED' is returned; otherwise the stored code is returned.
  • CONFIG_STATUS_MEANING — the meaning of the resolved status from the AHL_CONFIG_STATUS lookup.
  • CONFIG_STATUS_DESC — the description of the resolved status from the same lookup.
  • Audit and descriptive columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, SECURITY_GROUP_ID, DESCRIPTION, and ATTRIBUTE_CATEGORY through ATTRIBUTE15.

Common Use Cases and Queries

The view is commonly used to report current configuration status, to feed integration interfaces that require decoded status values, and to identify configurations whose status has effectively expired even though no explicit status change was recorded. A typical query lists active configurations with their status meaning:

  • SELECT mc_header_id, name, config_status_code, config_status_meaning FROM ahl_mc_headers_v WHERE config_status_code = 'EXPIRED';
  • SELECT name, version_number, revision, config_status_meaning FROM ahl_mc_headers_v WHERE config_status_code = 'CLOSED';
  • SELECT m.name, m.config_status_meaning, m.description FROM ahl_mc_headers_v m WHERE m.config_status_code IN ('RELEASED','EXPIRED') ORDER BY m.name;

Because the expiration logic depends on the current date at execution time, results for non-closed configurations can change between runs without any data modification, which should be considered when the view output is persisted or compared across time.