[Home] [Help]
[Dependency Information]
Object Name: | MSD_DP_SCENARIOS |
---|---|
Object Type: | TABLE |
Owner: | MSD |
FND Design Data: | ![]() |
Subobject Name: | |
Status: | VALID |
This table specifies the Scenarios to be generated from a particular Demand Plan. [To actually generate this scenario from Oracle Express, an instance of this scenario needs to be created in the Demand Plan Parameters table].
Tablespace: | ![]() |
---|---|
PCT Free: | 10 |
PCT Used: |
Index | Type | Uniqueness | Tablespace | Column |
---|---|---|---|---|
MSD_DP_SCENARIOS_U1 | NORMAL | UNIQUE |
![]() |
![]() |
MSD_DP_SCENARIOS_N1 | NORMAL | NONUNIQUE |
![]() |
![]() |
Name | Datatype | Length | Mandatory | Comments |
---|---|---|---|---|
DEMAND_PLAN_ID | NUMBER | Yes | Demand Plan Unique ID. | |
SCENARIO_ID | NUMBER | Yes | Demand Plan Scenario ID. | |
SCENARIO_NAME | VARCHAR2 | (45) | Yes | Scenario Name. |
DESCRIPTION | VARCHAR2 | (240) | Scenario Description. | |
OUTPUT_PERIOD_TYPE | VARCHAR2 | (30) | Time Level ID. | |
HORIZON_START_DATE | DATE | Time output start date. | ||
HORIZON_END_DATE | DATE | Time output end date. | ||
FORECAST_DATE_USED | VARCHAR2 | (30) | The date 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_BASED_ON | VARCHAR2 | (30) | This is the data on which the forecast is generated. The possible values are : 1. Booking History, and 2. Shipment History. | |
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 | ||
ATTRIBUTE_CATEGORY | VARCHAR2 | (30) | Descriptive Flexfield Structure Column | |
ATTRIBUTE1 | VARCHAR2 | (150) | Descriptive Flexfield Segment | |
ATTRIBUTE2 | VARCHAR2 | (150) | Descriptive Flexfield Segment | |
ATTRIBUTE3 | VARCHAR2 | (150) | Descriptive Flexfield Segment | |
ATTRIBUTE4 | VARCHAR2 | (150) | Descriptive Flexfield Segment | |
ATTRIBUTE5 | VARCHAR2 | (150) | Descriptive Flexfield Segment | |
ATTRIBUTE6 | VARCHAR2 | (150) | Descriptive Flexfield Segment | |
ATTRIBUTE7 | VARCHAR2 | (150) | Descriptive Flexfield Segment | |
ATTRIBUTE8 | VARCHAR2 | (150) | Descriptive Flexfield Segment | |
ATTRIBUTE9 | VARCHAR2 | (150) | Descriptive Flexfield Segment | |
ATTRIBUTE10 | VARCHAR2 | (150) | Descriptive Flexfield Segment | |
ATTRIBUTE11 | VARCHAR2 | (150) | Descriptive Flexfield Segment | |
ATTRIBUTE12 | VARCHAR2 | (150) | Descriptive Flexfield Segment | |
ATTRIBUTE13 | VARCHAR2 | (150) | Descriptive Flexfield Segment | |
ATTRIBUTE14 | VARCHAR2 | (150) | Descriptive Flexfield Segment | |
ATTRIBUTE15 | VARCHAR2 | (150) | Descriptive Flexfield Segment | |
SCENARIO_TYPE | NUMBER | Scenario Type. This is based on the MSD_SCENARIO_TYPE lookup. The possible values are : 1. Manufacturing Scenario, 2. Sales Scenario, and 3. Manufacturing and Sales Scenario. | ||
STATUS | VARCHAR2 | (1) | Scenario Status. This is based on the MSD_SCENARIO_STATUS lookup. The possible values are : 1. New, 2. Recieved, 3. In Collobration, 4. Demand Planned, 5. Approved, 6. Publish to APS, and 7. Error. | |
HISTORY_START_DATE | DATE | History Start Date | ||
HISTORY_END_DATE | DATE | History End Date | ||
PUBLISH_FLAG | VARCHAR2 | (30) | Publishable to Source Instance. | |
ENABLE_FLAG | VARCHAR2 | (30) | Enable Flag. | |
PRICE_LIST_NAME | VARCHAR2 | (240) | Price List Name. | |
PARAMETER_NAME | VARCHAR2 | (255) | Refers to the Name described in the Parameter. | |
LAST_REVISION | VARCHAR2 | (40) | Last revision of this scenario that was written back by DPE | |
ERROR_TYPE | VARCHAR2 | (30) | Code for Accuracy Measure | |
CONSUME_FLAG | VARCHAR2 | (30) | Consume Flag | |
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 | |
SUPPLY_PLAN_FLAG | VARCHAR2 | (15) | Identifies whether the scenario is ASCP plan specific or not. | |
SUPPLY_PLAN_ID | NUMBER | ID of the Supply Plan | ||
SUPPLY_PLAN_NAME | VARCHAR2 | (80) | Name of The Supply Plan | |
OLD_SUPPLY_PLAN_ID | NUMBER | ID of the Old Supply Plan | ||
OLD_SUPPLY_PLAN_NAME | VARCHAR2 | (240) | Name of The Old Supply Plan | |
SCENARIO_DESIGNATOR | VARCHAR2 | (80) | Identifies certain types of scenarios like Total Liability | |
DMD_PRIORITY_SCENARIO_ID | NUMBER | Specifies the corresponding demand priority scenario ID | ||
SC_TYPE | VARCHAR2 | (50) | Scenario Type | |
ASSOCIATE_PARAMETER | VARCHAR2 | (200) | Associated parameter if this scenario is used for feedback | |
RETURN_FORECAST | NUMBER |
Cut, paste (and edit) the following text to query this object:
SELECT DEMAND_PLAN_ID
, SCENARIO_ID
, SCENARIO_NAME
, DESCRIPTION
, OUTPUT_PERIOD_TYPE
, HORIZON_START_DATE
, HORIZON_END_DATE
, FORECAST_DATE_USED
, FORECAST_BASED_ON
, LAST_UPDATE_DATE
, LAST_UPDATED_BY
, CREATION_DATE
, CREATED_BY
, LAST_UPDATE_LOGIN
, REQUEST_ID
, PROGRAM_APPLICATION_ID
, PROGRAM_ID
, PROGRAM_UPDATE_DATE
, ATTRIBUTE_CATEGORY
, ATTRIBUTE1
, ATTRIBUTE2
, ATTRIBUTE3
, ATTRIBUTE4
, ATTRIBUTE5
, ATTRIBUTE6
, ATTRIBUTE7
, ATTRIBUTE8
, ATTRIBUTE9
, ATTRIBUTE10
, ATTRIBUTE11
, ATTRIBUTE12
, ATTRIBUTE13
, ATTRIBUTE14
, ATTRIBUTE15
, SCENARIO_TYPE
, STATUS
, HISTORY_START_DATE
, HISTORY_END_DATE
, PUBLISH_FLAG
, ENABLE_FLAG
, PRICE_LIST_NAME
, PARAMETER_NAME
, LAST_REVISION
, ERROR_TYPE
, CONSUME_FLAG
, DELETEABLE_FLAG
, ENABLE_NONSEED_FLAG
, SUPPLY_PLAN_FLAG
, SUPPLY_PLAN_ID
, SUPPLY_PLAN_NAME
, OLD_SUPPLY_PLAN_ID
, OLD_SUPPLY_PLAN_NAME
, SCENARIO_DESIGNATOR
, DMD_PRIORITY_SCENARIO_ID
, SC_TYPE
, ASSOCIATE_PARAMETER
, RETURN_FORECAST
FROM MSD.MSD_DP_SCENARIOS;
MSD.MSD_DP_SCENARIOS does not reference any database object
MSD.MSD_DP_SCENARIOS is referenced by following:
|
|
|