Search Results origination_name




Overview
Explore in AI Chat

Overview

APPS.MSC_FLP_END_DEMAND2_V is a supplementary database view in the Oracle E-Business Suite Applications schema, shipped under the MSC (Advanced Supply Chain Planning) product and registered in FND Design Data as MSC.MSC_FLP_END_DEMAND2_V. Its documented status is VALID in both Oracle EBS 12.1.1 and 12.2.2. The view belongs to the family of "FLP" (Flow/Planning) simplification views that Oracle supplies to support forms coding within the supply chain planning modules.

The view presents end demand records derived from the planning demand tables, enriching the raw keys with descriptive text. In practical terms it exposes one row per demand record tied to an inventory item, organization and plan, together with the demand date, requirement quantity, demand type, origination information, project and task context, customer, priority and satisfaction date. User-visible attributes are expanded through a lookup routine so that a form field such as Origination Name can be populated directly from the view rather than being resolved by the form at runtime.

Because it is an Oracle-supplied supplementary view, Oracle explicitly warns that the view is not recommended for direct querying or data alteration and that its definition may change dramatically in subsequent minor or major releases. It should therefore be treated as an internal forms-support object rather than a stable integration interface.

Underlying Base Objects

The documented dependency list for APPS.MSC_FLP_END_DEMAND2_V comprises three objects:

No database object references MSC_FLP_END_DEMAND2_V in turn, confirming its position as a leaf, presentation-oriented construct. ROW_ID is exposed as a ROWID pseudocolumn to support row-level identification within the originating form block.

Key Columns

  • DEMAND_ID, PLAN_ID, INVENTORY_ITEM_ID, ORGANIZATION_ID — the core planning keys identifying the demand, the plan it belongs to, and the item/organization in which it is planned.
  • USING_ASSEMBLY_DEMAND_DATE and ASSEMBLY_DEMAND_COMP_DATE — the demand date and its completion/comparison date used in pegging and scheduling logic.
  • USING_REQUIREMENTS_QUANTITY — the quantity required by the end demand.
  • DEMAND_TYPE and ORIGINATION_TYPE — numeric classifiers for the kind of demand and its originating source; the user searched term ORIGINATION_NAME corresponds to the resolved, human-readable form of ORIGINATION_TYPE.
  • ORIGINATION_NAME (VARCHAR2 4000) — the descriptive origination of the demand, resolved through MSC_GET_NAME, used in form display.
  • DISPOSITION — the resolved disposition description of the demand.
  • ITEM_ORG, DESCRIPTION — concatenated item/organization context and the item description.
  • PROJECT_NUMBER, TASK_NUMBER, UNIT_NUMBER, LENDING_PROJECT_NUMBER, LENDING_TASK_NUMBER — project and task context, including lending project/task references used in cross-charge or inter-project supply scenarios.
  • CUSTOMER, SR_INSTANCE_ID — customer identification and the source (external) instance identifier for demands originating outside the current instance.
  • SATISFIED_DATE and DEMAND_PRIORITY — the date the demand was satisfied and its planning priority.
  • ATTRIBUTE1 — a descriptive flexfield segment available for customer-specific extension.

Common Use Cases and Queries

Typical scenarios include investigating which origination source drives a given end demand, reconciling planned end demands against projects and tasks, and reviewing satisfaction status and priority for a plan. A representative query, based on the documented query text, is:

  • Locate demands by origination name: SELECT DEMAND_ID, INVENTORY_ITEM_ID, ORGANIZATION_ID, PLAN_ID, ORIGINATION_NAME, USING_REQUIREMENTS_QUANTITY, USING_ASSEMBLY_DEMAND_DATE FROM APPS.MSC_FLP_END_DEMAND2_V WHERE ORIGINATION_NAME = :p_origination_name;
  • Project-related end demands: SELECT PROJECT_NUMBER, TASK_NUMBER, ITEM_ORG, DESCRIPTION, CUSTOMER, SATISFIED_DATE FROM APPS.MSC_FLP_END_DEMAND2_V WHERE PROJECT_NUMBER IS NOT NULL AND PLAN_ID = :p_plan_id;
  • Unsatisfied high-priority demands: SELECT DEMAND_ID, DEMAND_PRIORITY, USING_REQUIREMENTS_QUANTITY, USING_ASSEMBLY_DEMAND_DATE FROM APPS.MSC_FLP_END_DEMAND2_V WHERE SATISFIED_DATE IS NULL ORDER BY DEMAND_PRIORITY, USING_ASSEMBLY_DEMAND_DATE;

All such queries should be treated as diagnostic and read-only. Given Oracle's explicit warning that the view may change without notice, any durable reporting requirement should be satisfied by building a custom view or extract against the base MSC_DEMANDS and MSC_ITEMS tables rather than depending on APPS.MSC_FLP_END_DEMAND2_V.