Steps to do LO Extraction

Lo Extrection

Get your own at Scribd or explore others: Education Certificate Programs

Update types in BW/BI

With the update type, you control whether a key figure/data field is updated in the InfoProvider.
Functions
For InfoCubes:

· Depending on the aggregation type you entered in the Key Figure Maintenance for this key figure, you are given the options Addition or Maximum or Minimum. If you choose one of these options, new values are updated in the InfoCube.

The aggregation type (addition, minimum & maximum) determines how key figures are updated where primary keys are the same. Thus the total, the minimum or the maximum for these values is formed for new values.

If you entered one of these aggregation types in the key figure definition, it is transferred for the update. Otherwise, the aggregation type addition is automatically selected.

· If you choose no update, the key figures are not updated in the InfoCube, meaning that no data records are written in the InfoCube with the first data transfer, or that data records that already exist, will remain in place with subsequent transfers.
For InfoObjects:

Only the Overwrite option is available. With this option, new values are updated to the InfoObject.
For ODS Objects:

1. Depending on the type of data and DataSource, you have the options Addition, Minimum, Maximum or Overwrite. If you choose one of these options, new values are updated in the ODS object.

For numerical data fields, you are given a proposal for the update type through the characteristic 0RECORDMODE. If only the after-image is delivered, the system proposes Overwrite. However, it could make sense to change this: For example, with the meter data field “# Changes”, which is filled with a constant 1 but still has to be updated through addition, although only an after-image is delivered.

Characteristic 0RECORDMODE is used to pass indicators of the DataSource (from SAP systems) to the update.

You do not need characteristic 0RECORDMODE as long as you do not load delta requests in the ODS object or only from file DataSources.

a. Addition:

Addition is not supported with the data types CHAR, DAT, TIMS, CUKY and UNIT. To be able to use the addition function, make sure the DataSource is compatible with an additive delta.

b. Overwrite:

Whether overwriting is supported is determined by the delta-compatibility of the DataSource.

In this example, the order quantity changes after it has been loaded into BW. With the second load process the data is overwritten since it has the same primary key.

First load process

Document No.	Document Item	Order Quantity	Unit of measure
100001	10	200	Pieces
100001	20	150	Pieces
100002	10	250	Kg

Second load process

Document No.	Document Item	Order Quantity	Unit of measure
100001	10	180	Pieces
100001	20	165	Pieces

When you update data, the system keeps to the time sequence of the data packages and requests. You have to decide the logical order of the update yourself. Meaning, for example, orders must be requested before deliveries; otherwise the wrong results may appear when you overwrite the data.

c. If you choose no update, the data fields are not updated in the ODS object, meaning that no data records are written in the ODS object with the first data transfer, or that data records that already exist will remain in place with subsequent transfers.

Info object creation

Info Objects Creation - Upload a Document to Scribd

Function module creation

Function Module - Upload a Document to Scribd

New features in process chains

In Netweaver BI 2004s we can find many new features in process chains. Below I have listed some of them

Copying of process chains:In BI 2004s there is a copy option in the process chain menu.

Go to RSPC -----> Process chain ----> Copy. Enter the technical name and description, save it and click on refresh button. You can see the new process chain in the list.

Client dependent: We have a option of assigning a particular process chain to a particular client.



Go to RSPC ----> Process chain ----> Attributes. Enter client id and save it. Once you assign, the process chain can only monitored in this client. Note: Process variants which are used in one client will not be used in other client.

Display mode: Display, here in BI 2004s we don't have locking issues. One user may change the process chain while the other is just displaying it. Process chain can be scheduled in display mode.



Authorization for process chain: There is a new authorization object on process chian itself S_RS_PC which checks on the sub objects:
.DEFINITION, the activities display(03) and change(23),
.PROTOCOLS, the activity deletion(06),
.RUNTIME, the activity execution(16).

Some new Process Types:

Decision between Multiple Alternatives:

This process Supports if (condition1) then (event1) elseif; decisions up to 99 resulting events and an error event can be defined.

