5.3.1 Creating Jurisdiction in the Database

Behavior Detection uses Jurisdictions to limit user access to data in the database. Records from the Oracle client that the Data Management loads must be identified with a jurisdiction, users of the system must be associated with one or more jurisdictions. In Currency Transaction Reporting, users can view data only associated with jurisdictions to which they have access.

You can use a jurisdiction to divide data in the database; for example:

• Geographical: Division of data based on geographical boundaries, such as countries.
• Organizational: Division of data based on different legal entities that compose the client’s business.
• Other: Combination of geographic and organizational definitions. In addition, it is client driven and can be customized.

In most scenarios, a jurisdiction also implies a threshold that enables use of this data attribute to define separate threshold sets based on jurisdictions.