Search Results msc_x_default_calendar

Overview

APPS.MSC_X_RECEIVE_CAPACITY_PKG is a PL/SQL package within the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) schema, defined with AUTHID CURRENT_USER. Its central purpose is the reception, calculation, and persistence of supplier capacity data used by the MSC (Advanced Planning) engine. The package supports the supplier capacity planning model, in which declared supplier capacities are converted into time-bucketed supply information that the planning engine treats as constrained supply during the planning run.

The package version header indicates ship level 115.15, dated 2004, reflecting its origins in the MSC cooperative planning / "X" extension namespace used for external or collaborative supplier capacity receipt. It reads profile options MSC_CP_DEBUG (debugging control) and MSC_X_DEFAULT_CALENDAR (default manufacturing or capacity calendar) during package initialization, with declared constants governing system booleans (SYS_YES, SYS_NO) and the supply commit type (SUPPLY_COMMIT = 3).

Key Procedures and Functions

• RECEIVE_CAPACITY — The public entry point. It accepts horizon start and end dates, an ABC class filter, item, planner, supplier and supplier site identifiers, an MPS designator, and control flags for overwrite and spread behavior. It orchestrates the receipt of a capacity feed and drives downstream processing.
• CALCULATE_CAPACITY — Performs the capacity computation for a specific service reference (SR) instance, organization, supplier, site, MPS designator, and item combination. Parameters include receipt date, capacity quantity, bucket type, calendar code, refresh number, level start and end dates, horizon boundaries, ABC class, planner, mapped supplier identifiers, rounding control, and overwrite/spread flags. It applies bucket definitions and rounding rules to derive capacity values suitable for planning.
• POPULATE_CAPACITY — Inserts or refreshes capacity for a given date range and horizon window, using refresh number, level start/end dates, and overwrite control. It manages the staging of calculated capacity records into the MSC supplier capacity tables.
• INSERT_CAPACITY — The low-level insert routine that writes individual capacity records for a service reference, organization, supplier, and related key dimensions. This is the procedure targeted when users search for "insert_capacity," as it is the row-level write operation within the capacity pipeline.
• LOAD_SUPPLY_SCHEDULE — Loads supply schedule data, translating capacity declarations into the supply schedule representation consumed by the planning engine.
• INSERT_MPS_DESIGNATOR — Creates MPS designator records, associating capacity data with master production schedule designators.
• INSERT_SUPPLY_SCHEDULE — Writes supply schedule rows corresponding to capacity receipts, reflecting committed supply across time buckets.

Tables Accessed

The package reads and writes through APPS synonyms. Capacity data is stored in MSC_SUPPLIER_CAPACITIES and its translated view base MSC_SUPPLIER_CAPACITIES_S. Supply schedule and capacity-derived supply rows are written to MSC_SUPPLIES and MSC_SUPPLIES_S. Calendar handling draws on MSC_CALENDAR_DATES, MSC_CAL_WEEK_START_DATES, and MSC_PERIOD_START_DATES, which supply bucket boundary dates for the configured calendar. Supplier and organization context is sourced from MSC_COMPANIES, MSC_COMPANY_RELATIONSHIPS, and MSC_COMPANY_SITES. Item and sourcing data come from MSC_ITEMS and MSC_ITEM_SUPPLIERS. MPS designator data is maintained via MSC_DESIGNATORS and MSC_DESIGNATORS_S. Staging and internal collection activity is logged in MSC_COLLECTION_S.

Usage Notes

MSC_X_RECEIVE_CAPACITY_PKG is typically invoked from supplier capacity collaborative planning flows and from concurrent programs that load external supplier capacity feeds. RECEIVE_CAPACITY operates as the highest-level call, cascading into CALCULATE_CAPACITY, POPULATE_CAPACITY, and INSERT_CAPACITY to validate, compute, and persist capacity rows. Because the package is AUTHID CURRENT_USER and version-controlled at the MSC ship level, it should be treated as an internal engine API rather than a published extension point.

Custom integrations that ingest supplier capacity generally call RECEIVE_CAPACITY with explicit horizon and supplier parameters, allowing the package to apply calendar bucketing and rounding per the default or specified calendar. The metadata indicates no documented reverse dependencies — no other packages reference it — confirming it is a leaf-level utility invoked directly by capacity collection or planning orchestration jobs rather than a shared library. The overwrite and spread flags permit callers to control whether existing capacity buckets are replaced or distributed across dates, which is critical when re-receiving revised supplier commitments.