Once you put all conditions in the process type, then when you connect a link between decision process type to the next process, it will asks on what condition you need to proceed to next process type.
You can find the process type in "General Services".



Data Transfer Process:

This proess is used for automatically load data into an Infoprovider. It is just like an info package.
You can find the process type in "Load process and post-processing".



Close Request of Real-Time Infopackage:

With this process type, you can close an open PSA request for a Web service DataSource or a DataSource for real-time data acquisition in an SAP source system before the entry value is reached.
You can find the process type in "Load process and post-processing".



Archive Data from Info Provider:

This process type is used to automate the Archiving data from info provider.
You can find the process type in "Data Target Administration".



Deletion of Request from the Change log:

This process is used for deleting data from the change log of a DataStore object is which are no longer needed for the delta update.
You can find the process type in "Other BW Processes".



Switch Real time Infocube to Plan mode & Switch Real time Infocube to Load mode:

This both process types are used to automate the process of converting real time Infocube to plan mode or load mode.
You can find the process types in "Other BW Processes".

key performance indicators

If you are struggling to define your company's key performance indicators (KPIs), here is a useful bit of information. I recently discovered an interesting website dedicated to identifying KPIs for just about every category you can think of. And it is FREE!

Yes, indeed -- a website described as "The free Key Performance Indicator (KPI) Library is a community of business professionals that provides guidance in identifying and prioritizing the KPIs that really matter for your organization's success." The categories include business, compliance & legislation, environmental, finance, HR, IT, outsourcing, procurement, project portfolio, R & D, supply chain & logistics, and many others. Warning -- you have to register to use the site but I found it quite useful.

The site contains (at the time of this posting) 943 KPIs. Here are a few by name:

Market share gain comparison %
Ad click-through ratio (CTR)
Cash dividends paid
Share price
Perfect Order Measure
Average customer recency
Average number of trackbacks per post
Number of past due loans
% of service requests posted via web (self-help)
Total energy used per unit of production
Cumulative Annual Growth Rate (CAGR)

With each entry, you get a definition, the category it belongs to, and the ability to share it using any number of book marking applications. You can also comment on the KPI and add your own to the listing. As an example, here is the entry for Cumulative Annual Growth Rate (CAGR):

"This tells the story about any company as to what rate the company has grown over years irrespective of consistency in growth YoY basis. A company might have one successful year and then a bad year. If you compare the growth rate YoY basis it may give a different picture and be concluded as lack of consistency in management. But if one looks at the CAGR, it will explain the real growth over years. It is calculated as:

=Power(Revenue Year (n)/Revenue Year(1),1/n) - 1

Where, Revenue Year (n)= n-th year Revenue Revenue Year(1) = 1st year Revenue"

And on it goes...

Variable Types

Types of Variables:

The type of variable being used. This determines the object that the variable represents as a placeholder for a concrete value.

Structure

There are different types of variables depending on the object for which you want to define variables. These types specify where you can use the variables.

· Characteristic Value Variables

Characteristic value variables represent characteristic values and can be used wherever characteristic values are used.

If you restrict characteristics to specific characteristic values, you can also use characteristic value variables.

· Hierarchy Variables

Hierarchy variables represent hierarchies and can be used wherever hierarchies can be selected.

If you restrict characteristics to specific hierarchies or select presentation hierarchies, you can also use hierarchy variables.

· Hierarchy Node Variables

Hierarchy node variables represent a node in a hierarchy and can be used wherever hierarchy nodes are used.

If you restrict characteristics to specific hierarchy nodes, you can also use hierarchy node variables.

· Text Variables

Text variables represent a text and can be used in descriptions of queries, calculated key figures and structural components.

BW Architecture

Data flow in BW

Questions and answers of V3 Update

V3 update: Questions and answers

Question 1
Update records are written to the SM13, although you do not use the extractors from the logistics cockpit (LBWE) at all.
Active datasources have been accidentally delivered in a PI patch.For that reason, extract structures are set to active in the logistics cockpit. Select transaction LBWE and deactivate the active structures. From now on, no additional records are written into SM13.
If the system displays update records for application 05 (QM) in transaction SM13, even though the structure is not active, see note 393306 for a solution.

