[Home] [Help] [Dependency Information]

TABLE: MRP.MRP_SCHEDULE_DATES

Object Details

Object Name:	MRP_SCHEDULE_DATES
Object Type:	TABLE
Owner:	MRP
FND Design Data:	MRP.MRP_SCHEDULE_DATES
Subobject Name:
Status:	VALID

MRP_SCHEDULE_DATES stores the master demand and master production
schedules. Each row represents a schedule entry for a given item for
a given quantity on a given date.
.
Master demand schedules will only have entries with a
SUPPLY_DEMAND_TYPE of "Demand". It will never have rows with a
SUPPLY_DEMAND_TYPE of "Supply". Master production schedules will have
entries with a SUPPLY_DEMAND_TYPE of "Supply". If a master production
schedule is planned by the planning processes, then it may also have
entries with a SUPPLY_DEMAND_TYPE of "Demand". These rows exist so
that the planning processes can peg the source of the demand. Master
production schedule entries with a SUPPLY_DEMAND_TYPE of "Demand" are
for internal purposes only, and are never visible to the user.
.
Discretely planned items will always have discretely defined schedule
entries. For discretely defined schedule entries, SCHEDULE_DATE holds
the date of the entries and SCHEDULE_QUANTITY holds the quantity.
RATE_END_DATE and REPETITIVE_DAILY_RATE will be NULL. Repetitively
planned items will always have repetitively defined schedule entries.
For repetitively defined schedule entries, SCHEDULE_DATE holds the
start date of the rate and RATE_END_DATE holds the end date.
REPETITIVE_DAILY_RATE holds the daily rate. SCHEDULE_QUANTITY will be
NULL. SCHEDULE_WORKDATE will be set equal to SCHEDULE_DATE, unless
SCHEDULE_DATE is not a valid workday, in which case SCHEDULE_WORKDATE
will equal the previous valid workday.
.
RATE_END_DATE must always be a valid work date. SCHEDULE_DATE must be
a valid work date for repetitive entries, regardless of if it is for a
master demand schedule or a master production schedule. SCHEDULE_DATE
must be a valid workday for discrete master production entries.
SCHEDULE_DATE may or may not be a valid work date for discrete master
demand entries.
.
ORIGINAL_SCHEDULE_QUANTITY equals SCHEDULE_QUANTITY when a schedule is
first created. As a schedule is consumed, SCHEDULE_QUANTITY will
decrement while ORIGINAL_SCHEDULE_QUANTITY will remain the same. The
difference between ORIGINAL_SCHEDULE_QUANTITY and SCHEDULE_QUANTITY
will always be the sum of the consumptions that have occurred for a
given entry.
.
MRP_SCHEDULE_DATES can be loaded from several different sources.
SCHEDULE_ORIGINATION_TYPE identifies the originating source.
FORECAST_DESIGNATOR, FORECAST_ID, SOURCE_ORGANIZATION_ID,
SOURCE_SCHEDULE_DESIGNATOR, SOURCE_SALES_ORDER_ID, RESERVATION_ID,
SOURCE_CODE and SOURCE_LINE identify the specific entity that
generated the schedule entry. If the origination type indicates the
order was generated by an item forecast load, the
SOURCE_ORGANIZATION_ID, FORECAST_DESIGNATOR and FORECAST_ID will store
the organization, forecast designator and specific forecast entry from
which it was loaded. If the origination type indicates the order was
generated by a sales order load, the SOURCE_ORGANIZATION_ID,
SOURCE_SALES_ORDER_ID and RESERVATION_ID identify the organization,
sales order and specific entry in MTL_DEMAND from which the sales
order was loaded. If the origination type indicates the order was
generated by a schedule copy, the SOURCE_ORGANIZATION_ID and
SOURCE_SCHEDULE_DESIGNATOR identify the organization and schedule name
from which the entry was loaded. If the origination type indicates
the order was generated by a schedule import, SOURCE_CODE and
SOURCE_LINE may be populated to indicate where the rows came from.
The SOURCE_CODE and SOURCE_LINE columns are user defined and optional.
.

