eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

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

TABLE: DDR.DDR_R_BASE_DAY

Object Details

Object Name:	DDR_R_BASE_DAY
Object Type:	TABLE
Owner:	DDR
Subobject Name:
Status:	VALID

Defines a day in a calendar

Storage Details

Tablespace:	APPS_TS_TX_DATA
PCT Free:	10
PCT Used:

Indexes

Index	Type	Uniqueness	Tablespace	Column
DDR_R_BASE_DAY_U1	NORMAL	UNIQUE	APPS_TS_TX_IDX	BASE_DAY_ID

Columns

Name	Datatype	Length	Mandatory	Comments
MFG_ORG_CD	VARCHAR2	(30)	Yes	Manufacturer Organization Code
BASE_DAY_ID	NUMBER		Yes	Manufacturer Organization Code
CLNDR_CD	VARCHAR2	(30)	Yes	The unique identifier for a calendar
DAY_CD	VARCHAR2	(30)	Yes	The unique identifier for a calendar
CLNDR_TYP	VARCHAR2	(30)	Yes	An indicator of the calendar type. The values in the other columns of this record, correspond to the respective Calendar.For example: F denotes a Fiscal calendar.
WK_ID	NUMBER			An indicator of the calendar type. The values in the other columns of this record, correspond to the respective Calendar.For example: F denotes a Fiscal calendar.
WK_CD	VARCHAR2	(30)		Unique warehouse code of the week, in the Calendar.
MNTH_ID	NUMBER			Unique warehouse key of the month, in the Calendar.
MNTH_CD	VARCHAR2	(30)		Unique warehouse code of the month, in the Calendar.
DAY_OF_YR	NUMBER		Yes	Unique warehouse code of the month, in the Calendar.
WKEND_IND	VARCHAR2	(1)		The flag representing if the day is a weekend or not. For example, 0 is a weekday and 1 is a weekend.
CLNDR_STRT_DT	DATE		Yes	Start date of Calendar
CLNDR_END_DT	DATE		Yes	End date of Calendar
SRC_SYS_IDNT	VARCHAR2	(40)	Yes	User Information of who loaded the data, for auditing purpose
SRC_SYS_DT	DATE		Yes	The date that the data was created. It can be used to cross-reference the data with the source system, mainly for auditing purpose
CRTD_BY_DSR	VARCHAR2	(30)	Yes	User Information of who loaded the data, for auditing purpose
LAST_UPDT_BY_DSR	VARCHAR2	(30)	Yes	User Information of last updated by, for auditing purpose
CREATED_BY	NUMBER	(15)	Yes	Number code of who last updated the data in target table, for auditing purpose
CREATION_DATE	DATE		Yes	Date on which the data was loaded in target table, for auditing purpose
LAST_UPDATED_BY	NUMBER	(15)	Yes	Number code of who last updated the data in target table, for auditing purpose
LAST_UPDATE_DATE	DATE		Yes	Date on which the data was last udpated in target table, for auditing purpose
LAST_UPDATE_LOGIN	NUMBER	(15)	Yes	Login ID of the User who last updated the data in target table, for auditing purpose

Query Text

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


SELECT MFG_ORG_CD
,      BASE_DAY_ID
,      CLNDR_CD
,      DAY_CD
,      CLNDR_TYP
,      WK_ID
,      WK_CD
,      MNTH_ID
,      MNTH_CD
,      DAY_OF_YR
,      WKEND_IND
,      CLNDR_STRT_DT
,      CLNDR_END_DT
,      SRC_SYS_IDNT
,      SRC_SYS_DT
,      CRTD_BY_DSR
,      LAST_UPDT_BY_DSR
,      CREATED_BY
,      CREATION_DATE
,      LAST_UPDATED_BY
,      LAST_UPDATE_DATE
,      LAST_UPDATE_LOGIN
FROM DDR.DDR_R_BASE_DAY;

Dependencies

[top of page]

DDR.DDR_R_BASE_DAY does not reference any database object

DDR.DDR_R_BASE_DAY is referenced by following:

APPS: DDR_R_BASE_DAY_DN_MV; DDR_R_PRD_DRTN_DN_MV
DDR: DDR_R_BASE_DAY#