Oracle eBusiness Suite Technical Reference

Release 11i - Copyright (c) 2001 - 2005 Oracle

This Technical Reference Manual (TRM) in any form, software or printed matter, contains proprietary information of Oracle ; it is provided under an Oracle agreement containing restrictions on use and disclosure and is also protected by copyright, patent, and other intellectual property law. Restrictions applicable to this TRM include, but are not limited to: (a) exercising either the same degree of care to safeguard the confidentiality of this TRM as you exercise to safeguard the confidentiality of your own most important Confidential Information or a reasonable degree of care, whichever is greater; (b) maintaining agreements with your employees and agents that protect the Confidential Information of third parties such as Oracle and instructing such employees and agents of these requirements for this TRM; (c) restricting disclosure of this TRM to those of your employees who have a 'need to know' consistent with the purposes for which this TRM was disclosed to you; (d) maintaining this TRM at all times on your premises; (e) not removing or destroying any proprietary or confidential legends or markings placed upon this TRM in whatever form, software or printed matter; and (f) not reproducing or transmitting this TRM in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Oracle. You should not use this TRM in any form, software or printed matter, to create software that performs the same or similar functions as any Oracle products.

The information in this TRM is subject to change without notice. If you find any problems in the TRM in any form, software or printed matter, please report them to us in writing. Oracle does not warrant that this TRM is error free. This TRM is provided to customer 'as is' with no warranty of any kind. This TRM does not constitute Documentation as that term is defined in Oracle's agreements. Reverse engineering of the Programs (software and documentation) associated with this TRM are prohibited. The Programs associated with this TRM are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be licensee's responsibility to take all appropriate fail safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and Oracle disclaims liability for any damages caused by such use of the Programs. Program Documentation is licensed for use solely to support the deployment of the Programs and not for any other any other purpose. Restricted Rights Legend

This TRM and the Programs associated with this TRM delivered subject to the DOD FAR Supplement are 'commercial computer software' and use, duplication and disclosure of the TRM and the Programs associated with this TRM shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement. Otherwise, this TRM and the Programs associated with this TRM delivered subject to the Federal Acquisition Regulations are 'restricted computer software' and use, duplication and disclosure of the TRM and the Programs associated with this TRM shall be subject to the restrictions in FAR 52.227-14, Rights in Data General, including Alternate III (June 1987). Oracle, 500 Oracle Parkway, Redwood City, CA 94065.

Oracle is a registered trademark. AIM Advantage™, Big Business. Small Business. All Business.™, CDM Advantage™, .comference™, ConText®, Des40®, Easy*Query™, Easy*SQL®, Education Objects™, EMM Advantage™, Enabling the Information Age®, ExpertDetectSM, Express®, FastForwardSM, GEMMS®, Gist™, Hyper*SQL™, instantOracle™, "Internet Business Intelligence - Insight for Everyone"™, iSQL*Plus™, JInitiator™, NLS*Workbench®, Object Marketplace™, ODP Pulse™, ODP Techwire™, OLA™, On Oracle™, Oracle®, Oracle Book®, Oracle Bookbatch®, Oracle BookBuilder®, OracleBRONZE®, Oracle Business OnLine®, OracleDevConnectSM, Oracle® Discoverer™, Oracle® Expert™, Oracle Financials®, OracleGOLDSM, OracleIncidentSM, OracleJSP™, OracleLifeCycleSM, Oracle Media Objects®, OracleMERCURYSM, OracleMetaLinkSM, OraclemetalsSM, OracleMobile™, Oracle Names®, Oracle NetSolutions®, Oracle® One™, Oracle Open Gateways®, Oracle OpenWorld®, OraclePLATINUMSM, Oracle Power Objects®, Oracle Press®, Oracle Procedural Gateway®, Oracle Quality®, Oracle Secure Network Services®, OracleSILVERSM, Oracle® SQL/Services™, Oracle® SQL*TutorSM, OracleSTERLINGSM, Oracle Store®, Oracle Transparent Gateway®, OracleWare®, Oracle8i™, Oracle9i™, PC Express®, Personal Express®, PJM Advantage™, PL/SQL™, Pro*Ada®, Pro*C™, Pro*C/C++™, Pro*COBOL®, Pro*FORTRAN®, Pro*Pascal®, Pro*PL/1®, Pro*REXX®, Profit™, ProREXX™, Report Card™, Secure Access 2.0™, Secure Network Services®, Security Without Compromise™, SellingPoint®, SQL*Plus®, Tutor™ are trademarks or registered trademarks of Oracle. Other names may be trademarks of their respective owners. The absence of a product or service name, slogan, or logo from this list does not constitute a waiver of Oracle's trademark or other intellectual property rights concerning that name, slogan, or logo.

