[Home] [Help] [Dependency Information]
Object Name: | MSC_LOCAL_ID_DEMAND |
---|---|
Object Type: | TABLE |
Owner: | MSC |
FND Design Data: | MSC.MSC_LOCAL_ID_DEMAND |
Subobject Name: | |
Status: | VALID |
MSC_LOCAL_ID_DEMAND table stores the mappings between the Local IDs and the User Defined Keys for all types of Demands. The table is striped by ENTITY_NAME. The entities and their mappings with staging table columns are listed below.
ENTITY_NAME: DISPOSITION_ID_FCT
Sequence for Generating LOCAL_ID: MSC_ST_DEMAND_DISPOSITION_ID_S
Staging Table for this Entity: MSC_ST_DEMANDS
CHAR1 - SR_INSTANCE_CODE
CHAR2 - COMPANY_NAME
CHAR3 - ORGANIZATION_CODE
CHAR4 - FORECAST_DESIGNATOR
CHAR5 - ITEM_NAME
CHAR6 - SCHEDULE_LINE_NUM
DATE1 - SCHEDULE_DATE
NUMBER1 - ORIGINATION_TYPE
ENTITY_NAME: SALES_ORDER_ID
Sequence for Generating LOCAL_ID: MSC_ST_SALES_ORDER_ID_S
Staging Table for this Entity: MSC_ST_DEMANDS
CHAR1 - SR_INSTANCE_CODE
CHAR2 - COMPANY_NAME
CHAR3 - ORGANIZATION_CODE
CHAR4 - SALES_ORDER_NUMBER
ENTITY_NAME: DEMAND_ID
Sequence for Generating LOCAL_ID: MSC_ST_DEAMND_ID_S
Staging Table for this Entity: MSC_ST_DEMANDS
CHAR1 - SR_INSTANCE_CODE
CHAR2 - COMPANY_NAME
CHAR3 - ORGANIZATION_CODE
CHAR4 - SALES_ORDER_NUMBER
NUMBER1 - LINE_NUM
ENTITY_NAME:DISPOSITION_ID_MDS
Sequence for Generating LOCAL_ID: MSC_ST_DEMAND_DISPOSITION_ID_S
Staging Table for this Entity: MSC_ST_DEMANDS
CHAR1 - SR_INSTANCE_CODE
CHAR2 - COMPANY_NAME
CHAR3 - ORGANIZATION_CODE
CHAR4 - DEMAND_SCHEDULE_NAME
CHAR5 - ITEM_NAME
CHAR6 - SCHEDULE_LINE_NUM
DATE1 - SCHEDULE_DATE
NUMBER1 - ORIGINATION_TYPE
Tablespace: | APPS_TS_TX_DATA |
---|---|
PCT Free: | 10 |
PCT Used: |
Index | Type | Uniqueness | Tablespace | Column |
---|---|---|---|---|
MSC_LOCAL_ID_DEMAND_N1 | NORMAL | NONUNIQUE | APPS_TS_TX_IDX |
CHAR4
ENTITY_NAME CHAR3 CHAR1 CHAR2 NUMBER1 |
MSC_LOCAL_ID_DEMAND_N2 | NORMAL | NONUNIQUE | APPS_TS_TX_IDX |
CHAR6
CHAR4 ENTITY_NAME CHAR3 CHAR1 CHAR2 |
Name | Datatype | Length | Mandatory | Comments |
---|---|---|---|---|
LOCAL_ID | NUMBER | ID generated locally by Pre-processor | ||
ST_TRANSACTION_ID | NUMBER | Transaction ID in the staging table for the record | ||
INSTANCE_ID | NUMBER | Instance Identifier | ||
ENTITY_NAME | VARCHAR2 | (80) | The entity name to identity the target for the user defined keys | |
DATA_SOURCE_TYPE | VARCHAR2 | (15) | Source type to identify the source of data , BATCH/XML | |
NUMBER1 | NUMBER | Number1 | ||
NUMBER2 | NUMBER | Number2 | ||
NUMBER3 | NUMBER | Number3 | ||
NUMBER4 | NUMBER | Number4 | ||
NUMBER5 | NUMBER | Number5 | ||
CHAR1 | VARCHAR2 | (255) | Char1 | |
CHAR2 | VARCHAR2 | (255) | Char2 | |
CHAR3 | VARCHAR2 | (255) | Char3 | |
CHAR4 | VARCHAR2 | (255) | Char4 | |
CHAR5 | VARCHAR2 | (255) | Char5 | |
CHAR6 | VARCHAR2 | (255) | Char6 | |
CHAR7 | VARCHAR2 | (255) | Char7 | |
CHAR8 | VARCHAR2 | (255) | Char8 | |
CHAR9 | VARCHAR2 | (255) | Char9 | |
CHAR10 | VARCHAR2 | (255) | Char10 | |
DATE1 | DATE | Date1 | ||
DATE2 | DATE | Date2 | ||
DATE3 | DATE | Date3 | ||
DATE4 | DATE | Date4 | ||
DATE5 | DATE | Date5 | ||
LAST_UPDATE_DATE | DATE | Standard WHO column | ||
LAST_UPDATED_BY | NUMBER | Standard WHO column | ||
CREATION_DATE | DATE | Standard WHO column | ||
CREATED_BY | NUMBER | Standard WHO column | ||
LAST_UPDATE_LOGIN | NUMBER | Standard WHO column | ||
REQUEST_ID | NUMBER | Concurrent WHO column | ||
PROGRAM_APPLICATION_ID | NUMBER | Concurrent WHO column | ||
PROGRAM_ID | NUMBER | Concurrent WHO column | ||
PROGRAM_UPDATE_DATE | DATE | Concurrent WHO column | ||
SOURCE_ORG_ID | NUMBER | This is the Organization ID for the Organization in the legacy(source) system.This is needed to relate the data in planning server to the legacy system and is for reference purpose only. | ||
SOURCE_INVENTORY_ITEM_ID | NUMBER | This is the Inventory Item ID for the Item in the legacy(source) system.This is needed to relate the data in planning server to the legacy system and is for reference purpose only. | ||
SOURCE_USING_ASSEMBLY_ITEM_ID | NUMBER | This is the Using Assembly ID for the Assembly in the legacy(source) system.This is needed to relate the data in planning server to the legacy system and is for reference purpose only. | ||
SOURCE_SALES_ORDER_LINE_ID | NUMBER | This is the Sales Order Line ID for the Sales Order Line in the legacy(source) system.This is needed to relate the data in planning server to the legacy system and is for reference purpose only. | ||
SOURCE_PROJECT_ID | NUMBER | This is the Project ID for the Project in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. | ||
SOURCE_TASK_ID | NUMBER | This is the Task ID for the Task in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. | ||
SOURCE_CUSTOMER_SITE_ID | NUMBER | This is the Customer Site ID for the Customer Site in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only | ||
SOURCE_BILL_ID | NUMBER | This is the Bill ID for the Bill in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. | ||
SOURCE_DISPOSITION_ID | NUMBER | This is a unique ID to identify this MDS in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. | ||
SOURCE_DEMAND_SOURCE_HEADER_ID | NUMBER | This is the Demand Source Header ID for the Demand Source Header in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. | ||
SOURCE_ORIGINAL_ITEM_ID | NUMBER | This is the Original Item ID for the Original Item in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only | ||
SOURCE_DEMAND_ID | NUMBER | This is the Demand ID for the Demand in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. | ||
SOURCE_CUSTOMER_ID | NUMBER | This is the Customer ID for the Customer in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. | ||
SOURCE_BILL_TO_SITE_USE_ID | NUMBER | This is the Bill To Site Use ID for the Bill To Site Use in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. | ||
SOURCE_SHIP_TO_SITE_USE_ID | NUMBER | This is the Ship to site Use ID for the Ship to site Use in the legacy (source) system. This is needed to relate the data in planning server to the legacy system and is for reference purpose only. |
Cut, paste (and edit) the following text to query this object:
SELECT LOCAL_ID
, ST_TRANSACTION_ID
, INSTANCE_ID
, ENTITY_NAME
, DATA_SOURCE_TYPE
, NUMBER1
, NUMBER2
, NUMBER3
, NUMBER4
, NUMBER5
, CHAR1
, CHAR2
, CHAR3
, CHAR4
, CHAR5
, CHAR6
, CHAR7
, CHAR8
, CHAR9
, CHAR10
, DATE1
, DATE2
, DATE3
, DATE4
, DATE5
, LAST_UPDATE_DATE
, LAST_UPDATED_BY
, CREATION_DATE
, CREATED_BY
, LAST_UPDATE_LOGIN
, REQUEST_ID
, PROGRAM_APPLICATION_ID
, PROGRAM_ID
, PROGRAM_UPDATE_DATE
, SOURCE_ORG_ID
, SOURCE_INVENTORY_ITEM_ID
, SOURCE_USING_ASSEMBLY_ITEM_ID
, SOURCE_SALES_ORDER_LINE_ID
, SOURCE_PROJECT_ID
, SOURCE_TASK_ID
, SOURCE_CUSTOMER_SITE_ID
, SOURCE_BILL_ID
, SOURCE_DISPOSITION_ID
, SOURCE_DEMAND_SOURCE_HEADER_ID
, SOURCE_ORIGINAL_ITEM_ID
, SOURCE_DEMAND_ID
, SOURCE_CUSTOMER_ID
, SOURCE_BILL_TO_SITE_USE_ID
, SOURCE_SHIP_TO_SITE_USE_ID
FROM MSC.MSC_LOCAL_ID_DEMAND;
MSC.MSC_LOCAL_ID_DEMAND does not reference any database object
MSC.MSC_LOCAL_ID_DEMAND is referenced by following:
|
|
|