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: PJM.PJM_UNIT_NUMBERS

Object Details

Object Name:	PJM_UNIT_NUMBERS
Object Type:	TABLE
Owner:	PJM
FND Design Data:	PJM.PJM_UNIT_NUMBERS
Subobject Name:
Status:	VALID

PJM_UNIT_NUMBERS holds unique End Item Model/Unit Numbers for model/unit number effectivity controlled end items. The End Item Model/Unit Number is an alphanumeric string that typically includes a prefix and a number in sequence; for example, FAN-0001. The unit numbers defined for end items must be unique across organizations and across items.
This table corresponds to the Maintain Model/Unit Numbers window.

Storage Details

Tablespace:	APPS_TS_TX_DATA
PCT Free:	10
PCT Used:

Indexes

Index	Type	Uniqueness	Tablespace	Column
PJM_UNIT_NUMBERS_U1	NORMAL	UNIQUE	APPS_TS_TX_IDX	UNIT_NUMBER
PJM_UNIT_NUMBERS_N1	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	END_ITEM_ID

Columns

Name	Datatype	Length	Mandatory	Comments
UNIT_NUMBER	VARCHAR2	(30)	Yes	End item model/unit number
CREATION_DATE	DATE		Yes	Standard Who column
CREATED_BY	NUMBER		Yes	Standard Who column
LAST_UPDATE_DATE	DATE		Yes	Standard Who column
LAST_UPDATED_BY	NUMBER		Yes	Standard Who column
LAST_UPDATE_LOGIN	NUMBER	(15)		Standard Who column
REQUEST_ID	NUMBER			Extended Who column
PROGRAM_APPLICATION_ID	NUMBER			Extended Who column
PROGRAM_ID	NUMBER			Extended Who column
PROGRAM_UPDATE_DATE	DATE			Extended Who column
END_ITEM_ID	NUMBER		Yes	End item unique identifier
MASTER_ORGANIZATION_ID	NUMBER		Yes	Inventory item master organization unique identifier
PREFIX	VARCHAR2	(30)	Yes	End item model/unit number prefix
COMMENTS	VARCHAR2	(240)		User-entered comments
ATTRIBUTE_CATEGORY	VARCHAR2	(30)		Descriptive flexfield context
ATTRIBUTE1	VARCHAR2	(150)		Descriptive flexfield segment
ATTRIBUTE2	VARCHAR2	(150)		Descriptive flexfield segment
ATTRIBUTE3	VARCHAR2	(150)		Descriptive flexfield segment
ATTRIBUTE4	VARCHAR2	(150)		Descriptive flexfield segment
ATTRIBUTE5	VARCHAR2	(150)		Descriptive flexfield segment
ATTRIBUTE6	VARCHAR2	(150)		Descriptive flexfield segment
ATTRIBUTE7	VARCHAR2	(150)		Descriptive flexfield segment
ATTRIBUTE8	VARCHAR2	(150)		Descriptive flexfield segment
ATTRIBUTE9	VARCHAR2	(150)		Descriptive flexfield segment
ATTRIBUTE10	VARCHAR2	(150)		Descriptive flexfield segment
ATTRIBUTE11	VARCHAR2	(150)		Descriptive flexfield segment
ATTRIBUTE12	VARCHAR2	(150)		Descriptive flexfield segment
ATTRIBUTE13	VARCHAR2	(150)		Descriptive flexfield segment
ATTRIBUTE14	VARCHAR2	(150)		Descriptive flexfield segment
ATTRIBUTE15	VARCHAR2	(150)		Descriptive flexfield segment

Query Text

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


SELECT UNIT_NUMBER
,      CREATION_DATE
,      CREATED_BY
,      LAST_UPDATE_DATE
,      LAST_UPDATED_BY
,      LAST_UPDATE_LOGIN
,      REQUEST_ID
,      PROGRAM_APPLICATION_ID
,      PROGRAM_ID
,      PROGRAM_UPDATE_DATE
,      END_ITEM_ID
,      MASTER_ORGANIZATION_ID
,      PREFIX
,      COMMENTS
,      ATTRIBUTE_CATEGORY
,      ATTRIBUTE1
,      ATTRIBUTE2
,      ATTRIBUTE3
,      ATTRIBUTE4
,      ATTRIBUTE5
,      ATTRIBUTE6
,      ATTRIBUTE7
,      ATTRIBUTE8
,      ATTRIBUTE9
,      ATTRIBUTE10
,      ATTRIBUTE11
,      ATTRIBUTE12
,      ATTRIBUTE13
,      ATTRIBUTE14
,      ATTRIBUTE15
FROM PJM.PJM_UNIT_NUMBERS;

Dependencies

[top of page]

PJM.PJM_UNIT_NUMBERS does not reference any database object

PJM.PJM_UNIT_NUMBERS is referenced by following:

PJM: PJM_UNIT_NUMBERS#