Results for “manufacture_date_to”

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, the view APPS.AHL_MR_EFFECTIVITY_DTLS_V is a reporting and integration object within the AHL (Complex Maintenance Repair and Overhaul) product family. It presents the detail rows that define the applicability, or effectivity, of a maintenance requirement against specific unit characteristics such as manufacturer, serial number range, manufacturing date range, and country of origin. The underlying transactional table, AHL_MR_EFFECTIVITY_DTLS, stores these criteria in coded form; the view enriches each row with human-readable descriptions by joining to territory, lookup, and manufacturer reference data. This makes the view well suited for operational reporting, concurrent program output, and inbound/outbound integration interfaces where deciphered values are required rather than raw identifiers.

The view status is VALID in the APPS schema. Its role is largely read-only, surfacing effectivity detail lines for display in OAF pages, BI Publisher reports, and custom SQL extracts.

Underlying Base Objects

The view is defined over four documented base objects. AHL_MR_EFFECTIVITY_DTLS (exposed through a SYNONYM) is the driving table and supplies the effectivity detail attributes. FND_TERRITORIES_VL is a view supplying the translated territory short name, joined on COUNTRY_CODE to TERRITORY_CODE using an outer join. FND_LOOKUP_VALUES_VL supplies the meaning of the EXCLUDE_FLAG, joined via LOOKUP_CODE where LOOKUP_TYPE equals 'AHL_YES_NO_TYPE'. MTL_MANUFACTURERS, also exposed through a SYNONYM, supplies the manufacturer name, joined on MANUFACTURER_ID using an outer join.

Both the FND and MTL joins are outer joins, indicated by the (+) operator. Consequently, effectivity rows are retained even when the country, manufacturer, or exclude lookup value is missing or inactive, though the descriptive columns will then return null for that row.

Key Columns

• MR_EFFECTIVITY_DETAIL_ID — Primary key identifying a single effectivity detail line.
• OBJECT_VERSION_NUMBER — Optimistic locking column used for concurrent update control.
• MR_EFFECTIVITY_ID — Foreign key to the parent maintenance requirement effectivity header.
• EXCLUDE_FLAG / EXCLUDE — Stored flag and its translated meaning, indicating whether the criteria include or exclude matching units.
• SERIAL_NUMBER_FROM / SERIAL_NUMBER_TO — Serial number range boundaries for the effectivity rule.
• MANUFACTURER_ID / MANUFACTURER — Manufacturer identifier and the resolved manufacturer name from MTL_MANUFACTURERS.
• MANUFACTURE_DATE_FROM / MANUFACTURE_DATE_TO — Date range within which the unit must have been manufactured.
• COUNTRY_CODE / COUNTRY — Territory code and translated short name.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — Descriptive flexfield segments capturing customer-defined information.

Common Use Cases and Queries

Typical usage includes reporting all effectivity lines for a given maintenance requirement, exporting applicability criteria to external maintenance systems, and validating manufacturer or serial ranges during unit evaluation. Because the user search referenced "mtl_manufacturers," the view is frequently queried to resolve manufacturer names for effectivity rules.

A representative query listing effectivity details for a specific maintenance requirement is shown below:

SELECT mr_effectivity_detail_id,
       mr_effectivity_id,
       exclude,
       serial_number_from,
       serial_number_to,
       manufacturer,
       manufacture_date_from,
       manufacture_date_to,
       country
FROM   apps.ahl_mr_effectivity_dtls_v
WHERE  mr_effectivity_id = :p_mr_effectivity_id;

A second pattern filters by manufacturer name to identify all affected requirements:

SELECT mr_effectivity_id,
       serial_number_from,
       serial_number_to,
       country
FROM   apps.ahl_mr_effectivity_dtls_v
WHERE  manufacturer = :p_manufacturer_name;

The view should be treated as a query-only object; DML must be directed to AHL_MR_EFFECTIVITY_DTLS to preserve the integrity of the base effectivity model.