DBA Data[Home] [Help] [Dependency Information]


TABLE: MSD.MSD_DEM_CTO_BOM

Object Details
Object Name: MSD_DEM_CTO_BOM
Object Type: TABLE
Owner: MSD
Subobject Name:
Status: VALID


Table shall have details of the BOMs.


Storage Details
Tablespace: TablespaceAPPS_TS_TX_DATA
PCT Free: 10
PCT Used:
Indexes
Index Type Uniqueness Tablespace Column
MSD_DEM_CTO_BOM_U1 NORMAL UNIQUE TablespaceAPPS_TS_TX_IDX ColumnCTO_CODE
Columns
Name Datatype Length Mandatory Comments
BASE_MODEL_ID NUMBER

Inventory item identifier of the base model
TOP_ATO_MODEL_ID NUMBER

Inventory item identifier of the top ATO model item in the BOM.
PARENT_ITEM_ID NUMBER

Inventory item identifier of parent item in the BOM
OPTION_ID NUMBER

Inventory item identifier of Option in the BOM
BASE_MODEL_SR_ID NUMBER

Inventory item identifier in the source application instance of the base model
PARENT_ITEM_SR_ID NUMBER

Inventory item identifier in the source application instance of the parent item
OPTION_SR_ID NUMBER

Inventory item identifier in the source application instance of the option in BOM
BASE_MODEL_CODE VARCHAR2 (250)
Name of the inventory base model item
PARENT_ITEM_CODE VARCHAR2 (250)
Name of the inventory parent item in the bom
OPTION_CODE VARCHAR2 (250)
Name of the inventory optional item in the bom
ORG_CODE VARCHAR2 (7)
The code includes instance code and organization code
EFFECTIVITY_DATE DATE

Date of effectivity for this component
DISABLE_DATE DATE

End of effectivity for this component
PLNG_PCT_EXISTING NUMBER

Planning factor for this component (percent)
ATO_FORECAST_CONTROL NUMBER

ATO forecast control code: Consume(1), Consume and derive(2), None(3)
CTO_TYPE VARCHAR2 (120)
Is the item a basemodel, option class or option
COMPONENT_QTY NUMBER

Quantity of the component to build one unit of item
OPTIONAL_FLAG NUMBER

Yes/No flag if optional use planning factor to determine demand
CTO_START_DATE DATE

Date of effectivity for this component as calculated by data available in demantra
CTO_END_DATE DATE

End of effectivity for this component as calculated by data available in demantra
CTO_CODE VARCHAR2 (2000)
Contains unique identifier for CTO level in demantra.(sr instance id::sr org id::sr basemodel id-sr option class id- sr option id). Its a unique identifier of BOM line from top item to bottom most item.
CTO_CHILD_CODE VARCHAR2 (2000)
Contains unique identifier for CTO child level in demantra.(basemodel id-option class id-option id)
CTO_PARENT_CODE VARCHAR2 (2000)
Contains unique identifier for CTO parent level in demantra.(basemodel id-option class id or basemodel id). Its the immediate parent of the optional item.
Query Text

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


SELECT BASE_MODEL_ID
,      TOP_ATO_MODEL_ID
,      PARENT_ITEM_ID
,      OPTION_ID
,      BASE_MODEL_SR_ID
,      PARENT_ITEM_SR_ID
,      OPTION_SR_ID
,      BASE_MODEL_CODE
,      PARENT_ITEM_CODE
,      OPTION_CODE
,      ORG_CODE
,      EFFECTIVITY_DATE
,      DISABLE_DATE
,      PLNG_PCT_EXISTING
,      ATO_FORECAST_CONTROL
,      CTO_TYPE
,      COMPONENT_QTY
,      OPTIONAL_FLAG
,      CTO_START_DATE
,      CTO_END_DATE
,      CTO_CODE
,      CTO_CHILD_CODE
,      CTO_PARENT_CODE
FROM MSD.MSD_DEM_CTO_BOM;

Dependencies

[top of page]

MSD.MSD_DEM_CTO_BOM does not reference any database object

MSD.MSD_DEM_CTO_BOM is referenced by following:

SchemaMSD
ViewMSD_DEM_CTO_BOM#