Question 2
How can I selectively delete update records from SM13?
Start the report RSM13005 for the respective module (z.B. MCEX_UPDATE_03).

• Status COL_RUN INIT: without Delete_Flag but with VB_Flag (records are updated).

• Status COL_RUN OK: with Delete_Flag (the records are deleted for all modules with COL_RUN -- OK)

With the IN_VB flag, data are only deleted, if there is no delta initialization. Otherwise, the records are updated.
MAXFBS : The number of processed records without Commit.

ATTENTION: The delta records are deleted irrevocably after executing report RSM13005 (without flag IN_VB). You can reload the data into BW only with a new delta-initialization!

Question 3
What can I do when the V3 update loops?
Refer to Note 0352389. If you need a fast solution, simply delete all entries from SM13 (executed for V2), however, this does not solve the actual problem.

ATTENTION: THIS CAUSES DATA LOSS. See question 2 !

Question 4
Why has SM13 not been emptied even though I have started the V3 update?

• The update record in SM13 contains several modules (for example, MCEX_UPDATE_11 and MCEX_UPDATE_12). If you start the V3 update only for one module, then the other module still has INIT status in SM13 and is waiting for the corresponding collective run. In some cases, the entry might also not be deleted if the V3 update has been started for the second module.In this case, schedule the request RSM13005 with the DELETE_FLAG (see question 2).

• V3 updating no longer functions after the PI upgrade because you did not load all the delta records into the BW system prior to the upgrade.Proceed as described in note 328181.

Question 5
The entries from SM13 have not been retrieved even though I followed note 0328181!
Check whether all entries were actually deleted from SM13 for all clients. Look for records within the last 25 years with user * .

Question 6
Can I schedule V3 update in parallel?
The V3 update already uses collective processing.You cannot do this in parallel.

Question 7
The Logistics Cockpit extractors deliver incorrect numbers. The update contains errors !
Have you installed the most up-to-date PI in your OLTP system?
You should have at least PI 2000.1 patch 6 or PI 2000.2 patch 2.

Question 8
Why has no data been written into the delta queue even though the V3 update was executed successfully?
You have probably not started a delta initialization. You have to start a delta initialization for each DataSource from the BW system before you can load the delta.Check in RSA7 for an entry with a green status for the required DataSource. Refer also to Note 0380078.

Question 9
Why does the system write data into the delta queue, even though the V3 update has not been started?
You are using the automatic goods receipt posting (transaction MRRS) and start this in the background.In this case the system writes the records for DataSources of application 02 directly into the delta queue (RSA7).This does not cause double data records.This does not result in any inconsistencies.

Question 10
Why am I not able to carry out a structural change in the Logistics Cockpit although SM13 is blank?
Inconsistencies occurred in your system. There are records in update table VBMOD for which there are no entries in table VBHDR. Due to those missing records, there are no entries in SM13. To remove the inconsistencies, follow the instructions in the solution part of Note 67014. Please note that no postings must be made in the system during reorganization in any case!

Question 11
Why is it impossible to plan a V3 job from the Logistics Cockpit?
The job always abends immediately. Due to missing authorizations, the update job cannot be planned. For further information see Note 445620.

New Terms in BI

Differences between BW 3.5 and BI 7.0

Major Differences between Sap Bw 3.5 & sapBI 7.0 version:

1. In Infosets now you can include Infocubes as well.

2. The Remodeling transaction helps you add new key figure and characteristics and handles historical data as well without much hassle. This is only for info cube.

3. The BI accelerator (for now only for infocubes) helps in reducing query run time by almost a factor of 10 - 100. This BI accl is a separate box and would cost more. Vendors for these would be HP or IBM.

4. The monitoring has been imprvoed with a new portal based cockpit. Which means you would need to have an EP guy in ur project for implementing the portal ! :)

