Explore topic-wise InterviewSolutions in .

The transfer method only determines how the data is transferred.

IDoc transfer method: A data IDoc consists of a control record, a data record, and a status record. The control record contains administration information such as receiver, sender, and client. The status record describes the status of the IDoc, for example "MODIFIED". The data stores in the ALE INBOX and outbox have to be emptied or reorganized.

PSA (tRFC) transfer method: With this transfer method, a transactional Remote Function Call is used to transfer the data directly from the source system to the SAP BW. Here, there is the option of STORING the data in the PSA (the tables have the same structure as the transfer structure.) This is the preferred transfer method, because it improves performance BETTER than the IDoc method. When you USE tRFCs to transfer data, the maximum number of fields that can be used is restricted to 255. The length of a data record is also restricted to 1962 bytes when you use tRFCs (IDoc --> 1000 bytes.)

The transfer method only determines how the data is transferred.

IDoc transfer method: A data IDoc consists of a control record, a data record, and a status record. The control record contains administration information such as receiver, sender, and client. The status record describes the status of the IDoc, for example "modified". The data stores in the ALE inbox and outbox have to be emptied or reorganized.

PSA (tRFC) transfer method: With this transfer method, a transactional Remote Function Call is used to transfer the data directly from the source system to the SAP BW. Here, there is the option of storing the data in the PSA (the tables have the same structure as the transfer structure.) This is the preferred transfer method, because it improves performance better than the IDoc method. When you use tRFCs to transfer data, the maximum number of fields that can be used is restricted to 255. The length of a data record is also restricted to 1962 bytes when you use tRFCs (IDoc --> 1000 bytes.)

• RFC Connections
• ALE SETTINGS
• Partner AGREEMENTS
• Ports
• IDOC TYPES
• IDoc SEGMENTS

• The fields copied from the Transfer STRUCTURE and are not modified
• FIXED Value can be assigned to an InfoObject
• An ABAP ROUTINE or a FORM FIELD determines the value of the InfoObject

• DIRECT INFOSOURCE
• FLEXIBLE InfoSource

• TRANSACTION DATA
• ATTRIBUTES
• TEXTS
• HIERARCHY

• SAP Systems – SAP Basis RELEASE 3.11 and above – SAPI
• DATABASES – USE SAP DB Connect
• External Systems – BAPI
• File Systems
• SAP BW

In serialized V3 Update DATA is TRANSFERRED from the LIS communication structure, using extract structures (e.g. MC02M_0HDR for the header purchase documents), into a central delta management area.

With Unserialized V3 Update mode, the extraction data continues to be WRITTEN to the update tables using a V3 update module and then is read and processed by a collective update run (through LBWE).

In serialized V3 Update data is transferred from the LIS communication structure, using extract structures (e.g. MC02M_0HDR for the header purchase documents), into a central delta management area.

With Unserialized V3 Update mode, the extraction data continues to be written to the update tables using a V3 update module and then is read and processed by a collective update run (through LBWE).

Newly GENERATED records will be stored in the EXTRACTION QUEUE and from there a scheduled job will push it to delta queue.

Newly generated records will be stored in the extraction queue and from there a scheduled job will push it to delta queue.

DELTA queue stores records that have been generated after last delta upload and YET to be sent to BW. The queued data will be sent to BW from here. DEPENDING on the method selected, generated records will EITHER come directly to this queue or through EXTRACTION queue.

Delta queue stores records that have been generated after last delta upload and yet to be sent to BW. The queued data will be sent to BW from here. Depending on the method selected, generated records will either come directly to this queue or through extraction queue.

Quotation à INQUIRY à SALES ORDER à Delivery à Post goods issue àInvoice à ACCOUNTING document

Quotation à inquiry à Sales order à Delivery à Post goods issue àInvoice à Accounting document

• Start ROUTINE
• Update routine
• InfoPackages (to POPULATE selection parameters )
• TRANSFER Rules
• Variable EXITS
• To create any generic DataSources

• Depends on the characteristic and cardinality.
• The characteristics that logically belong together can be grouped together in a Dimension.
• FIRST we will DECIDE the dimensions of the INFOCUBE. After that we will ASSIGN NECESSARY InfoObjects to the corresponding dimensions.

