Extraneous fields from an external data feed need to be defined to map the external data feed field to a database field type. You can also define field definitions when creating a profile. When creating a profile, you use field definitions to define the structure of the external data.
When usage data is imported, it is uploaded into the database. During data import, data validation checks are performed. Invalid records are not uploaded into the database. Before data is imported into the database, you can apply rules to filter out erroneous or irrelevant data. Field definitions hold the definition of these validation rules, specifying a validation rule on each column of data imported.
To define data fields for Data Mediation
The All Fields list of existing fields displays.
The Define a Field window displays.
Specifies the field name that appears on the GUI to end users.
Specifies the database field name.
Specifies the database field type and size.
Specifies the check type, if applicable.
Specifies that the field value must not be empty.
Specifies that the field value falls within the specified range.
Specifies that a field value exists in a database table field.
Specifies a replacement value, if the value in the field exists in the specified database table field.
These validation rules are enforced when usage data is imported. If the driver validation rules are violated upon import, a kickoff report is generated. The report is available through the Data Management user interface.
The data fields are defined.
Usage data has to be normalized into a common format understood by data mediation before it is aggregated. The aggregation results in an error if the following server mandatory fields are not included:
Associates a data record to a Accounting Component account ID.
Associates a data record to an event (Event ID).
Associates a data record to a fiscal period (Time Stamp).
Associates a data record with a metric value.
Associates a data record with a service offering (Service Offering ID).
Note: Formatting data to include all server mandatory fields prior to data import is unnecessary. Data Mediation features complex data mapping mechanisms, such as validation and normalization, which help the administrator include server mandatory fields.
Copyright © 2013 CA.
All rights reserved.
|
|