A structure is a set of features with filters F T.
A structure is a set of ratios with filters F T.
The "Cells" option is always available F T.
The "Cells" option requires two structures to be available F T.
Variables can be used to filter characteristics F T.
Variables can be used to filter ratios F T.
Variables can be used in the Exceptions F T.
Variables can be used in the Conditions F T.
The offset can only be applied to variables F T.
The views are independent of the query F T.
The queries require special transport orders F T.
To migrate a query 3.x just open it and save it with version 7.0 F T.
The function of "TOP N" is an Exception F T.
The function of "TOP N" is a Condition F T.
Restricted ratios can generate a query sa level or InfoProvider level F T.
The calculated ratios can generate a query sa level or InfoProvider level F T.
The report-to-report admit that any query of a cube can be linked with another query F T.
The IO that make up the Compoding must be defined as attributes F T.
The hierarchy may contain other InfoObjects as nodes F T.
The IO having compoding have a SID for each IO code that makes up the "key" F T.
The following are virtual IP: MultiProviders, Aggregation Level F T.
The following are not virtual IP: InfoCubes, InfoSets, DSO F T.
The DSO support for writing and deleting records F T.
All systems support import sources (refresh) datasouces from the source system F T.
Aggregates only support any attribute always belonging to an IO hub F T.
The process that updates using hierarchies aggregates known as Roll Up F T.
They can not restructure InfoCubes that already contain data F T.
All have logtable DSO F T.
The Open Hub is used for both export and import data F T.
A transformation only supports connecting InfoProviders F T.
The Change Run allows restructure aggregates F T.
The transaction PFCG to define roles F T.
There are two types of roles: simple and complex F T.
To find out what time a job will run use the SM50 transaction F T.
To know if a job finished executing correctly use the SM37 F T.
A process chain can be executed directly or from another process chain F T.
To find out what permissions a user has enabled use the transaction SU56 F T.
The transaction SE11 is what allows us to see the structure of a table F T.
The RSA3 transaction allows us to see what data extracts a datasouces F T.
You can release an order transport twice F T.
Hierarchies are transportable F T.
The transaction allows to debug reports RSRV F T.
The OLAP Cache is Administer from RSRW transaction F T.
DS in a working mode Delta Direct job needs to carry the delta data queue F T.
The DS logistics makers Full updates delta queue F T.
For enhacement takes a datasource must execute the transaction RSA6 F T.
Any datasource is valid for both ODS and for InfoCubes F T.
Variables can be used in formulas T F.
Variables can be used in titles F T.
The workbook are independent of the queries that comprise T F.
In a report-to-report can relate one query with R3 transaction T F.
An InfoObject is the smallest unit of information BW T F.
Simply define an attribute as "navigable" to make it available at any InfoProvider T F.
It is mandatory that an InfoObject have at least some kind of text T F.
An InfoProvider is any object type BW to allow use in a query T F.
All InfoProviders contain "physical" data T F.
A Infoset supports a maximum of 3 cubes T F.
A MultiProvider admits InfoCubes, InfoSets, DSO, InfoObjects, Aggregation Levels T F.
All DSO allow DTP T F.
The PSA can be generated or not T F.
The PSA can be used or not T F.
All source systems support the generation of own datasources in BW T F.
A datasource is a set of InfoObjects T F.
The datasource is a compulsory subject in all data transfer T F.
To load data into a cube, they are loaded into the fact table "F" T F.
When compressed data pass a bucket table E to F T F.
The aggregates allow selection of ratios T F.
The filling process is called aggregates Change Run T F.
Requests for a cube can be removed in order cualqueir T F.
Requests for a DSO can be removed in order cualqueir T F.
The Archiving is applicable to both InfoCubes as DSO T F.
The partition of a cube can be done by any unit of time T F.
A line-item allows to bypass the use of SID Tables T F.
Cubes support secondary indexes T F.
The DSO support secondary indexes T F.
The DSO allow Line-Items T F.
A DSO-type InfoCube Full update uses the log table T F.
A DSO-type Delta InfoCube update uses the active data table T F.
The Open Hub allows you to export data tables, ASCII files types T F.
A transformation can assign values InfoObjects that are not in the source and target objects T F.
The InfoCubes include: Standard, Real-adqusition and virtual T F.
The RSECADMIN transaction authorization level to define master data T F.
The transaction SE16 is what allows us to see the contents of a table T F.
The RSA7 transaction allows us to see the delta queue T F.
To transport a BW object from one server to another must generate a transport T F.
The datasources are transportable T F.
The SBIW transaction can only run on R3 T F.
The SPRO transaccón allows you to enter the general customizing T F.
The RSRT transaccón allows you to run diagnostic processes T F.
The Delta depends on the datasource T F.
The infopaquete running an update delta inherits the filter initialization T F.
Generic datasources allows deltas of Additive type T F.