Explore topic-wise InterviewSolutions in .

LOADING time DEPENDS on the work LOAD both on the BW side and source system side. It might also depend upon the network connectivity.

Loading time depends on the work load both on the BW side and source system side. It might also depend upon the network connectivity.

tRFC and iDoc errors- when you load data , these are connection specific and if the source system is not set properly or is interrupted , you get these errors.

Intermediate DOCUMENT (IDoc) is a container for exchanging data between R/3, R/2 and non-SAP systems. IDOCS are sent in the COMMUNICATION layer by transactional Remote FUNCTION Call (tRFC) or by other file interfaces (for example, EDI). tRFC guarantees that the data is transferred once only. Was not able to find out when the errors occur.

tRFC and iDoc errors- when you load data , these are connection specific and if the source system is not set properly or is interrupted , you get these errors.

Intermediate Document (IDoc) is a container for exchanging data between R/3, R/2 and non-SAP systems. IDocs are sent in the communication layer by transactional Remote Function Call (tRFC) or by other file interfaces (for example, EDI). tRFC guarantees that the data is transferred once only. Was not able to find out when the errors occur.

DATA is EXTRACTED from SYSTEMS other than R/3 and flat files using staging BAPIs.

Data is extracted from systems other than R/3 and flat files using staging BAPIs.

Multi-layered STRUCTURE in ODS STAGE is USED to consolidate DATA from different DataSources.

Multi-layered structure in ODS stage is used to consolidate data from different DataSources.

MODIFICATIONS can't be MADE to an InfoCube if there is data present in the InfoCube. If we WANT to modify an InfoCube and no backup for data exist then we can DESIGN another InfoCube with the parameters specified and load data from the old InfoCube.

Modifications can't be made to an InfoCube if there is data present in the InfoCube. If we want to modify an InfoCube and no backup for data exist then we can design another InfoCube with the parameters specified and load data from the old InfoCube.

Data is stored in MULTIPLE tables in R/3 based on ERM (Entity Relationship model) to PREVENT the redundant STORAGE of data.

Data is stored in multiple tables in R/3 based on ERM (Entity Relationship model) to prevent the redundant storage of data.

When requests loaded into ODS object are neither required for delta update nor for initialization, they can be deleted. If delta initialization for update EXISTS in connected data targets, the requests have to be UPDATED first before the data can be deleted.

When requests loaded into ODS object are neither required for delta update nor for initialization, they can be deleted. If delta initialization for update exists in connected data targets, the requests have to be updated first before the data can be deleted.

Transactional InfoCubes differ from Basic InfoCubes in their ability to support parallel WRITE ACCESSES. Basic InfoCubes are technically optimized for read accesses to the detriment of write accesses. Transactional InfoCubes are designed to meet the demands of SEM, where multiple USERS write simultaneously into an INFOCUBE.

Transactional InfoCubes differ from Basic InfoCubes in their ability to support parallel write accesses. Basic InfoCubes are technically optimized for read accesses to the detriment of write accesses. Transactional InfoCubes are designed to meet the demands of SEM, where multiple users write simultaneously into an InfoCube.

A FEATURE provided by relational database management systems (RDBMS) that prevents users or applications from ENTERING inconsistent data. For example, suppose Table B has a FOREIGN key that POINTS to a field in Table A.

• Referential integrity would prevent from adding a record to Table B that cannot be linked to Table A.
• Referential integrity rules might also specify that WHENEVER you delete a record from Table A, any records in Table B that are linked to the deleted record will also be deleted. This is called cascading delete.
• Referential integrity rules could specify that whenever youmodify the value of a linked field in Table A, all records in Table B that are linked to it will also be modified accordingly. This is called cascading update.

A feature provided by relational database management systems (RDBMS) that prevents users or applications from entering inconsistent data. For example, suppose Table B has a foreign key that points to a field in Table A.

EFFICIENT reporting is ONE of the TARGETS of using HIERARCHIES. Easy DRILLDOWN paths can be built using hierarchies.

Efficient reporting is one of the targets of using hierarchies. Easy drilldown paths can be built using hierarchies.

If the REQUIREMENT specifies a DIFFERENT NEED for each characteristic then we have separate update RULES for each of the characteristics.

If the requirement specifies a different need for each characteristic then we have separate update rules for each of the characteristics.

Because ODS is meant to STORE a detailed document for quick use and HELP MAKE short-term DECISIONS.

Because ODS is meant to store a detailed document for quick use and help make short-term decisions.

HUGE DIMENSION TABLES make an InfoCube INEFFICIENT.

The query TAKES a long time.

Huge Dimension tables make an InfoCube inefficient.

The query takes a long time.

Replication of DATA Source ENABLES the extract STRUCTURE from the source SYSTEM to be replicated in the BW.

Replication of Data Source enables the extract structure from the source system to be replicated in the BW.

INFOCUBE is more NORMALIZED than ODS.

InfoCube is more normalized than ODS.

Data Marts are used to exchange data between DIFFERENT BW systems or to update data WITHIN the same BW system (Myself Data MART). Here, the InfoProviders that are used to PROVIDE data are called Data Marts.

