Explore topic-wise InterviewSolutions in .

a. CO-PA datasource must be defined at OPERATING Concern I Client Level
b. DEFINE DATA source for full updates (summarization level, segment level and line item)
c. Select SBIW transaction to get into CO-PA setup
d. Select the characteristics
e. Select the value fields
f. Generate the data source.

a. CO-PA datasource must be defined at Operating Concern I Client Level
b. Define data source for full updates (summarization level, segment level and line item)
c. Select SBIW transaction to get into CO-PA setup
d. Select the characteristics
e. Select the value fields
f. Generate the data source.

The QUERY on BW is the source for the retraction; data is RETRACTED after drill down using all free CHARACTERISTICS (drill down is PERFORMED internally).

The query on BW is the source for the retraction; data is retracted after drill down using all free characteristics (drill down is performed internally).

a. allowed only for cost based CO-PA
b. no delta functionality; but runs can be cancelled
c. RETRACTOR uses RSCRM_BAPI to run query
d. ACTUAL DATA is always updated using record type H and PLANNING data, record type and version can be specified.
e. Use the valuation option if you want CO-PA valuation.

a. allowed only for cost based CO-PA
b. no delta functionality; but runs can be cancelled
c. retractor uses RSCRM_BAPI to run query
d. actual data is always updated using record type H and planning data, record type and version can be specified.
e. Use the valuation option if you want CO-PA valuation.

a. enable the query for OLE DB
b. only one structure allowed for query and should include company code and a time dimension
c. user for RFC connection should have dialog or service type.
d. The query is run one time and sent to R13 in one PACKET; because of this queries with LARGE amount of data should be divided and run as several queries (with different selection CRITERIA using VARIABLES)

a. enable the query for OLE DB
b. only one structure allowed for query and should include company code and a time dimension
c. user for RFC connection should have dialog or service type.
d. The query is run one time and sent to R13 in one packet; because of this queries with large amount of data should be divided and run as several queries (with different selection criteria using variables)

a. append the STANDARD data structure
b. add the custom fields
c. EDIT the right user exit and populate the extra fields
d. don’t forget to ACTIVATE the user exit
e. create info objects corresponding to the new fields
F. replicate the datasources
g. map the new fields to the info objects
H. activate communication structure and transfer rules
i. create info package and load data

a. append the standard data structure
b. add the custom fields
c. edit the right user exit and populate the extra fields
d. don’t forget to activate the user exit
e. create info objects corresponding to the new fields
f. replicate the datasources
g. map the new fields to the info objects
h. activate communication structure and transfer rules
i. create info package and load data

All NEW FIELDS in the APPENDED structure should start with ZZ.

All new fields in the appended structure should start with ZZ.

RSAP00001.

RSAP00001.

EX1T_SAPLRSAP_001 TRANSACTION data
EXIT_SAPLRSAPJ)02- master data
EXIT_SAPLRSAP_003- TEXT
EXIT_SAPLRSAPJ)04- hierarchy

EX1T_SAPLRSAP_001 transaction data
EXIT_SAPLRSAPJ)02- master data
EXIT_SAPLRSAP_003- text
EXIT_SAPLRSAPJ)04- hierarchy

YES; that is why you should use case statement to check the DATA SOURCE name to code.

Yes; that is why you should use case statement to check the data source name to code.

a. create an infinite loop on a value EXAMPLE x = 3. do while x> 1.
b. Start the EXTRACTION on BW
C. Now the process on R/3 goes on infinite loop
d. Look for process in SM5O
e. Debug the process
f. With in debugger change value of x to 1.
g. Now you can see and debug your code.

a. create an infinite loop on a value example x = 3. do while x> 1.
b. Start the extraction on BW
c. Now the process on R/3 goes on infinite loop
d. Look for process in SM5O
e. Debug the process
f. With in debugger change value of x to 1.
g. Now you can see and debug your code.

No; USER EXIT is only to APPEND DATA to the RECORD.

No; user exit is only to append data to the record.

a. I_T_FIELDS - list of TRANSFER STRUCTURE fields
b. I_T_DATA - internal table CONTAINING data for the MASTER ATTRIBUTES; remember this contains all data
c. LUPDMODE - update mode
d. I_CHABASNM - basic characteristics
e. I_SOURCE - name of the info source

a. I_T_FIELDS - list of transfer structure fields
b. I_T_DATA - internal table containing data for the master attributes; remember this contains all data
c. LUPDMODE - update mode
d. I_CHABASNM - basic characteristics
e. I_SOURCE - name of the info source

