View Field Descriptions

This article contains the following topics:
casm1401
This article contains the following topics:
You can use the field description information in the basic and advanced views that are supplied with CA SDM.
The following points apply to many of the tables:
  • You must turn on audit logging, found in Administration, Options Manager, Audit Log, to see data in the advanced views.
  • pdmtime refers to date/time fields that are in GMT format (the number of elapsed seconds since 1/1/1970).
  • The terms change request and change order are used interchangeably.
View_Act_Log
The following is a basic view of the request activity log table. Activity type and the analyst’s full name are also listed in the view. The activity log table (act_log) was joined with the activity type table (act_type) and the contact table (ca_contact) to give the actual activity type of each activity log entry, and the analyst who performed the activity. Extracted fields from the joins that might be useful are located at the end of this list.
Field
Remarks
id
act_log.id: The unique identifier for this record in the act_log table.
persid
act_log.persid: The unique identifier for this record in the act_log table, preceeded by the object identifier (alg for act_log) and a colon.
call_req_id
act_log.call_req_id: Pointer to call request persid to which this activity belongs. act_log.call_req_id = call_req.persid.
last_mod_dt
act_log.last_mod_dt: The last modify date/time (pdmtime).
time_spent
act_log.time_spent: The duration of time spent on this activity, stored as the total number of seconds. For example, 80 = 1 minute, 20 seconds.
time_stamp
act_log.time_stamp: User modifiable date/time of activity (pdmtime).
system_time
act_log.system_time: The date/time of record creation (pdmtime).
analyst
act_log.analyst: The uuid pointer to the contact uuid to get the analyst who performed the activity. act_log.analyst = ca_contact.contact_uuid.
description
act_log.description: The text description of this activity, which can be modified by the user.
action_desc
act_log.action_desc: The text description of automated action, which cannot be modified by the user.
type
act_log.type: The text pointer to a record in the activity type table. For example, act_log.type = act_type.code.
knowledge_session
act_log.knowledge_session: An identifier for a particular session of a particular user.
knowledge_tool
act_log.knowledge_tool: An indicator of the knowledge management tool used for the search, such as NLS_FAQ or EXPERT, etc.
internal
act_log.internal: An integer flag (1 or 0), which indicates if this log entry is intended for all to see or just for internal use.
activity_type
act_type.symActivity: The type derived from act_log.type = act_type.code.
analyst_lastname
View_Contact_Full.last_name: The analyst's last name, derived from act_log.analyst = ca_contact.contact_uuid.
analyst_firstname
View_Contact_Full.first_name: The analyst's first name.
analyst_middlename
View_Contact_Full.middle_name: The analyst's middle name.
 
View_Audit_Assignee
The following is an advanced view of the audit log where assignee is tracked. This view shows the duration of time between assignee changes for every request and change order. Requests or change orders that are changed from a particular assignee to a null assignee, and then from null assignee back to a particular assignee, do not have the duration of the null assignee listed in this view. This view lists the following fields for both requests and change orders. There may be more than one entry for each audobj_uniqueid (request or change order).
Field
Remarks
audobj_uniqueid
audit_log.audobj_uniqueid: The audit log object unique id representing the chg.id or the call_req.id.
from_val
audit_log.attr_after_val: The ‘changed from’ assignee value.
to_val
audit_log.attr_after_val: The ‘changed to’ assignee value.
from_time
audit_log.attr_from_time: The beginning time an assignee was assigned (pdmtime).
to_time
audit_log.attr_from_time: The ending time the same assignee was assigned (pdmtime).
 
View_Audit_Group
The following is an advanced view of the audit log where group is tracked. This view shows the duration of time between group changes for every request and change order. Requests or change orders that are changed from a particular group to null group, and then from null group back to a particular group, do not have the duration of the null group listed in this view. This view lists the following fields for both requests and change orders. There may be more than one entry for each audobj_uniqueid (request or change order).
Field
Remarks
audobj_uniqueid
audit_log.audobj_uniqueid: The audit log object unique id which represents chg.id or call_req.id.
from_val
audit_log.attr_after_val: The ‘changed from’ group value.
to_val
audit_log.attr_after_val: The ‘changed to’ group value.
from_time
audit_log.attr_from_time: The beginning time group was assigned (pdmtime).
to_time
audit_log.attr_from_time: The ending time same group was assigned (pdmtime).
 
View_Audit_Priority
The following is an advanced view of the audit log where priority is tracked. This view shows the duration of time between priority changes for every request and change order. This view lists the following fields for both requests and change orders. There may be more than one entry for each audobj_uniqueid (request or change order).
Field
Remarks
audobj_uniqueid
audit_log.audobj_uniqueid: The audit object unique id, represents a request call_req.id or change order chg.id.
from_val
audit_log.attr_after_val: The ‘changed from’ value of priority.
to_val
audit_log.attr_after_val: The ‘changed to’ value of priority.
from_time
audit_log.attr_from_time: The beginning time priority was in a particular state (pdmtime).
to_time
audit_log.attr_from_time: The ending time priority was in the same state (pdmtime).
 
View_Audit_Status
The following is an advanced view of the audit log where status is tracked. This view shows the duration of time between status changes for every request and change order. This view lists the following fields for both requests and change orders. There may be more than one entry for each audobj_uniqueid (request or change order).
Field
Remarks
audobj_uniqueid
audit_log.audobj_uniqueid: The audit object unique id, which represents a request call_req.id or change order chg.id.
from_val
audit_log.attr_after_val: The ‘changed from’ value of priority.
to_val
audit_log.attr_after_val: The ‘changed to’ value of priority.
from_time
audit_log.attr_after_time: The beginning time status was in a particular state (pdmtime).
to_time
audit_log.attr_after_time: The ending time status was in the same state (pdmtime).
 
View_Change_Act_Log
The following is a basic view of all change order activity logs. This is a view of the change request activity log table (chgalg) joined with the activity type table (act_type) and the contact table (ca_contact) to give more meaningful data, such as the actual activity type description and full name of the analyst who performed the activity.
Field
Remarks
id
chgalg.id: The unique identifier for this record in the chgalg table.
persid
chgalg.persid: The unique identifier for this record in the chgalg table, preceded by the object identifier (chgalg for chgalg) and a colon.
change_id
chgalg.change_id: The pointer to the change order id to which this activity belongs.chgalg.change_id = chgalg.id
last_mod_dt
chgalg.last_mod_dt: The last modify date/time (pdmtime).
time_spent
chgalg.time_spent: The duration of time spent on this activity, stored as the total number of seconds. For example, 80 = 1 minute, 20 seconds.
time_stamp
chgalg.time_stamp: The user modifiable date/time of activity (pdmtime).
system_time
chgalg.system_time: The date/time of record creation (pdmtime).
analyst
chgalg.analyst: The uuid pointer to the contact uuid to get the analyst who performed the activity.chgalg.analyst = ca_contact.contact_uuid
description
chgalg.description: The text description of this activity, which can be modified by the user.
action_desc
chgalg.action_desc: The text description of the automated action, which cannot be modified by the user.
type
chgalg.type: The text pointer to a record in the activity type table.chgalg.type = act_type.code
internal
chgalg.internal: The integer flag (1 or 0), which indicates if this log entry is intended for all to see or just for internal use.
knowledge_session
chgalg.knowledge_session: An identifier for a particular session of a particular user.
knowledge_tool
chgalg.knowledge_tool: An indicator of the knowledge management tool used for the search, such as NLS_FAQ or EXPERT, and so on.
analyst_lastname
View_Contact_Full.last_name: The analyst's last name, derived from chgalg.analyst = ca_contact.contact_uuid.
analyst_firstname
View_Contact_Full.first_name: The first name of the analyst.
analyst_middlename
View_Contact_Full.middle_name: The middle name of the analyst.
activity_type
act_type.sym: The activity type referenced by chgalg.type = act_type.code.
 
