Explore topic-wise InterviewSolutions in .

a. Info PACKAGE.
b. Read PSA and update data target .
c. Save HIERARCHY .
d. Update ODS data object .
e. Data export (Open hub) .
F. Delete overlapping requests — useful if you do a full load every day for the current FISCAL year period and delete the data from PREVIOUS day.

a. Info package.
b. Read PSA and update data target .
c. Save hierarchy .
d. Update ODS data object .
e. Data export (Open hub) .
f. Delete overlapping requests — useful if you do a full load every day for the current fiscal year period and delete the data from previous day.

a. delete index.
b. generate index .
C. construct database statistics .
d. initial fill of new AGGREGATES .
e. roll up of filled aggregates .
f. compression of the infocube .
G. ACTIVATE ODS .
h. complete deletion of DATA target.

a. delete index.
b. generate index .
c. construct database statistics .
d. initial fill of new aggregates .
e. roll up of filled aggregates .
f. compression of the infocube .
g. activate ODS .
h. complete deletion of data target.

a. exception reporting.
B. print in the BACKGROUND.
c. pre CALCULATION of web templates .
d. pre calculation of VALUE sets.

a. exception reporting.
b. print in the background.
c. pre calculation of web templates .
d. pre calculation of value sets.

a. ATTRIBUTE CHANGE run.
b. ADJUSTMENT of time dependent aggregates .
c. deletion of requests from PSA .
d. reorganize attributes and TEXTS for MASTER data.

a. attribute change run.
b. adjustment of time dependent aggregates .
c. deletion of requests from PSA .
d. reorganize attributes and texts for master data.

DIRECT scheduling or start from meta chain (parent chain) or API; USE the second OPTION for your child process CHAINS.

Direct scheduling or start from meta chain (parent chain) or API; use the second option for your child process chains.

a. hierarchy attribute change run .
b. LOADING master data for same INFO OBJECT; for example avoid loading master data from different source systems at the same time .
c. rolling up for same info cube .
d. selecting deletion of info cube/ODS and parallel loading .
e. ACTIVATION or deletion of ODS object when loading parallel.

a. hierarchy attribute change run .
b. loading master data for same info object; for example avoid loading master data from different source systems at the same time .
c. rolling up for same info cube .
d. selecting deletion of info cube/ODS and parallel loading .
e. activation or deletion of ODS object when loading parallel.

When this option is enabled (by default), when you insert a process any corresponding process types are inserted automatically; for example if you drag and drop a info PACKAGE LOAD for ODS, then the process types like “Update from PSA”, “Activate ODS”, “Further processing” are automatically inserted; to disable this USE RSPC .> SETTINGS -> default chains -> check mark “Do not suggest processes”.

When this option is enabled (by default), when you insert a process any corresponding process types are inserted automatically; for example if you drag and drop a info package load for ODS, then the process types like “Update from PSA”, “Activate ODS”, “Further processing” are automatically inserted; to disable this use RSPC .> Settings -> default chains -> check mark “Do not suggest processes”.

PROCESS CHAIN -> ATTRIBUTES -> Display components.

Process Chain -> Attributes -> Display components.

PLANNING VIEW, checking view, log view and JOB overview.

Planning view, checking view, log view and job overview.

RIGHT click on the process you want to monitor (for example LOAD info package)
-> select create message -> select when you want to send message (Success, FAIL or always) -> create a variant for the mail.

Right click on the process you want to monitor (for example load info package)
-> select create message -> select when you want to send message (Success, fail or always) -> create a variant for the mail.

Double click on the info package group, click on the “Process CHAIN Maint.” BUTTON and TYPE in the NAME and description; the individual info packages are inserted automatically.

Double click on the info package group, click on the “Process Chain Maint.” Button and type in the name and description; the individual info packages are inserted automatically.

This is a TOOL by which you can SEND data from BW to different targets; it is a controlled distribution of consolidated and CLEANSED data.

This is a tool by which you can send data from BW to different targets; it is a controlled distribution of consolidated and cleansed data.

BW, EXTERNAL systems, relational table, FLAT file and ODBO interface.

BW, External systems, relational table, flat file and ODBO interface.

Yes.

Yes.

Transaction RSBO or AWB -> Tools -> OPEN HUB Service.

Transaction RSBO or AWB -> Tools -> Open Hub Service.

Cube, ODS, info OBJECT (attributes and TEXTS).

Cube, ODS, info object (attributes and texts).

CSV FILE or DATABASE table.

CSV file or database table.

if you CHOOSE this OPTION, the table contents are deleted before any new record is written. Disable if you want to KEEP historical data.

if you choose this option, the table contents are deleted before any new record is written. Disable if you want to keep historical data.

Extracting DATA from SAP BW by any MEANS REQUIRES ADDITIONAL licensing.

Extracting data from SAP BW by any means requires additional licensing.

USING BADI you can TRANSFORM OPEN hub data according to the destination REQUIREMENT.

Using BADI you can transform open hub data according to the destination requirement.

a. use HTTP compression to reduce NETWORK traffic.
b. use the client browser caching .
c. use the iemon.exe program and use the log file option to time the QUERY .
d. use analyze_iemon.exe to GET CSV file to a spread SHEET for further analysis.

a. use HTTP compression to reduce network traffic.
b. use the client browser caching .
c. use the iemon.exe program and use the log file option to time the query .
d. use analyze_iemon.exe to get csv file to a spread sheet for further analysis.

a. the right COMBINATION of resources LIKE CPU, memory and disk spaces .
B. load BALANCING with several APPLICATION servers .
c. check for unnecessary traces and logs.

a. the right combination of resources like CPU, memory and disk spaces .
b. load balancing with several application servers .
c. check for unnecessary traces and logs.

