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:

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.

 

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).

 

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).

 

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).

 

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).

 

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.

 

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.

 

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.

 

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.

 

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.

 

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.

 

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.

 

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.

 

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.

 

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.

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:

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.

 

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.

 

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.

 

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.

 

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.

 

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.

 

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.

 

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.

 

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.

 

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.

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.