No. If there is DATA in the Data Source we can only append the fields. No data will be LOST. But you need to have separate mechanism to FILL in the HISTORICAL data for the newly added fields.

No. If there is data in the Data Source we can only append the fields. No data will be lost. But you need to have separate mechanism to fill in the historical data for the newly added fields.

Go to the FIRST INFOOBJECT screen in ADMINISTRATION work BENCH go to compounding tab, create the InfoObject that is dependent on the former InfoObject and ACTIVATE.

Go to the first InfoObject screen in administration work bench go to compounding tab, create the InfoObject that is dependent on the former InfoObject and activate.

Reactivating the INFOOBJECT shouldn't AFFECT UNLESS he has made some CHANGES to that and then REACTIVATED it.

Reactivating the InfoObject shouldn't affect unless he has made some changes to that and then reactivated it.

We had collected data from the user and created HLD (High level Design document) and we analyzed to find the source for the data. Then data models were done indicating DATAFLOW, lookups. While designing the data MODEL considerations were given to use existing objects (like ODS and InfoCube) not STORING redundant data, volume of data, Batch dependency.

We had collected data from the user and created HLD (High level Design document) and we analyzed to find the source for the data. Then data models were done indicating dataflow, lookups. While designing the data model considerations were given to use existing objects (like ODS and InfoCube) not storing redundant data, volume of data, Batch dependency.

A MultiCube is a TYPE of InfoProvider that combines data from a NUMBER of InfoCubes and makes them available as a whole to reporting.

A RemoteCube is an InfoCube whose TRANSACTION data is not managed in the BW but EXTERNALLY. Only the structure of the RemoteCube is DEFINED in BW. The data is read for reporting using a BAPI from another system.

A MultiCube is a type of InfoProvider that combines data from a number of InfoCubes and makes them available as a whole to reporting.

A RemoteCube is an InfoCube whose transaction data is not managed in the BW but externally. Only the structure of the RemoteCube is defined in BW. The data is read for reporting using a BAPI from another system.

Remote Cube is USED when we like to report on TRANSNATIONAL data. In a Remote Cube data is not STORED on BW side. IDEALLY used when detailed data is required and we WANT to bypass loading of data into BW.

Remote Cube is used when we like to report on transnational data. In a Remote Cube data is not stored on BW side. Ideally used when detailed data is required and we want to bypass loading of data into BW.

A Remote Cube is an INFO Cube whose DATA is not managed in the BW but externally. Only the structure of the Remote Cube is defined in BW. The data is READ for reporting using a BAPI from another system.

With a Remote Cube, we can report using data in external systems without having to physically store transaction data in BW. We can, for example, include an external system from market data providers using a Remote Cube.

This is best USED only for small volume of data and when LESS users access the query.

A Remote Cube is an Info Cube whose data is not managed in the BW but externally. Only the structure of the Remote Cube is defined in BW. The data is read for reporting using a BAPI from another system.

With a Remote Cube, we can report using data in external systems without having to physically store transaction data in BW. We can, for example, include an external system from market data providers using a Remote Cube.

This is best used only for small volume of data and when less users access the query.

FACT table

Fact table

MASTER DATA table.

Master Data table.

When the OBJECTS are ACTIVATED, the tables are CREATED. The location depends on the BASIS installation.

When the objects are activated, the tables are created. The location depends on the Basis installation.

• Errors in loading data (ODS loading, INFOCUBE loading, delta loading ETC)
• Errors in activating BW or other OBJECTS.

Star SCHEMA: Only characteristics of the dimension tables can be used to access FACTS. No structured drill downs can be created. SUPPORT for many languages is difficult.

Extended star schema: Master data tables and their ASSOCIATED fields (ATTRIBUTES), External hierarchy tables for structured access to data, Text tables with extensive multilingual descriptions are supported using SIDs.

Star schema: Only characteristics of the dimension tables can be used to access facts. No structured drill downs can be created. Support for many languages is difficult.

Extended star schema: Master data tables and their associated fields (attributes), External hierarchy tables for structured access to data, Text tables with extensive multilingual descriptions are supported using SIDs.

ODS is MAINLY USED as a STAGING AREA.

ODS is mainly used as a staging area.

All deltas are TAKEN from the delta queue. The WAY of POPULATING the delta queue differs for LO and other Data SOURCES.