eTRM - FLM Tables and Views

TABLE - FLM.FLM_EKB_ACT_SNAPSHOT

TABLE - FLM.FLM_EKB_CARDS_INTERFACE

TABLE - FLM.FLM_EKB_DEMAND_INTERFACE

TABLE - FLM.FLM_EKB_HORIZONTAL_PLAN_TEMP

TABLE - FLM.FLM_EKB_PREFERENCE_DEFINITIONS

TABLE - FLM.FLM_EKB_PREFERENCE_LEVELS

TABLE - FLM.FLM_EKB_PREFERENCE_VALUES

TABLE - FLM.FLM_EKB_PULL_SEQ_INTERFACE

TABLE - APPS.FLM_EKB_PULL_SEQ_TEMP

TABLE - FLM.FLM_EKB_RUN_DETAILS

TABLE - FLM.FLM_EKB_SUPPLIER_INTERFACE

TABLE - FLM.FLM_EXE_LOT_NUMBERS

TABLE - FLM.FLM_EXE_OPERATIONS

TABLE - FLM.FLM_EXE_PREFERENCES

TABLE - FLM.FLM_EXE_PREF_ENTITIES

TABLE - FLM.FLM_EXE_REQ_OPERATIONS

TABLE - FLM.FLM_EXE_SERIAL_NUMBERS

TABLE - FLM.FLM_FILTER_CRITERIA

TABLE - FLM.FLM_KANBAN_PURGE_TEMP

TABLE - FLM.FLM_KANBAN_SUMMARY

TABLE - FLM.FLM_MMM_LINES

TABLE - FLM.FLM_MMM_OPERATIONS

TABLE - FLM.FLM_MMM_OP_ITEMS

TABLE - FLM.FLM_MMM_OP_RESOURCES

TABLE - FLM.FLM_MMM_PLANS

TABLE - FLM.FLM_SEQ_ATTRIBUTES

TABLE - FLM.FLM_SEQ_LINE_RULES

TABLE - FLM.FLM_SEQ_RULES

TABLE - FLM.FLM_SEQ_RULE_CONSTRAINTS

TABLE - FLM.FLM_SEQ_TASKS

TABLE - FLM.FLM_SEQ_TASK_CONSTRAINTS

TABLE - FLM.FLM_SEQ_TASK_DEMANDS

TABLE - FLM.FLM_SEQ_TASK_EXCEPTIONS

TABLE - FLM.FLM_SEQ_TASK_LINES

VIEW - APPS.FLM_MMM_DEPT_RESOURCES_V

VIEW - APPS.FLM_MMM_LINES_V

VIEW - APPS.FLM_MMM_LINE_RESOURCES_V

VIEW - APPS.FLM_MMM_OPERATIONS_V

VIEW - APPS.FLM_MMM_OP_RESOURCES_V

VIEW - APPS.FLM_MMM_PLANS_V

VIEW - APPS.FLM_MMM_SUM_RESOURCES_V

Table: FLM_EKB_ACT_SNAPSHOT

Comments

This table stores snapshot infomration of the actual kanban transactions.

Indexes

Columns

[top of page]

FLM.FLM_EKB_ACT_SNAPSHOT does not reference any database object