Data Marts are used to exchange data between different BW systems or to update data within the same BW system (Myself Data Mart). Here, the InfoProviders that are used to provide data are called Data Marts.

No.

No.

SIDS are STATIC.

SIDs are static.

A TRANSACTIONAL ODS object differs from a standard ODS object in the way it PREPARES data. In a standard ODS object, data is stored in different versions (ACTIVE, delta, modified); whereas a transactional ODS object contains the data in a single VERSION. Therefore, data is stored in precisely the same form in which it was written to the transactional ODS object by the application.

A transactional ODS object differs from a standard ODS object in the way it prepares data. In a standard ODS object, data is stored in different versions (active, delta, modified); whereas a transactional ODS object contains the data in a single version. Therefore, data is stored in precisely the same form in which it was written to the transactional ODS object by the application.

Activation of objects enables them to be EXECUTED, in other words USED elsewhere for DIFFERENT purposes. UNLESS an OBJECT is activated it cannot be used.

Activation of objects enables them to be executed, in other words used elsewhere for different purposes. Unless an object is activated it cannot be used.

A DATASOURCE is CREATED from the InfoCube which is supposed to feed. This can be done by right-clicking on the InfoCube and SELECTING export DataSource. Then a suitable INFOSOURCE can be created for this DataSource. And the intended data target InfoCube can be FED.

A DataSource is created from the InfoCube which is supposed to feed. This can be done by right-clicking on the InfoCube and selecting export DataSource. Then a suitable InfoSource can be created for this DataSource. And the intended data target InfoCube can be fed.

Data in PSA is deleted when ONE FEELS that there is no USE of it in future. There is a trade off between WASTAGE of space and use as a back up.

Data in PSA is deleted when one feels that there is no use of it in future. There is a trade off between wastage of space and use as a back up.

In an INBOUND ODS object, the DATA is saved in the same form as it was when delivered from the source system. This ODS type can be USED to report the original data as it comes from the source system.

In a CONSISTENT ODS object, data is stored in granular form and consolidated. This consolidated data on a document LEVEL creates the basis for further processing in BW.

In an Inbound ODS object, the data is saved in the same form as it was when delivered from the source system. This ODS type can be used to report the original data as it comes from the source system.

In a Consistent ODS object, data is stored in granular form and consolidated. This consolidated data on a document level creates the basis for further processing in BW.

The DATA of Change Log can be SCHEDULED to be deleted PERIODICALLY. Usually the Data is REMOVED after it has been UPDATED into the data targets.

The data of Change Log can be scheduled to be deleted periodically. Usually the Data is removed after it has been updated into the data targets.

THIRD normal form is NORMALIZED form of storing data in a relational database. It eliminates functional DEPENDENCIES on non-key fields by putting them in a separate table. At this stage, all non-key fields are dependent on only the key.

Star SCHEMA is a demoralized form of storing data, which paves the path for storing data in a multi-dimensional model.

Third normal form is normalized form of storing data in a relational database. It eliminates functional dependencies on non-key fields by putting them in a separate table. At this stage, all non-key fields are dependent on only the key.

Star schema is a demoralized form of storing data, which paves the path for storing data in a multi-dimensional model.

Some data targets and MODULES have delta Update feature. Those can be USED for delta Update of data. Say ODS, InfoCube, COPA are delta capable. Data can be expected STAGE WISE. After first accumulation of data, BIW expects the data in delta for these data target. When a data target does not have this feature (delta update), it can be made delta capable using ODS as data target.

Some data targets and modules have delta Update feature. Those can be used for delta Update of data. Say ODS, InfoCube, COPA are delta capable. Data can be expected stage wise. After first accumulation of data, BIW expects the data in delta for these data target. When a data target does not have this feature (delta update), it can be made delta capable using ODS as data target.

Time dependant master data are ONE which KEEPS changing according to time. For EXAMPLE: Assume a Scenario, Sales PERSON A works in East Zone till (Jan 30th 2004), and then moves to North Zone from Jan31st 2004. Thus the master data with regard to Sales person A, should be changed to different zone based on a time

Time dependant master data are one which keeps changing according to time. For example: Assume a Scenario, Sales person A works in East Zone till (Jan 30th 2004), and then moves to North Zone from Jan31st 2004. Thus the master data with regard to Sales person A, should be changed to different zone based on a time

In BIW, Saving à actually saves the defined structure and RETRIEVES whenever required.

ACTIVATING à It saves and generates required tables and structures.

In BIW, Saving à actually saves the defined structure and retrieves whenever required.

Activating à It saves and generates required tables and structures.

Yes.

Yes.

If transfer RULES are not DEFINED for InfoObjects, then TRAFFIC lights will not be green.

If transfer rules are not defined for InfoObjects, then traffic lights will not be green.

BAPI & ALE are programs to extract DATA from DataSources. BW CONNECTS SAP SYSTEMS (R/3 or BW) and flat files VIA ALE. BW connects with non SAP systems via BAPI.

BAPI & ALE are programs to extract data from DataSources. BW connects SAP systems (R/3 or BW) and flat files via ALE. BW connects with non SAP systems via BAPI.