View_Change
The following is a basic view of all change orders, listing the status, priority, category, organizations, the affected end user’s full name, the requester’s full name, the assignee’s full name, the group name and ID, and so on. Here, the change request table (chg) was joined with many other tables to give some more meaningful data about the change order.
Field
Remarks
id
chg.id: The unique identifier for this record in the chg table.
persid
chg.persid: The unique identifier for this record in the chg table, preceded by the object identifier (chg for table chg) and a colon.
chg_ref_num
chg.chg_ref_num: The change order reference number, which is used by analysts and customers to refer to a particular change order.
description
chg.description: The long description of a change order, as dictated by an analyst or customer.
status
chg.status: The unique identifier of a change order status, which is a pointer to the chgstat table.chg.status = chgstat.code.
active_flag
chg.active_flag: The integer flag to determine whether this change record is active or not (1 or 0).
start_date
chg.start_date: The date the first task goes to a pending status (pdmtime).
open_date
chg.open_date: The change order creation date (pdmtime).
last_mod_dt
chg.last_mod_dt: The last modified date (pdmtime).
last_mod_by
chg.last_mod_by: The pointer to the contact uuid who was the last contact to modify this change order.chg.last_mod_by = ca_contact.contact_uuid.
close_date
chg.close_date: The date the change order was set to inactive (pdmtime).
resolve_date
chg.resolve_date: The date the change order was set to a status configured to indicate the change was resolved (pdmtime).
rootcause
chg.rootcause: A pointer to a record in the rootcause table, which represents the original situation which required this change order to be executed.chg.rootcause = rootcause.id.
est_total_time
chg.est_total_time: The estimated total time (pdmtime) it will take to complete this change.
actual_total_time
chg.actual_total_time: The actual total time (pdmtime) it took to complete this change.
log_agent
chg.log_agent: A binary unique identifier referencing the ca_contact table, referencing the person who was the change's original creator.chg.log_agent = ca_contact.contact_uuid.
assignee
chg.assignee: The pointer to the contact uuid who is currently assigned to the change order.chg.assignee = ca_contact.contact_uuid.
organization
chg.organization: The pointer to internal organization uuid, which represents the organization to whom this change order belongs.chg.organization = ca_organization.organization_uuid.
group_id
chg.group_id: The pointer to contact uuid, which represents the group currently assigned to the change order.chg.group_id = ca_contact.contact_uuid
affected_contact
chg.affected_contact: The pointer to the contact uuid, which represents the affected contact for this change order.chg.affected_contact = ca_contact.contact_uuid
requestor
chg.requrestor: The pointer to the contact uuid, which represents the person who ordered the change.chg.requestor = ca_contact.contact_uuid
category
chg.category: The pointer to the change category code to get the category into which this change falls.chg.category = chgcat.code
priority
chg.priority: The pointer to priority enum, which represents the priority into which this change falls.chg.priority = pri.enum
need_by
chg.need_by: The date which indicates when the affected_end_user needs to have the change completed (pdmtime).
est_comp_date
chg.est_comp_date: The estimated completion date (pdmtime) for this Change Order.
actual_comp_date
chg.actual_comp_date:The actual completion date (pdmtime) of this change order.
est_cost
chg.est_cost: The estimated cost of this change order.
actual_cost
chg.actual_cost: The actual cost to implement this change order.
justification
chg.justification: A text field which allows a requestor to document the reason(s) this change is required.
backout_plan
chg.backout_plan: A text field that allows an analyst to document a backout plan for this change.
impact
chg.impact: A pointer to an impact table record, which indicates the scope of resources that this change affects.chg.impact = impact.enum
parent
chg.parent: A pointer to another change request id, which allows creation of a hierarchy of change orders.chg.parent = chg.id
effort
chg.effort: A text field which explains the plan for implementing this change order.
support_lev
chg.support_lev: A pointer to a service desc record, which automates some constraints for which this change must be completed.chg.support_lev = srv_desc.code
template_name
chg.template_name: The name of and pointer to a change order template.chg.template_name = chg_template.template_name
sla_violation
chg.sla_violation: The integer to count the number of times slas attached to this "change has been violated".
predicted_sla_viol
chg.predicted_sla_viol: (r5.5) Neugent related technology field.
macro_predict_viol
chg.macro_predict_viol: (r5.5) Neugent related technology field.
created_via
chg.created_via: A pointer to a record in the interface table, which indicates from which interface the change order originated. chg.created_via = interface.id
call_back_date
chg.call_back_date:A date/time field (pdmtime), which indicates a future date/time the requestor is to be contacted.
call_back_flag
chg.call_back_flag: A boolean indicator displayed as a checkbox to the user, indicating whether or not to notify the analyst at the chg.call_back_date.
string1
This is a user-definable text field.
string2
This is a user-definable text field.
string3
This is a user-definable text field.
string4
This is a user-definable text field.
string5
This is a user-definable text field.
string6
This is a user-definable text field.
service_date
chg.service_date: The Date/ Time (pdmtime) that an outside vendor is expected to spend to service this change order.
service_num
chg.service_num: The text field to document an outside vendor's service or purchase order number.
product
chg.product: A pointer to a record in the product table, which indicates the product that is affected by this change.chg.product = product.id
actions
chg.actions: A big text field for documenting actions.
type_of_contact
chg.type_of_contact: A pointer to a record in the toc table, which indicates a general categorization of the affected_end_user's perspective of the change order.chg.type_of_contact = toc.id
reporting_method
chg.reporting_method: A pointer to a record in the repmeth table, which classifies the origination of the change order, and is selected by the person creating the change order.chg.reporting_method = repmeth.id
person_contacting
chg.person_contacting: A pointer to a record in the perscon table, which indicates the role of the affected_end_user or requestor.chg.person_contacting = perscon.id
status_name
chgstat.sym: The description of the status as seen by a user.chg.status = chgstat.code
priority_num
pri.sym: The description of the priority as seen by a user.chg.priority = pri.enum
category_name
chgcat.sym: The name of the Change Category as viewed by a user.chg.category = chgcat.code
organization_name
ca_organization.org_name: The name of an organization as viewed by a user.chg.organization = ca_organization.organization_uuid
affected_end_user_lastname
ca_contact.last_name: The affected end user's last name.chg.affected_end_user = ca_contact.contact_uuid
affected_end_user_firstname
ca_contact.first_name: The affected end user's first name.chg.affected_end_user = ca_contact.contact_uuid
affected_end_user_middlename
ca_contact.middle_name: The affected end user's middle name.chg.affected_end_user = ca_contact.contact_uuid
requester_lastname
ca_contact.last_name: The requestor's last name.chg.requestor = ca_contact.contact_uuid
requester_firstname
ca_contact.first_name: The requestor's first name.chg.requestor = ca_contact.contact_uuid
requester_middlename
ca_contact.middle_name: The requestor's middle name.chg.requestor = ca_contact.contact_uuid
business
ca_organization.org_name: The name of the Requester's organization as seen by users.chg.requestor = ca_organization.organization_uuid
assignee_lastname
ca_contact.last_name: The assignee's last name.chg.assignee = ca_contact.contact_uuid
assignee_firstname
ca_contact.first_name: The assignee's first name.chg.assignee = ca_contact.contact_uuid
assignee_middlename
ca_contact.middle_name: The assignee's middle name.chg.assignee = ca_contact.contact_uuid
groupID
ca_contact.contact_uuid: A binary representation of the internal id used for the group assigned to this change order.chg.group_id = ca_contact.contact_uuid
group_name
ca_contact.last_name: The name of the group assigned to this change order.chg.group = ca_contact.contact_uuid
service_type
srv_desc.sym: The name of the service type applied to this change order.chg.support_lev = srv_desc.code
impact_num
impact.sym: The description of the impact as seen by users.chg.impact = impact.enum
product_sym
product.sym: The product description as seen by users.chg.product = product.id
type_of_contact_sym
toc.sym: The Type Of Contact description as seen by users.chg.type_of_contact = toc.id
rpting_method_sym
repmeth.sym: The Reporting method description as seen by users.chg.reporting_method = repmeth.id
person_contacting_sym
perscon.sym: The Person Contacting description as seen by users.chg.person_contacting = perscon.id
 
View_Change_to_Assets
The following list of fields is a basic view of change orders and their assets. The change request table (chg) is indirectly joined with the network resource table (ca_owned_resource) to get a list of each change order’s assets. This view may not list all change orders, particularly those that have no assets.
Field
Remarks
View_Change.*
All fields listed in the View_Change view defined earlier in this document.
assetID
ca_owned_resource.own_resource_uuid: The binary field which serves as the internal, unchanging unique identifier for an asset record.
asset_serial_num
ca_owned_resource.serial_number: The serial number for an asset record.
asset_class
ca_resource_class.name: A short description of the class to which an asset belongs.ca_owned_resource.resource_class = ca_resource_class.id
asset_family
ca_resource_family.name: The family of assets to which this asset belongs.ca_owned_resource.resource_class = ca_resource_class.id AND ca_resource_class.family_id = ca_resource_family.id
asset_name
ca_owned_resource.resource_name: The network name by which this asset is known.
 