FLM.FLM_EKB_ACT_SNAPSHOT is referenced by following:

FLM

VIEW - FLM_EKB_ACT_SNAPSHOT#

[top of page]

Table: FLM_EKB_CARDS_INTERFACE

Comments

This table is used for importing kanban cards from other kanban systems.

Indexes

Columns

[top of page]

FLM.FLM_EKB_CARDS_INTERFACE does not reference any database object

FLM.FLM_EKB_CARDS_INTERFACE is referenced by following:

FLM

VIEW - FLM_EKB_CARDS_INTERFACE#

[top of page]

Table: FLM_EKB_DEMAND_INTERFACE

Comments

This table is used for importing kanban demands from other kanban systems.

Indexes

Columns

[top of page]

FLM.FLM_EKB_DEMAND_INTERFACE does not reference any database object

FLM.FLM_EKB_DEMAND_INTERFACE is referenced by following:

FLM

VIEW - FLM_EKB_DEMAND_INTERFACE#

[top of page]

Table: FLM_EKB_HORIZONTAL_PLAN_TEMP

Comments

This table stores snapshot information of the Horizontal Plan information for a kanban Pull Sequence.

Indexes

Columns

[top of page]

FLM.FLM_EKB_HORIZONTAL_PLAN_TEMP does not reference any database object

FLM.FLM_EKB_HORIZONTAL_PLAN_TEMP is referenced by following:

FLM

VIEW - FLM_EKB_HORIZONTAL_PLAN_TEMP#

[top of page]

Table: FLM_EKB_PREFERENCE_DEFINITIONS

Comments

This table stores the definition of eKanban Parameters.

Indexes

Columns

[top of page]

FLM.FLM_EKB_PREFERENCE_DEFINITIONS does not reference any database object

FLM.FLM_EKB_PREFERENCE_DEFINITIONS is referenced by following:

FLM

VIEW - FLM_EKB_PREFERENCE_DEFINITION#

[top of page]

Table: FLM_EKB_PREFERENCE_LEVELS

Comments

This table stores the various levels of eKanban Parameters.

Indexes

Columns

[top of page]

FLM.FLM_EKB_PREFERENCE_LEVELS does not reference any database object

FLM.FLM_EKB_PREFERENCE_LEVELS is referenced by following:

FLM

VIEW - FLM_EKB_PREFERENCE_LEVELS#

[top of page]

Table: FLM_EKB_PREFERENCE_VALUES

Comments

This table stores the various values for eKanban Parameters.

Indexes

Columns

[top of page]

FLM.FLM_EKB_PREFERENCE_VALUES does not reference any database object

FLM.FLM_EKB_PREFERENCE_VALUES is referenced by following:

FLM

VIEW - FLM_EKB_PREFERENCE_VALUES#

[top of page]

Table: FLM_EKB_PULL_SEQ_INTERFACE

Comments

This table is used for importing Pull Sequences from other kanban systems.

Indexes

Columns

[top of page]

FLM.FLM_EKB_PULL_SEQ_INTERFACE does not reference any database object

FLM.FLM_EKB_PULL_SEQ_INTERFACE is referenced by following:

FLM

VIEW - FLM_EKB_PULL_SEQ_INTERFACE#

[top of page]

Table: FLM_EKB_PULL_SEQ_TEMP

Comments

Columns

[top of page]

APPS.FLM_EKB_PULL_SEQ_TEMP does not reference any database object

APPS.FLM_EKB_PULL_SEQ_TEMP is not referenced by any database object

[top of page]

Table: FLM_EKB_RUN_DETAILS

Comments

This table stores information regarding the execution of eKanban Metric concurrent programs.

Indexes

Columns

[top of page]

FLM.FLM_EKB_RUN_DETAILS does not reference any database object

FLM.FLM_EKB_RUN_DETAILS is referenced by following:

FLM

VIEW - FLM_EKB_RUN_DETAILS#

[top of page]

