2.3 Oracle Financial Services Operations

As the Oracle administrator, you can coordinate the overall operations of the application Data Ingestion, Behavior Detection, and Post-Processing.

In a production environment, an Oracle client typically establishes a processing cycle to identify occurrences of behaviors of interest (that is, scenarios) on a regular basis. Each cycle of the Currency Transaction Reporting process begins with Data Ingestion, Behavior Detection, and Post-Processing, which prepares the detection results for presentation for the users.

Several factors determine specific scheduling of these processing cycles, including availability of data and the nature of the behavior that the system is to detect. The following sections describe each of the major steps in a typical production processing cycle.

Start Batch

Using the Batch Control Utility, you can manage the beginning of a batch process (See Administrative Utilities, for more information).

Data Ingestion

Your raw business data can be loaded into the Oracle Financial Services Data Model (FSDM) in various ways. The following approaches are available either through the OFSDF Common Staging Area Model (CSA) or converting the raw data into Data Interface Specification (DIS) files.

The Data Interface Specification (DIS) contains a definition of the flat file data ingestion process for each solution set. For more information about data ingestion, see the Oracle Financial Services Behavior Detection Administration Guide.

Behavior Detection

During Behavior Detection, Detection Algorithms control the scenario detection process. The Detection Algorithms search for events and behaviors of interest in the ingested data. Upon identification of an event or behavior of interest, the algorithms record a match in the database.

The application executes the following processes in this order to find and record scenario matches:

  1. The system populates temporary tables in the database; some scenarios depend on these tables for performance reasons.
  2. A network creation process generates and characterizes networks, filtering the links that the system evaluates in the construction of these networks.
  3. A match creation process creates matches based on detection of specific sequences of events in data that correspond to patterns or the occurrences of pre-specified conditions in business data. The process also records additional data that the analysis of each match may require.

Post-Processing

During Post-Processing, the detection results are prepared for presentation to users. This preparation is dependent upon the following processes:

  1. An alert creation process packages the scenario matches as units of work (that is, alerts), potentially grouping similar matches together, for disposition by end users (See section To Run Match Alert Creator for more information).
  2. During batch execution, alerts are converted into CTR records. See Batch Execution of CTR, for more information.

End Batch

The system ends batch processing when processing of data from the Oracle client is complete (See section Ending a Batch Process, for more information.