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: MSC.MSC_FORECAST_UPDATES

Object Details

Object Name:	MSC_FORECAST_UPDATES
Object Type:	TABLE
Owner:	MSC
FND Design Data:	MSC.MSC_FORECAST_UPDATES
Subobject Name:
Status:	VALID

This table describes the relationship between consumed forecast entries and sales order demands

Storage Details

Tablespace:	APPS_TS_TX_DATA
PCT Free:	10
PCT Used:

Indexes

Index	Type	Uniqueness	Tablespace	Column
MSC_FORECAST_UPDATES_N1	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	PLAN_ID ORGANIZATION_ID INVENTORY_ITEM_ID SR_INSTANCE_ID
MSC_FORECAST_UPDATES_N2	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	PLAN_ID SR_INSTANCE_ID ORGANIZATION_ID FORECAST_DEMAND_ID
MSC_FORECAST_UPDATES_N3	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	PLAN_ID SR_INSTANCE_ID ORGANIZATION_ID SALES_ORDER_ID

Columns

Name	Datatype	Length	Mandatory	Comments
FORECAST_DEMAND_ID	NUMBER		Yes	Forecast Demand identifier
SALES_ORDER_ID	NUMBER		Yes	Sales order identifier
PLAN_ID	NUMBER		Yes	Plan Identifier
INVENTORY_ITEM_ID	NUMBER		Yes	Inventory Item Identifier
ORGANIZATION_ID	NUMBER		Yes	Organization Identifier
SR_INSTANCE_ID	NUMBER		Yes	Source application identifier
DESIGNATOR_ID	NUMBER			Designator identifier
SHIP_ID	NUMBER			Forecast ship code identifier
BILL_ID	NUMBER			Forecast billing address identifier
CUSTOMER_ID	NUMBER			Customer Id
SALES_ORDER_QTY	NUMBER			Sales order quantity
CONSUMED_QTY	NUMBER			Quantity Consumed
OVERCONSUMPTION_QTY	NUMBER			Over COnsumption Quantity
FORECAST_QTY	NUMBER			Forecast Quantity
SALES_ORDER_DATE	DATE			Sales order date
CONSUMPTION_DATE	DATE			Quantity Consumed
DEMAND_CLASS	VARCHAR2	(35)		Demand class identifier
LAST_UPDATE_DATE	DATE		Yes	Standard Who column
CREATION_DATE	DATE		Yes	Standard Who column
LAST_UPDATED_BY	NUMBER		Yes	Standard Who column
CREATED_BY	NUMBER		Yes	Standard Who column
LAST_UPDATE_LOGIN	NUMBER			Standard Who column
SALES_ORDER_NUMBER	VARCHAR2	(123)		Sales order Number
ORIGINAL_ITEM_ID	NUMBER			Original Item Id
PARENT_ITEM_ID	NUMBER			Immediate Parent Model/Config Item Id
WIP_SUPPLY_TYPE	NUMBER			WIP Supply type
USAGE_QUANTITY	NUMBER			Usage of the exploded Sales Order w.r.t item is Sales Order
ZONE_ID	NUMBER			To store the Zone Id which consumed this forecast

Query Text

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


SELECT FORECAST_DEMAND_ID
,      SALES_ORDER_ID
,      PLAN_ID
,      INVENTORY_ITEM_ID
,      ORGANIZATION_ID
,      SR_INSTANCE_ID
,      DESIGNATOR_ID
,      SHIP_ID
,      BILL_ID
,      CUSTOMER_ID
,      SALES_ORDER_QTY
,      CONSUMED_QTY
,      OVERCONSUMPTION_QTY
,      FORECAST_QTY
,      SALES_ORDER_DATE
,      CONSUMPTION_DATE
,      DEMAND_CLASS
,      LAST_UPDATE_DATE
,      CREATION_DATE
,      LAST_UPDATED_BY
,      CREATED_BY
,      LAST_UPDATE_LOGIN
,      SALES_ORDER_NUMBER
,      ORIGINAL_ITEM_ID
,      PARENT_ITEM_ID
,      WIP_SUPPLY_TYPE
,      USAGE_QUANTITY
,      ZONE_ID
FROM MSC.MSC_FORECAST_UPDATES;

Dependencies

[top of page]

MSC.MSC_FORECAST_UPDATES does not reference any database object

MSC.MSC_FORECAST_UPDATES is referenced by following:

MSC: MSC_FORECAST_UPDATES#