Table: FLM_EKB_SUPPLIER_INTERFACE

Comments

This table is used for importing multiple suppliers for Pull Sequences from other kanban systems.

Indexes

Columns

[top of page]

FLM.FLM_EKB_SUPPLIER_INTERFACE does not reference any database object

FLM.FLM_EKB_SUPPLIER_INTERFACE is referenced by following:

FLM

VIEW - FLM_EKB_SUPPLIER_INTERFACE#

[top of page]

Table: FLM_EXE_LOT_NUMBERS

Comments

FLM_EXE_LOT_NUMBERS stores the recorded lot numbers.

Indexes

Columns

[top of page]

FLM.FLM_EXE_LOT_NUMBERS does not reference any database object

FLM.FLM_EXE_LOT_NUMBERS is referenced by following:

FLM

VIEW - FLM_EXE_LOT_NUMBERS#

[top of page]

Table: FLM_EXE_OPERATIONS

Comments

FLM_EXE_OPERATIONS stores the current line operation as well as the history of line operation completions
Each time a line operation is completed for a flow schedule, a record is entered into this table that identifies the completed schedule, line operation and the next line operation to which schedule has been moved. It also stores whether a schedule is current on a line operation.

Indexes

Columns

[top of page]

FLM.FLM_EXE_OPERATIONS does not reference any database object

FLM.FLM_EXE_OPERATIONS is referenced by following:

FLM

VIEW - FLM_EXE_OPERATIONS#

[top of page]

Table: FLM_EXE_PREFERENCES

Primary Key: FLM_EXE_PREFERENCES_PK

1. PREFERENCE_ID

Comments

FLM_EXE_PREFERENCES stores the preferences for execution workstation.
The set of preferences for a workstation contain single value preferences and multiple value preferences. This table stores single value preferences that drive different aspects of workstation , like whether workstation is enabled, mode of work on this workstation, size of instruction frame, check engineering changes automatically etc.

Indexes

Columns

[top of page]

FLM.FLM_EXE_PREFERENCES does not reference any database object

FLM.FLM_EXE_PREFERENCES is referenced by following:

FLM

VIEW - FLM_EXE_PREFERENCES#

[top of page]

Table: FLM_EXE_PREF_ENTITIES

Primary Key: FLM_EXE_PREF_ENTITIES_PK

1. PREFERENCE_ENTITY_ID

Comments

FLM_EXE_PREFERENCES stores the details of preferences for different entities for execution workstation.
The set of preferences for a workstation contain single value preferences and multiple value preferences. This table stores multiple value preferences that drive different aspects of workstation , like which regions of information to be shown on each page and the order of these regions, list of sources from which the instruction list would be generated and their order.

Indexes

Columns

[top of page]

FLM.FLM_EXE_PREF_ENTITIES does not reference any database object

FLM.FLM_EXE_PREF_ENTITIES is referenced by following:

FLM

VIEW - FLM_EXE_PREF_ENTITIES#

[top of page]

Table: FLM_EXE_REQ_OPERATIONS

Comments

FLM_EXE_REQ_OPERATIONS stores the component requirements

Indexes

Columns

[top of page]

FLM.FLM_EXE_REQ_OPERATIONS does not reference any database object

FLM.FLM_EXE_REQ_OPERATIONS is referenced by following:

FLM

VIEW - FLM_EXE_REQ_OPERATIONS#

[top of page]

Table: FLM_EXE_SERIAL_NUMBERS

Comments

FLM_EXE_SERIAL_NUMBERS stores the recorded serial numbers.

Indexes

Columns

[top of page]

FLM.FLM_EXE_SERIAL_NUMBERS does not reference any database object

FLM.FLM_EXE_SERIAL_NUMBERS is referenced by following:

FLM

VIEW - FLM_EXE_SERIAL_NUMBERS#

[top of page]

Table: FLM_FILTER_CRITERIA

Primary Key: FLM_FILTER_CRITERIA_PK

1. CRITERIA_ID