All deltas are taken from the delta queue. The way of populating the delta queue differs for LO and other Data Sources.

In R/3 the RECORD mode determines this as seen in the RODELTAM table i.e., whether it will be a new status or additive delta for the RESPECTIVE DataSource. Based on this you need to select the appropriate update type for the data TARGET in BW. For e.g., ODS supports additive as well as Overwrite function. Depending on which DataSource is updating the ODS, and the record mode supported by this DataSource, you need to do the right SELECTION in BW.

In R/3 the record mode determines this as seen in the RODELTAM table i.e., whether it will be a new status or additive delta for the respective DataSource. Based on this you need to select the appropriate update type for the data target in BW. For e.g., ODS supports additive as well as Overwrite function. Depending on which DataSource is updating the ODS, and the record mode supported by this DataSource, you need to do the right selection in BW.

This is UPDATING of InfoObject without using UPDATE RULES but only the Transfer Rules.

This is updating of InfoObject without using Update Rules but only the Transfer Rules.

These are extractors supplied by SAP for SPECIFIC BUSINESS modules. Eg. 2FI_AR_4: Customers: Line Items with Delta EXTRACTION / 2FI_GL_6: General Ledger SALES Figures via Delta Extraction.

These are extractors supplied by SAP for specific business modules. Eg. 2FI_AR_4: Customers: Line Items with Delta Extraction / 2FI_GL_6: General Ledger Sales Figures via Delta Extraction.

If the extract structure is activated then any ONLINE TRANSACTION or on the compilation of SETUP tables, the data is posted to the extract structures depending on the update METHOD selected. Activation marks the DataSource with green else it is yellow. The activation/deactivation MAKES entries to the TMC EXACT table.

If the extract structure is activated then any online transaction or on the compilation of setup tables, the data is posted to the extract structures depending on the update method selected. Activation marks the DataSource with green else it is yellow. The activation/deactivation makes entries to the TMC EXACT table.

RSA7 is to view BW delta queue. This gets overwritten each time

LBWF is the Log for LO Extract Structures. This is POPULATED only when the User parameter MCL is SET, and is recommended only for testing purposes.

RSA7 is to view BW delta queue. This gets overwritten each time

LBWF is the Log for LO Extract Structures. This is populated only when the User parameter MCL is set, and is recommended only for testing purposes.

An InfoCube will have additive Delta, but you will still be able to see all individual RECORDS in the InfoCube contents. This is because if you choose to delete the current request - then the records have to be rolled back to the prior STATUS. You build a query on the InfoCube and on the query you will FIND that the data is ACTUALLY summed up. The ODS records will not have duplicate records. You will have only one RECORD.

An InfoCube will have additive Delta, but you will still be able to see all individual records in the InfoCube contents. This is because if you choose to delete the current request - then the records have to be rolled back to the prior status. You build a query on the InfoCube and on the query you will find that the data is actually summed up. The ODS records will not have duplicate records. You will have only one record.

These are PURCHASING RELATED COMMUNICATION STRUCTURES.

These are purchasing related communication structures.

EXTRACT structures are maintained in case of LO Data Sources. There are multiple extract structures for each Data Source in the LO for DIFFERENT APPLICATIONS. Any enhancements to Data Source in case of LO are done using maintenance of extract structures.

Extract structures are maintained in case of LO Data Sources. There are multiple extract structures for each Data Source in the LO for different applications. Any enhancements to Data Source in case of LO are done using maintenance of extract structures.

It is the maintenance of required FIELDS in a particular Data Source for which there are REPORTING requirements in BW and data for the same NEEDS to be extracted.

It is the maintenance of required fields in a particular Data Source for which there are reporting requirements in BW and data for the same needs to be extracted.

INFOCUBE: 0IC_C03

InfoCube: 0IC_C03

This you COULD do with SELECTIVE DELETION

This you could do with selective deletion

ADD the FIELD to extract structure and replicate the Data SOURCE again into BW and this field will APPEAR in BW ALSO.

Add the field to extract structure and replicate the Data Source again into BW and this field will appear in BW also.

DIMENSION TABLES link Master Data tables with the FACT table through SID's.

Dimension tables link Master Data tables with the fact table through SID's.

 We ALWAYS do full LOAD for Master Data. It would always overwrite the PREVIOUS entries.

 We always do full load for Master Data. It would always overwrite the previous entries.

