Universe generation
This function is used to create or recreate (in case of modification) a universe that can be reused by the Business Intelligence functions. Launching it automatically creates all the objects in the Business Objects dictionary.
The update of an already existing universe entails a report "remapping" stage for those reports that are already created in the universe to operate again. Launching this stage is optional.
Prerequisite
Refer to documentation Implementation
Screen management
Entry screen
Presentation
The screen associated to the function is used to define the setups associated to the universe creation or update.
Close
Fields
The following fields are present on this tab :
Datamart
| Used to specify the datawarehouse code from which the universe is generated. |
| Used to specify the datamart code from which the universe is generated. |
| This field is display only ; its contents is determined in the following fashion :
The creation of the universe is made in a systematic fashion without deleting the previous universes that exist, for obvious security reasons. |
Translation
| Define the original language in which the standard business objects reports are shipped ; these are the reports that will be duplicated and mapped with the universe being created during the generation operation. |
| Define the language to be used to create the universe (a universe is strictly defined for a given language). The standard reports supplied with the package are also translated into this language. |
Options
| This box present for information purposes is not entered, it is checked if, in the definition of the datamart, the box Authorization by site is checked. In this case, the generation automatically adds the standard filters on the objects concerned. |
| This box is used to define if the management of authorizations by access code in the universe is required. In this case the generation automatically adds the standard filters on the objects concerned. |
| When this box is checked, the universe is not actually created, but a detailed log file gives all the operations that will be carried out by creation function. |
|
|
|
|
| If this box is checked, the universe generated in the universe designer is exported to the business objects server. The common reference is then up to date. If the box is not checked, the universe remains confined to the designer ; the designer can then be used to view the universe on the server and potentially modified before exporting it. The fact of un-checking this box is only of interest when ready to carryout tests. |
| If box is checked, a copy is made of the standard shipped reports in the reference database of the newly created universe. |
Close
Batch task
This function can be run in batch mode. The standard task ABICREUNV is provided for that purpose.
Error messages
In addition to the generic error messages, the following messages can appear during the entry :
Impossible to determine the BO machine
There is server access problem (probably at network level).
Datamart not present in the datawarehouse
The entered datamart does not exist in the selected datawarehouse.
Error messages in the log file
The universe generation process generates a log file. The following messages thus appear in the log file.
The remote directory could not be created
Upon creation of a universe, directories must exist on the server where Business Objects is installed, so that the appropriate creation scripts can be placed there. This message means that the directories in question could not be created, namely because the user was not authorized to create them of for any other reason (for instance, no disk space available anymore).
Non existent object: xxx
During the coherence control of all the elements of the universe, an inconsistency was detected: for instance, a hierarchy described in the universe refers to an element that no longer exists, a nonexistent predefined condition (prompt), etc.
No active field on the table
A table cannot be created because all the fields in this table are deactivated via inactive activity codes.
Inactive dimension
A link between tables refers to a dimension bearing an inactive activity code.
xxx: Field not present in the yyy aggregate
The field controlling the access to a table is not present in the aggregate. This can be the case if a control by access code has been activated.