5. Search functionality hass improved!! You can search any object. Not like 3.5

6. Transformations are in and routines are passe! Yess, you can always revert to the old transactions too.

7. The Data Warehousing Workbench replaces the Administrator Workbench.

8. Functional enhancements have been made for the DataStore object:
New type of DataStore object
Enhanced settings for performance optimization of DataStore objects.

9. The transformation replaces the transfer and update rules.

10. New authorization objects have been added

11. Remodeling of InfoProviders supports you in Information
Lifecycle Management.

12 The Data Source:
There is a new object concept for the Data Source.
Options for direct access to data have been enhanced.
From BI, remote activation of Data Sources is possible in SAP source systems.

13.There are functional changes to the Persistent Staging Area (PSA).

14.BI supports real-time data acquisition.

15 SAP BW is now known formally as BI (part of NetWeaver 2004s). It implements the Enterprise Data Warehousing (EDW). The new features/ Major differences include:
a) Renamed ODS as DataStore.
b) Inclusion of Write-optmized DataStore which does not have any change log and the requests do need any activation
c) Unification of Transfer and Update rules
d) Introduction of "end routine" and "Expert Routine"
e) Push of XML data into BI system (into PSA) without Service API or Delta Queue
f) Intoduction of BI accelerator that significantly improves the performance.
g) Load through PSA has become a must. I am not too sure about this. It looks like we would not have the option to bypass the PSA Yes,

16. Load through PSA has become a mandatory. You can't skip this, and also there is no IDoc transfer method in BI 7.0. DTP (Data Transfer Process) replaced the Transfer and Update rules. Also in the Transformation now we can do "Start Routine, Expert Routine and End Routine". during data load.

New features in BI 7 compared to earlier versions:

i. New data flow capabilities such as Data Transfer Process (DTP), Real time data Acquisition (RDA).

ii. Enhanced and Graphical transformation capabilities such as Drag and Relate options.

iii. One level of Transformation. This replaces the Transfer Rules and Update Rules

iv. Performance optimization includes new BI Accelerator feature.

v. User management (includes new concept for analysis authorizations) for more flexible BI end user authorizations.

Need to delete data...? for enhancing datasource..?

No need to delete any data in BW or R/3 side for enhancing datasource if loading data into ODS in overwrite mode.

Simply follow the below steps:

1. Add new fields to ODS & cubes and adjust update rules.

2. Clear LBWQ(update queue - Run V3 job only).

3. Clear RSA7(Delta queue - Run infopak to pull data into bw)

4. Move datasource changes to Production, replicate and activate transfer rules.

5. Delete data in LBWG(setup tables).

6. Fill setup tables for historic data.

7. Initialize datasource if required, without data transfer(Zero initialization).

8. Pull data from R/3 to BW ODS in overwrite mode with Repair Full option.

Loading data in overwrite mode, so no problem, Just load again historic data as well. and push delta from ODS to further(ods/cube).

9. Push delta from ODS to CUBE.

Creation of Infoobjects

Creation of Infoobject Chars and Keyfigures

Extracts

Extracts:

Since internal tables have fixed line structures, they are not suited to handle data sets with varying structures. Instead, you can use extract datasets for this purpose.

An extract is a sequential dataset in the memory area of the program. You can only address the entries in the dataset within a special loop. The index or key access permitted with internal tables is not allowed. You may only create one extract in any ABAP program. The size of an extract dataset is, in principle, unlimited. Extracts larger than 500KB are stored in operating system files. The practical size of an extract is up to 2GB, as long as there is enough space in the filesystem.

An extract dataset consists of a sequence of records of a pre-defined structure. However, the structure need not be identical for all records. In one extract dataset, you can store records of different length and structure one after the other. You need not create an individual dataset for each different structure you want to store. This fact reduces the maintenance effort considerably.

In contrast to internal tables, the system partly compresses extract datasets when storing them. This reduces the storage space required. In addition, you need not specify the structure of an extract dataset at the beginning of the program, but you can determine it dynamically during the flow of the program.

