Installation Guide

Figure 21: Data Mapping Between Unified CCE child and Unified ICME parent
In the figure:
1. On the child, the record in the Call_Type_Half_Hour table you are interested in has a
CallTypeID value of 5000.
2. On the parent, you would search the Service table for a Service with a PeripheralNumber
field that matches the CallTypeID on the child (5000).
3. The SkillTargetID for that Service is 6000.
4. Using the SkillTargetID value (6000), look up the corresponding record in any of the
Service Tables (for example, Service_Half_Hour, Service_Real_Time).
Understanding Similar Data Concepts in Unified CCE Child Call Type and Unified ICME Parent Service Database
Tables
This section describes the relationship between customer experience data available at the Unified
ICME parent and at the Unified CCE child. It discusses Services data concepts at the Unified
ICME parent and corresponding similar concepts at the Unified CCE child.
Note: "Similar concept" in this discussion means "closest in meaning"; it does not imply an
absolute match.
Due to the variety of reasons discussed in "Differences between Unified ICME Parent and
Unified CCE Child Reporting" (page 57), the data collected and presented in Service database
tables and Services WebView reports at the Unified ICME parent is expected to vary from data
collected and presented on Call Type database tables and Call Type reports on the Unified CCE
child. Although the two data sets are not expected to be an exact match, in some cases, the
customer can look at a specific data field in the Services table at the Unified ICME parent and
see a corresponding data field in Call Type table in the Unified CCE child that is similar in
meaning.
Cisco IPCC Gateway Deployment Guide for Unified ICME, Unified CCE, and Unified CCX, Enterprise Releases 7.2(1) and Express Release 5.0(1)
62
Chapter 4: - Understanding Reporting in an IPCC Gateway Deployment
Understanding Reporting in the Unified ICME Parent and Unified CCE Child Deployment Model