View_Change_to_Change_Act_Log
The following is a basic view of all change orders and the activity logs that go with them. This view joins the View_Change view with the Change Order Activity Log (chgalg) to give detailed information about change orders and their activity logs.
Field
Remarks
View_Change.*
This shows all fields listed in the View_Change view defined earlier in this document.
chgalg_id
chgalg.id: The unique identifier for this record in the chgalg table.
chgalg_persid
chgalg.persid: The unique identifier for this record in the chgalg table, preceded by the object identifier (chgalg for chgalg) and a colon.
change_id
chgalg.change_id: This is a pointer to change the order id to which this activity belongs.chgalg.change_id = chgalg.id
chgalg_last_mod_dt
chgalg.last_mod_dt: The last modify date/time (pdmtime).
time_spent
chgalg.time_spent: The duration of time spent on this activity, stored as the total number of seconds. For example, 80 = 1 minute, 20 seconds.
time_stamp
chgalg.time_stamp: The user modifiable date/time of activity (pdmtime).
system_time
chgalg.system_time: The date/time of record creation (pdmtime).
analyst
chgalg.analyst: The uuid pointer to contact uuid to get the analyst who performed the activity.chgalg.analyst = ca_contact.contact_uuid
chgalg_description
chgalg.description: The text description of this activity, which can be modified by the user.
action_desc
chgalg.action_desc: The text description of automated action, which cannot be modified by the user.
type
chgalg.type: The text pointer to a record in the activity type table.chgalg.type = act_type.code
internal
chgalg.internal: The integer flag (1 or 0), which indicates if this log entry is intended for all to see or just for internal use.
knowledge_session
chgalg.knowledge_session: This is an identifier for a particular session of a particular user.
knowledge_tool
chgalg.knowledge_tool: This is an indicator of the knowledge management tool used for the search, such as NLS_FAQ or EXPERT, and so on.
chgalg_analyst_id
chgalg.analyst: This is the uuid pointer to contact uuid to get the analyst who performed the activity.chgalg.analyst = ca_contact.contact_uuid
 
View_Change_to_Change_WF
This view is a result of the View_Change view joined with the Workflow task table (wf) to give a basic view of change orders and their workflow tasks. This may not list all change orders, particularly when there are no workflow tasks assigned.
Field
Remarks
View_Change.*
This shows all fields listed in the View_Change view defined earlier in this document.
wf_id
wf.id: The unique identifier for a record in the wf table.
wf_persid
wf.persid: This is a unique identifier for this record in the wf table, preceded by the object identifier (wf for wf) and a colon.
del
wf.del: This is a boolean indicator. It specifies whether this record is to be displayed to the user.
object_type
wf.object_type: This is the factory name, which is used to identify the type of record (for example, chg) to which this workflow task is attached.
object_id
wf.object_id: This is the unique identifier used to identify the specific record to which this workflow task is attached.wf.object_id = chg.id
task
wf.task: This is an identifier, which references the type of task this record represents.wf.task = tskty.code
wf_template
wf.wf_template: This is an identifier, which references from which template this workflow task record was created.wf.wf_template = wftpl.id
sequence
wf.sequence: This is an integer, which indicates the order this particular workflow task record should be displayed and executed by CA SDM (for example, Ascending).
wf_status
wf.status: This is an identifier, which references a tskstat record that indicates the current status of this workflow task.wf.status = tskstat.code
group_task
wf.group_task: This is a Boolean, which indicates whether this task belongs to a group.
asset
wf.asset: This is a UUID (binary) identifier, which references a record in the ca_owned_resource table.wf.asset = ca_owned_resource.own_resource_uuid
creator
wf.creator: This is a UUID (binary) identifier, which references a record in the ca_contact table. It indicates the person who created this workflow task.wf.creator = ca_contact.contact_uuid
date_created
wf.date_created: This is the Date/timestampe this workflow task was created (pdmtime).
wf_assignee
wf.assignee: This is the UUID (binary) identifier, which references a record in the ca_contact table. It indicates the person who is currently assigned to this workflow task.wf.assignee = ca_contact.contact_uuid
done_by
wf.done_by: This is the UUID (binary) identifier, which references a record in the ca_contact table. It indicates the person who completed or approved this workflow task.wf.done_by = ca_contact.contact_uuid
wf_start_date
wf_start_date: This is the timestamp when the workflow task moved into an active status (pdmtime).
wf_est_comp_date
wf.est_comp_date: This is the timestamp (pdmtime) when users believe this task will be completed.
est_duration
wf.est_duration: This is the estimated duration for this workflow task.
completion_date
wf.completion_dat: This is the timestamp (pdmtime) when this workflow task was completed.
actual_duration
wf.actual_duration: This is the actual amount of time it took to complete this workflow task.
wf_est_cost
wf.est_cost: This is the estimated cost of this workflow task.
cost
wf.cost: This is the actual cost required to complete this workflow task.
wf_description
wf.description: This is the description of the workflow task.
wf_last_mod_dt
wf.last_mod_dt: This is the timestamp (pdmtime) when this workflow task was last changed.
wf_last_mod_by
wf.last_mod_by: This is the UUID (binary) unique identifier referencing a record in the contact table, which indicates the last person to make changes to this workflow task.wf.last_mod_by = ca_contact.contact_uuid
 
View_Change_to_Properties
This view is a result of the View_Change view joined with the Properties table (prp) to give a basic view of change orders and their assigned properties. This may not list all change orders, particularly when there are no properties assigned.
Field
Remarks
View_Change.*
This shows all fields listed in the View_Change view defined earlier in this document.
prp_id
prp.id: This is an integer unique identifier for the property record.
prp_persid
prp.persid: This is a unique identifier for this record in the wf table, preceded by the object identifier (prp for prp) and a colon.
object_type
prp.object_type: This is the factory name, which is used to identify the type of record (for example, chg) to which this property record is attached.
object_id
prp.object_id: This is the unique identifier used to identify the specific record to which this property is attached.prp.object_id = chg.id
sequence
prp.sequence: This is an integer that indicates the order for which this particular property record should be displayed by CA SDM (for example, Ascending).
property
prp.property: This is an identifier, which references a record in the prptpl table. It represents the template from which this property was created.prp.property=prptpl.code
value
prp.value: This is the value entered by the user in response to the prp_description and prp.label fields.
prp_last_mod_dt
prp.last_mod_dt: This is the timestamp (pdmtime) when this property was last modified.
prp_last_mod_by
prp.last_mod_by: This is a binary identifier, which references a record in the ca_contact table. It represents the person who last modified this record.prp.last_mod_by = ca_contact.contact_uuid
required
prp.required: This is a Boolean indicating whether this property must have a prp.value before the record is saved.
sample
prp.sample: This is a text field, which displays example values to guide the user in typing the most useful value in prp.value.
prp_description
prp.description: This is a text field, which explains what kind of value should be entered in prp.value.
label
prp.label: This is a short description of what should be placed in the prp.value field.
 