HRPTDWO1 - for HR TIME RELATED DATA.

HRPTDWO1 - for HR time related data.

SAP has GIVEN a utility to load data from EXTERNAL DATABASES DIRECTLY like Oracle; this is called DB connect.

SAP has given a utility to load data from external databases directly like Oracle; this is called DB connect.

a. DBSL MUST be installed on SAP server
b. Database specific DB CLIENT must be installed
c. Table and FIELD NAMES must be in capital LETTERS

a. DBSL must be installed on SAP server
b. Database specific DB Client must be installed
c. Table and field names must be in capital letters

a. FIRST VERIFY that the DB connection works from the server
b. AWB -> Source systems -> create
c. Select Database source system
d. Enter the database user name, password and connect string; for example Oracle enter the TNS name
e. Generate the data source using transaction RSDBC
f. Assign data source to INFO source
G. Maintain and activate communication structure and transfer rules
h. Create info PACKAGE and load data

a. first verify that the DB connection works from the server
b. AWB -> Source systems -> create
c. Select Database source system
d. Enter the database user name, password and connect string; for example Oracle enter the TNS name
e. Generate the data source using transaction RSDBC
f. Assign data source to info source
g. Maintain and activate communication structure and transfer rules
h. Create info package and load data

In the UPDATE rule or in Bex; if you do it in the update rule then you LOSE the information on the ORIGINAL CURRENCY.

In the update rule or in Bex; if you do it in the update rule then you lose the information on the original currency.

DEFINES how the EXCHANGE rate is CALCULATED; the TARGET currency can be fixed or can be determined at the time of TRANSLATION.

Defines how the exchange rate is calculated; the target currency can be fixed or can be determined at the time of translation.

TCURV.

TCURV.

RSW_CURRENCYTRANSLATION.

RSW_CURRENCYTRANSLATION.

USE the PROGRAM RSEURO.

Use the program RSEURO.

ACCELERATED SAP.

Accelerated SAP.

a. Project preparation - initial stuff; do a conceptual review after this PHASE
b. Business blue print - FUNCTIONAL spec; do a design review after this phase
c. Realization - DEVELOP; do a configuration review after this phase
d. Final preparation - QA and other final stuff before MOVING to production; do a performance review after this phase
e. Go live and support - to production and support

a. Project preparation - initial stuff; do a conceptual review after this phase
b. Business blue print - Functional spec; do a design review after this phase
c. Realization - develop; do a configuration review after this phase
d. Final preparation - QA and other final stuff before moving to production; do a performance review after this phase
e. Go live and support - to production and support

Usually the TEAM has a project manager, one or more Functional consultants, one or more developers and one or more QA TESTERS and the usual BASIS team.

Usually the team has a project manager, one or more Functional consultants, one or more developers and one or more QA testers and the usual basis team.

FINISH within 90 DAYS and PROVE using delivered business content.

Finish within 90 days and prove using delivered business content.

The pre configured objects delivered by SAP is business CONTENT; it is roles, queries, INFO PROVIDERS, info source, data source, info objects, info package, ETC; for example OMATERIAL is a business content delivered by sap.

The pre configured objects delivered by SAP is business content; it is roles, queries, info providers, info source, data source, info objects, info package, etc; for example OMATERIAL is a business content delivered by sap.

A dimension containing a characteristics which changes over a TIME; for example TAKE employee job TITLE; this changes over a PERIOD of time with different job titles.

A dimension containing a characteristics which changes over a time; for example take employee job title; this changes over a period of time with different job titles.

Check the MAPPING at BW side for 0STREET in transfer rules. Check the data in PSA for the same field. If the PSA is also doesn't have COMPLETE data then check the field in RSA3 in SOURCE SYSTEM.

Check the mapping at BW side for 0STREET in transfer rules. Check the data in PSA for the same field. If the PSA is also doesn't have complete data then check the field in RSA3 in source system.

One of the biggest and most important challenges in any implementation is gathering and understanding the end user and process TEAM functional requirements. These functional requirements represent the scope of analysis needs and expectations (both now and in the FUTURE) of the end user. These typically involve all of the following:- Business reasons for the project and business questions answered by the implementation- Critical success factors for the implementation- Source systems that are involved and the scope of INFORMATION needed from each- Intended audience and stakeholders and their analysis needs- Any major transformation that is needed in order to provide the information- Security requirements to prevent unauthorized use This process involves one seemingly simple task: Find out exactly what the end users' analysis requirements are, both now and in the future, and build the BW system to these requirements. Although simple in concept, in practice gathering and REACHING a CLEAR understanding and agreement on a complete set of BW functional requirements is not always so simple.