Foreign Keys from this table:

Comments

FLM_FILTER_CRITERIA table stores the filtering criteria of flow manufacturing related query.
The filtering criteria are grouped using CRITERIA_GROUP_ID column. The type of the group criteria defined in CRITERIA_GROUP_TYPE column indicates the usage of the filtering criteria. Each group can contain one or more filtering criteria. Each filtering criteria in the filtering criteria group is identified using CRITERIA_NUM column. The type of each criteria is stored in CRITERIA_TYPE column. In one criteria, there can be one or more operations (defined in CRITERIA_OPERATION column).

Indexes

Columns

[top of page]

FLM.FLM_FILTER_CRITERIA does not reference any database object

FLM.FLM_FILTER_CRITERIA is referenced by following:

FLM

VIEW - FLM_FILTER_CRITERIA#

[top of page]

Table: FLM_KANBAN_PURGE_TEMP

Comments

FLM_KANBAN_PURGE_TEMP table stores the temporary information for building kanban purging report.

Columns

[top of page]

FLM.FLM_KANBAN_PURGE_TEMP does not reference any database object

FLM.FLM_KANBAN_PURGE_TEMP is referenced by following:

FLM

VIEW - FLM_KANBAN_PURGE_TEMP#

[top of page]

Table: FLM_KANBAN_SUMMARY

Primary Key: FLM_KANBAN_SUMMARY_PK

1. SUMMARY_ID

Foreign Keys from this table:

Comments

FLM_KANBAN_SUMMARY table stores the summary information for ranges of pull sequences that
are displayed in the Graphical Kanban Workbench

Indexes

Columns

[top of page]

FLM.FLM_KANBAN_SUMMARY does not reference any database object

FLM.FLM_KANBAN_SUMMARY is referenced by following:

FLM

VIEW - FLM_KANBAN_SUMMARY#

[top of page]

Table: FLM_MMM_LINES

Primary Key: FLM_MMM_LINES_PK

1. ORGANIZATION_ID
2. PLAN_ID
3. CALCULATION_OPERATION_TYPE
4. LINE_ID

Foreign Keys from this table:

Foreign Keys to this table:

Comments

FLM_MMM_LINES table stores the mixed model map calculated result for lines.

Indexes

Columns

[top of page]

FLM.FLM_MMM_LINES does not reference any database object

FLM.FLM_MMM_LINES is referenced by following:

FLM

VIEW - FLM_MMM_LINES#

[top of page]

Table: FLM_MMM_OPERATIONS

Primary Key: FLM_MMM_OPERATIONS_PK

1. ORGANIZATION_ID
2. PLAN_ID
3. STANDARD_OPERATION_ID

Foreign Keys from this table:

Foreign Keys to this table:

Comments

FLM_MMM_OPERATIONS table stores the mixed model map calculated result for line operations and processes.

Indexes

Columns

[top of page]

FLM.FLM_MMM_OPERATIONS does not reference any database object

FLM.FLM_MMM_OPERATIONS is referenced by following:

FLM

VIEW - FLM_MMM_OPERATIONS#

[top of page]

Table: FLM_MMM_OP_ITEMS

Primary Key: FLM_MMM_OP_ITEMS_PK

1. ORGANIZATION_ID
2. PLAN_ID
3. STANDARD_OPERATION_ID
4. ASSEMBLY_ITEM_ID

Foreign Keys from this table:

Comments

FLM_MMM_OP_ITEMS table stores the mixed model map calculated result for assembly items.

Indexes

Columns

[top of page]

FLM.FLM_MMM_OP_ITEMS does not reference any database object

FLM.FLM_MMM_OP_ITEMS is referenced by following:

FLM

VIEW - FLM_MMM_OP_ITEMS#

[top of page]

Table: FLM_MMM_OP_RESOURCES

Primary Key: FLM_MMM_OP_RESOURCES_PK

1. ORGANIZATION_ID
2. PLAN_ID
3. RESOURCE_ID
4. STANDARD_OPERATION_ID