View_Change_to_Request
The following is a basic view of change orders that have assigned requests only. This view is a result of the View_Change view joined with the request table (call_req) to give details about the change order and its associated request.
Field
Remarks
View_Change.*
This shows all fields listed in the View_Change view defined earlier in this document.
cr_id
call_req.id: This is the unique identifier for this record in the call_req table.
ref_num
call_req.ref_num: This is the Request reference number, which is used by analysts and customers to refer to a particular Request.
cr_summary
call_req.summary: This is a brief description of the request for quick reference.
cr_persid
call_req.persid: This is a unique identifier for this record in the call_req table, preceded by the object identifier (cr for table call_req) and a colon.
cr_description
call_req.description: This is the long description of a request, as dictated by an analyst or customer.
cr_status
call_req.status: This is a unique identifier referencing a record in the cr_stat table. It indicates the status of this request:call_req.status = cr_stat.code
cr_active_flag
call_req.active_flag: This is the Integer flag used to determine whether this request record is active (1 or 0).
time_spent_sum
call_req.time_spent_sum: This is the derived total of all act_log records' time_spent fields, stored in seconds (i.e. 80 = 1 minute 20 seconds).
cr_open_date
call_req.open_date: This is the Request creation timestamp (pdmtime).
cr_last_mod_dt
call_req.last_mod_dt: This is the last modified timestamp (pdmtime).
cr_close_date
call_req.close_date: This is the Timstamp for when the request was set to inactive (pdmtime).
cr_log_agent
call_req.log_agent: This is a binary unique identifier referencing the ca_contact table. It references the person who was the request's original creator.call_req.log_agent = ca_contact.contact_uuid
cr_group_id
call_req.group_id: This is a binary unique identifier referencing a record in the ca_contact table. It represents the group currently assigned to the request.call_req.group_id = ca_contact.contact_uuid
cr_assignee
call_req.assignee: This is a binary unique identifier referencing a record in the ca_contact table. It represents the person currently assigned to the request.call_req.assignee = ca_contact.contact_uuid
customer
call_req.customer: This is a binary unique identifier referencing a record in the ca_contact table. It represents the affected end user for this request.call_req.customer = ca_contact.contact_uuid
charge_back_id
charge_back_id: This is a text field available for use as an indicator of accounting jargon for expensing this request to the appropriate cost center.
affected_rc
call_req.affected_rc: This is a binary unique identifier referencing a row in the ca_owned_resource table. It represents the asset to which this request applies.call_req.affected_rc = ca_owned_resource.own_resource_uuid.
cr_support_lev
call_req.support_lev: This is a pointer to a service desc record, which automates some constraints under which this request must be completed.call_req.support_lev = srv_desc.code
cr_category
call_req.category: This is a unique identifier referencing a record in the prob_ctg table,. It represents the category to which this request belongs.call_req.category = prob_ctg.persid
solution
call_req.solution: This is a pointer to call solution to get solution.call_req.solution = crsol.persid
cr_impact
call_req.impact: This is an integer unique identifier referencing a row in the impact table. It indicates the scope this request is affecting.call_req.impact = impact.enum
cr_priority
call_req.priority: This is an integer unique identifier referencing a record in the pri table. It indicates how analysts will prioritize the work associated with this request.call_req.priority = pri.enum
urgency
call_req.urgency: This is an integer unique identifier referencing a row in the urgncy table. It documents the user's feeling of urgency for having this request resolved.call_req.urgency = urgncy.enum
severity
call_req.severity: This is an integer unique identifier referencing a row in the severity table. It indicates the severity of the consequences of this unresolved request.call_req.severity = sevrty.enum
extern_ref
This specifies an associated ticket.
last_act_id
This is the id of the last activity.
cr_tticket
This is a pointer to a trouble ticket to get the associated ticket.
cr_parent
call_req.parent: This is a persid pointer to another request persid, which facilitates creation of a hierarchy of change orders.call_req.parent = call_req.persid
cr_template_name
call_req.template_name: This is a text value, which indicates this request is designated for and can be chosen from a list as a template for other similar requests.cr_template.template = call_req.persid
cr_sla_violation
call_req.sla_violation: This is an integer, which counts number of times slas attached to this request have been violated.
cr_predicted_sla_viol
call_req.predicted_sla_viol: (r5.5) Neugent related technology field.
cr_created_via
call_req.created_via: This is an integer pointer to a record in the interface table. It indicates from which interface the change order originated.call_req.created_via = interface.id
cr_call_back_date
call_req.call_back_date: This is a timestamp field (pdmtime), which indicates a future date/time the affected_end_user is to be contacted.
cr_call_back_flag
call_req.call_back_flag: This is a Boolean indicator displayed as a checkbox to the user, indicating whether to notify the analyst at the call_req.call_back_date.
event_token
call_req.event_token: This is used by CA NSM for message matching.
type
call_req.type: This is a text field referencing a record in the crt table. It indicates the ITIL type of this request.call_req.type = crt.code
cr_string1
This is a user-definable string.
cr_string2
This is a user-definable string.
cr_string3
This is a user-definable string.
cr_string4
This is a user-definable string.
cr_string5
This is a user-definable string.
cr_string6
This is a user-definable string.
change
call_req.change: This is an integer unique identifier, referencing a row in the chg table. It indicates the change order that was created as a result of this request.call_req.change = chg.id.
 
View_Contact_Full
The following of fields is a basic view of all contacts. This view lists all fields in the ca_contact table, plus referenced fields such as short descriptions for contact type, location name, organization names, and service type for each contact. This view has already been joined with the ca_location, ca_organization, srv_desc, and ca_contact_type tables to get the actual names and symbols for some of the fields in the ca_contact table. The actual names and symbols are located at the end of this view’s field list.
Field
Remark
contact_uuid
ca_contact.contact_uuid: A binary-unique identifier for each ca_contact record.
middle_name
ca_contact. middle_name: The middle name of this contact.
alias
ca_contact.alias: The alternate, often informal name for this contact.
last_name
ca_contact.last_name: This contact's surname.
first_name
ca_contact.first_name: This contact's formal first name.
pri_phone_number
ca_contact.pri_phone_number: The contact's primary phone number.
alt_phone_number
ca_contact.alt_phone_number: The contact's alternate phone number.
fax_number
ca_contact.fax_number: The contact's facsimile number.
mobile_phone
ca_contact.mobile_phone: The contact's mobile phone number.
pager_number
ca_contact.pager_number: The number for issuing a page to the contact's page.
email_address
ca_contact.email_address: The contact's email address.
location_uuid
ca_contact.location_uuid: A binary-unique identifier referencing a record in the ca_location table, which indicates the contact's static location.ca_contact.location_uuid = ca_location.location_uuid
floor_location
ca_contact.floor_location: A contact's floor number.
pager_email_address
ca_contact.pager_email_address: A contact's email address for their pager.
room_location
ca_contact.room_location: The contact's specific room on the floor at the static location.
contact_type
ca_contact.contact_type: An unique integer-identifier, referring to a row in the ca_contact_type table, which indicates the general function of this contact within the service desk application.ca_contact.contact_type = ca_contact_type.id
inactive
ca_contact.inactive: A boolean indicator of the state of this record, determining its inclusion or exclusion from standard searches within service desk.
creation_user
ca_contact.creation_user: The userid of the contact who created this record.ca_contact.creation_user = ca_contact.userid
creation_date
ca_contact.creation_date: A timestamp (pdmtime), indicating the date and time this contact was created.
last_update_user
ca_contact.last_update_user: The userid of the contact who last updated this contact record.ca_contact.last_update_user = ca_contact.userid
last_update_date
ca_contact.last_update_date: A timestamp (pdmtime), indicating the date and time this record was last modified.
version_number
ca_contact.version number: The internal version indicator.
department
ca_contact.department: An integer-unique identifier, referencing a row in the ca_resource_department table, that indicates the contact's department.ca_contact.department = ca_resource_department.id
comment
ca_contact.comment: A freeform text comment field for analysts to document important facts that influence the handling of this particular contact.
company_uuid
ca_contact.company_uuid: A binary-unique identifier, which references a row in the ca_company table. It indicates this contact's affiliation with a company.ca_contact.company_uuid = ca_company.company_uuid
organization_uuid
ca_contact.organizaiton_uuid: A binary-unique identifier which references a row in the ca_organization table. It indicates this contact's working organization.ca_contact.organizaiton_uuid = ca_organization.organization_uuid
admin_organization_uuid
ca_contact.admin_organization_uuid: A binary-unique identifier, which references a row in the ca_organization table. It indicates this contact's administrative organization.ca_contact.admin_organization_uuid = ca_organization.organization_uuid
alternate_identifier
ca_contact.alternate_identifier: A user-defined identifier, usually an entity used by human resources to uniquely identify this contact.
job_title
ca_contact.job_title: An integer-unique identifier, which references the ca_job_title table. It indicates the standardized job title for this contact.ca_contact.job_title = ca_job_title.id
job_function
ca_contact.job_function: An integer-unique identifier, which references the ca_job_function table. It indicates a standardized general description of the contact's job function.ca_contact.job_function = ca_job_function.id
mail_stop
ca_contact.mail_stop: Mail Stop.
cost_center
ca_contact.cost_center: An integer-unique identifier, which references the ca_resource_cost_center table. It indicates this contact's primary cost center.ca_contact.cost_center = ca_cost_center.id
userid
ca_contact.userid: The user identifier this contact will use for logging into service desk.
supervisor_contact_uuid
ca_contact.supervisor_contact_uuid: A binary-unique identifier, referencing a row in the ca_contact table, that creates a hierarchy of contacts to indicate the reporting structure of each contact.ca_contact.supervisor_contact_uuid = ca_contact.contact_uuid
exclude_registration
ca_contact.exclude registration: An internal flag.
delete_time
ca_contact.delete_time: A timestamp indicating when the inactive flag was set to 1.
contact_type_name
ca_contact_type.name: A short description of this contact's ca_contact.contact_type.
location_name
ca_location.name: A short description of this contact's static location.
organization
ca_organization.org_name: A short description of this contact's ca_contact.organizaiton_uuid.
admin_organization
ca_organization.org_name: A short description of this contact's organization name.ca_contact.admin_organization_uuid
service_type
srv_desc.sym: A short description of this contact's usp_contact.c_service_type.ca_contact.contact_uuid = usp_contact.contact_uuid AND usp_contact.c_service_type = srv_desc.code
state_sym
ca_location.state: An integer-unique identifier, referencing a row in the ca_state_provice table, that indicates the State, Province, or other artificially defined geographic region.ca_contact.location_uuid = ca_location.location_uuid AND ca_location.state = ca_state_province.id
 
