Results for “intro_plan_name”

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

Overview

MSD_INTRODUCTION_PLANS_V is a reporting view in the Oracle E-Business Suite Demand Planning module (MSD). It exposes introduction plan definitions maintained by the demand planning application, presenting a simplified, denormalized projection of introduction plan header data for consumption by reports, concurrent programs, and integration interfaces. Introduction plans in Demand Planning are used to model the phased introduction of new products into the supply chain, allowing planners to define ramp-up profiles, launch dates, and associated demand characteristics for items that do not yet have historical sales data. The view provides a stable, read-only access path to these plan definitions without requiring consumers to join or understand the underlying normalized schema.

Because it is a view rather than a table, MSD_INTRODUCTION_PLANS_V carries no independent storage and cannot be directly updated. It functions purely as a queryable interface, which makes it suitable for ad hoc reporting, custom concurrent programs, and outbound integration extracts where only the plan identity and descriptive attributes are required.

Underlying Base Objects

The view is defined over the base table MSD_INTRODUCTION_PLANS, as shown in the documented view text:

• MSD_INTRODUCTION_PLANS — the single referenced base table holding the master records for introduction plans in Demand Planning.

The view text is a straightforward projection: SELECT INTRO_PLAN_ID, INTRO_PLAN_NAME, DESCRIPTION FROM MSD_INTRODUCTION_PLANS. No joins, unions, aggregations, or filter predicates are applied, so the view returns one row per introduction plan record present in the base table. According to the ETRM documentation, the metadata lists no additional referenced base objects beyond MSD_INTRODUCTION_PLANS, and Owner information is not documented. The view is also noted as "Not implemented in this database" in the captured metadata, which indicates that availability depends on whether the Demand Planning module and its schema objects have been deployed in the target environment. Consumers should verify existence and privileges before depending on the view in custom code.

Key Columns

• INTRO_PLAN_ID — The unique numeric identifier for the introduction plan. This is the primary key of the underlying base table and the value that should be used in joins to other Demand Planning tables or in foreign key references from downstream objects.
• INTRO_PLAN_NAME — The internal name of the introduction plan. In the underlying table this attribute maps to the DESCRIPTION column, and the view aliases it to PLAN_DESCRIPTION in its documented column listing. This is the human-readable label planners assign when defining a new product introduction profile.
• PLAN_DESCRIPTION — The descriptive text associated with the introduction plan. Note the naming nuance: the view text selects DESCRIPTION from the base table, while the documented column list presents the column as PLAN_DESCRIPTION. The user search term plan_description maps directly to this column, which is the most probable target for report labels and descriptive lookups.

No additional columns are documented. The view is intentionally narrow, exposing only the plan identity and descriptive attributes rather than the full set of planning parameters, which typically reside in related Demand Planning tables referenced by INTRO_PLAN_ID.

Common Use Cases and Queries

The view is most commonly used to populate LOVs, report headers, and integration extracts where a plan identifier must be paired with a readable name or description. Typical scenarios include:

• Listing all introduction plans available in the instance for selection in a custom concurrent program parameter.
• Resolving an INTRO_PLAN_ID captured in a staging or interface table into a readable plan name or description.
• Joining to other Demand Planning objects to enrich detailed planning data with plan-level descriptive context.

A basic lookup by description:

SELECT INTRO_PLAN_ID, INTRO_PLAN_NAME, PLAN_DESCRIPTION
FROM MSD_INTRODUCTION_PLANS_V
WHERE UPPER(PLAN_DESCRIPTION) LIKE UPPER('%' || :p_search || '%');

Resolving an ID to a description:

SELECT INTRO_PLAN_NAME, PLAN_DESCRIPTION
FROM MSD_INTRODUCTION_PLANS_V
WHERE INTRO_PLAN_ID = :p_intro_plan_id;

Because the view is unfiltered, it may return all plans across operating units or organizations depending on how the base table is structured; consumers should apply appropriate security or organizational predicates in custom queries. As with any custom code against MSD objects, verify the view's presence and the calling user's privileges in each environment before deployment.