Search Results msc_atp_peg




Overview
Explore in AI Chat

Overview

MSC_ATP_PEG is an Oracle Applications (APPS) PL/SQL package that belongs to the Advanced Supply Chain Planning (ASCP) and Available-to-Promise (ATP) module of Oracle E-Business Suite. Its primary business function is to perform pegging for ATP calculations — that is, to trace the relationship between supply and demand records so that the planning engine can determine which on-hand, scheduled receipt, or planned order is satisfying a given demand. Pegging is fundamental to ATP and capable-to-promise queries because it establishes the supply/demand linkage needed to confirm whether a request can be fulfilled and on what date.

The package operates over temporary staging tables (MRP_ATP_*_TEMP family) as well as the persistent MSC_ATP_PEGGING result table. Its status in the ETRM reference is VALID, and it is classified as an OTHER API — it is not a public, supported extension API but an internal engine component invoked by other planning packages and concurrent processes.

Key Procedures and Functions

The documented ETRM metadata lists five callable units within the package. Each supports the pegging computation lifecycle:

  • CREATE_ATP_PEGGING — The core routine that builds the ATP pegging records, matching supplies to demands and writing the resulting relationships into the pegging tables.
  • POST_PLAN_PEGGING — Persists or posts the pegging results after the plan computation has completed, making the pegged relationships available to downstream consumers such as the plan results and ATP queries.
  • GENERATE_SIMPLIFIED_PEGGING — Produces a reduced or simplified pegging result set, typically used where full end-to-end pegging would be prohibitively expensive or where only direct supply/demand relationships are required.
  • ADD_OFFSET_DATA — Adds offset (lead-time or date-shift) information to the pegging records so that pegged dates and quantities reconcile correctly against the planning calendar.
  • REMOVE_OFFSET_DATA — The inverse of the previous routine, removing offset data to reset or clean up pegging staging records before regeneration.

Parameter lists are not documented in the ETRM excerpt and should be verified against the deployed package source in the target release.

Tables Accessed

The package reads and writes a set of APPS-synonym tables that fall into several functional groups. Pegging result and staging tables include MSC_ATP_PEGGING, MSC_ATP_PEG_TEMP, and MSC_ATP_DETAIL_PEG_TEMP, which hold the computed supply/demand relationships and their intermediate detail. Temporary ATP ATP engine tables include MRP_ATP_DETAILS_TEMP and MRP_ATP_SCHEDULE_TEMP_S. Demand and supply sources are represented by MSC_DEMANDS, MSC_DEMANDS_S, MSC_ALLOC_DEMANDS, MSC_ALLOC_SUPPLIES, and MSC_FORECAST_UPDATES. Bill-of-material component data is drawn from MSC_BOM_COMPONENTS. Package control and environment information is read from MSC_ATP_PARAMETERS, FND_CONCURRENT_REQUESTS, FND_ORACLE_USERID, and FND_PRODUCT_INSTALLATIONS, the latter three providing concurrent-request context and installation identity.

Usage Notes

MSC_ATP_PEG is an internal engine package rather than a user-facing API. It is referenced by MSC_ATP_DB_UTILS, MSC_ATP_PVT, MSC_POST_PRO, and by itself, which confirms it is called from within the ATP and planning processing chain. Typical invocation occurs during concurrent program execution of ATP and pegging-related planning requests, or from other PL/SQL packages performing ATP calculation and post-plan processing. It depends on MRP_ATP_PUB and the SYS STANDARD package.

Because the package is classified as OTHER in ETRM, custom code should not call it directly; instead, invoke the supported ATP concurrent programs or the supported planning APIs. Any direct usage carries upgrade risk, since internal packages may change between 12.1.1 and 12.2.2 without a public API commitment.