No. An ODS object contains key fields (for example, document number/item) and DATA fields that can also CONTAIN character fields (for example, order STATUS, customer).

No. An ODS object contains key fields (for example, document number/item) and data fields that can also contain character fields (for example, order status, customer).

It is an InfoObject which SPECIFIES the method in which the DELTA information is SUPPLIED. ODS uses 0RECORDMODE for delta LOAD. 0RECORDMODE can have any of the 6 values as “ ”, “X”, “A”, “N”, “D” & “R”.

It is an InfoObject which specifies the method in which the delta information is supplied. ODS uses 0RECORDMODE for delta load. 0RECORDMODE can have any of the 6 values as “ ”, “X”, “A”, “N”, “D” & “R”.

Hierarchies are organizing DATA in a STRUCTURED WAY. For EXAMPLE BOM (Bill of material) can be configured as hierarchies.

Hierarchies are organizing data in a structured way. For example BOM (Bill of material) can be configured as hierarchies.

ONE can display the elements of CHARACTERISTICS in HIERARCHY form and evaluate query data for the individual hierarchy levels in the Web applications.

One can display the elements of characteristics in hierarchy form and evaluate query data for the individual hierarchy levels in the Web applications.

No.

No.

INFORMATICA, ACTA, COGNOS, BUSINESS OBJECTS are other ETL tools.

Informatica, ACTA, COGNOS, Business Objects are other ETL tools.

ODS has three database TABLES. New Table, ACTIVE Table and CHANGE Log Table. Initially new data are loaded and their TRACES are kept in Change log table. When another set of data comes, it actually compares with change log and transfers the data (delta data) into active table and also NOTES in Change log. Every time the tables are compared and data is written into the targets.

ODS has three database tables. New Table, Active Table and Change Log Table. Initially new data are loaded and their traces are kept in Change log table. When another set of data comes, it actually compares with change log and transfers the data (delta data) into active table and also notes in Change log. Every time the tables are compared and data is written into the targets.

SIDs are Surrogate IDs which are system GENERATED numbers and assigned to each CHARACTERISTIC value when they are uploaded. Search on Numeric CHARACTER is FASTER than Alpha characters and HENCE SIDs.

SIDs are Surrogate IDs which are system generated numbers and assigned to each characteristic value when they are uploaded. Search on Numeric character is faster than Alpha characters and hence SIDs.

When transactional data is PULLED from R3 SYSTEM INSTEAD of PULLING all the data daily (Instead of having FULL load), if we pull only the changed records, or newly added records, the load on the system will be very less.

When transactional data is pulled from R3 system instead of pulling all the data daily (Instead of having full load), if we pull only the changed records, or newly added records, the load on the system will be very less.

This defines a superior InfoObject which MUST be combined to define another InfoObject and it MAKES the superior InfoObject uniquely identifiable. For EXAMPLE, in a Plant, there can be some similar products manufactured. (Plant A-- Soap, Paste, Lotion; plant B--Soap, paste, Lotion) In this case Plant A and Plant B should be made unique. So the characteristics can be COMPOUNDED to make them unique.

This defines a superior InfoObject which must be combined to define another InfoObject and it makes the superior InfoObject uniquely identifiable. For example, in a Plant, there can be some similar products manufactured. (Plant A-- Soap, Paste, Lotion; plant B--Soap, paste, Lotion) In this case Plant A and Plant B should be made unique. So the characteristics can be compounded to make them unique.

• Check if the COLORS have been checked as navigational ATTRIBUTE of material.
• Check if MASTER data for the same is maintained and extractION in BW.

• “After Image” = Record Mode “ ” - The way a record looks after the change
• “Before Image” = Record Mode “X” - The way a record looked before the change
• “Additive Image” = Record Mode “A” - Shows only the difference for all numeric values
• “New Image” = Record Mode “N” - For each change, a new, unique record is GENERATED
• “Delete” = Record Mode “D” - Only PROVIDES the key information required to make a deletion
• “REVERSE” = Record Mode = “R” - Sends information to NUMERICALLY “cancel” a deleted record.

1. At the TIME of the transaction – DIRECT Delta
2. At a later date after the transaction (V3 JOB) – Queued Delta
3. At the time the extractor job is CALLED by BW – Unserialized V3 Update

• IMPROVED PERFORMANCE and REDUCED volumes of data
• Simple handling
• Standardized solution for all Logistics applications
• No use of LIS functions

• DIRECT DELTA
• QUEUED Delta
• Unserialized V3 UPDATE

• FULL UPDATE
• INITIALIZE DELTA
• Delta Update

• Maintaining EXTRACT Structures
• Maintaining DATASOURCES
• ACTIVATING UPDATES
• Controlling Updates

• Transfer data and Metadata from SAP Systems
• Transfer data from XML FILES
• Transfer data between BW data targets or from one BW system to another (Data Marts)

• Source SYSTEM
• MAXIMUM SIZE of the Data Package
• Maximum NUMBER of rows in a Data Package
• FREQUENCY
• Maximum number of parallel processes during the transfer of data
• Target system for batch job