Explore topic-wise InterviewSolutions in .

DISPLAY only and navigational; display only attributes are only for display and no ANALYSIS can be done; navigational attributes BEHAVE like regular characteristics; for example assume that we have a CUSTOMER characteristics with country as a navigational attribute; you can analyze the DATA using customer and country.

Display only and navigational; display only attributes are only for display and no analysis can be done; navigational attributes behave like regular characteristics; for example assume that we have a customer characteristics with country as a navigational attribute; you can analyze the data using customer and country.

Alpha conversion is used to store data consistently by storing any numeric values with prefixing with OS; for example if you DEFINED material as 6 Numc then number I is stored as 000001 but displayed as 1; this removes inconsistencies between 01 vs. 001.

Alpha conversion is used to store data consistently by storing any numeric values with prefixing with Os; for example if you defined material as 6 Numc then number I is stored as 000001 but displayed as 1; this removes inconsistencies between 01 vs. 001.

This is used to CHECK CONSISTENCY for BW 2.x before UPGRADING the SYSTEM to 3.x; the TRANSACTION is RSMDCNVEX1T.

This is used to check consistency for BW 2.x before upgrading the system to 3.x; the transaction is RSMDCNVEX1T.

If the flag is SET, no master DATA is STORED; this is only USED as attribute for other characteristics; for example comments on a AR document.

If the flag is set, no master data is stored; this is only used as attribute for other characteristics; for example comments on a AR document.

This defines the superior INFO object which MUST be combined to DEFINE an object; for example when you define COST CENTER then controlling area is the compounding (superior) object.

This defines the superior info object which must be combined to define an object; for example when you define cost center then controlling area is the compounding (superior) object.

AMOUNT, NUMBER, INTEGER, DATE and TIME.

Amount, number, integer, date and time.

If you are DEFINING prices then you may want to set “no aggregation” or you can DEFINE max, mm, SUM; you can also define exception aggregation like first, LAST, etc; this is helpful in getting headcount; for EXAMPLE if you define a monthly inventory count key figure you want the count as of last day of the month.

If you are defining prices then you may want to set “no aggregation” or you can define max, mm, sum; you can also define exception aggregation like first, last, etc; this is helpful in getting headcount; for example if you define a monthly inventory count key figure you want the count as of last day of the month.

a. Identify fact table
b. Identify dimension tables
c. Define ATTRIBUTES of entities
d. Define granularity of the fact table
e. Pre calculated key figures
f. Slowly CHANGING DIMENSIONS
g. Aggregates
h. How long data will be kept
i. How OFTEN data is EXTRACTED

a. Identify fact table
b. Identify dimension tables
c. Define attributes of entities
d. Define granularity of the fact table
e. Pre calculated key figures
f. Slowly changing dimensions
g. Aggregates
h. How long data will be kept
i. How often data is extracted

233.

233.

248.

248.

a. P table — Time INDEPENDENT master DATA attributes
B. Q table — Time dependent master data attributes
c. M view - Combines P and Q
d. X table — INTERFACE between master data SIDs and time independent navigational attributes SIDs ( P is linked to the X table)
e. Y table — Interface between master data SIDs and time dependent navigational attributes SIDs (Q is linked to the Y table)

a. P table — Time independent master data attributes
b. Q table — Time dependent master data attributes
c. M view - Combines P and Q
d. X table — Interface between master data SIDs and time independent navigational attributes SIDs ( P is linked to the X table)
e. Y table — Interface between master data SIDs and time dependent navigational attributes SIDs (Q is linked to the Y table)

It is LIKE a start ROUTINE; this is independent of the DATA source and valid for all transfer ROUTINES; you can USE this to define global data and global checks.

It is like a start routine; this is independent of the data source and valid for all transfer routines; you can use this to define global data and global checks.

DIM IDS LINK DIMENSIONS to the FACT table.

Dim ids link dimensions to the fact table.

USUALLY 2 extra PARTITIONS are CREATED to ACCOMMODATE DATA before the begin date and after the end date.

Usually 2 extra partitions are created to accommodate data before the begin date and after the end date.

No; the cube MUST be empty to do this; one work around is to make a copy of the cube A to cube B; export data from A to B USING export data source; empty cube A; CREATE partition on A; re-import data from B; DELETE cube B.