You can use control level processing with extracts just as you can with internal tables. The internal administration for extract datasets is optimized so that it is quicker to use an extract for control level processing than an internal table.

Procedure for creating an extract:

1. Define the record types that you want to use in your extract by declaring them as field groups. The structure is defined by including fields in each field group. ----- Defining an Extract -----
2. Fill the extract line by line by extracting the required data.------ Filling an Extract with Data -----
3. Once you have filled the extract, you can sort it and process it in a loop. At this stage, you can no longer change the contents of the extract. ------ Processing Extracts ------

Dimensions

Dimensions:

Fact table and the relevant dimension tables of an InfoCube are connected with one another relationally using the dimension keys. The dimension key is provided by the system per characteristic combination in a dimension table.

• With the execution of a query the OLAP processor checks the dimension tables of the InfoCube to be evaluated for the characteristic combinations required in the selection.
• The dimension keys determined in this way point the way to the information in the fact table.
• Dimension tables consist of a maximum of 248 characteristics.
• The Time dimension holds the time characteristics needed for analysis.
• The Unit dimension contains the unit of measure and currency characteristics needed to describe the key figures properly.

The Data Packet dimension is used to identify discrete packets of information loaded into the InfoCube. In this way, packets can be deleted, reloaded or maintained individually

InfoCubes are made up of a number of InfoObjects. All InfoObjects (characteristics and key figures) are available InfoCube-independently. Characteristics relate to master data with their attributes and text descriptions.

An InfoCube consists of several InfoObjects and is structured according to the star schema. This means there is a (large) fact table that contains the key figures for the InfoCube as well as several (smaller) dimension tables which surround it. The characteristics of the InfoCube are stored in these dimensions.

An InfoCube fact table only contains key figures, in contrast to an ODS object, whose data part can also contain characteristics. The characteristics of an InfoCube are stored in its dimensions.

The dimensions and the fact table are linked to one another via abstract identification numbers (dimension IDs), which are in the key part of the particular database table. As a result, the key figures of the InfoCube relate to the characteristics of the dimension. The characteristics determine the granularity (the degree of fineness), in which the key figures are managed in the InfoCube.

Characteristics that logically belong together (district and area, for example, belong to the regional dimension) are grouped together in a dimension. By adhering to this design criterion, dimensions are to a large extent independent of each other, and dimension tables remain small with regards to data volume, which is desirable for reasons of performance. This InfoCube structure is optimized for Reporting.

What Is SPRO In BW Project?

1) What is spro?
2) How to use in bw project?
3) What is difference between idoc and psa in transfer methods?

1. SPRO is the transaction code for Implementation Guide, where you can do configuration settings.
* Type spro in the transaction box and you will get a screen customizing :
Execute Project.
* Click on the SAP Reference IMG button. you will come to Display IMG Screen.
* The following path will allow you to do the configuration settings :
SAP Cutomizing Implementation Guide -> SAP Netweaver ->SAP Business Warehouse Information.

2. SPRO is used to configure the following settings :
* General Settings like printer settings, fiscal year settings, ODS Object Settings, Authorisation settings, settings for displaying SAP Documents, etc., etc.,
* Links to other systems : like links between flat files and BW Systems, R/3 and BW, and other data sources, link between BW system and Microsoft Analysis services, and crystal enterprise....etc., etc.,
* UD Connect Settings : Like configuring BI Java Connectors, Establishing the RFC Desitination for SAP BW for J2EEE Engine, Installation of Availability monitoring for UD Connect.
* Automated Processes: like settings for batch processes, background processes etc., etc.,
* Transport Settings : like settings for source system name change after transport and create destination for import post-processing.
* Reporting Relevant Settings : Like Bex Settings, General Reporting Settings.
* Settings for Business Content : which is already provided by SAP.

3. PSA : Persistant Staging Area : is a holding area of raw data. It contains detailed requests in the format of the transfer structure. It is defined according to the Datasource and source system, and is source system dependent.

IDOCS : Intermediate DOCuments : Data Structures used as API working storage for applications, which need to move data in or out of SAP Systems.

