Search Results p_category_structure_id

Overview

APPS.EAM_PM_CONCURRENT_REQUESTS is a public PL/SQL package in Oracle Enterprise Asset Management (eAM) that supports the preventive maintenance (PM) scheduling process and the conversion of forecasted work orders into executable work orders. Declared with AUTHID CURRENT_USER, the package executes under the privileges of the calling schema, which is the standard pattern for eAM concurrent program entry points that must respect the caller's organization and security context. Its two procedures form part of the batch backbone that drives planned maintenance on assets: one evaluates PM definitions against user-supplied selection criteria and creates forecasted work orders, while the other takes the resulting forecast records and converts them into actual work orders in the Work in Process (WIP) interface. The package is referenced by no other PL/SQL packages, confirming that it is a top-level concurrent program wrapper rather than a shared utility library. The header revision (120.2) dates the package to an early eAM release, and its interface remains stable across the 12.1.1 and 12.2.2 application releases.

Key Procedures and Functions

The package exposes two documented procedures:

• GENERATE_PM_SCHEDULES — The principal entry point for the eAM preventive maintenance generation concurrent program. It accepts a wide set of selection parameters that scope the run, including a start date and end date, organization ID, user ID, location ID, category structure ID, category ID, owning department ID, item type name and item type, inventory item name, asset group ID, asset number, set name and set name ID, a view-only flag, project number and ID, task number and ID, and parent work order and ID. The procedure evaluates the PM definitions and asset records that satisfy these criteria and produces forecasted work orders for the eligible maintenance activities. The p_category_structure_id parameter identified in the user search targets the asset category structure used to restrict which categories of assets are considered, working in conjunction with p_category_id to narrow the population of assets scheduled in a given run.
• CONVERT_FORECAST_WORK_ORDERS — Converts previously generated forecasted work orders, selected by a single group ID, into actual work orders. It is the second stage of the two-step eAM process: schedules are first forecast, reviewed or adjusted, and then converted to live work orders.

Both procedures follow the standard concurrent program signature convention, returning errbuf and retcode output parameters so that the concurrent manager can record completion status and messages.

Tables Accessed

The documented table references reflect the two-stage design of the package:

• EAM_FORECASTED_WORK_ORDERS — The central staging table. GENERATE_PM_SCHEDULES writes forecasted work order records here, and CONVERT_FORECAST_WORK_ORDERS reads them for conversion.
• WIP_JOB_SCHEDULE_INTERFACE and WIP_JOB_SCHEDULE_INTERFACE_S — The WIP open interface tables used to pass work order scheduling information to Oracle Work in Process for import into the discrete job tables.
• PJM_ORG_PARAMETERS — Project Manufacturing organization parameters, consulted to determine whether the organization operates under project manufacturing rules and how project and task references should be derived.
• DUAL — Used for lightweight PL/SQL expression evaluation and control-flow checks.

Usage Notes

EAM_PM_CONCURRENT_REQUESTS is designed to be invoked from concurrent programs rather than from interactive forms. In a typical eAM implementation, the Generate PM Schedules and Convert Forecasted Work Orders concurrent programs are registered against these procedures, and users submit them from the Standard Concurrent Programs or eAM responsibility menus. The p_view_only flag supports a preview execution in which the selection criteria are validated and matching assets are reported without creating forecasted work orders. Because the package is AUTHID CURRENT_USER and relies on APPS synonyms, custom callers must be granted EXECUTE on the package and must supply a valid p_org_id so that multi-organization access controls are honored. The two procedures are intended to run in sequence, and any custom automation should invoke CONVERT_FORECAST_WORK_ORDERS only after GENERATE_PM_SCHEDULES has populated EAM_FORECASTED_WORK_ORDERS for the relevant group.