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: AR.HZ_PURGE_BATCHES

Object Details

Object Name:	HZ_PURGE_BATCHES
Object Type:	TABLE
Owner:	AR
FND Design Data:	AR.HZ_PURGE_BATCHES
Subobject Name:
Status:	VALID

The HZ_PURGE_BATCHES table stores header level information about purge requests that contain sets of parties to purge from the TCA Registry. Purge requests are submitted and processed with a concurrent program. The table also includes the number of candidates initially identified for purge, the actual number of parties marked for purge, and the status of the request.

Storage Details

Tablespace:	APPS_TS_TX_DATA
PCT Free:	10
PCT Used:

Indexes

Index	Type	Uniqueness	Tablespace	Column
HZ_PURGE_BATCHES_U1	NORMAL	UNIQUE	APPS_TS_TX_IDX	BATCH_ID

Columns

Name	Datatype	Length	Mandatory	Comments
BATCH_ID	NUMBER	(15)	Yes	Surrogate primary key for purge request
IDENT_REQUEST_ID	NUMBER	(15)		Identify Purge Candidates concurrent request ID for this purge request. Will be NULL for online purge
PURGE_REQUEST_ID	NUMBER	(15)		Purge Parties concurrent request ID for this purge request. Will be NULL for online purge
BATCH_NAME	VARCHAR2	(255)	Yes	User-defined name for purge request
NUM_CANDIDATES	NUMBER			Number of candidates identified for purge
NUM_MARKED	NUMBER			Number of parties marked for purge
STATUS	VARCHAR2	(255)		Purge request status. IDENTIFICATION_PENDING, IDENTIFICATION_COMPLETE, IDENT_CONC_PGM_ERROR, PURGE_COMPLETE- PURGE_CONC_PGM_ERROR.
PURGE_REASON	VARCHAR2	(2000)		User-entered reason for purge request
PURGE_DATE	DATE			Date the Batch has been Purged
SUBSET_SQL	VARCHAR2	(2000)		SQL where clause that specifies subset of parties for purge candidate identification.
CREATION_DATE	DATE		Yes	Standard who column - date when this row was created.
LAST_UPDATE_LOGIN	NUMBER	(15)		Standard who column - operating system login of user who last updated this row (foreign key to FND_LOGINS.LOGIN_ID).
LAST_UPDATE_DATE	DATE		Yes	Standard Who column - date when a user last updated this row.
LAST_UPDATED_BY	NUMBER	(15)	Yes	Standard who column - user who last updated this row (foreign key to FND_USER.USER_ID).
CREATED_BY	NUMBER	(15)		Standard who column - user who created this row (foreign key to FND_USER.USER_ID).
ATTRIBUTES_FLAG	VARCHAR2	(1)		Indicates if batch was created using party attributes as criteria. Y for yes, N or null for no.

Query Text

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


SELECT BATCH_ID
,      IDENT_REQUEST_ID
,      PURGE_REQUEST_ID
,      BATCH_NAME
,      NUM_CANDIDATES
,      NUM_MARKED
,      STATUS
,      PURGE_REASON
,      PURGE_DATE
,      SUBSET_SQL
,      CREATION_DATE
,      LAST_UPDATE_LOGIN
,      LAST_UPDATE_DATE
,      LAST_UPDATED_BY
,      CREATED_BY
,      ATTRIBUTES_FLAG
FROM AR.HZ_PURGE_BATCHES;

Dependencies

[top of page]

AR.HZ_PURGE_BATCHES does not reference any database object

AR.HZ_PURGE_BATCHES is referenced by following:

AR: HZ_PURGE_BATCHES#