Search Results load_milestones

Overview

MSC_CL_AHL_PULL is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and defined with AUTHID CURRENT_USER, meaning its SQL statements execute under the privileges of the calling user rather than the package owner. It belongs to the MSC (Advanced Planning / Supply Chain Planning) module family and, based on its header and procedure naming conventions, addresses the collection of asset- and maintenance-related source data into the planning repository. The procedure prefixes LOAD_WO, LOAD_MILESTONES, and LOAD_CMRO indicate that the package handles work order, milestone, and condition-based maintenance work order information associated with Enterprise Asset Management (EAM) and maintenance organizations. The package is part of the collections layer that moves transactional data from the operational source tables into the MSC staging and planning tables consumed by Advanced Supply Chain Planning and related planning engines. It is a source-only specification; the body is not documented in the excerpt, and the package is registered with an API classification of OTHER, indicating it is an internal, non-public interface rather than a supported extension point. The header comment references $Header: MSCPAHLS.pls 120.3 2012/06/05, confirming availability across the 12.1.1 and 12.2.2 release levels.

Key Procedures and Functions

The package exposes eleven documented procedures, each responsible for loading a distinct slice of maintenance or supply data into the planning schema:

• LOAD_VISITS — Loads visit records, the maintenance service visits associated with asset work orders, into the planning collection tables.
• LOAD_WO_ATTRIBUTES — Loads descriptive and controlling attributes of work orders required by the planner.
• LOAD_WO_TASK_HRY — Loads the work order task hierarchy, capturing parent-child relationships between work order tasks.
• LOAD_MILESTONES — Loads work order milestone information used for scheduling and progress tracking.
• LOAD_WO_OPER_RELN — Loads work order operation relationships, reflecting the sequencing of operations within a work order.
• LOAD_WORK_BREAKDOWN — Loads work breakdown structure information for maintenance activities.
• LOAD_WO_SUB_COMP — Loads sub-component or component-level details belonging to work orders.
• LOAD_CMRO_FORECASTS — Loads Condition-Based Maintenance Work Order (CMRO) forecasts. It accepts two date parameters bounding the start and end of the collection window (p_EAM_CMRO_ST_DATE and p_EAM_CMRO_END_DATE), as documented in the package signature.
• LOAD_SUPPLY_RESERVATIONS — Loads supply reservation records relevant to maintenance demand and supply matching.
• LOAD_CLOSED_CMRO_WOS — Loads closed condition-based maintenance work orders, preserving history for planning and reporting.
• LOAD_OSP_SUPPLY — Loads outside processing (OSP) supply, reflecting externally performed maintenance operations.

Tables Accessed

The ETRM metadata does not enumerate specific base tables for this package; tables are referenced indirectly through APPS synonyms, which is standard practice for MSC collection packages. Functionally, the procedures read from EAM and maintenance source entities — work orders, work order operations, task hierarchies, milestones, sub-components, visits, CMRO forecasts, supply reservations, and outside processing records — and write into MSC staging and planning tables used by the planning data model. Because the package is declared AUTHID CURRENT_USER, all such access is performed under the caller's schema privileges.

Usage Notes

MSC_CL_AHL_PULL is not a user-facing API. It is invoked internally by the MSC collections framework, typically as part of a larger data pull executed by concurrent programs during the planning data collection cycle. The LOAD_CMRO_FORECASTS procedure, with its explicit start and end date parameters, is consistent with date-window-driven collection runs. The package is referenced by one other package, indicating it is called from a coordinating collection driver rather than directly by forms or external code. Because the API classification is OTHER and the header carries a "noship" designation, customers should not call these procedures directly from custom code; they should instead rely on the standard planning collection concurrent programs, which invoke the package in the correct sequence and context. Any direct invocation risks partial or inconsistent staging data and is unsupported.