Foreign Keys from this table:

Comments

FLM_MMM_OP_RESOURCES table stores the mixed model map calculated result for resources.

Indexes

Columns

[top of page]

FLM.FLM_MMM_OP_RESOURCES does not reference any database object

FLM.FLM_MMM_OP_RESOURCES is referenced by following:

FLM

VIEW - FLM_MMM_OP_RESOURCES#

[top of page]

Table: FLM_MMM_PLANS

Primary Key: FLM_MMM_PLANS_PK

1. ORGANIZATION_ID
2. PLAN_ID

Foreign Keys from this table:

Foreign Keys to this table:

Comments

FLM_MMM_PLANS table stores the mixed model map plan information.

Indexes

Columns

[top of page]

FLM.FLM_MMM_PLANS does not reference any database object

FLM.FLM_MMM_PLANS is referenced by following:

FLM

VIEW - FLM_MMM_PLANS#

[top of page]

Table: FLM_SEQ_ATTRIBUTES

Primary Key: FLM_SEQ_ATTRIBUTES_PK

1. ATTRIBUTE_ID

Foreign Keys to this table:

Comments

FLM_SEQ_ATTRIBUTES table stores flow sequencing attribute definition.
The sequencing attribute must be defined before creating any constraint. It identifies the value domain on which the constraint is defined. As an example, we can define an attribute named 'Color'. For the given customer, the 'Color' is stored as the attribute1 column in the sales order table. Thus the 'Color' sequencing attribute will have ATTRIBUTE_NAME of 'Color', USER_DEFINED_FLAG of 'Y', ATTRIBUTE_TYPE of 'Sales Order Property', ATTRIBUTE_SOURCE of 'ATTRIBUTE1' and ATTRIBUTE_VALUE_TYPE of 'String'.

Indexes

Columns

[top of page]

FLM.FLM_SEQ_ATTRIBUTES does not reference any database object

FLM.FLM_SEQ_ATTRIBUTES is referenced by following:

FLM

VIEW - FLM_SEQ_ATTRIBUTES#

[top of page]

Table: FLM_SEQ_LINE_RULES

Primary Key: FLM_SEQ_LINE_RULES_PK

1. LINE_ID
2. RULE_ID

Foreign Keys from this table:

Comments

FLM_SEQ_LINE_RULES table stores the association between production line and flow sequencing rule.
A production line can be assigned to multiple rules, and a rule can be assigned to multiple production lines. Among many assigned rules to a production line, the user may choose one rule as the default rule to be used on the flow sequencing run. The user will also be able to overwrite the default rule assignment at the time of the flow sequencing run.

Indexes

Columns

[top of page]

FLM.FLM_SEQ_LINE_RULES does not reference any database object

FLM.FLM_SEQ_LINE_RULES is referenced by following:

FLM

VIEW - FLM_SEQ_LINE_RULES#

[top of page]

Table: FLM_SEQ_RULES

Primary Key: FLM_SEQ_RULES_PK

1. RULE_ID

Foreign Keys from this table:

Foreign Keys to this table:

Comments

FLM_SEQ_RULES table stores flow sequencing rule definition.
This table is the parent table of FLM_SEQ_RULE_CONTRAINTS table. It holds the group or collection of constraints.

Indexes

Columns

[top of page]

FLM.FLM_SEQ_RULES does not reference any database object

FLM.FLM_SEQ_RULES is referenced by following:

FLM

VIEW - FLM_SEQ_RULES#

[top of page]

Table: FLM_SEQ_RULE_CONSTRAINTS

Primary Key: FLM_SEQ_RULE_CONSTRAINTS_PK

1. CONSTRAINT_NUMBER
2. RULE_ID

Foreign Keys from this table:

Comments

