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: PV.PV_GE_HISTORY_LOG_B

Object Details

Object Name:	PV_GE_HISTORY_LOG_B
Object Type:	TABLE
Owner:	PV
FND Design Data:	PV.PV_GE_HISTORY_LOG_B
Subobject Name:
Status:	VALID

PV_GE_HISTORY_LOG_B is PRM's one of the Global Entitiy tables. It stores transaction history log details of an entity when that entity progresses.
Enrollment Request entity uses this table to log history of various transactions that happened with the enrollment request.
In order to have language translatability, MESSAGE_CODE is captured, which has the detailed log message for the transaction in FND message related table.
ARC_HISTORY_FOR_ENTITY_CODE stores the entity code, and HISTORY_FOR_ENTITY_ID stores the entity identifier.
HISTORY_CATEGORY_CODE categorizes the different type of history transactions.

Storage Details

Tablespace:	APPS_TS_TX_DATA
PCT Free:	10
PCT Used:

Indexes

Index	Type	Uniqueness	Tablespace	Column
PV_GE_HISTORY_LOG_B_U1	NORMAL	UNIQUE	APPS_TS_TX_IDX	ENTITY_HISTORY_LOG_ID
PV_GE_HISTORY_LOG_B_N1	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	PARTNER_ID ARC_HISTORY_FOR_ENTITY_CODE HISTORY_FOR_ENTITY_ID

Columns

Name	Datatype	Length	Mandatory	Comments
ENTITY_HISTORY_LOG_ID	NUMBER		Yes	Unique Identifier
OBJECT_VERSION_NUMBER	NUMBER	(9)	Yes	This column is used for locking purposes
ARC_HISTORY_FOR_ENTITY_CODE	VARCHAR2	(30)	Yes	Entity Code for which history transaction is being logged - Lookup
HISTORY_FOR_ENTITY_ID	NUMBER		Yes	Entity Id for which history transaction is being logged - Foreign key
MESSAGE_CODE	VARCHAR2	(30)	Yes	Foreign key to MESSAGE_CODE, which details the transaction history log
HISTORY_CATEGORY_CODE	VARCHAR2	(30)		History Category Code to categorize the different types of log messages - Lookup
CREATED_BY	NUMBER	(15)	Yes	Standard WHO column
CREATION_DATE	DATE		Yes	Standard WHO column
LAST_UPDATED_BY	NUMBER	(15)	Yes	Standard WHO column
LAST_UPDATE_DATE	DATE		Yes	Standard WHO column
LAST_UPDATE_LOGIN	NUMBER	(15)		Standard WHO column
PARTNER_ID	NUMBER		Yes	Partner ID for which history transaction is being logged - Foreign key
ACCESS_LEVEL_FLAG	VARCHAR2	(1)	Yes	The level of who has the access to see the corresponding log.
INTERACTION_LEVEL	NUMBER		Yes	The level to distinguish the importance of a log.

Query Text

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


SELECT ENTITY_HISTORY_LOG_ID
,      OBJECT_VERSION_NUMBER
,      ARC_HISTORY_FOR_ENTITY_CODE
,      HISTORY_FOR_ENTITY_ID
,      MESSAGE_CODE
,      HISTORY_CATEGORY_CODE
,      CREATED_BY
,      CREATION_DATE
,      LAST_UPDATED_BY
,      LAST_UPDATE_DATE
,      LAST_UPDATE_LOGIN
,      PARTNER_ID
,      ACCESS_LEVEL_FLAG
,      INTERACTION_LEVEL
FROM PV.PV_GE_HISTORY_LOG_B;

Dependencies

[top of page]

PV.PV_GE_HISTORY_LOG_B does not reference any database object

PV.PV_GE_HISTORY_LOG_B is referenced by following:

APPS: PV_GE_HISTORY_LOG_B