Results for “populate_budget_details”

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

Overview

The APPS.MSC_BUDGET_DETAILS package body is a server-side PL/SQL component within the Oracle Advanced Supply Chain Planning (ASCP) schema. Its principal business function is to populate and maintain budget detail records that support budget-versus-actual analysis and plan-level budget reporting in Oracle E-Business Suite. The package consolidates planning data — bill of materials inventory detail, item categories, plan buckets, safety stock positions, and system item attributes — into a staging structure (MSC_BUDGET_DETAILS) used by planning reports, dashboards, and budget comparison inquiries. It is classified under the ETRM API classification "OTHER," indicating it is an internal supporting package rather than a published, externally callable integration API. In release 12.1.1 and 12.2.2 the package is reported as VALID in the APPS schema, and it is not referenced by any other database object, confirming its role as a top-level population utility rather than a shared library routine.

Key Procedures and Functions

ETRM documents a single program unit within this package body:

• POPULATE_BUDGET_DETAILS — The sole documented procedure. Its purpose is to load or refresh the budget detail records consumed by budget analysis and planning inquiry functionality. The procedure derives its input from the plan, item category, safety stock, and inventory detail sources listed in the dependency metadata, then writes the resulting budget rows into MSC_BUDGET_DETAILS. Because the procedure relies on MSC_GET_BIS_VALUES and MSC_GET_NAME, it resolves business intelligence and naming attributes at runtime rather than storing them statically. No additional public functions are exposed, and the ETRM metadata does not document a parameter list; the procedure is therefore best treated as a batch-oriented loader invoked with internally resolved context.

Tables Accessed

The package reads from the following tables (through APPS synonyms) and writes to MSC_BUDGET_DETAILS:

• MSC_BUDGET_DETAILS — the target table and the package's namesake; holds the populated budget detail rows.
• MSC_BIS_INV_DETAIL — provides business intelligence inventory detail used to compute budget quantities and values.
• MSC_FORM_QUERY — supplies saved query definitions and plan/query context used by the population logic.
• MSC_ITEM_CATEGORIES — sources item category assignments for category-level budget grouping.
• MSC_PLAN_BUCKETS — defines the time-bucket boundaries (daily, weekly, monthly) into which budget amounts are aggregated.
• MSC_SAFETY_STOCKS — provides safety stock levels factored into budget quantities.
• MSC_SYSTEM_ITEMS — supplies item master attributes and planning flags that qualify which items are included.
• DBMS_OUTPUT — used for diagnostic or debug output during population runs.

Internal helper references include MSC_GET_BIS_VALUES and MSC_GET_NAME, both dependent code units invoked for value derivation and name resolution respectively.

Usage Notes

MSC_BUDGET_DETAILS is not invoked through a public integration interface and is not referenced by any other database object, so it is normally executed either from an ASCP planning concurrent program or from internal planner-facing forms that trigger budget detail regeneration. Typical invocation scenarios include regeneration of plan budget data after a planning run, refresh of budget-versus-actual comparison data for planner dashboards, and ad hoc execution from custom code where planning budget detail must be reloaded programmatically. Because the package depends on populated plan, bucket, category, and safety stock data, it should be run only after the relevant supply chain plan data has been collected and unconstrained or constrained plan output exists. Debug tracing through DBMS_OUTPUT should be enabled deliberately, as it is a diagnostic aid rather than a required runtime dependency. Customizations should not call this package as though it were a supported public API; instead, the recommended path is to invoke the same concurrent programs or planning processes that the standard product uses to drive budget detail population.