[Home] [Help]
[Dependency Information]
Object Name: | FLM_SEQ_TASKS |
---|---|
Object Type: | TABLE |
Owner: | FLM |
FND Design Data: | ![]() |
Subobject Name: | |
Status: | VALID |
FLM_SEQ_TASKS table stores the flow sequencing task parameters.
This is the parameter table that is used by the flow sequencing engine to control the behaviour of the sequencing process. It is populated by the user through the sequencing user interface. From this table, the user indicates the name of the sequencing run (SEQ_TASK_NAME column), the type of demand to be considered (SEQ_TASK_TYPE column), the demand horizon (DEMAND_START_DATE and DEMAND_END_DATE columns), the sequencing horizon (SEQ_START_DATE and SEQ_END_DATE columns), and optionally the schedule group (SCHEDULE_GROUP_ID column).
Tablespace: | ![]() |
---|---|
PCT Free: | 10 |
PCT Used: |
Index | Type | Uniqueness | Tablespace | Column |
---|---|---|---|---|
FLM_SEQ_TASKS_U1 | NORMAL | UNIQUE |
![]() |
![]() |
Name | Datatype | Length | Mandatory | Comments |
---|---|---|---|---|
SEQ_TASK_ID | NUMBER | Yes | Sequencing task identifier | |
OBJECT_VERSION_NUMBER | NUMBER | Yes | Object version number | |
SEQ_TASK_NAME | VARCHAR2 | (80) | Yes | Sequencing task name |
ORGANIZATION_ID | NUMBER | Yes | Organization identifier | |
SEQ_TASK_TYPE | NUMBER | Yes | Type of the sequencing. There are 3 types : sequencing sales order, sequencing planned order and resequence existing schedules | |
DEMAND_START_DATE | DATE | Start date of the demand | ||
DEMAND_END_DATE | DATE | End date of the demand | ||
SEQ_REQUEST_ID | NUMBER | Yes | Request identifier | |
SEQ_START_DATE | DATE | Yes | Start date of the sequencing horizon | |
SEQ_END_DATE | DATE | Yes | End date of the seuencing horizon | |
SCHEDULE_GROUP_ID | NUMBER | Schedule group identifier | ||
ALTERNATE_ROUTING_FLAG | VARCHAR2 | (1) | To indicate if the sales order for an alternate routing will be considered | |
DEMAND_CRITERIA_GROUP_ID | NUMBER | The criteria group identifier for the demand filter. | ||
CREATED_BY | NUMBER | Yes | Standard Who column | |
CREATION_DATE | DATE | Yes | Standard Who column | |
LAST_UPDATE_LOGIN | NUMBER | Standard Who column | ||
LAST_UPDATE_DATE | DATE | Yes | Standard Who column | |
LAST_UPDATED_BY | NUMBER | Yes | Standard Who column | |
REQUEST_ID | NUMBER | Standard Who column | ||
PROGRAM_ID | NUMBER | Standard Who column | ||
PROGRAM_APPLICATION_ID | NUMBER | Standard Who column | ||
PROGRAM_UPDATE_DATE | DATE | Standard Who column | ||
HONOR_PLANNING_FLAG | VARCHAR2 | (1) | To indicate honor or not planning recommendations |
Cut, paste (and edit) the following text to query this object:
SELECT SEQ_TASK_ID
, OBJECT_VERSION_NUMBER
, SEQ_TASK_NAME
, ORGANIZATION_ID
, SEQ_TASK_TYPE
, DEMAND_START_DATE
, DEMAND_END_DATE
, SEQ_REQUEST_ID
, SEQ_START_DATE
, SEQ_END_DATE
, SCHEDULE_GROUP_ID
, ALTERNATE_ROUTING_FLAG
, DEMAND_CRITERIA_GROUP_ID
, CREATED_BY
, CREATION_DATE
, LAST_UPDATE_LOGIN
, LAST_UPDATE_DATE
, LAST_UPDATED_BY
, REQUEST_ID
, PROGRAM_ID
, PROGRAM_APPLICATION_ID
, PROGRAM_UPDATE_DATE
, HONOR_PLANNING_FLAG
FROM FLM.FLM_SEQ_TASKS;
FLM.FLM_SEQ_TASKS does not reference any database object
FLM.FLM_SEQ_TASKS is referenced by following:
|
|
|