Search Results p_order_type
Overview
APPS.MSC_SUPPLIER_PKG is an Oracle Advanced Supply Chain Planning (ASCP) package that supports supplier-facing planning analytics. It belongs to the MSC (Master Scheduling / Supply Chain Planning) schema family and is owned by APPS. The package encapsulates supplier spend evaluation, purchase order classification, and supplier detail population logic used by ASCP reporting and planning workflows. Its header revision ($Header: MSCHBSPS.pls 120.3.12010000.2) confirms it was last updated in the 12.1.1 code line and remains present in 12.2.2.
The package provides two categories of functionality: scalar classification functions that evaluate purchase order characteristics (new buy, reschedule, cancellation, spend value), and set-based procedures that populate and purge supplier planning detail and summary staging tables. These operations feed supplier scorecards, capacity analysis, and supply-demand matching within the planning engine.
Key Procedures and Functions
- POPULATE_DETAILS — A procedure that populates supplier-level planning detail records for a given plan and plan run. It is the primary data-loading entry point, extracting supplier requirements, capacities, and trading-partner information into the MSC_ST_SUPPLIERS_F staging table for downstream processing.
- SUMMARIZE_SUPPLIERS_F — A function that aggregates staged supplier detail into summarized supplier records, supporting higher-level spend and capacity rollups (MSC_SUPPLIERS_F).
- EXPORT_SUPPLIERS_F — A function that exports summarized supplier data, typically for external reporting or integration with other planning or procurement systems.
- IMPORT_SUPPLIERS_F — A function that imports supplier data into the planning schema, enabling supplier capacity or commitment information to be brought into the planning model.
The package specification additionally declares supplier_spend_value, is_new_buy_order, is_rescheduled_po, and is_cancelled_po — functions used to evaluate purchase order disposition based on p_order_type, plan type, purchasing-enabled flags, and reschedule/cancellation indicators. The user search term "p_order_type" corresponds directly to the parameter these functions use to classify PO events (new buy, reschedule, cancel) before supplier spend or requirement records are generated.
Tables Accessed
- MSC_SUPPLIERS_F / MSC_ST_SUPPLIERS_F — Supplier master-level planning fact and its staging counterpart; primary write targets.
- MSC_SUPPLIER_CAPACITIES / MSC_SUPPLIER_REQUIREMENTS — Supplier capacity and demand inputs used during population.
- MSC_SUPPLIES / MSC_ITEM_SUPPLIERS — Sourcing and item-supplier relationships linking supply to approved vendors.
- MSC_TRADING_PARTNERS — Supplier/trading-partner identity resolution.
- MSC_PLAN_RUNS — Plan context used to scope populate and purge operations.
- MSC_CALENDAR_DATES — Calendar bucketing for time-phased supplier data.
- MSC_BIS_INV_DETAIL, MSC_HUB_QUERY, MSC_HUB_QUERY_S — Business intelligence and query infrastructure supporting summary extraction.
- DUAL — Used for scalar function evaluation.
Usage Notes
MSC_SUPPLIER_PKG is not exposed through a standard Oracle Forms UI; it is invoked indirectly by ASCP planning engine concurrent programs and planning manager workflows. The populate and purge procedures are typically scheduled as part of the plan run lifecycle, while the export/import functions support supplier collaboration and data exchange. Custom code calling the classification functions must supply a valid p_order_type value consistent with ASCP PO disposition coding. The package is referenced by zero other packages in the documented dependency graph, indicating it is a terminal node invoked by concurrent manager jobs rather than a shared utility library.
-
PACKAGE: APPS.MSC_SUPPLIER_PKG
12.1.1
-
PACKAGE BODY: APPS.MRP_MRPRPRSC_XMLP_PKG
12.1.1
-
PACKAGE BODY: APPS.EDW_POA_LN_TYPE_PKG
12.1.1
-
PACKAGE BODY: APPS.MRP_MRPRPRSC_XMLP_PKG
12.2.2
-
PACKAGE BODY: APPS.MSC_SELECT_ALL_FOR_RELEASE_PUB
12.1.1
-
PACKAGE BODY: APPS.MSC_SELECT_ALL_FOR_RELEASE_PUB
12.2.2
-
APPS.MSC_SECRULE_PKG SQL Statements
12.2.2
-
APPS.MSC_SECRULE_PKG SQL Statements
12.1.1
-
PACKAGE: APPS.MSC_SDA_PKG
12.2.2
-
APPS.EDW_POA_LN_TYPE_PKG SQL Statements
12.1.1
-
PACKAGE: APPS.MSC_SDA_PKG
12.1.1
-
APPS.MSD_SCE_RECEIVE_FORECAST_PKG SQL Statements
12.2.2
-
PACKAGE BODY: APPS.MSC_X_UTIL
12.1.1
-
PACKAGE: APPS.MSC_SECRULE_PKG
12.1.1
-
PACKAGE BODY: APPS.MSC_X_PURGE_SUPDEM_HISTORY_PKG
12.1.1
-
PACKAGE BODY: APPS.MSCX_UI_UTILITIES
12.1.1
-
PACKAGE BODY: APPS.MSC_X_UTIL
12.2.2
-
PACKAGE BODY: APPS.MSCX_UI_UTILITIES
12.2.2
-
PACKAGE BODY: APPS.MSC_X_PURGE_SUPDEM_HISTORY_PKG
12.2.2
-
PACKAGE: APPS.MSC_SECRULE_PKG
12.2.2
-
APPS.MSD_SCE_RECEIVE_FORECAST_PKG SQL Statements
12.1.1
-
PACKAGE BODY: APPS.MSD_SCE_RECEIVE_FORECAST_PKG
12.2.2
-
PACKAGE BODY: APPS.MSD_SCE_RECEIVE_FORECAST_PKG
12.1.1
-
PACKAGE BODY: APPS.OE_EXPORT_COMPLIANCE_CONC
12.2.2
-
PACKAGE: APPS.EDW_POA_LN_TYPE_PKG
12.1.1
-
PACKAGE: APPS.MSC_RP_RELEASE_PUB
12.2.2
-
APPS.AME_DYNAMIC_APPROVAL_PKG SQL Statements
12.1.1
-
PACKAGE: APPS.MSC_X_PURGE_SUPDEM_HISTORY_PKG
12.2.2
-
PACKAGE: APPS.MSC_X_PURGE_SUPDEM_HISTORY_PKG
12.1.1
-
PACKAGE BODY: APPS.OE_EXPORT_COMPLIANCE_CONC
12.1.1
-
PACKAGE: APPS.GMPRELAP
12.1.1
-
APPS.AME_DYNAMIC_APPROVAL_PKG SQL Statements
12.2.2
-
PACKAGE: APPS.OE_INV_IFACE_CONC
12.1.1
-
PACKAGE: APPS.OE_PUR_CONC_REQUESTS
12.1.1
-
PACKAGE: APPS.GMPRELAP
12.2.2
-
PACKAGE: APPS.MSC_PLAN_RELEASE
12.2.2
-
PACKAGE: APPS.OE_HOLDS
12.1.1
-
PACKAGE BODY: APPS.MSC_SECRULE_PKG
12.2.2
-
PACKAGE: APPS.OE_PUR_CONC_REQUESTS
12.2.2
-
PACKAGE: APPS.MSCX_UI_UTILITIES
12.1.1
-
PACKAGE: APPS.MSCX_UI_UTILITIES
12.2.2
-
PACKAGE: APPS.OE_INV_IFACE_CONC
12.2.2
-
PACKAGE: APPS.OE_HOLDS
12.2.2
-
PACKAGE: APPS.OE_EXPORT_COMPLIANCE_CONC
12.2.2
-
PACKAGE: APPS.OE_SCH_FIRM_CONC
12.1.1
-
PACKAGE BODY: APPS.MSC_SECRULE_PKG
12.1.1
-
PACKAGE: APPS.OE_EXPORT_COMPLIANCE_CONC
12.1.1
-
PACKAGE BODY: APPS.OM_REPORTS_MLS_LANG
12.1.1
-
PACKAGE: APPS.OE_SCH_FIRM_CONC
12.2.2
-
APPS.MSCX_UI_UTILITIES SQL Statements
12.2.2