One of the biggest and most important challenges in any implementation is gathering and understanding the end user and process team functional requirements. These functional requirements represent the scope of analysis needs and expectations (both now and in the future) of the end user. These typically involve all of the following:- Business reasons for the project and business questions answered by the implementation- Critical success factors for the implementation- Source systems that are involved and the scope of information needed from each- Intended audience and stakeholders and their analysis needs- Any major transformation that is needed in order to provide the information- Security requirements to prevent unauthorized use This process involves one seemingly simple task: Find out exactly what the end users' analysis requirements are, both now and in the future, and build the BW system to these requirements. Although simple in concept, in practice gathering and reaching a clear understanding and agreement on a complete set of BW functional requirements is not always so simple.

It depends on your PROJECT requirement. Customized cubes are not mandatory for all the projects. If your business requirement is differs from given scenario ( BI content cubes ) then only we will opt for customized cubes. Normally your BW customization or creation of new info providers all are depending on your source system. If your source system other that R3 then you should go with customization of your all objects. If your source system is R3 and your users are USING only R3 standard business scenarios like SD, MM or FI... etc., then you dont want to create any info providers or you dont want to enhance any thing in the existing BW Business Content. But 99% this is not possible. Because surely they should have included their new business scenario or new enhancements. For example, In my first project we implemented for Solution Manager BW implementation. There we have activated all the business content in CRM. But the source system have new scenarios for message escalation, ageing calculation etc., According their business scenario we couldn't use standard business content. For that we have taken only existing info objects and created new info objects which are not there in the business content. After that we have created custom DATA source to info providers as well as reports.

It depends on your project requirement. Customized cubes are not mandatory for all the projects. If your business requirement is differs from given scenario ( BI content cubes ) then only we will opt for customized cubes. Normally your BW customization or creation of new info providers all are depending on your source system. If your source system other that R3 then you should go with customization of your all objects. If your source system is R3 and your users are using only R3 standard business scenarios like SD, MM or FI... etc., then you dont want to create any info providers or you dont want to enhance any thing in the existing BW Business Content. But 99% this is not possible. Because surely they should have included their new business scenario or new enhancements. For example, In my first project we implemented for Solution Manager BW implementation. There we have activated all the business content in CRM. But the source system have new scenarios for message escalation, ageing calculation etc., According their business scenario we couldn't use standard business content. For that we have taken only existing info objects and created new info objects which are not there in the business content. After that we have created custom data source to info providers as well as reports.

Technical Specification:Here we will mention all the BW OBJECTS (info objects, data sources, info sources and info providers). Then we are going to say the data flow and behaviour of the data load (EITHER delta or full) also we can tell the duration of the cube ACTIVATION or creation. Pure BW technical things are available in this DOCUMENT. This is not for End users document. Functional Specification:Here we will describe the business requirements. That means here we are going to say which are all business we are implementing like SD, MM and FI etc., then we are going to tell the KPI and deliverable reports detail to the users. This document is going to mingle with both Function Consultants and Business Users. This document is applicable for end users also.

Technical Specification:Here we will mention all the BW objects (info objects, data sources, info sources and info providers). Then we are going to say the data flow and behaviour of the data load (either delta or full) also we can tell the duration of the cube activation or creation. Pure BW technical things are available in this document. This is not for End users document. Functional Specification:Here we will describe the business requirements. That means here we are going to say which are all business we are implementing like SD, MM and FI etc., then we are going to tell the KPI and deliverable reports detail to the users. This document is going to mingle with both Function Consultants and Business Users. This document is applicable for end users also.

Go to BW system and CREATE a new INFO PACKAGE for DELTA loads. DOUBLE click on new info package. Under update tab you can see the delta update radio button.

Go to BW system and create a new info package for delta loads. Double click on new info package. Under update tab you can see the delta update radio button.

Maintain project plans Manage all project activities, many of which are executed by resources not directly managed by the project leader (central BW development team, source system developer, business key users) Lease with key users to agree reporting requirements, report designs TRANSLATE requirements into design specifications( report specs, data mapping / translation, functional specs) Write and execute test plans and scripts . Coordinate and manage business / user testing Deliver training to key users Coordinate and manage product ionization and rollout activities Track CIP (continuous improvement) requests, work with users to prioritize, plan and manage CIP An SAP BW technical consultant is RESPONSIBLE for:SAP BW extraction using standard data extractor and available development tools for SAP and non-SAP data sources. -SAP ABAP programming with BWData modeling, star SCHEMA, MASTER data, ODS and cube design in BWData loading process and procedures (performance tuning)Query and report development using Bex ANALYZER and Query Designer Web report development using Web Application.

