Development >  Business intelligence >  Setup >  Predefined conditions  

Display all Hide all

This function is used to create pre-defined conditions used by Business objects to have filters on the datamart data available.

Prerequisites

SEEREFERTTO Refer to documentation Implementation

Screen management

The pre-defined conditions can be of two types:

  • either simple conditions, that involve fields and possibly constants.
  • or conditions involving setup values previously entered (these conditions are called prompts).

the pre-defined conditions entry screen is set on a single tab, but there are quick select lists that are used to view:

  • the datamart conditions via a first list organized in a tree structure, and then in a fact table.
  • and via a second list, the conditions in a global fashion.
  • via a third list, the prompts.

Entering a pre-defined condition is carried out on a datamart and on a given fact table.

In the section displaying the objects of the universe which reports are currently being created, the pre-defined conditions are displayed after the dimensions and the information. In order to display a pre-defined condition in the tree structure of a dimension, it is necessary to enter the dimension in the corresponding field.

If a pre-defined condition is not a prompt, it is defined as a SQL query (either independent from the database, or defined differently for each database).

However, if it is a prompt, this expression should be defined as an SQL query that includes variables instead of constants, and that sets conditions on the database fields. In order to display these variables, which title depends on the generation language, it is possible to pick one or two objects from the BO universe, which determines the database fields that concerns the conditions (#fld1, #fld2), as well as an associated selection(#obj1,#obj2).

A variable entered when launching a Business object report is defined by the following syntax:

@prompt('#txt1','D','#obj1',Mono,Constrained,Persistent,,)

The correspondences are the following:

  • The #txt1 fields corresponds to the text displayed to the user during the entry (this is the Prompt text field entered in the screen).
  • The #obj1 Field corresponds to a selection list depending on the selected criterion.

If an equality criterion should be defined on the field, the following will be entered:

#fld1 = @prompt('#txt1','D','#obj1',Mono,Constrained,Persistent,,)

Entry screen

Presentation

All the characteristics used to define the condition are entered in this screen.

Close

 

Fields

The following fields are present on this tab :

Block number 1

 
  • Order (field ORD)

 
  • Description (field ZDES)

 
  • Evaluated title (field INTEVAL)

 

Characteristics

 

 
  • Module (field MODULE)

 

Setup

 

 
  • field EXPLNK

 
  • Prompt text (#txt1) (field ZTEX)

 
  • Object 1 (#obj1) (field OBJ1)

 
  • Field 1 (#fld1) (field CHP1)

 
  • Object 2 (#obj2) (field OBJ2)

 
  • Field 2 (#fld2) (field CHP2)

 
  • Default condition (field CNDDEF)

 
  • Oracle condition (field CNDORA)

 
  • Sql-server condition (field CNDSQL)

 

Close

 

Specific Buttons

The following fields are included on the window opened through this button :

Block number 1

  • field OBJET

 
  • field CLES

 

Block number 2

  • From folder (field DOSORG)

Use this field to define the folder from which the record will be copied. The possible syntaxes are described in the Dedicated appendix.
  • All folders (field TOUDOS)

Use this option to copy the record to all the folders defined in the dictionary (ADOSSIER table of the current solution).
  • To folder (field DOSDES)

Use this field to define the folder to which the record will be copied. The possible syntaxes are described in the Dedicated appendix.

Close

This button is used to copy the record definition from or to another folder.

Error messages

The only error messages are the generic ones.

Tables used

SEEREFERTTO Refer to documentation Implementation