eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

DBA Data [Home] [Help] [Dependency Information]

VIEW: APPS.MSD_DP_SCENARIO_EVENTS_V

Object Details

Object Name:	MSD_DP_SCENARIO_EVENTS_V
Object Type:	VIEW
Owner:	APPS
FND Design Data:	MSD.MSD_DP_SCENARIO_EVENTS_V
Subobject Name:
Status:	VALID

View Type

A public view which may be useful for custom reporting or other data
requirements.

This view provides all the Events except for New Product Introduction Event - i.e., Promotion, Cannibalization, Product Phase Out, and Miscellaneous Events that are associated with a Demand Plan Scenario.

[View Source]

Columns

Name	Datatype	Length	Mandatory	Comments
ROW_ID	ROWID	(10)		Underlying row identifier.
DEMAND_PLAN_ID	NUMBER		Yes	The Demand Plan ID.
DEMAND_PLAN_NAME	VARCHAR2	(30)	Yes	The Demand Plan name.
SCENARIO_ID	NUMBER		Yes	The scenario ID.
SCENARIO_NAME	VARCHAR2	(45)	Yes	The scenario name.
DESCRIPTION	VARCHAR2	(240)		The scenario description.
OUTPUT_PERIOD_TYPE_ID	VARCHAR2	(30)		The Level ID in the time dimension at which the Scenario is to be published back from the ODP to the PS. The possible values are- 1. Mfg week, 2. Mfg period, 3. Fiscal month, 4. Fiscal quarter, 5. Fiscal year, 6. Gregorian month, 7. Gregorian quarter, 8. Gregorian year, 9. Day. This is based on the MSD_PERIOD_TYPE lookup.
OUTPUT_PERIOD_TYPE	VARCHAR2	(80)		The Level in the time dimension at which the Scenario is to be published back from the ODP to the PS.
HORIZON_START_DATE	DATE			The start date from which the Scenario is to be generated.
HORIZON_END_DATE	DATE			The date till which the scenario needs to be generated.
FORECAST_DATE_USED_ID	VARCHAR2	(30)		The date ID, used for generating the forecast. This is based on MSD_DATE_USED. The possible values are : 1. Booked Date, 2. Shipped Date, 3.Requested Date, 4.Scheduled Date, and 5.Promised Date.
FORECAST_DATE_USED	VARCHAR2	(100)		The date for the forecast date ID, as mentioned in previous column.
FORECAST_BASED_ON_ID	VARCHAR2	(30)		ID for the data based on which the forecast is generated. The possible values are : 1. Booking History, and 2. Shipment History.
FORECAST_BASED_ON	VARCHAR2	(496)		The data based on which the forecast is generated. Refer previous column.
PRICE_LIST_NAME	VARCHAR2	(240)		Price List Name
EVENT_ID	NUMBER		Yes	Event ID.
EVENT_NAME	VARCHAR2	(240)	Yes	Event name.
EVENT_DESCRIPTION	VARCHAR2	(240)		Event description.
EVENT_TYPE_ID	VARCHAR2	(1)	Yes	Identifier for the typeof event. The possible values are- 1. Competitive promotion, 2. Compulsory promotion, 3. New product introduction, 4. Product phase out, 5. Competitive cannibalization, 6. Compulsory cannibalization, 7. Competitive other, 8. Compulsory other.
EVENT_TYPE	VARCHAR2	(80)	Yes	Event type for the ID mentioned in the previous column.
INTRODUCTION_TYPE_ID	VARCHAR2	(1)		Type of introductions. The possible values are- 1. History based, 2. Forecast based.
INTRODUCTION_TYPE	VARCHAR2	(80)		Introduction type as in previous column.
FORECAST_BASIS_ID	VARCHAR2	(1)		Forecast Basis Id
FORECAST_BASIS	VARCHAR2	(80)		Forecast Basis
EVENT_ASSOCIATION_PRIORITY	NUMBER			Event Association priority.
DEFAULT_EVENT_PRIORITY	NUMBER			Default Event priority.
LAST_UPDATE_DATE	DATE		Yes	Standard Who column.
LAST_UPDATED_BY	NUMBER		Yes	Standard Who column.
CREATION_DATE	DATE		Yes	Standard Who column.
CREATED_BY	NUMBER		Yes	Standard Who column.
LAST_UPDATE_LOGIN	NUMBER			Standard Who column.
REQUEST_ID	NUMBER			Enhanced Who column.
PROGRAM_APPLICATION_ID	NUMBER			Enhanced Who column.
PROGRAM_ID	NUMBER			Enhanced Who column.
PROGRAM_UPDATE_DATE	DATE			Enhanced Who column.
DELETEABLE_FLAG	VARCHAR2	(15)		Indicates whether the record is deleteable or not
ENABLE_NONSEED_FLAG	VARCHAR2	(15)		Indicates whether the fields for this record need to be disabled for non seeded records also

Query Text

Cut, paste (and edit) the following text to query this object:


SELECT ROW_ID
,      DEMAND_PLAN_ID
,      DEMAND_PLAN_NAME
,      SCENARIO_ID
,      SCENARIO_NAME
,      DESCRIPTION
,      OUTPUT_PERIOD_TYPE_ID
,      OUTPUT_PERIOD_TYPE
,      HORIZON_START_DATE
,      HORIZON_END_DATE
,      FORECAST_DATE_USED_ID
,      FORECAST_DATE_USED
,      FORECAST_BASED_ON_ID
,      FORECAST_BASED_ON
,      PRICE_LIST_NAME
,      EVENT_ID
,      EVENT_NAME
,      EVENT_DESCRIPTION
,      EVENT_TYPE_ID
,      EVENT_TYPE
,      INTRODUCTION_TYPE_ID
,      INTRODUCTION_TYPE
,      FORECAST_BASIS_ID
,      FORECAST_BASIS
,      EVENT_ASSOCIATION_PRIORITY
,      DEFAULT_EVENT_PRIORITY
,      LAST_UPDATE_DATE
,      LAST_UPDATED_BY
,      CREATION_DATE
,      CREATED_BY
,      LAST_UPDATE_LOGIN
,      REQUEST_ID
,      PROGRAM_APPLICATION_ID
,      PROGRAM_ID
,      PROGRAM_UPDATE_DATE
,      DELETEABLE_FLAG
,      ENABLE_NONSEED_FLAG
FROM APPS.MSD_DP_SCENARIO_EVENTS_V;

Dependencies

[top of page]

APPS.MSD_DP_SCENARIO_EVENTS_V references the following:

APPS: MSD_DP_SCENARIOS_CS_V; MSD_DP_SCENARIO_EVENTS; MSD_EVENTS_V

APPS.MSD_DP_SCENARIO_EVENTS_V is referenced by following:

APPS: MSD_DP_SCENARIO_ALL_EVENTS_V