[Home] [Help] [Dependency Information]

TABLE: MRP.MRP_FORECAST_INTERFACE

Object Details

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

MRP_FORECAST_INTERFACE is used to load forecast entries into a
forecast from outside sources. Each row represents a forecast
quantity for a given date that should be loaded into
MRP_FORECAST_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_FORECAST_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_FORECAST_INTERFACE which
have a PROCESS_FLAG of 2 (pending process) and null value as
REQUEST_ID and ERROR_MESSAGE.
.
Each row will be validated to ensure that the data is accurate. It
checks to make sure all the columns contain valid values, including
ORGANIZATION_ID, FORECAST_DESIGNATOR, INVENTORY_ITEM_ID, etc. Any
validation error will cause the program not to load the given row and
flag it as erroneous by setting its PROCESS_FLAG to 4. A description
of the error will be posted in the ERROR_MESSAGE column of the row.
The user has the option of resubmitting the data by correcting the
error and setting the PROCESS_FLAG back to 2 and the REQUEST_ID and
ERROR_MESSAGE to null. If the validation phase is successful, then a
row is inserted into MRP_FORECAST_DATES and the PROCESS_FLAG column
for the row in MRP_FORECAST_INTERFACE is set to 5 to indicate that it
has been loaded into the planning system.
.
FORECAST_DATE and FORECAST_END_DATE must be valid workdays, week start
dates or period start dates depending on the value of BUCKET_TYPE.
The forecast import will take different actions if a date is not a
valid workday, week start date or period start date, as controlled by
the column WORKDAY_CONTROL. The forecast import will shift a date
forward or backward to the next or previous valid workday, week or
period if the WORKDAY_CONTROL column is set to "Shift forward" or
"Shift backward" respectively. Otherwise, the forecast import will
reject the row and set the PROCESS_STATUS to 4 ("Error").
.
The forecast import also permits the user to replace a prior entry in
the MRP_FORECAST_DATES table via the use of the TRANSACTION_ID column.
If this column is populated, the forecast import will first delete any
rows in MRP_FORECAST_DATES with the same TRANSACTION_ID, before
inserting the new row in the MRP_FORECAST_DATES table with the
TRANSACTION_ID specified.
.
Rows in MRP_FORECAST_INTERFACE will be purged from the database after
a certain number of days based on the profile "MRP:Interface Table
History Days".

Storage Details

Tablespace:	APPS_TS_INTERFACE
PCT Free:	10
PCT Used:

Indexes

Index	Type	Uniqueness	Tablespace	Column
MRP_FORECAST_INTERFACE_N1	NORMAL	NONUNIQUE	APPS_TS_INTERFACE	REQUEST_ID PROCESS_STATUS
MRP_FORECAST_INTERFACE_N2	NORMAL	NONUNIQUE	APPS_TS_INTERFACE	PROCESS_STATUS INVENTORY_ITEM_ID ORGANIZATION_ID

Columns

Query Text

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

SELECT INVENTORY_ITEM_ID
,      FORECAST_DESIGNATOR
,      ORGANIZATION_ID
,      FORECAST_DATE
,      LAST_UPDATE_DATE
,      LAST_UPDATED_BY
,      CREATION_DATE
,      CREATED_BY
,      LAST_UPDATE_LOGIN
,      QUANTITY
,      PROCESS_STATUS
,      CONFIDENCE_PERCENTAGE
,      COMMENTS
,      ERROR_MESSAGE
,      REQUEST_ID
,      PROGRAM_APPLICATION_ID
,      PROGRAM_ID
,      PROGRAM_UPDATE_DATE
,      WORKDAY_CONTROL
,      BUCKET_TYPE
,      FORECAST_END_DATE
,      TRANSACTION_ID
,      SOURCE_CODE
,      SOURCE_LINE_ID
,      ATTRIBUTE1
,      ATTRIBUTE2
,      ATTRIBUTE3
,      ATTRIBUTE4
,      ATTRIBUTE5
,      ATTRIBUTE6
,      ATTRIBUTE7
,      ATTRIBUTE8
,      ATTRIBUTE9
,      ATTRIBUTE10
,      ATTRIBUTE11
,      ATTRIBUTE12
,      ATTRIBUTE13
,      ATTRIBUTE14
,      ATTRIBUTE15
,      PROJECT_ID
,      TASK_ID
,      LINE_ID
,      ATTRIBUTE_CATEGORY
,      ACTION
FROM MRP.MRP_FORECAST_INTERFACE;

Dependencies

[top of page]

MRP.MRP_FORECAST_INTERFACE does not reference any database object

MRP.MRP_FORECAST_INTERFACE is referenced by following:

MRP

MRP_FORECAST_INTERFACE#