Maintain project plans Manage all project activities, many of which are executed by resources not directly managed by the project leader (central BW development team, source system developer, business key users) Lease with key users to agree reporting requirements, report designs Translate requirements into design specifications( report specs, data mapping / translation, functional specs) Write and execute test plans and scripts . Coordinate and manage business / user testing Deliver training to key users Coordinate and manage product ionization and rollout activities Track CIP (continuous improvement) requests, work with users to prioritize, plan and manage CIP An SAP BW technical consultant is responsible for:SAP BW extraction using standard data extractor and available development tools for SAP and non-SAP data sources. -SAP ABAP programming with BWData modeling, star schema, master data, ODS and cube design in BWData loading process and procedures (performance tuning)Query and report development using Bex Analyzer and Query Designer Web report development using Web Application.

BeX query GLOBAL structure to local structure Steps a local structure when you want to add structure elements that are unique to the SPECIFIC query. Changing the global structure changes the structure for all the queries that use the global structure. That is reason you go for a local structure. COMING to the navigation part--In the BEx Analyzer, from the SAP Business Explorer toolbar, choose the open query icon (icon tht looks like a folder) On the SAP BEx Open dialog box:Choose Queries. Select the desired InfoCubeChoose New.On the Define the query screen:In the left frame, expand the Structure node. Drag and drop the desired structure into EITHER the Rows or Columnsframe. Select the global structure. Right-click and choose Remove reference. A local structure is created. REMEMBER that you cannot revert back the changes made to global structure in this regard. You will have to delete the local structure and then drag ndrop global structure into query definition. When you try to save a global structure, a dialogue box prompts you to confirm changes to all queries. that is how you identify a global structure.

BeX query Global structure to local structure Steps a local structure when you want to add structure elements that are unique to the specific query. Changing the global structure changes the structure for all the queries that use the global structure. That is reason you go for a local structure. Coming to the navigation part--In the BEx Analyzer, from the SAP Business Explorer toolbar, choose the open query icon (icon tht looks like a folder) On the SAP BEx Open dialog box:Choose Queries. Select the desired InfoCubeChoose New.On the Define the query screen:In the left frame, expand the Structure node. Drag and drop the desired structure into either the Rows or Columnsframe. Select the global structure. Right-click and choose Remove reference. A local structure is created. Remember that you cannot revert back the changes made to global structure in this regard. You will have to delete the local structure and then drag ndrop global structure into query definition. When you try to save a global structure, a dialogue box prompts you to confirm changes to all queries. that is how you identify a global structure.

Cell in BEX:::Use * When you define selection criteria and formulas for structural components and there are two structural components of a query, generic cell definitions are created at the intersection of the structural components that determine the values to be presented in the cell. Cell-specific definitions allow you to define explicit formulas, along with implicit cell definition, and selection CONDITIONS for cells and in this way, to override implicitly created cell values. This function allows you to design much more detailed queries. In addition, you can define cells that have no DIRECT relationship to the structural components. These cells are not displayed and serve as containers for help SELECTIONS or help formulas. you need two structures to enable cell editor in bex. In every query you have one STRUCTURE for key figures, then you have to do another structure with selections or formulas inside. Then having two structures, the cross among them results in a fix reporting AREA of n rows * m columns. The cross of any row with any column can be defined as formula in cell editor. This is useful when you want to any cell had a different behaviour that the general one described in your query definition. For example imagine you have the following where % is a formula kfB/KfA *100.kfA kfB %chA 6 4 66%chB 10 2 20%chC 8 4 50%Then you want that % for row chC was the sum of % for chA and % chB. Then in cell editor you are enable to write a formula specifically for that cell as sum of the two cell before. chC/% = chA/% + chB/% then:kfA kfB %chA 6 4 66%chB 10 2 20%chC 8 4 86% Manager Round Review Questions.