No; the cube must be empty to do this; one work around is to make a copy of the cube A to cube B; export data from A to B using export data source; empty cube A; create partition on A; re-import data from B; delete cube B.

RSA1.

RSA1.

Any system that is sending DATA to BW like RJ3, flat file, ORACLE DATABASE or external SYSTEMS.

Any system that is sending data to BW like RJ3, flat file, oracle database or external systems.

The source which is SENDING DATA to a PARTICULAR INFO source on BW; for example we have a OCUSTOMER_ATTR data source to supply attributes to OCUSTOMER from R/3.

The source which is sending data to a particular info source on BW; for example we have a OCUSTOMER_ATTR data source to supply attributes to OCUSTOMER from R/3.

Group of logically related OBJECTS; for example the OCUSTOMER info source will contain DATA related to customer and ATTRIBUTES like customer number, address, PHONE no, etc.

Group of logically related objects; for example the OCUSTOMER info source will contain data related to customer and attributes like customer number, address, phone no, etc.

TRANSACTIONAL, ATTRIBUTES, TEXT and HIERARCHY.

Transactional, attributes, text and hierarchy.

Is an INDEPENDENT STRUCTURE CREATED from INFO SOURCE; it is independent of the source system/data source.

Is an independent structure created from info source; it is independent of the source system/data source.

The TRANSFORMATION rules for DATA from source system to INFO source/communication structure.

The transformation rules for data from source system to info source/communication structure.

This is a transfer ROUTINE (ABAP) defined at the info object LEVEL; this is common for all SOURCE systems.

This is a transfer routine (ABAP) defined at the info object level; this is common for all source systems.

a. RESULT - this GETS the result of the ABAP CODE
b. RETURNCODE - you set this to 0 if everything is OK; else this record is skipped
C. ABORT - set this to a value not 0, to abort the entire package

a. RESULT - this gets the result of the ABAP code
b. RETURNCODE - you set this to 0 if everything is OK; else this record is skipped
c. ABORT - set this to a value not 0, to abort the entire package

This COPIES DATA SOURCE structures from RJ3 to BW.

This copies data source structures from RJ3 to BW.

UPDATE RULE DEFINES the transformation of data from the communication structure to the data TARGETS; this is INDEPENDENT of the source systems/data sources.

Update rule defines the transformation of data from the communication structure to the data targets; this is independent of the source systems/data sources.

Time dimensions are automatically converted; for EXAMPLE if the cube contains calendar month and your TRANSFER STRUCTURE contains date, the date to calendar month is converted automatically.

Time dimensions are automatically converted; for example if the cube contains calendar month and your transfer structure contains date, the date to calendar month is converted automatically.

This is to distribute data according to time; for EXAMPLE if the SOURCE contains calendar week and the TARGET contains calendar day, the data is split for each calendar day. Here you can SELECT either the normal calendar or the FACTORY calendar.

This is to distribute data according to time; for example if the source contains calendar week and the target contains calendar day, the data is split for each calendar day. Here you can select either the normal calendar or the factory calendar.

Usually the update rule SENDS one RECORD to the data target; using this option you can send multiple records; for EXAMPLE if we are getting total telephone examples for the cost center, you can use this to RETURN telephone expenses for each employee (by dividing the total expenses by the number of employees in the cost center) and creating cost record for each employee in the ABAP code.

Usually the update rule sends one record to the data target; using this option you can send multiple records; for example if we are getting total telephone examples for the cost center, you can use this to return telephone expenses for each employee (by dividing the total expenses by the number of employees in the cost center) and creating cost record for each employee in the ABAP code.

The FIRST step in the UPDATE process is to call start routine; use this to fill GLOBAL VARIABLES to be used in update routines;

The first step in the update process is to call start routine; use this to fill global variables to be used in update routines;

Using this OPTION you can write ABAP code for UNIT CURRENCY conversion; if you enable this flag, then unit of the KEY FIGURE appears in the ABAP code as an additional parameter; for example you can use this to convert quantity in pounds to kilo grams.

Using this option you can write ABAP code for unit currency conversion; if you enable this flag, then unit of the key figure appears in the ABAP code as an additional parameter; for example you can use this to convert quantity in pounds to kilo grams.

