Search Results load_net_resource_avail

Overview

The APPS.MSC_RESOURCE_AVAILABILITY package is a core component of the Oracle Advanced Supply Chain Planning (ASCP) engine within Oracle E-Business Suite. Its primary business function is to compute and persist the availability of manufacturing and planning resources across a planning horizon. Resource availability represents the capacity of a resource (machine, department, production line, or similar asset) as derived from shift patterns, calendars, and capacity changes, expressed in the resource's native units. The results feed the ASCP planning engine so that the optimizer and the unconstrained/constrained planning modes can respect real capacity constraints when scheduling supply.

The package is classified as an "OTHER" API in the ETRM metadata and is owned by the APPS schema, with a status of VALID. It is not a public, customer-facing API; rather, it is an internal engine module invoked by the collections and ODS (Operational Data Store) load processes. The metadata confirms that the package references only the SYS.STANDARD package in terms of schema-level dependencies, and is itself referenced by APPS.MSC_CL_COLLECTION, MSC_CL_SETUP_ODS_LOAD, and its own package body, indicating that it sits downstream of data collection / ODS load and upstream of the planning engine.

Key Procedures and Functions

The ETRM metadata documents nine procedures and functions. Their purposes are as follows:

• CALC_RES_AVAIL — Calculates the available capacity for a given resource, applying shift, calendar, and capacity change rules. This is the primary per-resource calculation routine.
• COMPUTE_RES_AVAIL — Performs the underlying computation of resource availability, likely invoked as a lower-level worker by the calculation and driver routines.
• CALC_RESOURCE_AVAILABILITY — The top-level driver that orchestrates resource availability computation across the selected plan and scope of resources.
• POPULATE_AVAIL_RESOURCES — Identifies and populates the set of resources for which availability must be computed, based on plan scope and resource associations.
• POPULATE_AVAIL_RES_AHL — Populates available resources specifically at the ASCP "AHL" (aggregate/plan access) level, supporting the hierarchy used during plan execution.
• POPULATE_ORG_RESOURCES — Populates resources at the organization level, ensuring all relevant organizations contributing to the plan are represented.
• POPULATE_ALL_LINES — Populates all line-level resource records, ensuring the full production line structure is covered during availability computation.
• LOAD_NET_RESOURCE_AVAIL — Loads the computed net resource availability into the MSC_NET_RESOURCE_AVAIL and MSC_NET_RESOURCE_AVAIL_S tables, making the results available to the planner.
• LOG_MESSAGE — Writes diagnostic/status messages to the ASCP log tables, providing traceability for debugging and process monitoring.

Tables Accessed

The package reads and writes a defined set of MSC tables (accessed via APPS synonyms). Source/input tables include MSC_PLANS (plan definition and scope), MSC_APPS_INSTANCES and MSC_INSTANCE_ORGS (source instance and organization mapping), MSC_DEPARTMENT_RESOURCES (department-resource associations), MSC_RESOURCE_SHIFTS, MSC_SHIFT_DATES, MSC_SHIFT_TIMES, and MSC_CALENDAR_DATES (shift and calendar patterns that drive capacity), MSC_RESOURCE_CHANGES (capacity changes over time), MSC_ITEM_ID_LID (item identifier cross-reference), and MSC_PARAMETERS (planning parameters). Output tables are MSC_NET_RESOURCE_AVAIL, MSC_NET_RESOURCE_AVAIL_S (and the corresponding instance-level MSC_NET_RES_INST_AVAIL / MSC_NET_RES_INST_AVAIL_S), which store the computed net availability for the plan and its instances respectively. Reads combine master and transactional data to derive net capacity, while writes persist those results for the planning engine.

Usage Notes

MSC_RESOURCE_AVAILABILITY is an internal ASCP engine package and is not intended to be called directly by customer forms or custom code. It is normally invoked as part of the standard ASCP plan execution flow, specifically during the resource availability/loading phase that occurs after data collection and ODS setup but before the constrained plan solve. The metadata shows it is referenced by MSC_CL_COLLECTION and MSC_CL_SETUP_ODS_LOAD, confirming that collection and ODS load processes trigger or depend on this package. Because it is undocumented as a public API, any direct invocation from custom code should be avoided; the supported approach is to run ASCP plans and let the engine manage availability computation. For diagnostics, the LOG_MESSAGE routine writes to the ASCP log, so plan execution logs should be reviewed when resource availability results appear incorrect. Note that no explicit parameter lists are documented in the ETRM metadata, and callers should consult the package body via "show dependent code" in the EBS instance for exact signatures before attempting any integration.