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]

TABLE: MSD.MSD_DP_SCN_ENTRIES_DENORM

Object Details

Object Name:	MSD_DP_SCN_ENTRIES_DENORM
Object Type:	TABLE
Owner:	MSD
Subobject Name:
Status:	VALID

For ODP - This table stores the forecast data uploaded from ODP. After forecast data is
uploaded back to the planning server table MSD_DP_SCENARIO_ENTRIES. The data for eligible
forecast scenarios is copied to this table.
For Demantra - This table stores the forecast exported from Demantra.
Note: From 12.1 - the table is being used to store the forecast uploaded by users using
flat files (for SRP and web-services). A dummy demand plan (with id 5555555) and a
dummy scenario (the scenario name is specified by the user) is created

Storage Details

Tablespace:	APPS_TS_TX_DATA
PCT Free:	10
PCT Used:

Indexes

Index	Type	Uniqueness	Tablespace	Column
MSD_DP_SCN_ENTRIES_DENORM_N1	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	SCENARIO_ID

Columns

Name	Datatype	Length	Mandatory	Comments
DEMAND_PLAN_ID	NUMBER		Yes	Demand Plan Id. For ODP scenarios - the id for the demand plan from msd_demand_plans. For Demantra and all other scenarios (for e.g. forecast data loaded for SRP, Web Services etc) - the id is hard coded to 5555555
SCENARIO_ID	NUMBER		Yes	Scenario Id. For ODP scenarios - the id for the scenario of a demand plan from msd_dp_scenarios For Demantra - the id = 5555555 + id of the export data profile from TRANSFER_QUERY table. For all others - the id is the scenario id from msd_dp_scenarios with demand plan id = 5555555
DEMAND_ID	NUMBER		Yes	Demand Id. Unique id for each forecast row in a scenario. For ODP scenarios - the demand id corresponds to 'entry_id' from msd_dp_scenario_entries. For Demantra and all others - its a unique id for each forecast row in the scenario.
BUCKET_TYPE	NUMBER			Type of time bucket. Lookup Type = MSC_X_BUCKET_TYPE, 1 = Day, 2 = Week, 3 = Month/Period.
START_TIME	DATE			Start date of the time bucket.
END_TIME	DATE			End date of the time bucket.
QUANTITY	NUMBER			Forecast/Demand quantity. The quantity is in the primary UOM of the item. The primary UOM is the same as MSC_SYSTEM_ITEMS.UOM_CODE
SR_ORGANIZATION_ID	NUMBER			Source id of the Organization. For global forecasts (forecast is being uploaded/exported at non-org level) - the column will be populated with -1. For local forecasts (forecast being uploaded/exported at org level) - the column will be populated with the source organization id. In ASCP you can join this column with MSC_TRADING_PARTNERS.SR_TP_ID for partner_type = 3 (Organizations)
SR_INSTANCE_ID	NUMBER			Id of the source instance. This corresponds to MSC_APPS_INSTANCES.INSTANCE_ID.
SR_INVENTORY_ITEM_ID	NUMBER			Source id for the item. This corresponds to MTL_SYSTEM_ITEMS.INVENTORY_ITEM_ID in the source instance and MSC_SYSTEM_ITEMS.SR_INVENTORY_ITEM_ID in the destination instance.
ERROR_TYPE	VARCHAR2	(30)		Forecast error type. Values = MAD, MAPE,
FORECAST_ERROR	NUMBER			Forecast error value. This column is populated only if the column ERROR_TYPE is not null.
INVENTORY_ITEM_ID	NUMBER			Destination id for the item. This corresponds to MSC_SYSTEM_ITEMS.INVENTORY_ITEM_ID in the destination instance.
SR_SHIP_TO_LOC_ID	NUMBER			Source id of the Ship-To site. This corresponds to MSC_TP_SITE_ID_LID.SR_TP_SITE_ID for partner_type = 2 and sr_instance_id.
SR_CUSTOMER_ID	NUMBER			Source id of the customer account. This corresponds to MSC_TP_ID_LID.SR_TP_ID for partner_type = 2 and sr_instance_id.
SR_ZONE_ID	NUMBER			Source id of the zone. This corresponds to MSC_REGIONS.REGION_ID for the sr_instance_id.
PRIORITY	NUMBER			Demand priority. For ODP scenarios - this is the quantity from the demand priority scenario associated with the forecast scenario. For Demantra scenarios - this is the quantity from the demand priority series.
DP_UOM_CODE	VARCHAR2	(10)		Demand Planning UOM Code. For ODP - This is the uom code in which ODP published forecast back to the planning server. This corresponds to MSD_DP_SCENARIO_ENTRIES.TOTAL_QUANTITY_UOM. For Demantra, it is the uom in which the forecast is exported.
ASCP_UOM_CODE	VARCHAR2	(10)		ASCP UOM Code. This is the uom code in which the quantity is populated in this table. This corresponds to MSC_SYSTEM_ITEMS.UOM_CODE
DEMAND_CLASS	VARCHAR2	(240)		Demand Class code. This corresponds to MSC_DEMAND_CLASSES.DEMAND_CLASS
UNIT_PRICE	NUMBER			Unit Price for the item. For ODP - It is calculated as AMOUNT/TOTAL_QUANTITY from MSD_DP_SCENARIO_ENTRIES. If null and for Demantra scenarios it is calculated as LIST_PRICE * ( (100 - .AVERAGE_DISCOUNT)/100) from MSC_SYSTEM_ITEMS.
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

Query Text

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


SELECT DEMAND_PLAN_ID
,      SCENARIO_ID
,      DEMAND_ID
,      BUCKET_TYPE
,      START_TIME
,      END_TIME
,      QUANTITY
,      SR_ORGANIZATION_ID
,      SR_INSTANCE_ID
,      SR_INVENTORY_ITEM_ID
,      ERROR_TYPE
,      FORECAST_ERROR
,      INVENTORY_ITEM_ID
,      SR_SHIP_TO_LOC_ID
,      SR_CUSTOMER_ID
,      SR_ZONE_ID
,      PRIORITY
,      DP_UOM_CODE
,      ASCP_UOM_CODE
,      DEMAND_CLASS
,      UNIT_PRICE
,      CREATION_DATE
,      CREATED_BY
,      LAST_UPDATE_LOGIN
,      REQUEST_ID
,      PROGRAM_APPLICATION_ID
,      PROGRAM_ID
,      PROGRAM_UPDATE_DATE
FROM MSD.MSD_DP_SCN_ENTRIES_DENORM;

Dependencies

[top of page]

MSD.MSD_DP_SCN_ENTRIES_DENORM does not reference any database object

MSD.MSD_DP_SCN_ENTRIES_DENORM is referenced by following:

APPS: MSD_DEM_SCN_ENTRIES_MV; MSD_DP_SCN_ENTRIES_DENORM