RSRV is a powerful transaction to test consistency and FIX any issues;

RSRV is a powerful transaction to test consistency and fix any issues;

a. MASTER data.
b. TRANSACTION data.
C. hierarchies. 
d. database .
E. aggregates .
f. PSA TABLES.

a. master data.
b. transaction data.
c. hierarchies. 
d. database .
e. aggregates .
f. PSA tables.

a. MASTER DATA.
b. Transaction data.
c. Hierarchies. 
d. Database .
E. Aggregation.

a. Master data.
b. Transaction data.
c. Hierarchies. 
d. Database .
e. Aggregation.

No.

No.

Yes.

Yes.

ACTIVE DATA, NEW data and the CHANGE LOG table.

Active data, New data and the change log table.

Change LOG is used for DELTA updates to the target; it STORES all changes PER request and updates the target.

Change log is used for delta updates to the target; it stores all changes per request and updates the target.

AWB -> right CLICK on ODS -> Manage -> ENVIRONMENT -> Delete change LOG.

AWB -> right click on ODS -> Manage -> Environment -> Delete change log.

a. access via OLAP engine.
B. infosets can join FLAT BW objects like master data attributes, ETC.

a. access via OLAP engine.
b. infosets can join flat BW objects like master data attributes, etc.

a. you can load and activate ODS in parallel.
b. NoM table .
C. SECONDARY indexes are created in ODS OBJECTS itself .
d. SELECTIVE DELETION.

a. you can load and activate ODS in parallel.
b. NoM table .
c. Secondary indexes are created in ODS objects itself .
d. Selective deletion.

This has only the active table; this is FILLED using APIs; you report on this using Infoset only; USUALLY used for applications LIKE SEM.

This has only the active table; this is filled using APIs; you report on this using Infoset only; usually used for applications like SEM.

If you enable then when ODS gets duplicate record (identical to one in Active table), it rejects with an error. Use this feature to load a cube FILTERING any DUPLICATES (Cubes will SIMPLY add up duplicates).

If you enable then when ODS gets duplicate record (identical to one in Active table), it rejects with an error. Use this feature to load a cube filtering any duplicates (Cubes will simply add up duplicates).

Individual data PROVIDERS can be enabled to minimize overhead; AWB -> Tools -> BW statistics.

Individual data providers can be enabled to minimize overhead; AWB -> Tools -> BW statistics.

use the BUSINESS content to install
a. using the Business Content section of AWB, select info area “BW Statistics”; right CLICK and select INSERT objects for collections; select before and after data flow for grouping and install.
B. Similarly in all the Technical Content SAP_B W_TCONT role. 
c. Install the info package groups for Master data/text and TRANSACTION data.

use the business content to install
a. using the Business Content section of AWB, select info area “BW Statistics”; right click and select insert objects for collections; select before and after data flow for grouping and install.
b. Similarly in all the Technical Content SAP_B W_TCONT role. 
c. Install the info package groups for Master data/text and transaction data.

a. Mean TIME per query. 
b. RUNTIME query .
C. Using INFOCUBES. 
d. Utilizing OLAP.

a. Mean time per query. 
b. Runtime query .
c. Using infocubes. 
d. Utilizing OLAP.

AGGREGATES are mini CUBES; they are used to IMPROVE the performance when doing query; similar to INDEXES on a table; it is transparent to the user.

Aggregates are mini cubes; they are used to improve the performance when doing query; similar to indexes on a table; it is transparent to the user.

AWB -> RIGHT click on info cube -> SELECT maintain AGGREGATE.

AWB -> right click on info cube -> select maintain aggregate.

No.

No.

The DATA from INFOCUBE is SUMMARIZED into the AGGREGATES.

The data from infocube is summarized into the aggregates.

RSDDAGGRDIR;

RSDDAGGRDIR;

When you change master data ATTRIBUTES and hierarchies used in AGGREGATES, you USE change run PROCESS to realign aggregates.

When you change master data attributes and hierarchies used in aggregates, you use change run process to realign aggregates.

USING a PROCESS chain or AWB -> Tools -> APPLY HIERARCHY attribute change.

Using a process chain or AWB -> Tools -> Apply Hierarchy attribute change.

RSDDS_CHANGERUN_MONITOR.

RSDDS_CHANGERUN_MONITOR.

RSDDS_AGGREGATES_MAINTAIN.

RSDDS_AGGREGATES_MAINTAIN.

ROLL up is the PROCESS by which requests loaded in to the info cube are “rolled to” the aggregates; TILL roll up is done you cannot do a report on the REQUEST.

Roll up is the process by which requests loaded in to the info cube are “rolled to” the aggregates; till roll up is done you cannot do a report on the request.

It should have AROUND 10-20% of the size of the FACT table; for example if your fact table contains 1 MILLION rows, the AGGREGATE should have LESS than 200,000 rows.

It should have around 10-20% of the size of the fact table; for example if your fact table contains 1 million rows, the aggregate should have less than 200,000 rows.

You can ask the system to GET the optimal characteristics for aggregation by using the BW statistics DATA (like QUERY run TIME, etc).

You can ask the system to get the optimal characteristics for aggregation by using the BW statistics data (like query run time, etc).

a. PROPOSAL from BW statistics cube — history of bw statistics.
b. Propose from BW statistics (TABLES) — based on database tables RSDDSTAT and RSDDSTATAGGRDEF .
C. Propose from last navigation — suggestion based on the last ENTRY of the above mentioned tables for the current user .
d. Propose from query.

a. Proposal from BW statistics cube — history of bw statistics.
b. Propose from BW statistics (tables) — based on database tables RSDDSTAT and RSDDSTATAGGRDEF .
c. Propose from last navigation — suggestion based on the last entry of the above mentioned tables for the current user .
d. Propose from query.