Enter the Name for the constraint, and then select the Type for the condition. An

Creating and Reverse-Engineering a Model 5-11 Application data is not always valid for the constraints and declarative rules imposed by the information system. You may, for instance, find orders with no customer, or order lines with no product, etc. In addition, such incorrect data may propagate via integration flows.

5.6.1 Introduction to Data Integrity

Oracle Data Integrator provides a working environment to detect these constraint violation and store them for recycling or reporting purposes. There are two different main types of controls: Static Control and Flow Control. We will examine the differences between the two. Static Control Static Control implies the existence of rules that are used to verify the integrity of your application data. Some of these rules referred to as constraints may already be implemented in your data servers using primary keys, reference constraints, etc. With Oracle Data Integrator, you can refine the validation of your data by defining additional constraints, without implementing them directly in your servers. This procedure is called Static Control since it allows you to perform checks directly on existing - or static - data. Flow Control The information systems targeted by transformation and integration processes often implement their own declarative rules. The Flow Control function is used to verify an applications incoming data according to these constraints before loading the data into these targets. Setting up flow control is detailed in to Chapter 11, Working with Integration Interfaces .

5.6.2 Checking a Constraint

While creating a constraint in Oracle Data Integrator, it is possible to retrieve the number of lines violating this constraint. This action, referred as Synchronous Control is performed from the Control tab of the given constraint Editor by clicking the Check button. The result of a synchronous control is not persistent. This type of control is used to quickly evaluate the validity of a constraint definition.

5.6.3 Perform a Static Check on a Model, Sub-Model or Datastore

To perform a Static Check on a Model, Sub-Model or Datastore:

1. In the Models tree in the Designer Navigator, select the model that you want to

check. 2. Double-click this model to edit it.

3. In the Control tab of the model Editor, select the Check Knowledge Module

CKM used in the static check.

4. From the File menu, select Save All.

5. Right-click the model, sub-model or datastore that you want to check in the Model

tree in the Designer Navigator and select Control Check. 6. In the Execution window, select the execution parameters: 1. Select the Context into which the data must be checked.