Search Results msd_cs_defn_load_data




Overview
Explore in AI Chat

Overview

The APPS.MSD_CS_DEFN_LOAD_DATA package is a data-loading API within the Oracle EBS Demand Planning / Advanced Supply Chain Planning schema, owned by the MSD (Master Scheduling/MRP and Supply Chain) product family. Its central business function is to seed, insert, and maintain rows in the MSD_CS_DEFINITIONS hierarchy of tables — the definitions that describe planning stream characteristics, collection parameters, aggregation and allocation rules, measurement types, and associated server-side views used by the collections and planning engines. The package encapsulates the multi-language table structure (base table, _S and _TL variants) so that callers can register a definition with all associated attributes in a single, consistent operation rather than performing raw DML. In the Oracle EBS 12.1.1 and 12.2.2 releases this package is classified under ETRM API classification OTHER, meaning it is a support/loader utility rather than a public business-flow API. The user query term defn_update_row corresponds directly to the DEFN_UPDATE_ROW procedure described below.

Key Procedures and Functions

The documented package exposes five procedures. Their names and purposes are as follows; parameter lists are intentionally not reproduced where only the signature header is documented.

  • LOAD_ROW — The general-purpose loader entry point. It accepts a broad set of descriptive and control attributes (name, description, plan type, classification, strict/system/multiple-stream/stripe flags, view names, collection program name, additional where clauses, and validity/editable/aggregation/allocation/dependency attributes) and dispatches to the appropriate insert or update path. It carries p_owner, p_last_update_date, and p_custom_mode parameters, indicating support for both seeded and customer-defined definition rows.
  • DEFN_INSERT_ROW — Creates a new definition record, populating the base definition row along with its translated and secure variants. It mirrors the attribute set of LOAD_ROW and is invoked when no existing definition is found.
  • DEFN_UPDATE_ROW — Updates an existing definition row. This is the procedure matching the user's search term "defn_update_row". It applies changed attribute values to the definition, including the enable flag, LOV view name, lowest-level flag, and measurement type, while preserving key identifiers.
  • TRANSLATE_ROW — Inserts or updates the translated (TL) content for a definition, resolving the language context against the _TL table so that description text is available per installed language.
  • ADD_LANGUAGE — Registers a new language row for a definition, using FND_LANGUAGES as the source of installed languages and creating the corresponding translation record.

Tables Accessed

Per the documented references (via APPS synonyms), the package reads and writes the following objects:

  • MSD_CS_DEFINITIONS — The base definition table holding the core attributes (plan type, classification, flags, view names, program names, and where clauses). Inserted and updated by the loader procedures.
  • MSD_CS_DEFINITIONS_S — The security/secure variant of the definition table, maintained in parallel with the base row.
  • MSD_CS_DEFINITIONS_TL — The translation table storing language-specific description text; written by TRANSLATE_ROW and ADD_LANGUAGE.
  • FND_LANGUAGES — Read to enumerate installed languages when adding language rows.
  • DUAL — Used for single-row selection and validation logic.

Usage Notes

This package is a seed and maintenance utility. It is typically invoked during setup and data migration activities — for example, by concurrent programs or one-off scripts that load planning definition metadata, or by custom code performing bulk definition maintenance. Because the header indicates a private (noship) source and the ETRM classification is OTHER, it should be treated as an internal loader rather than a supported public API. Customizations should call LOAD_ROW rather than the individual insert/update procedures, since LOAD_ROW encapsulates the decision logic between inserting and updating and preserves the owner, last-update-date, and custom-mode semantics. Any direct invocation must supply the calling language context correctly so that the _TL rows remain synchronized with the base definition.