Difference Between PSA, ALE

how data is transferd using PSA&IDoc

The following update types are available in SAP BW:
1. PSA
2. ALE (data IDoc)

You determine the PSA or IDoc transfer method in the transfer rule maintenance screen. The process for loading the data for both transfer methods is triggered by a request IDoc to the source system. Info IDocs are used in both transfer methods. Info IDocs are transferred exclusively using ALE

A data IDoc consists of a control record, a data record, and a status record The control record contains, for example, administrative information such as the receiver, the sender, and the client. The status record describes the status of the IDoc, for example, "Processed". If you use the PSA for data extraction, you benefit from increased flexiblity (treatment of incorrect data records). Since you are storing the data temporarily in the PSA before updating it in to the data targets, you can check the data and change it if necessary. Unlike a data request with IDocs, the PSA gives you various options for additional data updates into data targets:

InfoObject/Data Target Only - This option means that the PSA is not used as a temporary store. You choose this update type if you do not want to check the source system data for consistency and accuracy, or you have already checked this yourself and are sure that you no longer require this data since you are not going to change the structure of the data target again.

PSA and InfoObject/Data Target in Parallel (Package by Package) - BW receives the data from the source system, writes the data to the PSA and at the same time starts the update into the relevant data targets. Therefore, this method has the best performance.

The parallel update is described in detail in the following: A dialog process is started by data package, in which the data of this package is writtein into the PSA table. If the data is posted successfully into the PSA table, the system releases a second, parallel dialog process that writes the data to the data targets. In this dialog process the transfer rules for the data records of the data package are applied, that data is transferred to the communcation structure, and then written to the data targets. The first dialog process (data posting into the PSA) confirms in the source system that is it completed and the source system sends a new data package to BW while the second dialog process is still updating the data into the data targets.

The parallelism relates to the data packages, that is, the system writes the data packages into the PSA table and into the data targets in parallel. Caution: The maximum number of processes setin the source system in customizing for the extractors does not restrict the number of processes in BW. Therefore, BW can require many dialog processes for the load process. Ensure that there are enough dialog processes available in the BW system. If there are not enough processes on the system side, errors occur. Therefore, this method is the least recommended.

PSA and then into InfoObject/Data Targets (Package by Package) - Updates data in series into the PSA table and into the data targets by data package. The system starts one process that writes the data packages into the PSA table. Once the data is posted successfuly into the PSA table, it is then written to the data targets in the same dialog process. Updating in series gives you more control over the overall data flow when compared to parallel data transfer since there is only one process per data package in BW. In the BW system the maximum number of dialog process required for each data request corresponds to the setting that you made in customizing for the extractors in the control parameter maintenance screen. In contrast to the parallel update, the system confirms that the process is completed only after the data has been updated into the PSA and also into the data targets for the first data package.

Only PSA - The data is not posted further from the PSA table immediately. It is useful to transfer the data only into the PSA table if you want to check its accuracy and consistency and, if necessary, modify the data. You then have the following options for updating data from the PSA table:

Automatic update - In order to update the data automatically in the relevant data target after all data packages are in the PSA table and updated successfully there, in the scheduler when you schedule the InfoPackage, choose Update Subsequently in Data Targets on the Processing tab page.

Interview Questions

Interview Questions:

1. Identify the statement(s) that is/are true. A change run...

a. Activates the new Master data and Hierarchy data
b. Aggregates are realigned and recalculated
c. Always reads data from the InfoCube to realign aggregates
d. Aggregates are not affected by change run

1: A, B

2. Which statement(s) is/are true about Multiproviders?

a. This is a virtual Infoprovider that does not store data
b. They can contain InfoCubes, ODSs, info objects and info sets
c. More than one info provider is required to build a Multiprovider
d It is similar to joining the data tables

2: A, B

3. The structure of the PSA table created for an info source will be...

a. Featuring the exact same structure as Transfer structure
b. Similar to the transfer rules
c. Similarly structured as the Communication structure
d. The same as Transfer structure, plus four more fields in the beginning