There will be DATA in APPLICATION tables even after fill up of setup tables. Setup tables are just TEMP tables that fill up from application tables for setting up Init/Full loads for BW.

There will be data in application tables even after fill up of setup tables. Setup tables are just temp tables that fill up from application tables for setting up Init/Full loads for BW.

The init LOADS in BW pull DATA from the Setup TABLES. The setup tables are only USED in CASE of first init/full loads.

The init loads in BW pull data from the Setup tables. The setup tables are only used in case of first init/full loads.

During the Setup RUN, these setup tables are FILLED. NORMALLY it's a good practice to delete the existing setup tables before EXECUTING the setup runs so as to avoid duplicate records for the same selections.

During the Setup run, these setup tables are filled. Normally it's a good practice to delete the existing setup tables before executing the setup runs so as to avoid duplicate records for the same selections.

Yes. By deleting the SETUP tables we are deleting the data that is in the setup tables from the PREVIOUS update. This AVOIDS updating the records TWICE into the BW.

Yes. By deleting the setup tables we are deleting the data that is in the setup tables from the previous update. This avoids updating the records twice into the BW.

In LO Extraction MECHANISM when we fill the SETUP TABLES the extract structure is filled with the data. When we SCHEDULE InfoPackage using FULL / INITI DELTA from BW, the data is picked from the setup tables

In LO Extraction Mechanism when we fill the setup tables the extract structure is filled with the data. When we schedule InfoPackage using FULL / INITI DELTA from BW, the data is picked from the setup tables

Setup tables are filled with data from application tables. They are the OLTP tables STORING transaction record. They interface between the application tables and EXTRACTOR. LO extractor takes data from Setup table while initialization and full upload. It is not needed to access the application table for data SELECTION. As setup tables are required only for full and init load we can delete the data after loading in order to AVOID duplicate data.

Setup tables are filled with data from application tables. They are the OLTP tables storing transaction record. They interface between the application tables and extractor. LO extractor takes data from Setup table while initialization and full upload. It is not needed to access the application table for data selection. As setup tables are required only for full and init load we can delete the data after loading in order to avoid duplicate data.

They ALLOW to do reverse POSTING. It WOULD ACTUALLY MULTIPLY the field by -1.

They allow to do reverse posting. It would actually multiply the field by -1.

Deletion of an initial load can be done in the InfoPackage. First set the QM STATUS of the request to red if not yet done, then delete it from all data targets. After that we go to the InfoPackage and choose from menu SCHEDULER à “initialization options for the source system”. There you should see your red request. Mark it and delete it. Accept deletion QUESTION and accept post information message. Now the request should be deleted from the initialization options. Now you can run a new init.

You can also run a repair request. That's a full request. With this you correct your data in the data target because of FAILED deltas or wrong inits. You do this in the InfoPackage too. Choose menu scheduler repair full request. But if you want to use the init/delta load you have to make a successful init first.

Deletion of an initial load can be done in the InfoPackage. First set the QM status of the request to red if not yet done, then delete it from all data targets. After that we go to the InfoPackage and choose from menu scheduler à “initialization options for the source system”. There you should see your red request. Mark it and delete it. Accept deletion question and accept post information message. Now the request should be deleted from the initialization options. Now you can run a new init.

You can also run a repair request. That's a full request. With this you correct your data in the data target because of failed deltas or wrong inits. You do this in the InfoPackage too. Choose menu scheduler repair full request. But if you want to use the init/delta load you have to make a successful init first.

• An aggregate is a materialized, aggregated view of the DATA in an InfoCube. In an aggregate, the dataset of an InfoCube is saved REDUNDANTLY and persistently in a consolidated form. Aggregates make it possible to access InfoCube data QUICKLY in Reporting. Aggregates can be used in following cases:

• To speed up the execution and NAVIGATION of a specific query.
• Use attributes often in queries.
• To speed up reporting with characteristic hierarchies by aggregating specific hierarchy LEVELS.

• An aggregate is a materialized, aggregated view of the data in an InfoCube. In an aggregate, the dataset of an InfoCube is saved redundantly and persistently in a consolidated form. Aggregates make it possible to access InfoCube data quickly in Reporting. Aggregates can be used in following cases:

• MANUAL
• AUTOMATIC