Storage Details

Tablespace:	APPS_TS_TX_DATA
PCT Free:	20
PCT Used:

Indexes

Index	Type	Uniqueness	Tablespace	Column
MRP_SCHEDULE_DATES_U1	NORMAL	UNIQUE	APPS_TS_TX_IDX	MPS_TRANSACTION_ID SCHEDULE_LEVEL SUPPLY_DEMAND_TYPE
MRP_SCHEDULE_DATES_N1	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	INVENTORY_ITEM_ID SCHEDULE_DESIGNATOR ORGANIZATION_ID SCHEDULE_LEVEL SCHEDULE_DATE SUPPLY_DEMAND_TYPE
MRP_SCHEDULE_DATES_N2	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	REFERENCE_SCHEDULE_ID SCHEDULE_LEVEL SUPPLY_DEMAND_TYPE
MRP_SCHEDULE_DATES_N3	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	SCHEDULE_DESIGNATOR ORGANIZATION_ID SCHEDULE_LEVEL SCHEDULE_ORIGINATION_TYPE SUPPLY_DEMAND_TYPE
MRP_SCHEDULE_DATES_N4	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	RESERVATION_ID
MRP_SCHEDULE_DATES_N5	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	OLD_TRANSACTION_ID
MRP_SCHEDULE_DATES_N6	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	PROJECT_ID TASK_ID

Columns

Query Text

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

SELECT MPS_TRANSACTION_ID
,      SCHEDULE_LEVEL
,      SUPPLY_DEMAND_TYPE
,      LAST_UPDATE_DATE
,      LAST_UPDATED_BY
,      CREATION_DATE
,      CREATED_BY
,      LAST_UPDATE_LOGIN
,      INVENTORY_ITEM_ID
,      ORGANIZATION_ID
,      SCHEDULE_DESIGNATOR
,      SCHEDULE_DATE
,      SCHEDULE_WORKDATE
,      RATE_END_DATE
,      SCHEDULE_QUANTITY
,      ORIGINAL_SCHEDULE_QUANTITY
,      REPETITIVE_DAILY_RATE
,      SCHEDULE_ORIGINATION_TYPE
,      SOURCE_FORECAST_DESIGNATOR
,      REFERENCE_SCHEDULE_ID
,      SCHEDULE_COMMENTS
,      SOURCE_ORGANIZATION_ID
,      SOURCE_SCHEDULE_DESIGNATOR
,      SOURCE_SALES_ORDER_ID
,      SOURCE_CODE
,      SOURCE_LINE_ID
,      RESERVATION_ID
,      FORECAST_ID
,      REQUEST_ID
,      PROGRAM_APPLICATION_ID
,      PROGRAM_ID
,      PROGRAM_UPDATE_DATE
,      OLD_TRANSACTION_ID
,      TO_UPDATE
,      DDF_CONTEXT
,      ATTRIBUTE_CATEGORY
,      ATTRIBUTE1
,      ATTRIBUTE2
,      ATTRIBUTE3
,      ATTRIBUTE4
,      ATTRIBUTE5
,      ATTRIBUTE6
,      ATTRIBUTE7
,      ATTRIBUTE8
,      ATTRIBUTE9
,      ATTRIBUTE10
,      ATTRIBUTE11
,      ATTRIBUTE12
,      ATTRIBUTE13
,      ATTRIBUTE14
,      ATTRIBUTE15
,      PROJECT_ID
,      TASK_ID
,      LINE_ID
,      END_ITEM_UNIT_NUMBER
FROM MRP.MRP_SCHEDULE_DATES;

Dependencies

[top of page]

MRP.MRP_SCHEDULE_DATES does not reference any database object

MRP.MRP_SCHEDULE_DATES is referenced by following:

MRP

MRP_SCHEDULE_DATES#