View_Contact_to_Environment
The following list of fields is a basic view of contacts and their environment (assets). This view is a view of the contact table (ca_contact), but is also joined with the owned resource table (ca_owned_resource) to get a list of all assets associated with a contact. This view may be joined with the View_Contact_Full view to get the contact type, service type, organizations and location of each contact. Or, this view may be joined with the individual tables to get that same information.
Field
Remarks
ca_contact.*
The ca_contact fields that are defined in the View_Contact_Full view definition.
asset_uuid
ca_owned_resource.own_resource_uuid: A binary-unique identifier for an asset in the ca_owned_resource table.
asset_name
ca_owned_resource.resource_name: The designated network name of this asset.
 
View_Group
The following list of fields is a basic view of the contact table, but lists only group contacts. Contact type id = 2308, which is for group types. You may want to join this view with other CA SDM tables to get more meaningful data for reporting. For example, you can join it with the Location (ca_location) table to find the name and address for the group’s location. You can also join this view with the Organization (ca_organization) table to get the functional and administrative organization names for the group.
Field
Remarks
ca_contact.*
The ca_contact fields that are defined in the View_Contact_Full view definition.
The following example shows how joining tables works, and how reporting fields are extracted. The field from one table (on the right) is joined (->) with a field from another table (on the left). To join properly between tables and views, you need to understand the differences in joins for the database. The field defined in the parentheses, as follows, is what you may want to use in your reports if the previous tables are joined with the View_Group view:
  • View_Group.contact_type -> ca_contact_type.id (ca_contact_type.sym)
  • View_Group.location_uuid -> ca_location.location_uuid (ca_location.location_name)
  • View_Group.organization_uuid -> ca_organization.organization_uuid (ca_organization.org_name)
  • View_Group.admin_organization_uuid -> ca_organization(2).organization_uuid (ca_organization(2). org_name)
View_Group_to_Contact
The following list of fields is a basic view of all group contacts (members). It also includes managers. Here, View_Group is joined with the Group_Member table, and then joined with the ca_contact table. All fields in View_Group are listed, as well as the first, middle and last name from the ca_contact table. The Group_Member manager flag is also listed. The group member manager flag is 1 or 0, which means that the member is either (yes - 1) a manager, or (no - 0) not a manager. Most of the information in this view pertains to the group itself, not the actual members. This view is used to find information on a particular group, including the names of its members.
Field
Remarks
View_Group.*
The View_Group fields that are defined in the View_Group definition.
member_lastname
ca_contact.last_name: The surname of the group member.
member_firstname
ca_contact.first_name: The formal first name of the group member.
member_middlename
ca_contact.middle_name: The middle name of the group member.
grpmem_manager_flag
ca_contact.manager_flag: The Group Member Manager (1 or 0) indicator.
 
View_Issue
The following is a basic view of all issues, listing the status, priority, category, organizations, the requester’s full name, the assignee’s full name, the group name and ID, and so on. Here, the issue table is joined with many other tables to give some more meaningful data about the issue.
Field
Remarks
id
issue.id: The unique identifier for this record in the issue table.
persid
issue.persid: The unique identifier for this record in the issue table, preceded by the object identifier (iss for table issue) and a colon.
issue_ref_num
issue.iss_ref_num: The Issue reference number, which is used by analysts and customers to refer to a particular issue.
description
issue.description: The long description of an issue as dictated by an analyst or customer.
status
issue.status: The unique identifier of an issue status, which is a pointer to the issstat table.issue.status = issstat.code
active_flag
issue.active_flag: The integer flag used to determine whether this issue is active (1 or 0).
start_date
issue.start_date: The date the first task goes to a pending status (pdmtime).
open_date
issue.open_date: The issue creation date (pdmtime).
last_mod_dt
issue.last_mod_dt: The last modified date (pdmtime).
last_mod_by
issue.last_mod_by: The pointer to the contact uuid, which indicates the last contact to modify this issue.issue.last_mod_by = ca_contact.contact_uuid
close_date
issue.close_date: The date the issue was set to inactive (pdmtime).
resolve_date
issue.resolve_date: The date the issue was set to a status configured to indicate the issue was resolved (pdmtime).
rootcause
issue.rootcause: A pointer to a record in the rootcause table, which represents the original situation that required this issue to be logged.issue.rootcause = rootcause.id
est_total_time
issue.est_total_time: The estimated total time (pdmtime) it will take to complete this issue.
actual_total_time
issue.actual_total_time actual: The total time (pdmtime) it took to complete this issue.
log_agent
issue.log_agent: A binary-unique identifier, this references the ca_contact table, which in turn references the person who was the issue's original creator.issue.log_agent = ca_contact.contact_uuid
assignee
issue.assignee: A pointer to the contact uuid who is currently assigned to the change order.issue.assignee = ca_contact.contact_uuid
organization
issue.organization: A pointer to the internal organization uuid, which represents the organization to whom this issue belongs.issue.organization = ca_organization.organization_uuid
group_id
issue.group_id: A pointer to the contact uuid, which represents the group currently assigned to the issue.issue.group_id = ca_contact.contact_uuid
affected_contact
issue.affected_contact: A pointer to the contact uuid, which represents the affected contact for this issue.issue.affected_contact = ca_contact.contact_uuid
requestor
issue.requrestor: A pointer to the contact uuid, which represents the person who asked this issue to be logged.issue.requestor = ca_contact.contact_uuid
category
issue.category: A pointer to the issue category code to reference the category into which this issue falls.issue.category = isscat.code
priority
issue.priority: A pointer to priority enum, which represents the priority into which this issue falls.issue.priority = pri.enum
need_by
issue.need_by: The date, which indicates when the affected_end_user needs to have the issue completed (pdmtime).
est_comp_date
issue.est_comp_date: The estimated completion date (pdmtime) for this Issue.
actual_comp_date
issue.actual_comp_date: The actual completion date (pdmtime) of this issue.
est_cost
issue.est_cost: The estimated cost of this issue.
actual_cost
issue.actual_cost: The actual cost to implement this issue.
justification
issue.justification: A text field, which allows a requester to document the reason(s) this issue is required.
backout_plan
issue.backout_plan: A text field that allows an analyst to document a backout plan for this issue.
impact
issue.impact: A pointer to an impact table record, which indicates the scope of resources that this issue affects.issue.impact = impact.enum
parent
issue.parent: A pointer to another issue id, which allows creation of a hierarchy of issues.issue.parent = issue.id
effort
issue.effort: A text field which explains the plan for implementing this issue.
support_lev
issue.support_lev: A pointer to a service desc record, which automates some constraints under which this issue must be completed.issue.support_lev = srv_desc.code
template_name
issue.template_name: The name of and pointer to an issue template.issue.template_name = iss_template.template_name
sla_violation
issue.sla_violation: The integer to count the number of times slas attached to this issue have been violated.
predicted_sla_viol
issue.predicted_sla_viol: (r5.5) Neugent related technology field.
macro_predict_viol
issue.macro_predict_viol: (r5.5) Neugent related technology field.
created_via
issue.created_via: A pointer to a record in the interface table. This indicates from which interface the issue originated.issue.created_via = interface.id
call_back_date
issue.call_back_date: A date/time field (pdmtime), which indicates a future date/time the requester is to be contacted.
call_back_flag
issue.call_back_flag: A boolean indicator displayed as a checkbox to the user, to indicate whether to notify the analyst at the issue.call_back_date.
string1
This is a user-definable text field.
string2
This is a user-definable text field.
string3
This is a user-definable text field.
string4
This is a user-definable text field.
string5
This is a user-definable text field.
string6
This is a user-definable text field.
service_date
issue.service_date: The Date/ Time (pdmtime) that an outside vendor is expected to service this issue.
service_num
issue.service_num: The text field to document an outside vendor's service or purchase order number.
product
issue.product: A pointer to a record in the product table, which indicates the product that is affected by this issue.issue.product = product.id
actions
issue.actions: A big text field for documenting actions.
type_of_contact
issue.type_of_contact: A pointer to a record in the toc table, which indicates a general categorization of the affected_end_user's perspective of the issue.issue.type_of_contact = toc.id
reporting_method
issue.reporting_method: A pointer to a record in the repmeth table, which classifies the origination of the issue, and is selected by the person creating the issue.issue.reporting_method = repmeth.id
person_contacting
issue.person_contacting: A pointer to a record in the perscon table, which indicates the role of the affected_end_user or requester.issue.person_contacting = perscon.id
status_name
issstat.sym: The description of the status as seen by a user.issue.status = issstat.code
priority_num
pri.sym: The description of the priority as seen by a user.issue.priority = pri.enum
category_name
isscat.sym: The name of the issue category as viewed by a user.issue.category = isscat.code
organization_name
ca_organization.org_name: The name of an organization as viewed by a user.issue.organization = ca_organization.organization_uuid
affected_end_user_lastname
ca_contact.last_name: The affected End User's last name.issue.affected_end_user = ca_contact.contact_uuid
affected_end_user_firstname
ca_contact.first_name: The affected End User's first name.issue.affected_end_user = ca_contact.contact_uuid
affected_end_user_middlename
ca_contact.middle_name: The affected End User's middle name.issue.affected_end_user = ca_contact.contact_uuid
assignee_lastname
ca_contact.last_name: The assignee's last name.issue.assignee = ca_contact.contact_uuid
assignee_firstname
ca_contact.first_name: The assignee's first name.issue.assignee = ca_contact.contact_uuid
assignee_middlename
ca_contact.middle_name: The assignee's middle name.issue.assignee = ca_contact.contact_uuid
groupID
View_Group.contact_uuid: A binary representation of the internal id used for the group assigned to this issue.issue.group_id = ca_contact.contact_uuid
group_name
View_Group.last_name: The name of the group assigned to this issue.issue.group = ca_contact.contact_uuid
service_type
srv_desc.sym: The name of the service type applied to this issue.issue.support_lev = srv_desc.code
impact_num
impact.sym: The description of the impact as seen by users.issue.impact = impact.enum
product_sym
product.sym: The product description as seen by users.issue.product = product.id
type_of_contact_sym
toc.sym: The Type Of Contact description as seen by users.issue.type_of_contact = toc.id
rpting_method_sym
repmeth.sym: The Reporting method description as seen by users.issue.reporting_method = repmeth.id
person_contacting_sym
perscon.sym: The Person Contacting description as seen by users.issue.person_contacting = perscon.id
created_via_sym
interface.sym: issue.created_via = interface.id.
rootcause_sym
rootcause.sym: issue.rootcause = rootcause.id.
 