FLM_SEQ_RULE_CONTRAINTS table stores flow sequencing constraint definition.
A flow sequencing constraint is a restriction defined in the production line that dictates the order on how the assembly is built. The constraint is defined for a certain attribute.
As an example, we can have required constraint for attribute 'Color' in which assembly having color 'Red' must be followed by assembly having color 'Green'. Such constraint is defined with CONSTRAINT_TYPE of 1(Required Transition'), ATTRIBUTE_ID of X (that reference Attribute 'Color' in FLM_SEQ_ATTRIBUTES table), ATTRIBUTE_VALUE1_NAME of 'Red', and ATTRIBUTE_VALUE2_NAME of 'Green'.
The FLM_SEQ_RULE_CONTRAINTS is the child table of FLM_SEQ_RULES. One rule defined in FLM_SEQ_RULE table can have multiple constraints defined in FLM_SEQ_RULE_CONTRAINTS table. A priority will be defined for each of the constraints for a rule. The constraint having high priority (with lower number) must be satisfied before the constraint having lower priority is satisfied.

Indexes

Columns

[top of page]

FLM.FLM_SEQ_RULE_CONSTRAINTS does not reference any database object

FLM.FLM_SEQ_RULE_CONSTRAINTS is referenced by following:

FLM

VIEW - FLM_SEQ_RULE_CONSTRAINTS#

[top of page]

Table: FLM_SEQ_TASKS

Primary Key: FLM_SEQ_TASKS_PK

1. SEQ_TASK_ID

Foreign Keys from this table:

Foreign Keys to this table:

Comments

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).

Indexes

Columns

[top of page]

FLM.FLM_SEQ_TASKS does not reference any database object

FLM.FLM_SEQ_TASKS is referenced by following:

FLM

VIEW - FLM_SEQ_TASKS#

[top of page]

Table: FLM_SEQ_TASK_CONSTRAINTS

Primary Key: FLM_SEQ_TASK_CONSTRAINTS_PK

1. LINE_ID
2. CONSTRAINT_NUMBER
3. SEQ_TASK_ID

Foreign Keys from this table:

Foreign Keys to this table:

Comments

FLM_SEQ_TASK_CONSTRAINTS table stores the flow sequencing constraint information for the flow sequencing task.
It is the child table of FLM_SEQ_TASK_LINES. It holds the definition on constraints for each production line that are used by the sequencing engine. The rows will initially be copied from FLM_SEQ_RULE_CONTRAINTS table. They consist of all the constraints defined for the default sequencing rule of a production line. The user will be able to override the constraints, adding new constraints, and deleting constraints for the specific sequencing run.

Indexes

Columns

[top of page]

FLM.FLM_SEQ_TASK_CONSTRAINTS does not reference any database object

FLM.FLM_SEQ_TASK_CONSTRAINTS is referenced by following:

FLM

VIEW - FLM_SEQ_TASK_CONSTRAINTS#

[top of page]

Table: FLM_SEQ_TASK_DEMANDS

Primary Key: FLM_SEQ_TASK_DEMANDS_PK

1. DEMAND_ID
2. SPLIT_NUMBER
3. SEQ_TASK_ID
4. LINE_ID

Foreign Keys from this table:

Comments

FLM_SEQ_TASK_DEMANDS table stores the demand information for the flow sequencing tasks.
It is the child table of FLM_SEQ_TASK_LINES table. It stores the demand for each production line that will be considered by the sequencing engine. There are 2 types of demands : sales order and planned order.

Indexes

Columns

[top of page]

FLM.FLM_SEQ_TASK_DEMANDS does not reference any database object

FLM.FLM_SEQ_TASK_DEMANDS is referenced by following:

FLM

VIEW - FLM_SEQ_TASK_DEMANDS#

[top of page]

Table: FLM_SEQ_TASK_EXCEPTIONS

Primary Key: FLM_SEQ_TASK_EXCEPTIONS_PK

1. SEQ_TASK_ID
2. SEQ_EXCEPTION_NUMBER

Foreign Keys from this table:

Comments

