Explore topic-wise InterviewSolutions in .

An info PROVIDER giving data by JOINING data from DIFFERENT SOURCES like ODS, MASTER data, etc.

An info provider giving data by joining data from different sources like ODS, master data, etc.

MULTI provider is a UNION whereas INFOSET is a “JOIN” (intersection).

Multi provider is a Union whereas infoset is a “Join” (intersection).

No; only ODS and MASTER DATA are ALLOWED.

No; only ODS and master data are allowed.

Only ONE CHARACTERISTIC is allowed PER line item dimension.

Only one characteristic is allowed per line item dimension.

These CUBES are used for both READ and WRITE; standard cubes are optimized for reading. The TRANSACTIONAL cubes are used in SEM.

These cubes are used for both read and write; standard cubes are optimized for reading. The transactional cubes are used in SEM.

RSRCACHE.

RSRCACHE.

YES EITHER globally or using query DEBUG TOOL RSRT.

Yes either globally or using query debug tool RSRT.

a. all characteristics with CONVERSION exit ALPHA, NUMC and GJAF[R].
B. all characteristics which are compounded to the EARLIER.

a. all characteristics with conversion exit ALPHA, NUMC and GJAF[R].
b. all characteristics which are compounded to the earlier.

Yes.

Yes.

if you are UPGRADING you MUST do it before PREPARE PHASE of UPGRADE.

if you are upgrading you must do it before PREPARE phase of upgrade.

This defines the maximum SIZE of packet, max no of RECORDS per packet, the number of PARALLEL processes, ETC.

This defines the maximum size of packet, max no of records per packet, the number of parallel processes, etc.

This defines the characteristic attributes; for EXAMPLE the object MATERIALNR defines the attributes of MATERIAL master LIKE the length, ETC.

This defines the characteristic attributes; for example the object MATERIALNR defines the attributes of material master like the length, etc.

USING TRANSACTION RSKC.

Using transaction RSKC.

Defines the LEVEL of PERCENTAGE change for realignment RUN will cause a reconstruction of aggregates.

Defines the level of percentage change for realignment run will cause a reconstruction of aggregates.

Defines whether the MASTER data (auto sid) is ADDED automatically for NON existing master data when you LOAD transaction data.

Defines whether the master data (auto sid) is added automatically for non existing master data when you load transaction data.

Defines number of PARALLEL PROCESSORS in ACTIVATION, mm number of DATA records and wait time.

Defines number of parallel processors in activation, mm number of data records and wait time.

RSCUSTV3.

RSCUSTV3.

These kinds of key figures are not summarized (unlike sales, etc); EXAMPLES are head count, inventory AMOUNT; these are always in relation to a point in TIME; for example we will ask how many EMPLOYEES we had as of last QUARTER. We don’t add up the head count.

These kinds of key figures are not summarized (unlike sales, etc); examples are head count, inventory amount; these are always in relation to a point in time; for example we will ask how many employees we had as of last quarter. We don’t add up the head count.

Standard aggregation -> specifies how a key figure is compressed USING all characteristics EXCEPT TIME; exception aggregation -> specifies how key figure is compressed using time characteristics.

Standard aggregation -> specifies how a key figure is compressed using all characteristics except time; exception aggregation -> specifies how key figure is compressed using time characteristics.

These are non CUMULATIVE CHANGES used to GET the right QUANTITY.

These are non cumulative changes used to get the right quantity.

Non CUMULATIVE are stored USING a “MARKER” for the current PERIOD.

Non cumulative are stored using a “Marker” for the current period.

Is a TIME CHARACTERISTIC which DETERMINES all other time characteristic; OCALDAY, OCALMONTH, OCALWEEK, OFISCPER.

Is a time characteristic which determines all other time characteristic; OCALDAY, OCALMONTH, OCALWEEK, OFISCPER.

2LIS_03_BF and 2LIS_03_UM.

2LIS_03_BF and 2LIS_03_UM.