Cell in BEX:::Use * When you define selection criteria and formulas for structural components and there are two structural components of a query, generic cell definitions are created at the intersection of the structural components that determine the values to be presented in the cell. Cell-specific definitions allow you to define explicit formulas, along with implicit cell definition, and selection conditions for cells and in this way, to override implicitly created cell values. This function allows you to design much more detailed queries. In addition, you can define cells that have no direct relationship to the structural components. These cells are not displayed and serve as containers for help selections or help formulas. you need two structures to enable cell editor in bex. In every query you have one structure for key figures, then you have to do another structure with selections or formulas inside. Then having two structures, the cross among them results in a fix reporting area of n rows * m columns. The cross of any row with any column can be defined as formula in cell editor. This is useful when you want to any cell had a different behaviour that the general one described in your query definition. For example imagine you have the following where % is a formula kfB/KfA *100.kfA kfB %chA 6 4 66%chB 10 2 20%chC 8 4 50%Then you want that % for row chC was the sum of % for chA and % chB. Then in cell editor you are enable to write a formula specifically for that cell as sum of the two cell before. chC/% = chA/% + chB/% then:kfA kfB %chA 6 4 66%chB 10 2 20%chC 8 4 86% Manager Round Review Questions.

SAP Records Management is a component of the SAP Web Application Server for the electronic management of records and even paper-based information can be part of the electronic RECORD in the SAP RMS. Other advantages of using SAP Records Management compared to other providers of record-based solutions: Records Management is a solution for the electronic management of records. The RMS divides various business units LOGICALLY thereby making it possible to provide particular groups of users with access to particular records, as needed within their business processes.

QUICK access to information is a key factor for performing business successfully. Records Management guarantees this quick access. In one record, all information objects of a business transaction are grouped together in a transparent hierarchical STRUCTURE. By converting paper records to electronic records, an organisation can enjoy all the advantages of a paper-free office: No storage costs for records, no cost-intensive copying procedures, and optimal retrieval of information.

However, SAP Records Management not only provides an electronic representation of the conventional paper record.

SAP Records Management is a component of the SAP Web Application Server for the electronic management of records and even paper-based information can be part of the electronic record in the SAP RMS. Other advantages of using SAP Records Management compared to other providers of record-based solutions: Records Management is a solution for the electronic management of records. The RMS divides various business units logically thereby making it possible to provide particular groups of users with access to particular records, as needed within their business processes.

Quick access to information is a key factor for performing business successfully. Records Management guarantees this quick access. In one record, all information objects of a business transaction are grouped together in a transparent hierarchical structure. By converting paper records to electronic records, an organisation can enjoy all the advantages of a paper-free office: No storage costs for records, no cost-intensive copying procedures, and optimal retrieval of information.

However, SAP Records Management not only provides an electronic representation of the conventional paper record.

The main task is Complete LIFE CYCLE development of SAP Authorization Roles. This INCLUDES participating in the HIGH level, low level, RMS's and technical development of the roles.

The main task is Complete life cycle development of SAP Authorization Roles. This includes participating in the high level, low level, RMS's and technical development of the roles.

It is an info object , 0Record mode is USED to identify the delta images in BW which is used in DSO .it is AUTOMATICALLY activated when u activate DSO in BW. Like that in R/3 also have field 0cancel. It holds delta images in R/3. When ever u extracting data from R/3 using LO or Generic.. Etc. this field 0Cancel is MAPPING with 0Record mode in BW. Like this BW identify the Delta images.

It is an info object , 0Record mode is used to identify the delta images in BW which is used in DSO .it is automatically activated when u activate DSO in BW. Like that in R/3 also have field 0cancel. It holds delta images in R/3. When ever u extracting data from R/3 using LO or Generic.. Etc. this field 0Cancel is mapping with 0Record mode in BW. Like this BW identify the Delta images.

From a query name or description, you WOULD not be able to judge whether the query is having any exception.There are TWO ways of FINDING exception against a query:1. Execute queries one by one, the one which is having background colour as exception reporting are with exceptions.2. Open queries in the BEX Query Designer. If you are finding exception TAB at the right SIDE of filter and rows/column tab, the query is having exception.

From a query name or description, you would not be able to judge whether the query is having any exception.There are two ways of finding exception against a query:1. Execute queries one by one, the one which is having background colour as exception reporting are with exceptions.2. Open queries in the BEX Query Designer. If you are finding exception tab at the right side of filter and rows/column tab, the query is having exception.

• The 3 options for DELTA Management with Flat Files:
- Full Upload
- New Status for Changed RECORDS (ODS OBJECT only)
- ADDITIVE Delta (ODS Object & InfoCube)

• The 3 options for Delta Management with Flat Files:
- Full Upload
- New Status for Changed records (ODS Object only)
- Additive Delta (ODS Object & InfoCube)

