Results for “msc_net_resource_avail_s”

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

Overview

MSC_UPDATE_RESOURCE is an Oracle EBS Advanced Supply Chain Planning (ASCP) package body owned by the APPS schema. Its central business function is to maintain and recalculate resource availability within the planning engine — specifically the net resource availability records that planners rely on when the planning engine schedules operations against constrained resources. The package takes the base resource capacity stored in MSC_NET_RESOURCE_AVAIL and its interface/staging counterpart MSC_NET_RESOURCE_AVAIL_S, applies calendar, department, and process-effectivity logic, and produces the net available capacity figures consumed downstream by resource requirement and supply netting routines.

The presence of procedures such as CALCULATE_CHANGE, APPLY_CHANGE, and CALCULATE_OPS indicates this is a change-propagation engine rather than a simple loader. It exists so that incremental updates — a shift change, a capacity adjustment, a department resource reassignment — propagate correctly through the planning hierarchy without requiring a full plan regeneration.

Key Procedures and Functions

The package exposes twenty documented programs. They fall into functional groups:

• Simulation and change application: APPLY_SIMULATION, APPLY_CHANGE, CALCULATE_CHANGE, RESET_CHANGES — compute the delta between proposed and existing resource states and commit or roll back that delta.
• Table and record maintenance: INITIALIZE_TABLE, UPDATE_TABLE, ADD_NEW_RECORD, REFRESH_PARENT_RECORD, VERIFY_DATA, GET_TRANSACTION_ID — stage, validate, and persist resource availability rows.
• Aggregation: AGGREGATE_CHILD_RECORDS, AGGREGATE_ONE_RESOURCE, AGGREGATE_SOME_RESOURCES — roll child resource/department availability into parent summary levels.
• Planning and calendar logic: PROCESSDATES, GET_NEW_TIME, CALCULATE_OPS, ISFIRSTOP, ROUTING_RES_UNIT — derive operation windows and effective working time from routing and calendar data.
• Undo and movement: INSERT_UNDO_DATA, MOVE_RES_REQ — capture reversal information in the undo tables and relocate resource requirements when availability shifts.

Tables Accessed

The package reads and writes through APPS synonyms against the MSC schema:

• MSC_NET_RESOURCE_AVAIL and MSC_NET_RESOURCE_AVAIL_S — the primary net resource availability table and its staging/interface sibling; these are the central objects the package maintains. The user's search term msc_net_resource_avail_s points directly at this dependency.
• MSC_CALENDAR_DATES, MSC_PLAN_BUCKETS, MSC_PROCESS_EFFECTIVITY — supply the calendar, bucket, and effectivity context used by PROCESSDATES and GET_NEW_TIME.
• MSC_DEPARTMENT_RESOURCES, MSC_OPERATION_RESOURCES, MSC_RESOURCE_REQUIREMENTS — define resource definition and demand-side data used by CALCULATE_OPS and ROUTING_RES_UNIT.
• MSC_NET_RES_INST_AVAIL and MSC_NET_RES_INST_AVAIL_S — instance-level availability used during aggregation.
• MSC_SUPPLIES, MSC_PLANS, MSC_TRADING_PARTNERS, MSC_FORM_QUERY — supporting plan, supply, partner, and query-definition references.
• MSC_UNDO_SUMMARY_S — the undo summary interface that INSERT_UNDO_DATA populates so changes can be reversed.

Usage Notes

MSC_UPDATE_RESOURCE is invoked indirectly rather than through a user-facing form. It is called by planning concurrent programs — notably resource availability maintenance and plan regeneration or simulation runs — and by other MSC packages. The metadata records that it is referenced by one other package but referenced by no database object directly, confirming its role as an internal engine component. Customizations that need to alter resource availability behaviour should call the package's documented entry points (for example APPLY_CHANGE or CALCULATE_CHANGE) rather than writing to MSC_NET_RESOURCE_AVAIL or MSC_NET_RESOURCE_AVAIL_S directly, since the package also maintains synchronization with the staging table and the undo summary. Any custom invocation should respect the transaction ID returned by GET_TRANSACTION_ID so that RESET_CHANGES can correctly unwind a partial update.