FLM_SEQ_TASK_EXCEPTIONS table stores the flow sequencing constraint violation for the flow sequencing task.
It is the child table of FLM_SEQ_TASK_CONSTRAINTS. It stores the exception information for each constraint defined in the FLM_SEQ_TASK_CONSTRAINTS table.

Indexes

Columns

[top of page]

FLM.FLM_SEQ_TASK_EXCEPTIONS does not reference any database object

FLM.FLM_SEQ_TASK_EXCEPTIONS is referenced by following:

FLM

VIEW - FLM_SEQ_TASK_EXCEPTIONS#

[top of page]

Table: FLM_SEQ_TASK_LINES

Primary Key: FLM_SEQ_TASK_LINES_PK

1. LINE_ID
2. SEQ_TASK_ID

Foreign Keys from this table:

Foreign Keys to this table:

Comments

FLM_SEQ_TASK_LINES table stores the specific production line information for the flow sequencing task.
It is the child table of FLM_SEQ_TASKS table. It holds the specific production line parameters for a specific run. The initial values will be defaulted from WIP_LINES (Production Line) table. Through the flow sequencing user interface, the user can override those values.

Indexes

Columns

[top of page]

FLM.FLM_SEQ_TASK_LINES does not reference any database object

FLM.FLM_SEQ_TASK_LINES is referenced by following:

FLM

VIEW - FLM_SEQ_TASK_LINES#

[top of page]

View: FLM_MMM_DEPT_RESOURCES_V

Comments

***** Warning: Oracle Internal Use Only *****

Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.

View Type

A supplementary view used to simplify forms coding.

Warning: Oracle does not recommend you query or alter datausing this view. It may change dramatically in subsequent minor or major releases.

Columns

[top of page]

APPS

SYNONYM - BOM_DEPARTMENTS

SYNONYM - BOM_DEPARTMENT_RESOURCES

SYNONYM - BOM_RESOURCES

SYNONYM - BOM_STANDARD_OPERATIONS

SYNONYM - FLM_MMM_OP_RESOURCES

APPS.FLM_MMM_DEPT_RESOURCES_V is not referenced by any database object

[top of page]

View: FLM_MMM_LINES_V

Comments

***** Warning: Oracle Internal Use Only *****

Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.

View Type

A supplementary view used to simplify forms coding.

Warning: Oracle does not recommend you query or alter datausing this view. It may change dramatically in subsequent minor or major releases.

Columns

[top of page]

APPS

SYNONYM - FLM_MMM_LINES

SYNONYM - WIP_LINES

APPS.FLM_MMM_LINES_V is not referenced by any database object

[top of page]

View: FLM_MMM_LINE_RESOURCES_V

Comments

***** Warning: Oracle Internal Use Only *****

Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.

View Type

A supplementary view used to simplify forms coding.

Warning: Oracle does not recommend you query or alter datausing this view. It may change dramatically in subsequent minor or major releases.

Columns

[top of page]

APPS

SYNONYM - BOM_RESOURCES

SYNONYM - FLM_MMM_OP_RESOURCES

- MFG_LOOKUPS

APPS.FLM_MMM_LINE_RESOURCES_V is not referenced by any database object

[top of page]

View: FLM_MMM_OPERATIONS_V

Comments

***** Warning: Oracle Internal Use Only *****

Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.

View Type

A supplementary view used to simplify forms coding.

Warning: Oracle does not recommend you query or alter datausing this view. It may change dramatically in subsequent minor or major releases.

Columns

[top of page]

APPS

SYNONYM - BOM_STANDARD_OPERATIONS

SYNONYM - FLM_MMM_OPERATIONS

SYNONYM - WIP_LINES

APPS.FLM_MMM_OPERATIONS_V is not referenced by any database object

[top of page]

View: FLM_MMM_OP_RESOURCES_V

Comments

***** Warning: Oracle Internal Use Only *****

Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.

View Type

A supplementary view used to simplify forms coding.

Warning: Oracle does not recommend you query or alter datausing this view. It may change dramatically in subsequent minor or major releases.

Columns