Search Results terminate_mr_instances

Overview

APPS.AHL_UMP_UNITMAINT_PUB is a public PL/SQL package in the Oracle Enterprise Asset Management (eAM) / Asset Lifecycle Management (AHL) module of Oracle E-Business Suite. It supports maintenance program execution for unit effectivities — the association between a maintenance requirement (MR) and a specific asset unit. The package is responsible for capturing the maintenance outcome data (status, accomplishment date, deferred-next due date, or termination date) together with the associated counter and counter values, and for processing unit effectivity records as they flow through the front-end maintenance screens.

The header comments show the package dates to the earliest AHL development cycle ($Header: AHLPUMXB.pls 115.5 2003/10/17), and its interface follows the standard EBS API conventions: p_api_version, p_init_msg_list, p_commit, p_validation_level as standard IN parameters and x_return_status, x_msg_count, and x_msg_data as standard OUT parameters. The p_module_type parameter (default 'JSP') indicates the calling front-end interface; when set to 'JSP', the API clears out all ID columns so that validations are driven by the descriptive values used to populate the IDs rather than by pre-existing ID values. The package is documented as referenced by two other packages and exposes three documented procedures.

Key Procedures and Functions

• CAPTURE_MR_UPDATES — The primary documented procedure. For a given set of unit effectivities, it records their statuses along with either an accomplishment date, a deferred next due date, or a termination date, together with the corresponding counter and counter values. It accepts a table of unit effectivities (p_unit_Effectivity_tbl) whose status, due/accomplished dates, and counter values need to be captured, and IN OUT collections that return the thresholds (counters and counter values) at which an MR becomes due (p_x_Unit_Threshold_tbl) and the counters and counter values at the last accomplishment of the MR (p_x_Unit_Accomplish_tbl).
• TERMINATE_MR_INSTANCES — Records the termination of one or more maintenance requirement instances associated with unit effectivities, updating the instance status and termination date so that the MR instance is no longer treated as active. This is the procedure most relevant to the term terminate_mr_instances for which the object was retrieved.
• PROCESS_UNITEFFECTIVITY — Drives processing of unit effectivity records, applying the appropriate status transitions and derived maintenance information for the unit in question. It acts as the processing entry point used alongside the capture and termination routines.

Tables Accessed

The metadata supplied does not enumerate the underlying tables explicitly; however, based on the AHL eAM data model and the documented parameters, the package operates on maintenance requirement instance data and the unit effectivity, counter, threshold, and accomplishment information passed through its collection parameters. The unit effectivity and MR instance tables are read to determine current status and due/accomplished/termination dates, and written to persist the outcome captured by CAPTURE_MR_UPDATES and the instance closures performed by TERMINATE_MR_INSTANCES. Counter and counter value records are consulted and updated to record meter readings at accomplishment, threshold, and termination points. All object references resolve through APPS synonyms under the APPS schema.

Usage Notes

Because the classification is PUB, the package forms part of the supported public API surface for AHL unit maintenance and is not intended to be called by directly manipulating base tables. It is typically invoked from the eAM maintenance execution forms and related HTML/JSP user interfaces; the p_module_type default of 'JSP' confirms that the JSP front end is the principal caller, with the API clearing ID columns so that validation works from the descriptive values entered by the user. The package is also invoked programmatically by the two documented referencing packages and can be called from custom extensions and concurrent programs that need to capture maintenance updates or terminate MR instances in bulk, provided callers follow the standard EBS API protocol: initialize the message list, check x_return_status after each call, retrieve messages via FND_MSG_PUB, and issue an explicit commit only when p_commit is passed as FND_API.G_TRUE.