3: D

4. In BW, special characters are not permitted unless it has been defined using this transaction:

a. rrmx
b. rskc
c. rsa15
d. rrbs

4: B

5. Select the true statement(s) about info sources:

a. One info source can have more than one source system assigned to it
b. One info source can have more than one data source assigned to it provided the data sources are in different source systems
c. Communication structure is a part of an info source
d. None of the above

5: A, C

6. Select the statement(s) that is/are true about the data sources in a BW system:

a. If the hide field indicator is set in a data source, this field will not be transferred to BW even after replicating the data source
b. A field in a data source won't be usable unless the selection field indicator has been set in the data source
c. A field in an info package will not be visible for filtering unless the selection field has been checked in the data source
d. All of the above

6: A, C

7. Select the statement(s) which is/are true about the 'Control parameters for data transfer from the Source System':

a. The table used to store the control parameters is ROIDOCPRMS
b. Field max lines is the maximum number of records in a packet
c. Max Size is the maximum number of records that can be transferred to BW
d. All of the above

7: A

8. The indicator 'Do not condense requests into one request when activation takes place' during ODS activation applies to condensation of multiple requests into one request to store it in the active table of the ODS.

a. True
b. False

8: B

9. Select the statement(s) which is/are not true related to flat file uploads:

a. CSV and ASCII files can be uploaded
b. The table used to store the flat file load parameters is RSADMINC
c. The transaction for setting parameters for flat file upload is RSCUSTV7
d. None of the above

9: C

10. Which statement(s) is/are true related to Navigational attributes vs Dimensional attributes?

a. Dimensional attributes have a performance advantage over Navigational attributes for queries
b. Change history will be available if an attribute is defined as navigational
c. History of changes is available if an attribute is included as a characteristic in the cube
d. All of the above

10: A, C

11. When a Dimension is created as a line item dimension in a cube, Dimensions IDs will be same as that of SIDs.

a. True
b. False

11: A

12. Select the true statement(s) related to the start routine in the update rules:

a. All records in the data packet can be accessed
b. Variables declared in the global area is available for individual routines
c. Returncode greater than 0 will be abort the whole packet
d. None of the above

12: A, B, C

13. If a characteristic value has been entered in InfoCube-specific properties of an InfoCube, only these values can be loaded to the cube for that characteristic.

a. True
b. False

13: A

14. After any changes have been done to an info set it needs to be adjusted using transaction RSISET.

a. True
b. False

14: A

15. Select the true statement(s) about read modes in BW:

a. Read mode determines how the OLAP processor retrieves data during query execution and navigation
b. Three different types of read modes are available
c. Can be set only at individual query level
d. None of the above

15: A, B

What is BDC and How you use it?

What is BDC
During data transfer, data is transferred from an external system into the SAP
R/3 System. •Transfer data from an external system into an R/3 System as it is
installed. •Transfer data regularly from an external system into an R/3 System.

Example: If data for some departments in your company is input using a system
other than the R/3 System, you can still integrate this data in the R/3 System. To do
this, you export the data from the external system and use a data transfer method to
import it into the R/3 System.
Batch input with batch input sessions : Data consistency check with the help of
screen logic.

With the batch input method, an ABAP program reads the external data that is to be
entered in the R/3 System and stores the data in a "batch input session". The
session records the actions that are required to transfer data into the system using
normal SAP transactions.

When the program has generated the session, you can run the session to execute
the SAP transactions in it. You can explicitly start and monitor a session with the
batch input management function (by choosing System ® Services ® Batch input), or
have the session run in the background processing system.

Use the BDC_OPEN_GROUP function module to create a new session. Once you
have created a session, then you can insert batch input data into it with
BDC_INSERT. Use the BDC_INSERT function module to add a transaction to a
batch input session. Use the BDC_CLOSE_GROUP function module to close a
session after you have inserted all of your batch input data into it.

Download a pdf of BDC&LSMW
http://www.savefile.com/files/799694