• Application Specific
o BW CONTENT FI, HR, CO, SAP CRM, LO COCKPIT
o Customer-Generated Extractors
LIS, FI-SL, CO-PA
• Cross Application (GENERIC Extractors)
o DB View, InfoSet, Function Module

• Application Specific
o BW Content FI, HR, CO, SAP CRM, LO Cockpit
o Customer-Generated Extractors
LIS, FI-SL, CO-PA
• Cross Application (Generic Extractors)
o DB View, InfoSet, Function Module

• The steps are:
o RSA5 Select the DataSources
o LBWE Maintain DataSources and Activate Extract Structures
o LBWG Delete Setup Tables
o 0LI*BW Setup tables
o RSA3 Check EXTRACTION and the DATA in Setup tables
o LBWQ Check the extraction queue
o LBWF Log for LO Extract Structures
o RSA7 BW DELTA Queue MONITOR

• The steps are:
o RSA5 Select the DataSources
o LBWE Maintain DataSources and Activate Extract Structures
o LBWG Delete Setup Tables
o 0LI*BW Setup tables
o RSA3 Check extraction and the data in Setup tables
o LBWQ Check the extraction queue
o LBWF Log for LO Extract Structures
o RSA7 BW Delta Queue Monitor

• ODS: Provides granular data, ALLOWS overwrite and data is in transparent tables, IDEAL for DRILLDOWN and RRI.
• CUBE: Follows the STAR schema, we can only append data, ideal for primary reporting.
• MultiProvider: Does not have physical data. It allows to access data from different InfoProviders (Cube, ODS, InfoObject). It is also preferred for reporting.

• ODS: Provides granular data, allows overwrite and data is in transparent tables, ideal for drilldown and RRI.
• CUBE: Follows the star schema, we can only append data, ideal for primary reporting.
• MultiProvider: Does not have physical data. It allows to access data from different InfoProviders (Cube, ODS, InfoObject). It is also preferred for reporting.

• LBW0 CONNECTING LIS InfoStructures to BW.

• LBW0 Connecting LIS InfoStructures to BW.

• START routine can be used to ACCESS INFOPACKAGE while update routines are used while UPDATING the DATA Targets.

• Start routine can be used to access InfoPackage while update routines are used while updating the Data Targets.

In Star Schema model, Fact table is SURROUNDED by dimensional tables. Fact table is usually very large, that means it contains millions to billions of records. On the other hand dimensional tables are very small. Hence they contain a few thousands to few million records. In practice, Fact table holds transactional data and dimensional table holdsmaster data.
The dimensional tables are specific to a fact table. This means that dimensional tables are not shared to across other fact tables. When other fact table such as a product needs the same product dimension data another dimension table that is specific to a NEW fact table is needed.
This SITUATION creates data management problems such as master data redundancy because the very same product is duplicated in several dimensional tables instead of sharing from ONE single master data table. This PROBLEM can be solved in extended star schema.

In Star Schema model, Fact table is surrounded by dimensional tables. Fact table is usually very large, that means it contains millions to billions of records. On the other hand dimensional tables are very small. Hence they contain a few thousands to few million records. In practice, Fact table holds transactional data and dimensional table holdsmaster data.
The dimensional tables are specific to a fact table. This means that dimensional tables are not shared to across other fact tables. When other fact table such as a product needs the same product dimension data another dimension table that is specific to a new fact table is needed.
This situation creates data management problems such as master data redundancy because the very same product is duplicated in several dimensional tables instead of sharing from one single master data table. This problem can be solved in extended star schema.

Actually INFO CUBE CONTAINS two table's E table and F (fact) table.

Actually info cube contains two table's E table and F (fact) table.

16(3 are sap DEFINES and 13 are CUSTOMER defined).

16(3 are sap defines and 13 are customer defined).

4(3 SAP DEFINED and 1 CUSTOMER defined).

4(3 Sap defined and 1 customer defined).

The 3 SAP defined dimensions are…..
1. DATA packet dimension (P)…..it contains 3characteristics.a) request Id (b) RECORD type (C) Change run id
2. Time dimension (T)….it contains time characteristics such as 0calmonth, 0calday etc
3. Unit Dimension (U)…it contains basically amount and quantity RELATED UNITS.

The 3 SAP defined dimensions are…..
1. Data packet dimension (P)…..it contains 3characteristics.a) request Id (b) Record type (c) Change run id
2. Time dimension (T)….it contains time characteristics such as 0calmonth, 0calday etc
3. Unit Dimension (U)…it contains basically amount and quantity related units.