When you START LOADING inventory data from R13 you start with a certain POINT in time; this is what is called opening balance; assume that you have inventory SINCE Jan 2002; you are loading data on Jan 2003 and the opening balance for the product is 200; the data before Jan 2003 is “HISTORIC data”; any data loaded after Jan 2003 is a delta load.

When you start loading inventory data from R13 you start with a certain point in time; this is what is called opening balance; assume that you have inventory since Jan 2002; you are loading data on Jan 2003 and the opening balance for the product is 200; the data before Jan 2003 is “Historic data”; any data loaded after Jan 2003 is a delta load.

if you CHOOSE this option when compressing Non cumulative cube, the reference point is not updated but the requests are moved to Request 0 (USUAL compression); you must do this for compressing historical DATA; for example USE this option to COMPRESS data before Jan 2003;

if you choose this option when compressing Non cumulative cube, the reference point is not updated but the requests are moved to Request 0 (usual compression); you must do this for compressing historical data; for example use this option to compress data before Jan 2003;

a. initialize opening balance in R/3 (S278)
b. activate extract structure MCO3BFO for data source 2LIS_03_BF
c. set up HISTORICAL material documents in R/3
d. load opening balance using data source 2LIS_40_S278
e. load historical movements and compress without MARKER UPDATE.
f. set up V3 update
G. load DELTAS using 2LIS_03_BF

a. initialize opening balance in R/3 (S278)
b. activate extract structure MCO3BFO for data source 2LIS_03_BF
c. set up historical material documents in R/3
d. load opening balance using data source 2LIS_40_S278
e. load historical movements and compress without marker update.
f. set up V3 update
g. load deltas using 2LIS_03_BF

That determines validity PERIOD of non cumulative cube; EXAMPLE PLANTS opening and CLOSING different time PERIODS.

That determines validity period of non cumulative cube; example plants opening and closing different time periods.

DEFINES the FIELDS for AUTHORIZATION CHECKS.

Defines the fields for authorization checks.

PFCG.

PFCG.

All the BW roles START with S_RS; S_RS_ROPAD- PRODUCTION SYSTEM administrator; S_RS_RREPU — BEX user.

All the BW roles start with S_RS; S_RS_ROPAD- Production system administrator; S_RS_RREPU — bex user.

a. infocube based approach — USE this in conjunction with Info area to limit access.
b. query name based approach — many customers use this to limit access; for z queries are read only, Y queries are read/write; FI* query names for H use, etc.
c. DATASET approach — limitation of characteristics and KEY figures; you can use REPORTING authorization for this.

a. infocube based approach — use this in conjunction with Info area to limit access.
b. query name based approach — many customers use this to limit access; for z queries are read only, Y queries are read/write; FI* query names for H use, etc.
c. Dataset approach — limitation of characteristics and key figures; you can use reporting authorization for this.

BW Warehouse AUTHORIZATION - SAP standard; BW REPORTING — Not delivered by SAP — user has to CREATE.

BW Warehouse authorization - SAP standard; BW Reporting — Not delivered by SAP — user has to create.

10.

10.

CREATE, CHANGE and DISPLAY.

Create, change and display.

a. S_RS_IOMAD - Master data
b. S_RS_ADMWB - AWB OBJECTS
c. S_RS_ODSO - ODS objects
d. S_RS_TOOLS — BEX tools
e. S_RS_ICUBE - INFO cube
f. S...RS_HIER — hierarchy
g. S_RS_COMP, S_RS_COMP1 - reporting authorization
h. S_RS_FOLD - folders
i. S_RS_IOBJ — info object
j. S_RS_ISOUR — info source (transaction data)
K. S_RSJSRCM - info source (master data)
1. S_GUI - GUI Activities (workbooks)
m. S_BDS_DS — document set (for workbooks)
n. S_USER_AGR — role check for saving workbook in a role
o. S_USER_TCD — transaction in roles for saving workbook in a role