The BW SYSTEM feeding data to itself is called the myself data mart; this is CREATED automatically; uses ALE for data TRANSFER.

The BW system feeding data to itself is called the myself data mart; this is created automatically; uses ALE for data transfer.

a. RIGHT click and create the export DATA source for the ODS/cube
b. in the TARGET SYSTEM replicate the data source
c. create transfer rules and UPDATE rules
d. create info package to load

a. right click and create the export data source for the ODS/cube
b. in the target system replicate the data source
c. create transfer rules and update rules
d. create info package to load

Yes.

Yes.

a. Simple to USE
B. Hub and spoke usage
C. Distributed data
d. Performance improvement in some CASES

a. Simple to use
b. Hub and spoke usage
c. Distributed data
d. Performance improvement in some cases

Events are BACKGROUND signal to tell the SYSTEM that certain status has been reached; you can use events in batch jobs; for example after you load data to the cube you can TRIGGER an event which will start ANOTHER job to run the reporting agent. Use SM62 to create and maintain events.

Events are background signal to tell the system that certain status has been reached; you can use events in batch jobs; for example after you load data to the cube you can trigger an event which will start another job to run the reporting agent. Use SM62 to create and maintain events.

This is a group of events which complete INDEPENDENTLY of one ANOTHER; use this to check the SUCCESSFUL status of multiple events; for EXAMPLE you can trigger a CHAIN event if all loads are successful.

This is a group of events which complete independently of one another; use this to check the successful status of multiple events; for example you can trigger a chain event if all loads are successful.

AWB -> TOOLS -> EVENT COLLECTOR.

AWB -> Tools -> Event collector.

PERSISTENT staging area — is BASED on the transfer STRUCTURE and SOURCE system dependent.

Persistent staging area — is based on the transfer structure and source system dependent.

a. PSA and DATA targets in parallel — IMPROVES performance
b. PSA and data target in SEQUENCE
c. PSA only — you have to manually LOAD data to data targets
d. Data targets only — No PSA

a. PSA and data targets in parallel — improves performance
b. PSA and data target in sequence
c. PSA only — you have to manually load data to data targets
d. Data targets only — No PSA

This is to avoid inconsistency and MAKE sure that only VERIFIED DATA is entered into the SYSTEM.

This is to avoid inconsistency and make sure that only verified data is entered into the system.

There are two fact tables for each INFO CUBE; it is the E table and the F table;

There are two fact tables for each info cube; it is the E table and the F table;

This is the PROCESS by which we DELETE the request iDs; this saves SPACE; all the regular requests are stored in the F table; when you COMPRESS, the request ID is deleted and data is MOVED from F table to E table; this saves space and improves performance but the disadvantage is that you cannot delete the compressed requests individually.

This is the process by which we delete the request iDs; this saves space; all the regular requests are stored in the F table; when you compress, the request ID is deleted and data is moved from F table to E table; this saves space and improves performance but the disadvantage is that you cannot delete the compressed requests individually.

This is the PROCESS by which you LOAD DATA in to the same CUBE or to a DIFFERENT cube.

This is the process by which you load data in to the same cube or to a different cube.

Remote CUBE is a logical cube where the DATA is extracted from an external source; usually it is USED to report REAL time data from an r/3 system instead of DRILLING down from BW to R3.

Remote cube is a logical cube where the data is extracted from an external source; usually it is used to report real time data from an r/3 system instead of drilling down from BW to R3.

In this CASE a USER DEFINED function module is used as DATA SOURCE.

In this case a user defined function module is used as data source.

These are used for small volume of DATA with few users; no MASTER data ALLOWED.

These are used for small volume of data with few users; no master data allowed.

OH_AP3 — VENDOR LINE ITEMS, OFI_AR_3 — CUSTOMER line items.

OH_AP3 — vendor line items, OFI_AR_3 — customer line items.

Using multi PROVIDER you can access DATA from DIFFERENT data sources like cubes, ODS, INFOSETS, MASTER data.

Using multi provider you can access data from different data sources like cubes, ODS, infosets, master data.

Prior to 3.x only MULTI CUBES were AVAILABLE; you cannot COMBINE a ODS and cube.

Prior to 3.x only multi cubes were available; you cannot combine a ODS and cube.