Search Results check_mr_type
Overview
APPS.AHL_FMP_COMMON_PVT is a private PL/SQL package within the Oracle Enterprise Asset Management (eAM) and Complex Maintenance, Repair, and Overhaul (CMRO) application family. The AHL module in Oracle E-Business Suite supports maintenance management for fleets, units, and complex assets, and the FMP (Fleet Maintenance Planning) subcomponent provides the plumbing used to validate and resolve maintenance requirements, maintenance programs, and their associated applicability rules. AHL_FMP_COMMON_PVT serves as the shared internal utility package for the FMP package group. It provides a centralized repository of validation and lookup routines, allowing other FMP packages to avoid duplicating referential-integrity logic. The API classification is PVT — a private package — meaning it is not intended for direct invocation by external consumers; it is called by other FMP and UMP packages within the same schema.
Key Procedures and Functions
The package exposes twenty-four documented procedures and functions, all focused on validation and identifier resolution. These fall into several functional clusters:
- Generic lookups: VALIDATE_LOOKUP, VALIDATE_ITEM, VALIDATE_COUNTRY, and VALIDATE_MANUFACTURER perform reference checks against lookup values, inventory items, country codes, and manufacturer records.
- Position and node validation: VALIDATE_PC_NODE, VALIDATE_POSITION, and VALIDATE_POSITION_ITEM confirm that physical configuration nodes and positions are valid and that a position is properly associated with an item.
- Maintenance requirement validation: VALIDATE_MR_STATUS, VALIDATE_MR_EFFECTIVITY, VALIDATE_MR_INTERVAL_THRESHOLD, CHECK_MR_TYPE, and CHECK_MR_STATUS validate the state, effectivity, and threshold attributes of maintenance requirements.
- Maintenance program validation: VALIDATE_MR_TYPE_PROGRAM, VALIDATE_MR_TYPE_ACTIVITY, and VALIDATE_MR_PM_STATUS validate the relationship between maintenance program types, activities, and preventive maintenance status.
- Identifier resolution: MR_TITLE_VERSION_TO_ID and MR_EFFECTIVITY_NAME_TO_ID convert human-readable names/titles into surrogate keys.
- Utility routines: VALIDATE_COUNTER_TEMPLATE, VALIDATE_SERIAL_NUMBERS_RANGE, and POPULATE_APPL_MRS support counter template validation, serial number range checking, and population of applicable maintenance requirements.
Tables Accessed
The package reads and writes a set of base and interface tables via APPS synonyms. Item-related validation relies on MTL_SYSTEM_ITEMS and the key-flexview MTL_SYSTEM_ITEMS_KFV. Maintenance requirement and effectivity logic touches AHL_APPLICABLE_MRS, AHL_MR_EFFECTIVITIES, and AHL_MR_HEADERS_B. Physical configuration validation uses AHL_PC_NODES_B, AHL_MC_PATH_POSITION_NODES, and AHL_MC_RELATIONSHIPS. Fleet and unit context is drawn from AHL_FLEET_HEADERS_B, AHL_MC_HEADERS_B, and AHL_UNIT_EFFECTIVITIES_B. Installation and counter data come from CSI_ITEM_INSTANCES, CSI_I_EXTENDED_ATTRIBS, CS_CSI_COUNTER_GROUPS, and CS_CTR_ASSOCIATIONS. Lookup codes are fetched from FND_LOOKUPS.
Usage Notes
AHL_FMP_COMMON_PVT is invoked indirectly rather than directly by end users. It is referenced by thirteen other packages, including AHL_FMP_MR_PUB, AHL_FMP_MR_HEADER_PVT, AHL_FMP_MR_EFFECTIVITY_PVT, AHL_FMP_MR_ROUTE_PVT, AHL_FMP_PVT, AHL_UMP_PROCESSUNIT_PVT, AHL_UMP_UNPLANNED_PVT, and AHL_UA_FLIGHT_SCHEDULES_PVT. These callers invoke the shared validation routines during maintenance requirement creation, fleet scheduling, and unplanned maintenance processing. The package is exercised from eAM/CMRO HTML and Forms-based UI flows, concurrent programs that build applicable maintenance requirements, and any custom code that already reaches the FMP public packages. Because it is a private package, direct calls should be avoided; developers extending FMP functionality should use the public wrapper packages, which in turn delegate to this shared validation layer.