Results for “process_status”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.MTH_PROCESS_STATUS_PKG package body is a core component of the Oracle EBS Equipment Tracking (ETRM/MTH) module, responsible for deriving, maintaining, and recalculating equipment status records from two distinct input sources: tag readings and comma-separated value (CSV) load files. Its header revision (mtheqstb.pls 120.12.12020000.3, dated 2013/05/22) indicates it has been maintained through the 12.1.1 and 12.2.2 release cycles. In operational terms, the package translates raw measurement data collected from plant equipment into meaningful status codes and reason codes, then aggregates those statuses for reporting and downtime analysis. Three procedural patterns recur throughout the package: initialization (INIT), incremental update (INCR), and recalculation (RECAL). This design allows the application to load historical data in bulk, append new readings as they arrive, and retroactively correct status history when source data is amended.

Key Procedures and Functions

• VALIDATE — The public entry point that verifies the integrity of a status processing request before any data is written. It accepts a mode and a source indicator, and returns a return code together with an error buffer. Internal declarations such as v_tag_reading_count, v_output_count, and a compileState collection suggest it counts eligible tag readings and expected output rows, rejecting requests when the source data set is empty or inconsistent.
• PROCESS_STATUS — Drives the transformation of source data into equipment status records, coordinating the INIT, INCR, and RECAL logic for both reading-based and CSV-based sources (INIT_STATUS_FROM_READING, INCR_STATUS_FROM_READING, RECAL_STATUS_FROM_READING, INIT_STATUS_FROM_CSV, INCR_STATUS_FROM_CSV, RECAL_STATUS_FROM_CSV). The recalculation variants accept a from-date, an optional to-date, an optional equipment key, and — for the CSV path — an optional plant key, enabling targeted recalculation by site or asset.
• PROCESS_STATUS_SUMMARY — Populates and maintains the equipment status summary used for reporting. Its supporting routines (PROCESS_STATUS_SMMRY_INIT, PROCESS_STATUS_SMMRY_INCR, PROCESS_STATUS_SMMRY_RECAL) operate on timestamp-based date ranges and accept optional equipment and plant keys, allowing summary rows to be rebuilt incrementally or recalculated for a specific asset or site.

Tables Accessed

The package reads setup and master data from MTH_ENTITIES, MTH_EQUIPMENTS_D, MTH_EQUIPMENT_DENORM_D, MTH_EQUIPMENT_REASON_SETUP, MTH_EQUIPMENT_SHIFTS_D, MTH_EQUIP_STATUSES, MTH_HOUR_D, MTH_PLANTS_D, MTH_SYSTEMS_SETUP, and MTH_RUN_LOG. Transactional input arrives via MTH_TAG_READINGS, with staging and error capture handled by MTH_EQUIP_STATUSES_STG and MTH_EQUIP_STATUSES_ERR, and MTH_TAG_READINGS_ERR respectively. Derived output is written to MTH_EQUIP_STATUSES and rolled up into MTH_EQUIP_STATUS_SUMMARY. MTH_RUN_LOG records processing executions, providing an audit trail for each status run.

Usage Notes

The package is classified as OTHER and is referenced by one other package, indicating it is invoked programmatically rather than through a direct form call. Typical invocation paths include ETRM concurrent programs that process tag readings or CSV uploads, and the Equipment Status or Work Order/Shift forms that trigger recalculation when historical data is corrected. Custom extensions should call VALIDATE first, then PROCESS_STATUS or PROCESS_STATUS_SUMMARY, honouring the date-range and key parameters so that recalculation remains scoped and performant. Because the package maintains both detail (MTH_EQUIP_STATUSES) and summary (MTH_EQUIP_STATUS_SUMMARY) layers, any concurrent program invoking it should run in a controlled window, and error rows should be reviewed in the ERR tables before rerunning.