[Home] [Help]
[Dependency Information]
| Object Name: | MSC_ST_SHIFT_EXCEPTIONS |
|---|---|
| Object Type: | TABLE |
| Owner: | MSC |
| FND Design Data: | MSC.MSC_ST_SHIFT_EXCEPTIONS
|
| Subobject Name: | |
| Status: | VALID |
The staging table used by the collection program to validate and process data for table MSC_SHIFT_EXCEPTIONS.
| Tablespace: | APPS_TS_INTERFACE |
|---|---|
| PCT Free: | 10 |
| PCT Used: |
| Name | Datatype | Length | Mandatory | Comments |
|---|---|---|---|---|
| CALENDAR_CODE | VARCHAR2 | (14) | Workday Calendar Identifier | |
| SHIFT_NUM | NUMBER | If SHIFT_NAME is numeric then SHIFT_NUM will be same as SHIFT_NAME. Otherwise it wiil be a unique number to identify this shift in the calendar. This should not be loaded directly into staging table during batch upload. | ||
| EXCEPTION_SET_ID | NUMBER | Exception set identifier | ||
| EXCEPTION_DATE | DATE | Should be within calendar start date and end date | ||
| EXCEPTION_TYPE | NUMBER | Exception type Possible values 1- On 2- Off | ||
| DELETED_FLAG | NUMBER | Yes/No flag indicates whether corresponding record in ODS will be deleted | ||
| 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 | ||
| REFRESH_ID | NUMBER | Refresh identifier | ||
| SR_INSTANCE_ID | NUMBER | Source application instance identifier | ||
| COMPANY_ID | NUMBER | Company identifier | ||
| COMPANY_NAME | VARCHAR2 | (255) | Company name | |
| SHIFT_NAME | VARCHAR2 | (80) | Shift Identifier | |
| SR_INSTANCE_CODE | VARCHAR2 | (3) | Source Instance Code | |
| MESSAGE_ID | NUMBER | This is a foreign key reference to ECX_DOCLOGS.INTERNAL_CONTROL_NUMBER for records got via XML | ||
| PROCESS_FLAG | NUMBER | Processing Flag indicating the status of records during pre-processing.1- New Record, 2- In-Process, 3- Error, 4- Propagated Error, 5- Successfully Processed | ||
| DATA_SOURCE_TYPE | VARCHAR2 | (15) | Source type indicating the source of data | |
| ST_TRANSACTION_ID | NUMBER | Transaction ID generated during pre-processing to uniquely identify a record in the staging table | ||
| ERROR_TEXT | VARCHAR2 | (2000) | If PROCESS_FLAG is equal to 3 for a record, then this will describe the reason for the error |
Cut, paste (and edit) the following text to query this object:
SELECT CALENDAR_CODE
, SHIFT_NUM
, EXCEPTION_SET_ID
, EXCEPTION_DATE
, EXCEPTION_TYPE
, DELETED_FLAG
, LAST_UPDATE_DATE
, LAST_UPDATED_BY
, CREATION_DATE
, CREATED_BY
, LAST_UPDATE_LOGIN
, REQUEST_ID
, PROGRAM_APPLICATION_ID
, PROGRAM_ID
, PROGRAM_UPDATE_DATE
, REFRESH_ID
, SR_INSTANCE_ID
, COMPANY_ID
, COMPANY_NAME
, SHIFT_NAME
, SR_INSTANCE_CODE
, MESSAGE_ID
, PROCESS_FLAG
, DATA_SOURCE_TYPE
, ST_TRANSACTION_ID
, ERROR_TEXT
FROM MSC.MSC_ST_SHIFT_EXCEPTIONS;
MSC.MSC_ST_SHIFT_EXCEPTIONS does not reference any database object
MSC.MSC_ST_SHIFT_EXCEPTIONS is referenced by following:
APPS
MSC_ST_SHIFT_EXCEPTIONS
|
|
|
|