Search Results msc_vertical_plan_sc
Overview
APPS.MSC_VERTICAL_PLAN_SC is a PL/SQL package in the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module, declared with AUTHID CURRENT_USER so that it executes with the privileges of the invoking schema rather than its owner. Its header ($Header: MSCVERPS.pls 115.7) indicates it belongs to the MSC (MSC/Vertical Plan) family of server-side components that support the vertical plan and planning-detail user interfaces. The package's core business function is to translate planning data—item supply and demand across an organization—into bucketed quantities and period strings that can be rendered in the planning workbench or exported to a reporting/analysis layer.
Rather than maintaining persistent planning state, the package acts as a computation and formatting utility: it reads calendar and plan definitions, derives the bucketing that applies to a given plan, and returns quantities and period labels back to the caller. This makes it a reusable building block for both interactive forms and batch jobs. Because the package is classified as OTHER in the ETRM metadata and is referenced by zero other packages, it is not a shared internal API; it is invoked directly by the code or UI that needs its services.
Key Procedures and Functions
- POPULATE_BUCKETED_QUANTITY — The central procedure of the package and the object referenced by the search term. It takes a plan, instance, organization, item, cutoff date, and bucket type, and returns a quantity string, a period string, and a period count. In practice it resolves the calendar bucketing for the plan (day, week, period, or similar), aggregates the item's supply/demand quantity into those buckets, and formats the results as delimited strings suitable for display or downstream parsing. The
NOCOPYhint on the OUT parameters avoids unnecessary copying of the returned strings back to the caller. - GET_EXCEPTION_GROUP — A function that accepts a WHERE-clause fragment and returns a collection of numbers (the
column_numberassociative array indexed by binary_integer). It is used to evaluate or group exception records against the supplied predicate, returning the set of numeric identifiers that satisfy the condition. - FLUSH_MULTI_RETURN — A procedure accepting the package-defined
sd_tbl_typerecord (itself composed of thenumber_arrcollectionsp_query_idandp_number_1). It consolidates the accumulated multi-row return data for output, supporting the multi-return action pattern noted in the source comments ("added by utham for multi_return action proc").
Tables Accessed
The package references the following tables through APPS synonyms:
- MSC_CALENDAR_DATES, MSC_CAL_WEEK_START_DATES, and MSC_PERIOD_START_DATES — provide the calendar hierarchy used to establish bucket boundaries for the requested bucket type.
- MSC_PLANS — supplies plan-level attributes, including the calendar assignment needed to interpret the cutoff date.
- MSC_FORM_QUERY — stores or resolves the query definitions associated with the form-driven exception and multi-return logic.
- MSC_TRADING_PARTNERS — used for partner-related selections relevant to plan data.
- PLITBLM — the standard EBS temporary table (PL/SQL index-by table mapping) used to pass arrays between the form and the database.
Usage Notes
MSC_VERTICAL_PLAN_SC is typically invoked from the ASCP planning workbench forms or from a concurrent program that renders vertical plan output. Custom code should call POPULATE_BUCKETED_QUANTITY only after the plan, organization, and calendar prerequisites are satisfied, and should be prepared to parse the returned quantity and period strings according to the bucket type requested. Because the package uses AUTHID CURRENT_USER, the invoking user must hold select privileges on the referenced MSC tables and PLITBLM. The package has no documented dependents, so it can be modified with limited blast radius, but any change to parameter signatures or output string formats will affect existing form integrations.
-
PACKAGE: APPS.MSC_VERTICAL_PLAN_SC
12.1.1
owner:APPS, object_type:PACKAGE, object_name:MSC_VERTICAL_PLAN_SC, status:VALID,
-
PACKAGE BODY: APPS.MSC_VERTICAL_PLAN_SC
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:MSC_VERTICAL_PLAN_SC, status:VALID,
-
PACKAGE: APPS.MSC_VERTICAL_PLAN_SC
12.2.2
owner:APPS, object_type:PACKAGE, object_name:MSC_VERTICAL_PLAN_SC, status:VALID,
-
PACKAGE BODY: APPS.MSC_VERTICAL_PLAN_SC
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:MSC_VERTICAL_PLAN_SC, status:VALID,
-
PACKAGE: APPS.MSC_VERTICAL_PLAN_SC
12.2.2
-
PACKAGE: APPS.MSC_VERTICAL_PLAN_SC
12.1.1
-
SYNONYM: APPS.MSC_CAL_WEEK_START_DATES
12.2.2
owner:APPS, object_type:SYNONYM, object_name:MSC_CAL_WEEK_START_DATES, status:VALID,
-
SYNONYM: APPS.MSC_CAL_WEEK_START_DATES
12.1.1
owner:APPS, object_type:SYNONYM, object_name:MSC_CAL_WEEK_START_DATES, status:VALID,
-
SYNONYM: APPS.MSC_PERIOD_START_DATES
12.1.1
owner:APPS, object_type:SYNONYM, object_name:MSC_PERIOD_START_DATES, status:VALID,
-
SYNONYM: APPS.MSC_PERIOD_START_DATES
12.2.2
owner:APPS, object_type:SYNONYM, object_name:MSC_PERIOD_START_DATES, status:VALID,
-
SYNONYM: APPS.MSC_FORM_QUERY
12.1.1
owner:APPS, object_type:SYNONYM, object_name:MSC_FORM_QUERY, status:VALID,
-
12.2.2 DBA Data
12.2.2
-
VIEW: APPS.MSC_VERTICAL_PLAN_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:MSC.MSC_VERTICAL_PLAN_V, object_name:MSC_VERTICAL_PLAN_V, status:VALID,
-
VIEW: APPS.MSC_VERTICAL_PLAN_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:MSC.MSC_VERTICAL_PLAN_V, object_name:MSC_VERTICAL_PLAN_V, status:VALID,
-
SYNONYM: APPS.MSC_CALENDAR_DATES
12.2.2
owner:APPS, object_type:SYNONYM, object_name:MSC_CALENDAR_DATES, status:VALID,
-
SYNONYM: APPS.MSC_FORM_QUERY
12.2.2
owner:APPS, object_type:SYNONYM, object_name:MSC_FORM_QUERY, status:VALID,
-
12.1.1 DBA Data
12.1.1
-
SYNONYM: APPS.MSC_CALENDAR_DATES
12.1.1
owner:APPS, object_type:SYNONYM, object_name:MSC_CALENDAR_DATES, status:VALID,
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
PACKAGE BODY: APPS.MSC_VERTICAL_PLAN_SC
12.2.2
-
SYNONYM: APPS.MSC_PLANS
12.1.1
owner:APPS, object_type:SYNONYM, object_name:MSC_PLANS, status:VALID,
-
PACKAGE BODY: APPS.MSC_VERTICAL_PLAN_SC
12.1.1
-
SYNONYM: APPS.MSC_PLANS
12.2.2
owner:APPS, object_type:SYNONYM, object_name:MSC_PLANS, status:VALID,
-
SYNONYM: APPS.MSC_TRADING_PARTNERS
12.1.1
owner:APPS, object_type:SYNONYM, object_name:MSC_TRADING_PARTNERS, status:VALID,
-
SYNONYM: APPS.MSC_TRADING_PARTNERS
12.2.2
owner:APPS, object_type:SYNONYM, object_name:MSC_TRADING_PARTNERS, status:VALID,
-
APPS.MSC_VERTICAL_PLAN_SC dependencies on MSC_VERTICAL_PLAN_SC
12.2.2
-
APPS.MSC_VERTICAL_PLAN_SC dependencies on MSC_VERTICAL_PLAN_SC
12.1.1
-
PACKAGE: APPS.FND_NUMBER
12.1.1
owner:APPS, object_type:PACKAGE, object_name:FND_NUMBER, status:VALID,
-
PACKAGE: APPS.FND_NUMBER
12.2.2
owner:APPS, object_type:PACKAGE, object_name:FND_NUMBER, status:VALID,
-
eTRM - MSC Tables and Views
12.1.1
description: This table contains the mapping between user-defined zone and included regions ,
-
SYNONYM: PUBLIC.PLITBLM
12.1.1
owner:PUBLIC, object_type:SYNONYM, object_name:PLITBLM, status:VALID,
-
SYNONYM: PUBLIC.PLITBLM
12.2.2
owner:PUBLIC, object_type:SYNONYM, object_name:PLITBLM, status:VALID,
-
12.2.2 DBA Data
12.2.2
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
12.1.1 DBA Data
12.1.1
-
eTRM - MSC Tables and Views
12.1.1
description: This table contains the mapping between user-defined zone and included regions ,
-
PACKAGE: SYS.STANDARD
12.1.1
owner:SYS, object_type:PACKAGE, object_name:STANDARD, status:VALID,