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_RESOLUTION_SUM_F

Object Details

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

This is the resolved Service Request base summary table. It stores details of resolved service requests. There is up to one row per service request. If the service request is closed without a resolution date then the closed date will be considered as resolution date

Storage Details

Tablespace:	APPS_TS_TX_DATA
PCT Free:	10
PCT Used:

Indexes

Index	Type	Uniqueness	Tablespace	Column
BIV_DBI_RESOLUTION_SUM_F_U1	NORMAL	UNIQUE	APPS_TS_TX_IDX	INCIDENT_ID
BIV_DBI_RESOLUTION_SUM_F_N1	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	CUSTOMER_ID
BIV_DBI_RESOLUTION_SUM_F_N2	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	REPORT_DATE

Columns

Name	Datatype	Length	Mandatory	Comments
REPORT_DATE	DATE		Yes	The date on which the service request was closed. Trunc of cs_incidents_audit_b.creation_date
INCIDENT_ID	NUMBER		Yes	Incident identifier
INCIDENT_TYPE_ID	NUMBER		Yes	Type identifier, from cs_incidents_audit_b.incident_type_id - Securing dimension
INVENTORY_ITEM_ID	NUMBER		Yes	Inventory item identifier, from cs_incidents_all_b.inventory_item_id
INV_ORGANIZATION_ID	NUMBER		Yes	Inventory organization identifier, from cs_incidents_all_b.inv_organization_id
INCIDENT_SEVERITY_ID	NUMBER		Yes	Severity identifier, from cs_incidents_audit_b.incident_severity_id
CUSTOMER_ID	NUMBER		Yes	Customer identifier, from cs_incidents_all_b.customer_id
OWNER_GROUP_ID	NUMBER		Yes	Owner group identifier, from cs_incidents_audit_b.group_id
SR_CREATION_CHANNEL	VARCHAR2	(50)	Yes	Channel identifier, from cs_incidents_all_b.sr_creation_channel
RESOLUTION_CODE	VARCHAR2	(50)	Yes	Resolution code identifer, from cs_incidents_all_b.resolution_code
TIME_TO_RESOLUTION	NUMBER			If the service request was not subsequently reopened, elapsed time between incident_date and close_date.
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).
ESCALATED_FLAG	VARCHAR2	(1)		Flag indicating a SR ever been escalated y/n
INCIDENT_URGENCY_ID	NUMBER			Identifier for service request urgency
INCIDENT_OWNER_ID	NUMBER			Identifier for the owner of the service request
RESPOND_ON_DATE	DATE			Date and time on which the SR was responded to.
RESPOND_BY_DATE	DATE			Date and time by which the SR is expected to be responded.
RESOLVE_BY_DATE	DATE			Date and time on which the SR is expected to be resolved.
INCIDENT_DATE	DATE			Date and time of incident occurred as reported in Service Request
CONTRACT_NUMBER	VARCHAR2	(120)		The contract with which the SR is associated.

Query Text

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


SELECT REPORT_DATE
,      INCIDENT_ID
,      INCIDENT_TYPE_ID
,      INVENTORY_ITEM_ID
,      INV_ORGANIZATION_ID
,      INCIDENT_SEVERITY_ID
,      CUSTOMER_ID
,      OWNER_GROUP_ID
,      SR_CREATION_CHANNEL
,      RESOLUTION_CODE
,      TIME_TO_RESOLUTION
,      CREATION_DATE
,      CREATED_BY
,      LAST_UPDATE_DATE
,      LAST_UPDATED_BY
,      LAST_UPDATE_LOGIN
,      ESCALATED_FLAG
,      INCIDENT_URGENCY_ID
,      INCIDENT_OWNER_ID
,      RESPOND_ON_DATE
,      RESPOND_BY_DATE
,      RESOLVE_BY_DATE
,      INCIDENT_DATE
,      CONTRACT_NUMBER
FROM BIV.BIV_DBI_RESOLUTION_SUM_F;

Dependencies

[top of page]

BIV.BIV_DBI_RESOLUTION_SUM_F does not reference any database object

BIV.BIV_DBI_RESOLUTION_SUM_F is referenced by following:

APPS: BIV_DBI_RESOLUTION_SUM_F; BIV_RES_SUM_MV; ISC_FS_009_MV; ISC_FS_011_MV