[Home] [Help] [Dependency Information]
Object Name: | FEM_COST_OBJECTS_HIER |
---|---|
Object Type: | TABLE |
Owner: | FEM |
FND Design Data: | FEM.FEM_COST_OBJECTS_HIER |
Subobject Name: | |
Status: | VALID |
Cost Object Hierarchy Details
Tablespace: | APPS_TS_TX_DATA |
---|---|
PCT Free: | 10 |
PCT Used: |
Index | Type | Uniqueness | Tablespace | Column |
---|---|---|---|---|
FEM_COST_OBJECTS_HIER_PK | NORMAL | UNIQUE | APPS_TS_TX_IDX |
RELATIONSHIP_ID
EFFECTIVE_START_DATE |
FEM_COST_OBJECTS_HIER_U1 | NORMAL | UNIQUE | APPS_TS_TX_IDX |
HIERARCHY_OBJ_ID
PARENT_ID CHILD_ID CHILD_SEQUENCE_NUM EFFECTIVE_START_DATE |
FEM_COST_OBJECTS_HIER_N1 | NORMAL | NONUNIQUE | APPS_TS_TX_IDX |
HIERARCHY_OBJ_ID
CHILD_ID CHILD_SEQUENCE_NUM |
Name | Datatype | Length | Mandatory | Comments |
---|---|---|---|---|
RELATIONSHIP_ID | NUMBER | (9) | Yes | Unique identifier for a parent-child relationship between Cost Objects |
EFFECTIVE_START_DATE | DATE | Yes | The first day of the time period during which this parent-child relationship is effective/applicable | |
HIERARCHY_OBJ_ID | NUMBER | (9) | Yes | Identifies the Bill Container |
PARENT_ID | NUMBER | Yes | Identifier of the parent dimension member | |
CHILD_ID | NUMBER | Yes | Identifier of the child dimension member | |
CHILD_SEQUENCE_NUM | NUMBER | (9) | Since it is possible for duplicate parent/child relationships to exist in the same hierarchy, it is necessary to employ CHILD_SEQUENCE_NUM as an additional portion of the logical key. This number need only be unique within a given hierarchy/parent/child combination. | |
DISPLAY_ORDER_NUM | NUMBER | Yes | Designates the relative order that the child is displayed on the user-interface. The order is relative to the immediate parent of the child. This means that all children of the same parent are displayed in the order indicated by DISPLAY_ORDER_NUM.\ | |
EFFECTIVE_END_DATE | DATE | Yes | Date on which the parent-child relationship expires | |
BOM_REFERENCE | VARCHAR2 | (30) | Bill of Materials reference information from the source system | |
CREATION_DATE | DATE | Yes | Identifies the date on which the row was created | |
CREATED_BY | NUMBER | (15) | Yes | Identifies the user that created the row |
LAST_UPDATED_BY | NUMBER | (15) | Yes | Identifies the user that last modified the row |
LAST_UPDATE_DATE | DATE | Yes | Identifies the date on which the row was last modified | |
LAST_UPDATE_LOGIN | NUMBER | (15) | Identifies the login user that last modified the row | |
OBJECT_VERSION_NUMBER | NUMBER | Yes | Object Version Number for stale data detection |
Cut, paste (and edit) the following text to query this object:
SELECT RELATIONSHIP_ID
, EFFECTIVE_START_DATE
, HIERARCHY_OBJ_ID
, PARENT_ID
, CHILD_ID
, CHILD_SEQUENCE_NUM
, DISPLAY_ORDER_NUM
, EFFECTIVE_END_DATE
, BOM_REFERENCE
, CREATION_DATE
, CREATED_BY
, LAST_UPDATED_BY
, LAST_UPDATE_DATE
, LAST_UPDATE_LOGIN
, OBJECT_VERSION_NUMBER
FROM FEM.FEM_COST_OBJECTS_HIER;
FEM.FEM_COST_OBJECTS_HIER does not reference any database object
FEM.FEM_COST_OBJECTS_HIER is referenced by following:
|
|
|