View_Issue_Act_Log
The following is a basic view of all issue activity logs. This is a view of the issue activity log table (issalg) joined with the activity type table (act_type) and the contact table (ca_contact) to give more meaningful data, such as the actual activity type and full name of the analyst who performed the activity.
Field
Remarks
id
issalg.id: The unique identifier for this record in the issalg table.
persid
issalg.persid: The unique identifier for this record in the issalg table, preceded by the object identifier (issalg for issalg) and a colon.
issue_id
issalg.issue_id: The pointer to issue id to which this activity belongs.issalg.issue_id = issalg.id
last_mod_dt
issalg.last_mod_dt: The last modify date/time (pdmtime).
time_spent
issalg.time_spent: The duration of time spent on this activity, stored as the total number of seconds. For example, 80 = 1 minute, 20 seconds.
time_stamp
issalg.time_stamp: The user modifiable date/time of activity (pdmtime).
system_time
issalg.system_time: The date/time of record creation (pdmtime).
analyst
issalg.analyst: A binary-unique identifier referring to the contact uuid to get the analyst who performed the activity.issalg.analyst = ca_contact.contact_uuid
description
issalg.description: The text description of this activity, which can be modified by the user.
action_desc
issalg.action_desc: The text description of the automated action, which cannot be modified by the user.
type
issalg.type: The text pointer to a record in the activity type table.issalg.type = act_type.code
internal
issalg.internal: The integer flag (1 or 0), which indicates if this log entry is intended for all to see or just for internal use.
knowledge_session
issalg.knowledge_session: An identifier for a particular session of a particular user.
knowledge_tool
issalg.knowledge_tool: An indicator of the knowledge management tool used for the search, such as NLS_FAQ or EXPERT, and so on.
analyst_lastname
View_Contact_Full.last_name: The Analyst's last name, derived from issalg.analyst = ca_contact.contact_uuid.
analyst_firstname
View_Contact_Full.first_name: The analyst's first name.
analyst_middlename
View_Contact_Full.middle_name: The middle name of the analyst.
activity_type
act_type.sym: The activity type referenced by issalg.type = act_type.code.
 
View_Issue_to_Assets
The following list of fields is a basic view of issues and their assets. The issue table (issue) is indirectly joined with the owned resource table (ca_owned_resource), and other asset-related tables, to get a list of each issue’s assets. This may not list all issues, particularly those that have no assets.
Field
Remarks
View_Issue.*
The View_Issue view which defines all fields listed in the View_Issue view.
assetID
ca_owned_resource.own_resource_uuid: The binary field which serves as the internal, unchanging unique identifier for an asset record.
asset_serial_num
ca_owned_resource.serial_number: The serial number for an asset record.
asset_class
ca_resource_class.name: A short description of the class to which an asset belongs.
ca_owned_resource.resource_class = ca_resource_class.id
asset_family
ca_resource_family.name: The family of assets to which this asset belongs.
ca_owned_resource.resource_class = ca_resource_class.id AND ca_resource_class.family_id = ca_resource_family.id
asset_name
ca_owned_resource.resource_name: The network name by which this asset is known.
 
View_Issue_to_Issue_Act_Log
The following is a basic view of all issues and the activity logs that go with them. This view joins the View_Issue view with the View_Issue_Act_Log view to give detailed information about issues and their activity logs. Actual data is at the end of the fields list.
Field
Remarks
View_Issue.*
Please refer to the View_Issue view defined earlier in this document.
issalg_id
issalg.id: The unique identifier for this record in the issalg table.
issalg_persid
issalg.persid: The unique identifier for this record in the issalg table, preceded by the object identifier (issalg for issalg) and a colon.
issue_id
issalg.issue_id: The pointer to issue id to which this activity belongs.issalg.issue_id = issalg.id
issalg_last_mod_dt
issalg.last_mod_dt: The last modify date/time (pdmtime).
time_spent
issalg.time_spent: The duration of time spent on this activity, stored as the total number of seconds. For example, 80 = 1 minute, 20 seconds.
time_stamp
issalg.time_stamp: The user modifiable date/time of activity (pdmtime).
system_time
issalg.system_time: The date/time of record creation (pdmtime).
analyst
issalg.analyst: The unique binary pointer to the contact uuid to get the analyst who performed the activity.issalg.analyst = ca_contact.contact_uuid
issalg_description
issalg.description: The text description of this activity, which can be modified by the user.
action_desc
issalg.action_desc: The text description of the automated action, which cannot be modified by the user.
type
issalg.type: The text pointer to a record in the activity type table.issalg.type = act_type.code
internal
issalg.internal: The integer flag (1 or 0), which indicates if this log entry is intended for all to see or just for internal use.
knowledge_session
issalg.knowledge_session: An identifier for a particular session of a particular user.
knowledge_tool
issalg.knowledge_tool: An indicator of the knowledge management tool used for the search, such as NLS_FAQ or EXPERT, and so on.
issalg_analyst_id
issalg.analyst: The unique binary pointer to the contact uuid to get the analyst who performed the activity.issalg.analyst = ca_contact.contact_uuid
 