a. S_RS_IOMAD - Master data
b. S_RS_ADMWB - AWB objects
c. S_RS_ODSO - ODS objects
d. S_RS_TOOLS — Bex tools
e. S_RS_ICUBE - info cube
f. S...RS_HIER — hierarchy
g. S_RS_COMP, S_RS_COMP1 - reporting authorization
h. S_RS_FOLD - folders
i. S_RS_IOBJ — info object
j. S_RS_ISOUR — info source (transaction data)
k. S_RSJSRCM - info source (master data)
1. S_GUI - GUI Activities (workbooks)
m. S_BDS_DS — document set (for workbooks)
n. S_USER_AGR — role check for saving workbook in a role
o. S_USER_TCD — transaction in roles for saving workbook in a role

This is used for BW reporting to CHECK authorizations by the OLAP processor.

This is used for BW reporting to check authorizations by the OLAP processor.

a. create profile USING transaction OOSP
b. assign user to profile using transaction OOSB
c. update T77UU table
d. run the program RHBAUSOO
e. activate the DATA source and related components OHR_PA_2 in BW
f. load ODS from R13
G. activate target info objects as “AUTHORIZATION relevant”
h. run the function module RSSB to generate BW authorization.

a. create profile using transaction OOSP
b. assign user to profile using transaction OOSB
c. update T77UU table
d. run the program RHBAUSOO
e. activate the data source and related components OHR_PA_2 in BW
f. load ODS from R13
g. activate target info objects as “Authorization relevant”
h. run the function module RSSB to generate BW authorization.

S_RS_COMP1 checks for authorization depending on the owner;
S_RS_FOLD info AREA view of BEX elements (to suppress); S_RS_ISET for info sets; S_GUI new ACTIVITY CODE 60 LOADED for upload.

S_RS_COMP1 checks for authorization depending on the owner;
S_RS_FOLD info area view of Bex elements (to suppress); S_RS_ISET for info sets; S_GUI new activity code 60 loaded for upload.

a. it ENABLES queries that do not contain a authorization relevant object that have been checked in info CUBE.
b. it allows summary data to be displayed if the user does not have access to detailed data; for example if you create 2 authorizations for ONE user one with Sales Org and customers and second with sales org 1000 and customers the user sees all customers for sales org 1000 and only SUMMARIZED report for other sales org.

a. it enables queries that do not contain a authorization relevant object that have been checked in info cube.
b. it allows summary data to be displayed if the user does not have access to detailed data; for example if you create 2 authorizations for one user one with Sales Org and customers and second with sales org 1000 and customers the user sees all customers for sales org 1000 and only summarized report for other sales org.

You use $ followed by a variable NAME (values POPULATED in user EXIT for bex); this AVOIDS having too many roles.

You use $ followed by a variable name (values populated in user exit for bex); this avoids having too many roles.

This is USED in HIERARCHY AUTHORIZATION.

This is used in hierarchy authorization.

USING TRANSACTIONS STOI and RSSMTRACE; a ‘X’ mark in the log shows a FAILED AUTHORIZATION check.

Using transactions STOI and RSSMTRACE; a ‘X’ mark in the log shows a failed authorization check.

To MINIMIZE SPACE, QUERY PERFORMANCE, LOAD performance.

To minimize space, query performance, load performance.

ADK ARCHIVE DEVELOPMENT KIT.

ADK Archive Development Kit.

SARA.

SARA.

a. Max FILE SIZE in M BYTE .
B. Max no of DATA objects.

a. Max file size in M byte .
b. Max no of data objects.

When you archive info cube or ODS, it is LOCKED for any loads TILL the delete is finished; you should make SURE that you archive and delete before you LOAD any new DATA.

When you archive info cube or ODS, it is locked for any loads till the delete is finished; you should make sure that you archive and delete before you load any new data.

You can restore in to ODS DIRECTLY from SARA transaction; for cube you should schedule an INFO PACKAGE.

You can restore in to ODS directly from SARA transaction; for cube you should schedule an info package.

Process chain is a utility to SCHEDULE batch jobs on BW LIKE SM37; it OFFERS good monitoring features and error handling.

Process chain is a utility to schedule batch jobs on BW like SM37; it offers good monitoring features and error handling.

RSPC.

RSPC.