1. Using Advanced Controls
  2. Define Transaction Model Results

Define Transaction Model Results

As you create a transaction model, select result attributes. When the model is run, it returns the values of these attributes for each risky transaction it finds.

A model may incorporate derived attributes. These are calculations performed by the model. One example is a label applied to each group by a filter that uses the Equals or Similar condition to create groups. Another example is the sum, average, or count in a function filter that performs one of these calculations. Model results automatically include derived attributes, and you can't remove them.

You must actively select any other attribute to include it among the model results. The recommended limit for result attributes is 50, including derived attributes.

Be careful to select attributes that reflect the level of detail you want to see in your results. For example, a model may use a function filter that calculates the sum of invoice amounts for each supplier. The sum value, a derived attribute, is included automatically in the result set.

Your model logic would have used the Amount attribute of the Payables Invoice business object. Even so, this attribute isn't included automatically in the result set. If you opt to include it, results would contain a row for each invoice, which would be required to display the amount for each invoice. (Each row would also display the sum of its supplier's invoices.) If you don't, the results include many fewer rows: only one for each supplier, displaying the sum of that supplier's invoices.

You may intend for controls to supply information to analyses, reports, or dashboards created in Oracle Transaction Business Intelligence (OTBI). Those controls inherit result attributes from the models on which they're based. Here are some things to consider as you select result attributes for those models:

  • You can use only the first 25 result attributes in an analysis or report. Derived attributes come after the attributes you actively select. For example, if a model includes a function filter that calculates a sum, and you actively select 25 result attributes for the model, the derived attribute containing the sum is result attribute 26, and so wouldn't be available for reporting. If you want to use a derived attribute in an analysis or report, be sure to leave room for it.

  • You may want to include amount values that are to be summarized in a reporting instrument. If so, position the amount attribute second among the result attributes. You may also want to include a date related to the amount; if so, position the date attribute third among the result attributes. Examples of such attributes are Amount and Date in the Payables Invoice business object.

Use the Result Display panel to define results:

  1. An Available box lists the attributes of all business objects included in the model, organized by object. The naming format for each attribute is [Object Name].[Attribute Name]. Search for attributes you want.

  2. Move attributes you want from the Available box to the Selected box. Or, if need be, move attributes you don't want from the Selected box to the Available box.