View_Issue_to_Issue_WF
This view is a result of the View_Issue view joined with the workflow task table (isswf) to give a basic view of issues and their workflow tasks. This may not list all issues, particularly if there are no workflow tasks assigned to them.
Field
Remarks
View_Issue.*
Please refer to the View_Issue definition earlier in this document for a description of each field.
wf_id
isswf.id: This is a unique identifier for a record in the isswf table.
wf_persid
isswf.persid: This is a unique identifier for this record in the isswf table, preceded by the object identifier (isswf) and a colon.
del
isswf.del: This is a boolean indicator of whether this record is to be displayed to the user.
object_type
isswf.object_type: This is the factory name, which is used to identify the type of record (for example, iss) to which this workflow task is attached.
object_id
isswf.object_id: This is a unique identifier used to identify the specific record to which this workflow task is attached.isswf.object_id = issue.id
task
isswf.task: This is an identifier, which references the type of task this record represents.isswf.task = tskty.code
wf_template
isswf.wf_template: This is an identifier, which references from which template this workflow task record was created.isswf.wf_template = wftpl.id
sequence
isswf.sequence: This is an integer that indicates the order for which this particular workflow task record should be displayed and executed by CA SDM (for example, Ascending).
wf_status
isswf.status: This is an identifier, which references a tskstat record. It indicates the current status of this workflow task.isswf.status = tskstat.code
group_task
isswf.group_task: This is a boolean, which indicates whether this task belongs to a group.
asset
isswf.asset: This is a unique binary identifier, which references a record in the ca_owned_resource table.isswf.asset = ca_owned_resource.own_resource_uuid
creator
isswf.creator: This is a unique binary identifier, which references a record in the ca_contact table. It indicates the person who created this workflow task.isswf.creator = ca_contact.contact_uuid
date_created
isswf.date_created: This is the date/timestamp that this workflow task was created (pdmtime).
wf_assignee
isswf.assignee: This is a unique binary identifier, which references a record in the ca_contact table. It indicates the person who is currently assigned to this workflow task.isswf.assignee = ca_contact.contact_uuid
done_by
isswf.done_by: This is a unique binary identifier, which references a record in the ca_contact table. It indicates the person who completed or approved this workflow task.isswf.done_by = ca_contact.contact_uuid
wf_start_date
wf_start_date: This is the timestamp when the workflow task moved into an active status (pdmtime).
wf_est_comp_date
isswf.est_comp_date: This is a timestamp (pdmtime) indicating when users believe this task will be completed.
est_duration
isswf.est_duration: This is the estimated duration for this workflow task.
completion_date
isswf.completion_date: This is a timestamp (pdmtime) indicating when this workflow task was completed.
actual_duration
isswf.actual_duration: This is the actual amount of time it took to complete this workflow task.
wf_est_cost
isswf.est_cost: This is the estimated cost of this workflow task
cost
isswf.cost: This is the actual cost required to complete this workflow task.
wf_description
isswf.description: This is a description of the workflow task.
wf_last_mod_dt
isswf.last_mod_dt: This is the timestamp (pdmtime) indicating when this workflow task was last changed.
wf_last_mod_by
isswf.last_mod_by: This is the unique binary identifier, which references a record in the contact table. It indicates the last person to make changes to this workflow task.isswf.last_mod_by = ca_contact.contact_uuid
 
View_Issue_to_Properties
This view is a result of the View_Issue view joined with the issue properties table (issprp) to give a basic view of issues and their assigned properties. This may not list all issues, particularly if there are no properties assigned to them.
Field
Remarks
View_Issue.*
Please refer to the View_Issue definition earlier in this document, for a description of each field.
prp_id
issprp.id: This is an integer-unique identifier for the property record.
prp_persid
issprp.persid: This is a unique identifier for this record in the prp table, preceded by the object identifier (prp) and a colon.
sequence
issprp.sequence: This is an integer that indicates the order for which this particular property record should be displayed by CA SDM (for example, Ascending).
label
issprp.label: This is a short description of what should be placed in the issprp.value field.
value
issprp.value: This is a value entered by the user in response to the prp_description and issprp.label fields.
prp_last_mod_dt
issprp.last_mod_dt: This is the timestamp (pdmtime) indicating when this property was last modified.
prp_last_mod_by
issprp.last_mod_by: This is a binary identifier, which references a record in the ca_contact table. It represents the person who last modified this record.issprp.last_mod_by = ca_contact.contact_uuid
required
issprp.required: This is a boolean, indicating whether this property must have a issprp.value before the record is saved.
sample
issprp.sample: This is a text field, which displays example values to guide the user in entering the most useful value in issprp.value.
owning_iss
issprp.owning_iss: This is a unique identifier used to identify the specific record to which this property is attached.issprp.object_id = issue.persid
prp_description
issprp.description: This is a text field, which explains the type of value that should be entered in issprp.value.
 
View_Request
The following is a basic view of all requests. Here, the Request table has been joined with other CA SDM tables to give you more specific information, such as the request service type, severity, urgency, category, and priority. There is some additional information about the request listed, as well. All fields from the Request (call_req) table are selected. The extracted fields that are a result of the joined tables are listed at the end of this fields list.
Field
Remarks
id
call_req.id: This is the unique identifier for this record in the call_req table.
persid
call_req.persid: This is a unique identifier for this record in the call_req table, preceded by the object identifier (cr for table call_req) and a colon.
ref_num
call_req.ref_num: This is a Request reference number, which is used by analysts and customers to refer to a particular Request.
summary
call_req.summary: This is a brief description of the request for quick reference.
description
call_req.description: This is the long description of a request, as dictated by an analyst or customer.
status
call_req.status: This is a unique identifier referencing a record in the cr_stat table. It indicates the status of this request. call_req.status = cr_stat.code
active_flag
call_req.active_flag: This is an integer flag to determine whether this request record is active (1 or 0).
open_date
call_req.open_date: This is the Request creation timestamp (pdmtime).
time_spent_sum
call_req.time_spent_sum: This is the derived total of all of the act_log records' time_spent fields, stored in seconds (i.e. 80 = 1 minute 20 seconds).
last_mod_dt
call_req.last_mod_dt: This is the last modified timestamp (pdmtime).
close_date
call_req.close_date: This is the timstamp when the request was set to inactive (pdmtime).
resolve_date
This is the date for when the request was resolved (pdmtime).
rootcause
This is a pointer to the rootcause.id.
log_agent
call_req.log_agent: This is a binary-unique identifier, referencing the ca_contact table. It references the person who was the request's original creator.call_req.log_agent = ca_contact.contact_uuid
assignee
call_req.assignee: This is a binary-unique identifier, referencing a record in the ca_contact table. It represents the person currently assigned to the request.call_req.assignee = ca_contact.contact_uuid
group_id
call_req.group_id: This is a binary-unique identifier, referencing a record in the ca_contact table. It represents the group currently assigned to the request.call_req.group_id = ca_contact.contact_uuid
customer
call_req.customer: This is a binary-unique identifier, referencing a record in the ca_contact table. It represents the affected end user for this request.call_req.customer = ca_contact.contact_uuid
charge_back_id
charge_back_id: This is a text field available for use as an indicator of accounting jargon for expensing this request to the appropriate cost center.
affected_rc
call_req.affected_rc: This is a binary-unique identifier, referencing a row in the ca_owned_resource table. It represents the asset to which this request applies.call_req.affected_rc = ca_owned_resource.own_resource_uuid.
support_lev
call_req.support_lev: This is a pointer to a service desc record, which automates some constraints under which this request must be completed.call_req.support_lev = srv_desc.code.
category
call_req.category: This is a unique identifier, referencing a record in the prob_ctg table. It represents the category to which this request belongs.call_req.category = prob_ctg.persid
solution
call_req.solution: This is a pointer to call solution to get solution.call_req.solution = crsol.persid
impact
call_req.impact: This is an integer-unique identifier, referencing a row in the impact table. It indicates the impact scope of the request.call_req.impact = impact.enum
priority
call_req.priority: This is an integer-unique identifier, referencing a record in the pri table. It indicates how analysts will prioritize the work associated with this request.call_req.priority = pri.enum
urgency
call_req.urgency: This is an integer-unique identifier, referencing a row in the urgency table. It indicates the user's feeling of urgency for having this request resolved.call_req.urgency = urgncy.enum
severity
call_req.severity: This is an integer-unique identifier, referencing a row in the severity table. It indicates the severity of the consequences of this unresolved request.call_req.severity = sevrty.enum
extern_ref
This is an external reference to an associated ticket.
last_act_id
This identifies the id of the last activity.
cr_tticket
This is a pointer to the trouble ticket to get the associated ticket.
parent
call_req.parent: This is a ersid pointer to another request persid, which facilitates creation of a hierarchy of change orders.call_req.parent = call_req.persid
template_name
call_req.template_name: This is a text value, which indicates this request is designated for and can be chosen from a list as a template for other similar requests.cr_template.template = call_req.persid
sla_violation
call_req.sla_violation: This is an integer, which counts the number of times that slas attached to this request have been violated.
predicted_sla_viol
This specifies that a request has been predicted by neugents to likely violate SLA.
macro_predicted_violation
This indicates that the request has been predicted by neugents to likely violate SLA.
created_via
call_req.created_via: This is an integer pointer to a record in the interface table that indicates from which interface the change order originated.call_req.created_via = interface.id
call_back_date
call_req.call_back_date: This is a timestamp field (pdmtime), which indicates a future date/time that the affected_end_user is to be contacted.
call_back_flag
call_req.call_back_flag: This is a boolean indicator, displayed as a checkbox to the user, indicating whether to notify the analyst at the call_req.call_back_date.
event_token
call_req.event_token: This is used by CA NSM for message matching.
sched_token
call_req.sched_token: This is used by CA NSM for message matching.
type
call_req.type: This is a text field referencing a record in the crt table. It indicates the ITIL type for this request.call_req.type = crt.code
string1
This is a user-definable string.
string2
This is a user-definable string.
string3
This is a user-definable string.
string4
This is a user-definable string.
string5
This is a user-definable string.
string6
This is a user-definable string.
problem
This is an ITIL problem.
incident_priority
This is an ITIL incident priority.
change
call_req.change: This is an integer-unique identifier, referencing a row in the chg table. It indicates the change order that was created as a result of this request.call_req.change = chg.id.
service_type
srv_desc.sym: This indicates the actual Service Type.call_req.support_lev = srv_desc.code
severity_num
sevrty.sym: This is the actual Severity number.call_req.severity = sevrty.enum
urgency_num
urgncy.sym: This indicates the actual Urgency number.call_req.urgency = urgncy.enum
category_name
prob_ctg.sym: This is the actual Request Area (problem category).call_req.category = prob_ctg.id
asset
ca_owned_resource.resource_name: This is the actual Asset name.call_req.affected_rc = ca_owned_resource.own_resource_uuid
impact_num
impact.sym: This is the actual Impact number.call_req.impact = impact.enum
assignee_lastname
ca_contact.last_name: This is the actual Assignee last name.call_req.assignee = ca_contact.contact_uuid
assignee_firstname
ca_contact.first_name: This is the actual Assignee first name.call_req.assignee = ca_contact.contact_uuid
assignee_middlename
ca_contact.middle_name: This is the actual Assignee middle name.call_req.assignee = ca_contact.contact_uuid
customer_lastname
ca_contact.last_name: This is the actual last name of the Affected End User.call_req.customer = ca_contact.contact_uuid
customer_firstname
ca_contact.first_name: This is the actual first name of the Affected End User.call_req.customer.ca_contact.contact_uuid
customer_middlename
ca_contact.middle_name: This is the actual middle name of the Affected End User.call_req.customer = ca_contact.contact_uuid
group_name
View_Group.last_name: This is the actual Group name.
GroupID
View_Group.contact_uuid: This is the actual Group key ID.
status_name
cr_stat.sym: This is the actual status.
priority_num
pri.sym: This is the actual Priority number.
 
