DataView in ATO

The DataView object is used in an ATO to allow the user to enter data in an InfoCube, therefore one or more data blocks should have data-entry enabled. The standard icon of the DataView that saves data is disabled in an ATO, the write-back is executed by a Button of the ATO or a procedure which the screen designer can freely place within the ATO. Refer to About ATO for details on the general structure of the ATO.

The DataView object or objects part of an ATO, are configured as standard DataView objects, refer to the DataView and the Layout sections of the manual for details.

When there is more than one DataView object with data-entry within the same ATO, the save button saves data for all DataView objects simultaneously. This allows the designer of the Capsule to create a screen where the end-user enters data at different granularity levels (on different DataViews) but save the data together. For example in a sales budget application you may want the user to input the product unit price, at Product and Year level, and the budget sales units at Product, Customer and Month level. With an ATO, having two DataViews, one for entering the unit price and the other one for entering the budget sales units, it is possible to control that the user inputs, for each budgeted product, both the unit price and the sales units.

When a an ATO contains one or more Pagers, then the Layout of the DataView objects present are executed only after the user selects an item on each of the Pagers. This allows the designer of the Capsule to create a screen where the end-user must explicitly make a selection on a Pager before he can enter or even view data.

Example of a screen with ATO

where a pager item hasn't been selected yet by the user: the Layouts are not executed (i.e. DataView objects are not populated).