[Home] [Help] [Dependency Information]

TABLE: MRP.MRP_SCHEDULE_INTERFACE

Object Details

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

MRP_SCHEDULE_INTERFACE is used to load master schedule entries into a
master schedule from outside sources. Each row represents a schedule
quantity for a given date that should be loaded into
MRP_SCHEDULE_DATES. Rows are processed automatically by the Planning
Manager.
.
On a regular basis, the Planning Manager checks to see if there are
rows waiting to be processed in MRP_SCHEDULE_INTERFACE. If there are
fewer rows than specified by the profile "MRP:Planning Manager Batch
Size", the Planning Manager will process those rows itself. If there
are more than the number of rows specified by the profile, the
Planning Manager spawns a worker process to process the rows. The
Planning Manager will spawn more workers if there are more rows to
process, up to a maximum as specified in the profile "MRP:Planning
Manager Max Workers".
.
The Planning Manager will process rows in MRP_SCHEDULE_INTERFACE that
have a PROCESS_FLAG of 2 (pending process) and null values for
REQUEST_ID and ERROR_MESSAGE.
.
Each row will be validated to ensure that the data is valid. It
checks to make sure all the columns contain valid values, including
ORGANIZATION_ID, SCHEDULE_DESIGNATOR, INVENTORY_ITEM_ID, CUSTOMER_ID,
etc. If the program encounters a validation error for a given row, it
will flag the row by setting the process flag to 4. A description of
the error will be inserted into the ERROR_MESSAGE column of the row.
The user has the option of resubmitting the data by correcting the
error, setting the PROCESS_FLAG back to 2, and setting the REQUEST_ID
and ERROR_MESSAGE columns to null. If no errors are encountered
during the validation phase, then a row is inserted into
MRP_SCHEDULE_DATES and the PROCESS_FLAG column on the row in
MRP_SCHEDULE_INTERFACE is set to 5 to indicate that it has been
successfully loaded into the planning system.
.
A row with a value in SCHEDULE_DATE and RATE_END_DATE is a repetitive
entry. A row with a value in SCHEDULE_DATE and a null value in
RATE_END_DATE is a discrete entry. Repetitive entries must have valid
workdates for SCHEDULE_DATE and RATE_END_DATE. In addition, discrete
master production schedule entries must have a valid workdate in
SCHEDULE_DATE. Discrete master demand schedule entries do not require
a valid workdate for SCHEDULE_DATE.
.
The schedule autoload will take different actions if either
SCHEDULE_DATE or RATE_END_DATE is not a valid workday. The schedule
autoload will shift a date forward or backward to the next or previous
valid workday if the WORKDAY_CONTROL column is set to "Shift forward"
or "Shift backward" respectively. If WORKDAY_CONTROL is set to
"Reject", the schedule autoload will reject the row and set the
PROCESS_STATUS to 5 (Error). The columns NEW_SCHEDULE_DATE and
NEW_RATE_END_DATE will hold the dates for SCHEDULE_DATE and
RATE_END_DATE after they have been moved to a valid workday. If
SCHEDULE_DATE or RATE_END_DATE contain valid dates, then their
corresponding values in NEW_SCHEDULE_DATE and NEW_RATE_END_DATE will
be the same.
.
The schedule autoload also permits the user to replace a prior entry
in the MRP_SCHEDULE_DATES table via the use of the TRANSACTION_ID
column. If this column is populated, the schedule autoload will first
delete any rows in MRP_SCHEDULE_DATES with the same transaction_id,
before inserting the new row in the MRP_SCHEDULE_DATES table with the
transaction id specified.
.

Storage Details

Tablespace:	APPS_TS_INTERFACE
PCT Free:	10
PCT Used:

Indexes

Index	Type	Uniqueness	Tablespace	Column
MRP_SCHEDULE_INTERFACE_N1	NORMAL	NONUNIQUE	APPS_TS_INTERFACE	REQUEST_ID PROCESS_STATUS
MRP_SCHEDULE_INTERFACE_N2	NORMAL	NONUNIQUE	APPS_TS_INTERFACE	PROCESS_STATUS INVENTORY_ITEM_ID

Columns

Query Text

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

SELECT INVENTORY_ITEM_ID
,      SCHEDULE_DESIGNATOR
,      ORGANIZATION_ID
,      LAST_UPDATE_DATE
,      LAST_UPDATED_BY
,      CREATION_DATE
,      CREATED_BY
,      LAST_UPDATE_LOGIN
,      SCHEDULE_DATE
,      NEW_SCHEDULE_DATE
,      RATE_END_DATE
,      NEW_RATE_END_DATE
,      SCHEDULE_QUANTITY
,      SCHEDULE_COMMENTS
,      ERROR_MESSAGE
,      WORKDAY_CONTROL
,      TRANSACTION_ID
,      PROCESS_STATUS
,      SOURCE_CODE
,      SOURCE_LINE_ID
,      PROGRAM_APPLICATION_ID
,      PROGRAM_ID
,      PROGRAM_UPDATE_DATE
,      REQUEST_ID
,      ATTRIBUTE1
,      ATTRIBUTE2
,      ATTRIBUTE3
,      ATTRIBUTE4
,      ATTRIBUTE5
,      ATTRIBUTE6
,      ATTRIBUTE7
,      ATTRIBUTE8
,      ATTRIBUTE9
,      ATTRIBUTE10
,      ATTRIBUTE11
,      ATTRIBUTE12
,      ATTRIBUTE13
,      ATTRIBUTE14
,      ATTRIBUTE15
,      PROJECT_ID
,      TASK_ID
,      LINE_ID
,      ACTION
FROM MRP.MRP_SCHEDULE_INTERFACE;

Dependencies

[top of page]

MRP.MRP_SCHEDULE_INTERFACE does not reference any database object

MRP.MRP_SCHEDULE_INTERFACE is referenced by following:

MRP

MRP_SCHEDULE_INTERFACE#