[Home] [Help] [Dependency Information]
Object Name: | MSC_ST_CALENDARS |
---|---|
Object Type: | TABLE |
Owner: | MSC |
FND Design Data: | MSC.MSC_ST_CALENDARS |
Subobject Name: | |
Status: | VALID |
This is an interface table for staging definition of workday calendars from Legacy Instances. The 'Pre-Processor' would then validate the data in this table and insert into MSC_CALENDARS.
You can follow any of the four following type of quarters for your yearly calendar identified by Quarterly Calendar Type
=
1. 4-4-5 : quarterly pattern having two 4 weeks followed
by a 5 week period
2. 5-4-4 : one 5 week followed by two 4 week periods
3. 13 periods : for calendar year
4. regular months of calendar year
=
Tablespace: | APPS_TS_INTERFACE |
---|---|
PCT Free: | 10 |
PCT Used: |
Name | Datatype | Length | Mandatory | Comments |
---|---|---|---|---|
CALENDAR_CODE | VARCHAR2 | (30) | Workday calendar identifier | |
DESCRIPTION | VARCHAR2 | (250) | Description | |
DAYS_ON | NUMBER | Number of consecutive working Days | ||
DAYS_OFF | NUMBER | Number of consecutive non-working days | ||
CALENDAR_START_DATE | DATE | Begining date of the calendar | ||
CALENDAR_END_DATE | DATE | End date of calendar | ||
QUARTERLY_CALENDAR_TYPE | NUMBER | Quarterely calendar type code. Possible Values:1. 4-4-5 : quarterly pattern having two 4 weeks followedby a 5 week period2. 5-4-4 : one 5 week followed by two 4 week periods3. 13 periods : for calendar year4. regular months of calendar year | ||
SR_INSTANCE_CODE | VARCHAR2 | (3) | Source Instance code | |
SR_INSTANCE_ID | NUMBER | Source instance id | ||
DELETED_FLAG | NUMBER | Deleted Flag | ||
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 Id | ||
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) | Data Source Type | |
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 | |
OVERWRITE_FLAG | VARCHAR2 | (1) | This is used by the pre-processor during the batch load to determine whether an existing calendar needs to be rebuilt. Possible values for this field are 'Y' and 'N'. If this flag is 'Y' and the calendar does not exist in the planning system, then this calendar record would not be accepted by the pre-processor. Also, if this flag is 'N' or empty and the calendar does exist in the planning system (ODS) then this record would be rejected by the pre-processor. | |
WEEK_START_DAY | NUMBER | Start day of the week, possible values are 1- Monday, 2- First day of the calendar | ||
COMPANY_NAME | VARCHAR2 | (255) | Party name with which the company is registered | |
COMPANY_ID | NUMBER | Company Id |
Cut, paste (and edit) the following text to query this object:
SELECT CALENDAR_CODE
, DESCRIPTION
, DAYS_ON
, DAYS_OFF
, CALENDAR_START_DATE
, CALENDAR_END_DATE
, QUARTERLY_CALENDAR_TYPE
, SR_INSTANCE_CODE
, SR_INSTANCE_ID
, 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
, MESSAGE_ID
, PROCESS_FLAG
, DATA_SOURCE_TYPE
, ST_TRANSACTION_ID
, ERROR_TEXT
, OVERWRITE_FLAG
, WEEK_START_DAY
, COMPANY_NAME
, COMPANY_ID
FROM MSC.MSC_ST_CALENDARS;
MSC.MSC_ST_CALENDARS does not reference any database object
MSC.MSC_ST_CALENDARS is referenced by following:
|
|
|