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: BIV.BIV_DBI_COLLECTION_STG

Object Details

Object Name:	BIV_DBI_COLLECTION_STG
Object Type:	TABLE
Owner:	BIV
Subobject Name:
Status:	VALID

The staging table is used by the incremental load process only. Data is extracted from the incidents audit table bases on the date (and other) parameters and the Backlog base summary and is inserted into the staging table. Further processing occurs on rows in the staging table. The completed staging table data is the basis of incrementally loading the Activity base summary, Closed base summary and Backlog base summary. These are done without the need to hit the incidents audit table again and also provide a time consistent view of the data (not effected by any changes resulting from actions of the transaction system uses).

Storage Details

Tablespace:	APPS_TS_INTERFACE
PCT Free:	10
PCT Used:

Indexes

Index	Type	Uniqueness	Tablespace	Column
BIV_DBI_COLLECTION_STG_N1	NORMAL	NONUNIQUE	APPS_TS_INTERFACE	INCIDENT_ID
BIV_DBI_COLLECTION_STG_N2	NORMAL	NONUNIQUE	APPS_TS_INTERFACE	CUSTOMER_ID

Columns

Name	Datatype	Length	Mandatory	Comments
INCIDENT_ID	NUMBER		Yes	Incident identifier, from cs_incidents_audit_b.incident_id
AUDIT_DATE	DATE		Yes	Audit date, from cs_incidents_audit_b.creation_date
INCIDENT_AUDIT_ID	NUMBER		Yes	Incident Audit identifier, from cs_incidents_audit_b.incident_audit_id
INCIDENT_TYPE_ID	NUMBER			Type identifier, from cs_incidents_audit_b.incident_type_id
INVENTORY_ITEM_ID	NUMBER			Inventory item identifier, from cs_incidents_audit_b.inventory_item_id
INV_ORGANIZATION_ID	NUMBER			Inventory organization identifier, from cs_incidents_audit_b.inv_organization_id
INCIDENT_SEVERITY_ID	NUMBER			Severity identifier, from cs_incidents_audit_b.incident_severity_id
INCIDENT_STATUS_ID	NUMBER			Status identifier, from cs_incidents_audit_b.incident_status_id
STATUS_FLAG	VARCHAR2	(1)		Status flag, from cs_incidents_audit_b.status_flag
CUSTOMER_ID	NUMBER			Customer identifier, from cs_incidents_all_b.customer_id
OWNER_GROUP_ID	NUMBER			Owner group identifier, from cs_incidents_audit_b.group_id
SR_CREATION_CHANNEL	VARCHAR2	(50)		Channel identifier, from cs_incidents_all_b.sr_creation_channel
RESOLUTION_CODE	VARCHAR2	(50)		Resolution code identifer, from cs_incidents_all_b.resolution_code
INCIDENT_DATE	DATE			Incident Date, from cs_incidents_all_b.incident_date
UNOWNED_DATE	DATE			If cs_incidents_audit_b individual owner is NULL, from cs_incidents_audit_b.owner_assigned_time
ESCALATED_DATE	DATE			If the incident is escalated, from jtf_tasks_b.actual_start_date
FIRST_OPENED_FLAG	VARCHAR2	(1)		Flag to indicate if this audit row represents a first opened activity
REOPENED_FLAG	VARCHAR2	(1)		Flag to indicate if this audit row represents a reopened activity
REOPENED_DATE	DATE			Reopened Date, from cs_incidents_audit_b.creation_date for reopened activity
CLOSED_FLAG	VARCHAR2	(1)		Flag to indicate if this audit row represents a closed activity
CLOSED_DATE	DATE			Close Date, cs_incidents_audit_b.close_date
BACKLOG_ROWID	ROWID	(10)		Rowid of most recent backlog row for this incident
LAST_FOR_DAY_FLAG	VARCHAR2	(1)		Flag to indicate if staging table row is the last row for that incident for that day
CREATION_DATE	DATE		Yes	Standard who column - date when this row was created.
CREATED_BY	NUMBER		Yes	Standard who column - user who created this row (foreign key to FND_USER.USER_ID).
LAST_UPDATE_DATE	DATE		Yes	Standard Who column - date when a user last updated this row.
LAST_UPDATED_BY	NUMBER		Yes	Standard who column - user who last updated this row (foreign key to FND_USER.USER_ID).
LAST_UPDATE_LOGIN	NUMBER			Standard who column - operating system login of user who last updated this row (foreign key to FND_LOGINS.LOGIN_ID).
PARTY_MERGE_FLAG	VARCHAR2	(1)		Flag to indicate if party merge has occured for this customer
OLD_CUSTOMER_ID	NUMBER			If party merge has occured, this is the old customer identifier
OLD_STATUS_FLAG	VARCHAR2	(1)		Old revision code for the Flag to denote whether the status of the SR is open or closed
RESOLVED_FLAG	VARCHAR2	(1)		Resolved status flag
INCIDENT_RESOLVED_DATE	DATE			Incident resolved date
RESOLVED_EVENT_FLAG	VARCHAR2	(1)		Flag indicates event switch from unresolved to resolved
UNRESOLVED_EVENT_FLAG	VARCHAR2	(1)		Flag indicates event switch from resolved to unresolved
INCIDENT_URGENCY_ID	NUMBER			Identifier for service request urgency
INCIDENT_OWNER_ID	NUMBER			Identifier for the owner of the service request
EVER_ESCALATED	VARCHAR2	(1)		Flag that indicated whether SR ever escalated or not

Query Text

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


SELECT INCIDENT_ID
,      AUDIT_DATE
,      INCIDENT_AUDIT_ID
,      INCIDENT_TYPE_ID
,      INVENTORY_ITEM_ID
,      INV_ORGANIZATION_ID
,      INCIDENT_SEVERITY_ID
,      INCIDENT_STATUS_ID
,      STATUS_FLAG
,      CUSTOMER_ID
,      OWNER_GROUP_ID
,      SR_CREATION_CHANNEL
,      RESOLUTION_CODE
,      INCIDENT_DATE
,      UNOWNED_DATE
,      ESCALATED_DATE
,      FIRST_OPENED_FLAG
,      REOPENED_FLAG
,      REOPENED_DATE
,      CLOSED_FLAG
,      CLOSED_DATE
,      BACKLOG_ROWID
,      LAST_FOR_DAY_FLAG
,      CREATION_DATE
,      CREATED_BY
,      LAST_UPDATE_DATE
,      LAST_UPDATED_BY
,      LAST_UPDATE_LOGIN
,      PARTY_MERGE_FLAG
,      OLD_CUSTOMER_ID
,      OLD_STATUS_FLAG
,      RESOLVED_FLAG
,      INCIDENT_RESOLVED_DATE
,      RESOLVED_EVENT_FLAG
,      UNRESOLVED_EVENT_FLAG
,      INCIDENT_URGENCY_ID
,      INCIDENT_OWNER_ID
,      EVER_ESCALATED
FROM BIV.BIV_DBI_COLLECTION_STG;

Dependencies

[top of page]

BIV.BIV_DBI_COLLECTION_STG does not reference any database object

BIV.BIV_DBI_COLLECTION_STG is referenced by following:

APPS: BIV_DBI_COLLECTION_STG