Navigation: » No topics above this level «

Business Objects

In this form you can register and change views. Open screen in browser Open Form

A view is a business object or a reporting object.

A view is a prepared collection of data from one or more tables.

There are two kind of views:

•reporting views: views only used for retrieving data. Their name is ‘<application>_<name>_r’.

•Business views: view in a logical format for organizational activities for loading and changing data. Their name is ‘<application>_<name>_v’.

Reporting views are specified as SQL text, while business views are a collection of view elements per used table.

The registration of views is a typical activity for application developers. See the warning under Application Development.

Views Screen

The meaning of the entry fields is:

Application	The application of which the view is part of.
Code	The code with which is referred to the view. Usually, three-letter codes are used.
Name	The name of the view.
Label singular	The label of the view when the data is used in singular, for example ‘Project’. It is also possible to use resources.
Label Plural	The label of the view when the data is used in plural, for example ‘Projects’. It is also possible to use resources.
Label Singular when Referenced	Reference to resource if the data is used in singular.
Label plural when Referenced	Reference to resource if the data is used in plural.
Additional Where Clause	An extra limitation to the data visible in the view. In the format of a ‘SQL where clause’.
Additional Select Clause	An extra list of columns, expressed as SQL, available in the column list of the view.
Order by Clause	An ordering of the data in the view. Expressed as SQL. Do mind: use the ‘order by clause’ for simple views only. Applying this to complex views might lead to performance reduction.
Create	Checked in case the view needs to be included in the database.
Hard Coded
Optimizer Hint	A hint for the view, expressed in SQL.
Definition	Definition of the data visible in the view.
Example	An example of the data in the view.
Documentation	Documentation concerning the view.
User May Select	Checked in case the application user is allowed to read data from this view.
User May Insert	Checked in case the application user is allowed to add data from this view.
User May Update	Checked in case the application user is allowed to update data from this view.
User May Delete	Checked in case the application user is allowed to delete data from the view.
Hard Coded Definition	The possible hard coded definition. Only for reporting views. For business views use view elements (see below).

A business view can consist of multiple view elements, whereby each view element will be a table or a ‘pseudo table’ for a report view that will be joined in the business object:

Elements Screen

Sequence	A view consists of several view elements. The sequence indicates on what position the view element is included in the view. Usually, the base table gets the lowest sequence.
Application	The application of which the view element is part of.
Table	The name of the table forming the view element.
Alias	The alias for the data in the table. Usually this will be the same as the table alias, but in case a table is used in more locations in a business view, every location will get a different alias.
Column Name	The name of the column on which the join is built.
Joined Alias	The alias of the table with which the view element is joined.
Joined Column Name	The name of the column used to make the join.
Additional Where Clause	An extra where clause, expressed in SQL.
Reference Columns	By default all reference columns from the table are included. If you would like you can include an other list of columns. Then, the reference columns are not included. If you use a ‘+’ in the list of reference columns, all reference columns of the table will be included.
Left outer join	Checked if a left outer join should be used.

Important Safety and Usage Information

Intended Use and Limitations: This software, developed by Invantive, is designed to support a variety of business and information technology data processing functions, such as accounting, financial reporting an sales reporting. It is important to note that this software is not designed, tested, or approved for use in environments where malfunction or failure could lead to life-threatening situations or severe physical or environmental damage. This includes, but is not limited to:

Nuclear facilities: The software should not be used for operations or functions related to the control, maintenance, or operation of nuclear facilities.
Defense and Military Applications: This software is not suitable for use in defense-related applications, including but not limited to weaponry control, military strategy planning, or any other aspects of national defense.
Aviation: The software is not intended for use in the operation, navigation, or communication systems of any aircraft or air traffic control environments.
Healthcare and Medicine Production: This software should not be utilized for medical device operation, patient data analysis for critical health decisions, pharmaceutical production, or medical research where its failure or malfunction could impact patient health.
Chemical and Hazardous Material Handling: This software is not intended for the management, control, or operational aspects of chemical plants or hazardous material handling facilities. Any malfunction in software used in these settings could result in dangerous chemical spills, explosions, or environmental disasters.
Transportation and Traffic Control Systems: The software should not be used for the control, operation, or management of transportation systems, including railway signal controls, subway systems, or traffic light management. Malfunctions in such critical systems could lead to severe accidents and endanger public safety.
Energy Grid and Utility Control Systems: This software is not designed for the control or operation of energy grid systems, including electrical substations, renewable energy control systems, or water utility control systems. The failure of software in these areas could lead to significant power outages, water supply disruptions, or other public utility failures, potentially endangering communities and causing extensive damage.
Other High-Risk Environments: Any other critical infrastructure and environments where a failure of the software could result in significant harm to individuals or the environment.

User Responsibility: Users must ensure that they understand the intended use of the software and refrain from deploying it in any setting that falls outside of its designed purpose. It is the responsibility of the user to assess the suitability of the software for their intended application, especially in any scenarios that might pose a risk to life, health, or the environment.

Disclaimer of Liability: Invantive disclaims any responsibility for damage, injury, or legal consequences resulting from the use or misuse of this software in prohibited or unintended applications.

Please enable JavaScript to view this site.

Invantive Estate

Business Objects

Important Safety and Usage Information