View_Request_to_Act_Log
The following is a basic view of all requests with their activity logs. The View_Request view is joined with the View_Act_Log view to give more detailed information about each activity per request.
Field
Remarks
View_Request.*
Please refer to the field defined in the View_Request section earlier in this document.
View_Act_Log.*
Please refer to the fields defined in the View_Act_Log section earlier in this document.
 
View_Request_to_Properties
The following is a basic view of call requests and their properties. This view lists everything from the call request (call_req) table and the request property (cr_prp) table.
Field
Remarks
View_Request.*
Please refer to the fields defined in the View_Request section of this document.
crprp_id
cr_prp.id: This is an integer-unique identifier for the property record.
crprp_persid
cr_prp.persid: This is a unique identifier for this record in the cr_prp table, preceded by the object identifier (cr_prp) and a colon.
sequence
cr_prp.sequence: This is an integer that indicates the order for which this particular property record should be displayed by CA SDM (for example, Ascending).
label
cr_prp.label: This is a short description of what should be placed in the cr_prp.value field.
value
cr_prp.value: This is a value entered by the user in response to the prp_description and cr_prp.label fields.
crprp_last_mod_dt
cr_prp.last_mod_dt: This is the timestamp (pdmtime) identifying when this property was last modified.
crprp_last_mod_by
cr_prp.last_mod_by: This is a binary identifier, which references a record in the ca_contact table. It represents the person who last modified this record.cr_prp.last_mod_by = ca_contact.contact_uuid
required
cr_prp.required: This is the boolean, indicating whether this property must have a cr_prp.value before the record is saved.
sample
cr_prp.sample: This is a text field, which displays example values to guide the user in entering the most useful value in cr_prp.value.
owning_cr
cr_prp.owning_cr: This is the unique identifier used to identify the specific record to which this property is attached.cr_prp.object_id = call_req.persid
crprp_description
cr_prp.description: This is a text field, which explains the type of value that should be entered in cr_prp.value.
View_Request_to_Request_WF
This feature will only be available if you apply a patch for CA Service Management Release 14.1.01. Find the patch and the download details from CA Support Online.
This view is a result of the View_Request view joined with the workflow task table (crwf) to give a basic view of requests and their workflow tasks. This may not list all requests, particularly if there are no workflow tasks assigned to them.
Field
Remarks
View_Request.*
Please refer to the View_Request definition earlier in this document for a description of each field.
wf_id
crwf.id: This is a unique identifier for a record in the crwf table.
wf_persid
crwf.persid: This is a unique identifier for this record in the crwf table, preceded by the object identifier (crwf) and a colon.
del
crwf.del: This is a boolean indicator of whether this record is to be displayed to the user.
object_type
crwf.object_type: This is the factory name, which is used to identify the type of record (for example, cr) to which this workflow task is attached.
object_id
crwf.object_id: This is a unique identifier used to identify the specific record to which this workflow task is attached.cr.object_id = issue.id
task
crwf.task: This is an identifier, which references the type of task this record represents.crwf.task = tskty.code
wf_template
crwf.wf_template: This is an identifier, which references from which template this workflow task record was created.crwf.wf_template = wftpl.id
sequence
crwf.sequence: This is an integer that indicates the order for which this particular workflow task record should be displayed and executed by CA SDM (for example, Ascending).
wf_status
crwf.status: This is an identifier, which references a tskstat record. It indicates the current status of this workflow task.crwf.status = tskstat.code
group_task
crwf.group_task: This is a boolean, which indicates whether this task belongs to a group.
creator
crwf.creator: This is a unique binary identifier, which references a record in the ca_contact table. It indicates the person who created this workflow task.crwf.creator = ca_contact.contact_uuid
date_created
crwf.date_created: This is the date/timestamp that this workflow task was created (pdmtime).
wf_assignee
crwf.assignee: This is a unique binary identifier, which references a record in the ca_contact table. It indicates the person who is currently assigned to this workflow task.crwf.assignee = ca_contact.contact_uuid
done_by
isswf.done_by: This is a unique binary identifier, which references a record in the ca_contact table. It indicates the person who completed or approved this workflow task.isswf.done_by = ca_contact.contact_uuid
wf_start_date
wf_start_date: This is the timestamp when the workflow task moved into an active status (pdmtime).
wf_est_comp_date
crwf.est_comp_date: This is a timestamp (pdmtime) indicating when users believe this task will be completed.
est_duration
crwf.est_duration: This is the estimated duration for this workflow task.
completion_date
crwf.completion_date: This is a timestamp (pdmtime) indicating when this workflow task was completed.
actual_duration
crwf.actual_duration: This is the actual amount of time it took to complete this workflow task.
wf_est_cost
crwf.est_cost: This is the estimated cost of this workflow task
cost
crwf.cost: This is the actual cost required to complete this workflow task.
wf_description
crwf.description: This is a description of the workflow task.
wf_last_mod_dt
crwf.last_mod_dt: This is the timestamp (pdmtime) indicating when this workflow task was last changed.
wf_last_mod_by
crwf.last_mod_by: This is the unique binary identifier, which references a record in the contact table. It indicates the last person to make changes to this workflow task.crwf.last_mod_by = ca_contact.contact_uuid
 
View_Request_to_Request_WF