SAP BW/BI Interview Questions
1). What are the extractor types?
Ans : There are three types of extractors
1). Application Specific - BW Content FI, HR, CO, SAP CRM, LO Cockpit
2).Customer-Generated Extractors - FI-SL, CO-PA
3).Cross Application - Generic Extractors based on Table, View, InfoSet, Function Module
2).Customer-Generated Extractors - FI-SL, CO-PA
3).Cross Application - Generic Extractors based on Table, View, InfoSet, Function Module
2). What are the steps involved in LO Extraction?
Ans: The steps are
1). RSA5 Select the DataSources
2). LBWE Maintain DataSources and Activate Extract Structures
3). LBWG Delete Setup Tables
4). 0LI*BW Setup tables
5). RSA3 Check extraction and the data in Setup tables
6). LBWQ Check the extraction queue
7).LBWF Log for LO Extract Structures
8). RSA7 BW Delta Queue Monitor
2). LBWE Maintain DataSources and Activate Extract Structures
3). LBWG Delete Setup Tables
4). 0LI*BW Setup tables
5). RSA3 Check extraction and the data in Setup tables
6). LBWQ Check the extraction queue
7).LBWF Log for LO Extract Structures
8). RSA7 BW Delta Queue Monitor
3). What is the difference between ODS and InfoCube and MultiProvider?
Ans:
1). ODS: Provides granular data, allows overwrite and data is in transparent tables and provides operational reports.
2) .CUBE: Follows the star schema, we can only append data i,e additive property and provides analytical reports.
2) .CUBE: Follows the star schema, we can only append data i,e additive property and provides analytical reports.
3). MultiProvider: It is the logical unification of physical infoproviders. It does not have physical data. There should be one characteristic in common for unifying the physical infoproviders.
4). What are Start routines, Transfer routines and Update routines?
Ans:
Start Routines: The start routine is run for each DataPackage after the data has been written to the PSA and before the transfer rules have been executed. It allows complex computations for a key figure or a characteristic. It has no return value. Its purpose is to execute preliminary calculations and to store them in global DataStructures. This structure or table can be accessed in the other routines. The entire DataPackage in the transfer structure format is used as a parameter for the routine.
Transfer / Update Routines: They are defined at the InfoObject level. It is like the Start Routine. It is independent of the DataSource. We can use this to define Global Data and Global Checks.
5). What is the table that is used in start routines?
Ans: Always the table structure will be the structure of an ODS or InfoCube. For example if it is an ODS then active table structure will be the table.
6). Explain how you used Start routines in your project?
Ans: Start routines are used for mass processing of records. In start routine all the records of
DataPackage is available for processing. So we can process all these records together in start routine.
In one of scenario, we wanted to apply size % to the forecast data. For example if material M1 is forecasted to say 100 in May. Then after applying size %(Small 20%, Medium 40%, Large 20%, Extra Large 20%), we wanted to have 4 records against one single record that is coming in the info package. This is achieved in start routine.
7). What are Return Tables?
Ans: When we want to return multiple records, instead of single value, we use the return table in the Update Routine. Example: If we have total telephone expense for a Cost Center, using a return table we can get expense per employee.
8). What is compression?
Ans: When we perform the compression the data in the infocube moves from F-Fact table to the E-Fact table. The entire request IDs will be deleted and compressed into a single request. When you perform this compression by choosing the check box “with zero elimination” keyfigures with the zero values also will be deleted. As a whole compression saves database size and increases the query performance.
9). What is Rollup?
Ans: This is used to load new requests (delta records) in the Infocube into the aggregates. If we have not performed a rollup then the current data (which is not rolled up) will not be available for reporting
10). What is table partitioning and what are the benefits of partitioning in an Infocube?
Ans: It is the method of dividing the fact table which would improve the query performance. We can perform partition only when we have either 0CALMONTH or 0FISCPER in the infocube. When we perform partition the E fact table of the infocube will be partitioned and hence we should perform the compression followed by partition in order to get the partition effect. Partitioning helps to run the report faster as data is stored in the relevant partitions.
11). What are the options available in transfer rules for mapping ?
Ans: InfoObject, Constant, Routine, Formula
12). How would you optimize the dimensions?
Ans: We should define as many dimensions as possible and we have to take care that no single dimension crosses more than 20% of the fact table size. If the dimension table crosses more than 20% of the size of the fact table, we should declare the dimension as line item dimension (There should not be more than one characteristic assigned to a dimension in order to declare it as line item dimension)
13). How to find the size of the dimension table?
Ans: With the program SAP_CUBES_DESIGN
14). What are Conversion Routines for units and currencies in the update rule?
Ans:Using this option we can write ABAP code for Units / Currencies conversion. If we enable this flag then unit of Key Figure appears in the ABAP code as an additional parameter. For example, we can convert units in Pounds to Kilos.
15). Can an InfoObject be an InfoProvider, how and why?
Ans: Yes, when we want to report on Characteristics or Master Data. We have to right click on the InfoArea and select "Insert characteristic as data target". For example, we can make 0CUSTOMER as an InfoProvider and report on it.
16). What is Open Hub Service?
Ans: The Open Hub Service (process) enables us to distribute data from an SAP BW system into external system. In BW 3.5 version an object called Infospoke is used to send data from BW to the external systems. In BI 7 version we use open hub destination (object) for this purpose.
17). What is BW Statistics and what is its use?
Ans: They are group of Business Content InfoCubes which are used to measure performance for Query and Load Monitoring. It also shows the usage of aggregates, OLAP and Warehouse management. There are some standard reports on these infocubes which provides us the in information about the BW system performance as a whole.
18). What are the delta options available when you load from flat file?
Ans: The 3 options for Delta Management with Flat Files:
Full Upload
New Status for Changed records (ODS Object only)
Additive Delta (ODS Object & InfoCube
19). Can we make a datasource to support delta?
Ans: If this is a custom (user-defined) datasource you can make the datasource delta enabled. While creating datasource from RSO2, after entering datasource name and pressing create, in the next screen there is one button at the top, which says generic delta.Generic delta can be enabled based-
1). Time stamp
2). Calendar day
3). Numeric pointer, such as document number & counter
20). How much time does it take to extract 1 million (10 lakhs) of records into an infocube?
Ans: This depends, if you have complex coding in update rules it will take longer time, or else it will take less than 30 minutes.
21).What is ASAP Methodologies?
Ans: ASAP stands for Accelerated SAP methodology which is used to implement and deliver the project efficiently.
The five stages of ASAP methodology asre-
Project plan, Business Blue print, Realization, Final preparation & Go-Live - support.
1. Project Preparation: In this phase the system landscape will be set up.
2. Business Blueprint: It is a detailed documentation of your company's requirements. (i.e. what are the
objects we need to develop are modified depending on the client's requirements).
3. Realization: In this only, the implementation of the project takes place (development of objects etc)
and we are involved in the project from here only.
4. Final Preparation: Final preparation before going live i.e. testing, conducting pre-go-live, end user
training etc.
End user training is given that is in the client site you train them how to work with the new environment,
as they are new to the technology.
5. Go-Live & support: The project has gone live and it is into production. The Project team will be
supporting the end users.
22). Difference between display attributes and navigational attributes?
Ans: Display attribute is one, which is used only for display purpose in the report. Whereas navigational attribute is used for drilling down in the report. We don't need to maintain Navigational attribute in the cube as a characteristic (that is the advantage) to drill down.
23). Some data is uploaded twice into infocube. How to correct it?
Ans: Selective deletion if the data is already compressed otherwise deletes the duplicate request
24). Can number of Datasources have one infosource?
A) Yes of course. For example, for loading text and hierarchies we use different data sources but the same Infosource which is already used for attribute
25). Can many infosources assign to one infoprovider?
Ans: Yes
26). Can many transaction Datasources can be assigned tone infosource?
Ans: No, it’s a one to one assignment in this case.
27). Currency conversions can be written in update rules. Why not in transfer rules?\
Ans:
28). What are the types of data update we have in BW?
Ans: Full, Initialize delta (init), Delta, Repair full
29). What is early delta?
Ans:
30). When do we go for initialization without data transfer?
Ans:
31. Why we delete the setup tables (LBWG) & fill them (OLI*BW)?
Ans: For the first time when we are loading the historical data in the setup tables as a caution we perform deletion for the setup tables in order to avoid any junk data residing in it. Also when a datasource is enhanced we will go for deleting the setup tables followed by the statistical setup (filling setup tables)
32). Why do we have set up tables in LO extraction only but not the other extractions?
Ans: As the historical data volume in case of logistics modules (SD,MM,PP) is high we have setup table which are the intermediate tables of type transparent tables.
33) What Are The Different Variables Used In Bex?
Ans: Different Variable's are Texts, Formulas, Hierarchies, Hierarchy nodes & Characteristic values.
34) What is processing type of a variable?
Ans: The way how the variable gets the input value is called processing type.
We have the following five processing types-
1). Variable Types are
2). Manual entry /default value
3). Replacement path
4). SAP exit
5). Customer exit
6). Authorization
35). How many Levels we can go In Reporting?
Ans: We can drill down to any level by using Navigational attributes and jump targets (RRI).
36). What are Indexes?
Ans: Indexes are data base indexes, which help in retrieving data faster.
37). What is the significance of KPI's?
Ans: KPI’s (Key Performance indicators) indicate the performance of a company. These are key figures
38). What types of partitioning are there for BW?
Ans: There are two Partitioning Performance aspects for BW (Cube & PSA)
39). How can I compare data in R/3 with data in a BW Cube after the daily delta loads? Are there any standard procedures for checking them or matching the number of records?
Ans: You can go to R/3 TCode RSA3 and run the extractor. It will give you the number of records extracted. Then go to BW Monitor to check the number of records in the PSA and check to see if it is the same & also in the monitor header tab.
40). What is the difference between writing a routine in transfer rules and writing a routine in update rules?
Ans: If you are using the same Infosource to update data in more than one data target its better u write in transfer rules because u can assign one InfoSource to more than one data target & and what ever logic we write in update rules it is specific to particular one data target.
41). Can one infosource send data to multiple datatargets?
Ans:Yes
42). What does the number in the 'Total' column in Transaction RSA7 mean?
Ans: The 'Total' column displays the number of LUWs that were written in the delta queue and that have not yet been confirmed. The number includes the LUWs of the last delta request (for repetition of a delta request) and the LUWs for the next delta request. A LUW only disappears from the RSA7 display when it has been transferred to the BW System and a new delta request has been received from the BW System.
43). How and where can I control whether a repeat delta is requested?
Ans: Via the status of the last delta in the BW Request Monitor. If the request is RED, the next load will be of type 'Repeat'. If you need to repeat the last load for certain reasons, set the request in the monitor to red manually. For the contents of the repeat see Question 14. Delta requests set to red despite of data being already updated lead to duplicate records in a subsequent repeat, if they have not been deleted from the data targets concerned before.
44). I would like to display the date the data was uploaded on the report. Usually, we load the
transactional data nightly. Is there any easy way to include this information on the report for users so that they know the validity of the report?
Ans: If I understand your requirement correctly, you want to display the date on which data was loaded into the data target from which the report is being executed. If it is so, configure your workbook to display the text elements in the report. This displays the relevance of data field, which is the date on which the data load has taken place.
45). How many days can we keep the data in PSA?
Ans: In our project we delete the PSA tables and ChangeLog tables excluding recent 10 days tables.
46). How can u get the data from client if u r working on offshore projects? Through which network.
Ans: VPN (Virtual Private Network), VPN is nothing but one sort of network where we can connect to the client systems sitting in offshore through RAS (Remote access server).
47). In BW we need to write abap routines. I wish to know when and what type of abap routines we got to write. Also, are these routines written in update rules? I will be glad, if this is clarified with real-time scenarios and few examples?
Ans: Over here we write our routines in the start routines in the update rules or in the transfer structure (you can choose between writing them in the start routines or directly behind the different characteristics. In the transfer structure you just click on the yellow triangle behind a characteristic and choose "routine". In the update rules you can choose "start routine" or click on the triangle with the green square behind an individual characteristic. Usually we only use start routine when it does not concern one single characteristic (for example when you have to read the same table for 4 characteristics).
We used ABAP Routines for example:
1). To convert to Uppercase (transfer structure)
2). To convert Values out of a third party tool with different keys into the same keys as our SAP System uses (transfer structure)
3). To select only a part of the data for from an infosource updating the Infocube (Start Routine) etc.
48). What does Infocube contains?
Ans: Each Infocube has a Fact Table and a maximum of 16 (13 userdefined+3 system defined, time, unit & data packet) dimensions.
49). What does FACT Table contain?
Ans: Fact Table consists of Keyfigures which hold the transaction data. Each Fact Table can contain a maximum of 233 key figures.
Note: One Dimension table can be assigned with 248 characteristics.
50). What does SID Table contain?
Ans: SID keys linked with dimension table & master data tables (attributes, texts, hierarchies)
51). What are the different master data tables in BW?
Ans:
52). Differences between STAR Schema & Extended Star Schema?
Ans: In STAR SCHEMA, A FACT Table in center, surrounded by dimensional tables and the dimension tables contains of master data. In Extended Schema the dimension tables does not contain master data, instead they are stored in Master data tables divided into attributes, text & hierarchy. These Master data & dimensional tables are linked with each other with SID keys. Master data tables are independent of Infocube & reusability in other InfoCubes.
53). When are Dimension ID's created?
Ans: When Transaction data is loaded into Infocube.
54). When are SID's generated?
Ans: When Master data loaded into Master Tables (Attribute, Text, Hierarchies).
55). How would we delete the data in ODS?
Ans: By request IDs, Selective deletion & change log entry deletion.
56). Partitioning possible for ODS?
Ans: No, It is possible only for Infocube and PSA in BW
57). Different types of Attributes?
Ans: Navigational attribute, Display attributes, Time dependent attributes, Compounding attributes, Transitive attributes.
58). Transitive Attributes?
Ans: Navigational attributes having navigational attribute, these navigational attributes are called transitive attributes.
59). Compounding attribute?
Ans:
60). Time dependent attributes?
Ans:
61). Steps in LO are Extraction?
Ans:
1. Maintain extract structures. (R/3)
2. Maintain DataSources. (R/3)
3. Replicate DataSource in BW.
4. Assign InfoSources.
5. Maintain communication structures/transfer rules.
6. Maintain InfoCubes & Update rules.
7. Activate extract structures. (R/3)
8. Delete setup tables/setup extraction. (R/3)
9. InfoPackage for the Delta initialization.
10. Set-up periodic V3 update. (R/3)
11. InfoPackage for Delta uploads.
62). Different types delta update modes in LO Extraction?
Ans: Direct Delta, Queued Delta, Serialized V3 update, Unserialized V3 Update.
Direct Delta: - In case of Direct delta LUW’s are directly posted to Delta Queue (RSA7) and we extract the LUW’s from Delta Queue to SAP BW by running Delta Loads. If we use Direct Delta it degrades the OLTP system performance because when LUW’s are directly posted to Delta Queue (RSA7) the application is kept waiting until all the enhancement code is executed.
Queued Delta: - In case of Queued Delta LUW’s are posted to Extractor queue (LBWQ), by scheduling the V3 job we move the documents from Extractor queue (LBWQ) to Delta Queue (RSA7) and we extract the LUW’s from Delta Queue to SAP BW by running Delta Loads. Queued Delta is recommended by SAP it maintain the Extractor Log which us to handle the LUW’s, which are missed.
Serialized V3 update:- In case of Serialized V3 update LUW’s are posted to Update Queue (SM13), by scheduling the V3 job which move the documents from Extractor queue (LBWQ) to Delta Queue (RSA7) in a serialized fashion and we extract the LUW’s from Delta Queue to SAP BW by running Delta Loads. Since the LUW’s are moved in a Serial fashion from Update queue to Delta queue if we have any error document it doesn’t lift the subsequent documents and as it sorts the documents based on the creation time, there every possibility for frequent failures in V3 job and missing out the delta records. It also degrades the OLTP system performance as it forms multiple segments with respective to the change in the language.
Unserialized V3 Update:- In case of Un serialized V3 update LUW’s are posted to Update Queue ( SM13 ), by scheduling the V3 job which move the documents from Extractor queue ( LBWQ ) to Delta Queue ( RSA7 ) and we extract the LUW’s from Delta Queue to SAP BW by running Delta Loads. Since the LUW’s are not moved in a Serial fashion from Update queue to Delta queue if we have any error document it considers the subsequent documents and no sorting of documents based on the creation time. It improves the OLTP system performance as it forms a segment for one language.
63). Some important T Codes?
Ans:
RSA6 -- Post processing of data sources
RSA7-- Delta Queue (allows you to monitor the current status of the delta attribute)
RSA3-- Extract checker.
LBWG -- Delete set-up tables in LO's.
OLI*BW-- Fill Set-up tables.
LBWE -- TCode for Logistics extractors.
RSO2 -- Maintaining Generic DataSources.
PFCG -- Role maintenance, assign users to these roles.
RSDCUBEM --- For Delete, Change or Delete the Infocube.
RSMO --- Monitoring of Dataloads.
RSCUSTV6 -- Partitioning of PSA.
RSRT -- Query monitor.
RSRV -- Analysis and Repair of BW Objects
RRMX -- BEx Analyzer
RSBBS -- Report to Report interface (RRI).
SPRO -- IMG (To make configurations in BW).
RSDDV -- Maintaining Aggregates.
RSKC -- Permit Special characteristics.
ST22 -- Checking Short Dump.
SM37 -- Scheduling Background jobs.
RSBOH1 - Open Hub Service: Create Infospoke.
ROOSOURCE - Table to find out details of Datasources.
SMOD - SAP Exits
CMOD - Customer Exits
SE11 - ABAP Dictionary – Create tables views and other objects.
SE16 - To see the data in tables, views and structures.
SE09 - Transport Organizer (workbench organizer) - Transport requests will be released
SE10 - Transport Organizer (Extended View)
SBIW - T-code used in LO Extraction for various aspects
64). What are Process Types & Process variant in process chain maintenance?
Ans: Process types are General services, Load Process & subsequent processing, Data Target
Administration, reporting agent & Other BW services. Process variant (start variant) is the place the process type knows when & where to start.
65). What is the T-Code to delete BEx query in production system?
Ans: RSZDELETE
66). what is the T-code for Copying Queries from one infoprovider to another infoprovider?
Ans: RSZC
67). How much time does it take to extract 1 million (10 lackhs) of records into an infocube?
Ans: This depends, if you have complex coding in update rules it will take longer time, or else it will take less than 30 minutes.
67). How to know in which table (SAP BW) contains Technical Name / Description and creation data of a particular Reports. Reports that are created using BEx Analyzer?
Ans: There is no such table in BW if you want to know such details while you are opening a particular query press properties button you will come to know all the details that you wanted. You will find your information about technical names and description about queries in the following tables. Directory of all reports (Table RSRREPDIR) and Directory of the reporting component elements (Table RSZELTDIR) for workbooks and the connections to queries check Where- used list for reports in workbooks (Table RSRWORKBOOK) Titles of Excel Workbooks in InfoCatalog (Table RSRWBINDEXT)
68). What is a LUW in the delta queue?
Ans: A LUW from the point of view of the delta queue can be an individual document, a group of documents from a collective run or a whole data packet of an application extractor.
69). Difference between Calculated KeyFigure & Formula?
Ans: Calculated keyfigure is the virtual keyfigure which is created based on physical keyfigures and some functions.CKF is global across all the queries on the same infoprovider. New same as CKF but its local to the query where it is created.
70). When does a transfer structure contain more fields than the communication structure of an Infosource?
Ans: If we use a routine to enhance a field in the communication from several fields in the transfer structure, the communication structure may contain more fields.
71). Why we use this RSRP0001 Enhancement?
Ans : For enhancing the Customer Exit in reporting.
72). What is the use of Filters?
Ans: It Restricts Data.
73). What is the use of Conditioning?
Ans: To retrieve data based on particular conditions like less than, greater than, less than or equal etc.,
74). What is NODIM?
Ans: For example it converts 5lts + 5kgs = 10. NODIM will be available in the functions set in BEX and this is used to remove the dimensions.
75). Why SAPLRSAP is used?
Ans: We use these function modules for enhancing the datasources in r/3. We have four EXITS –
SAPLRSAP_EXIT_001- Transaction datasources
SAPLRSAP_EXIT_002- Master Data Attribute
SAPLRSAP_EXIT_003- Master Data Text
SAPLRSAP_EXIT_004- Master Data Hierarchy
76). What are workbooks & uses?
Ans: Saved output of a query is called workbook
77). Where are workbooks saved?
Ans: Workbooks are saved in favorites.
78). Can Favorites accessed by other users?
Ans: No, they need authorization.
79). What is Business Content?
Ans: Business Content is the umbrella term for the preconfigured BW objects delivered by SAP. These objects provide ready-made solutions to basic business information requirements and are used to accelerate the implementation of a BW. TCODE RSOR(BW), RSA5(R/3)
Business Content includes:
R/3 extractor programs, DataSources, InfoObjects, InfoSources, InfoCubes, Queries, Roles, and Workbooks. From the Grouping menu, choose the additional Business Content objects that you want to include. Groupings gather together all of the objects from a single area:
Only Necessary Objects: Only those additional objects that are needed to activate the objects that you have selected are included (minimum selection). In Data Flow Before: All the objects that pass data on to another object are collected. In Data Flow Afterwards: All the objects that receive data from another object are collected. In Data Flow Before and Afterwards: All the objects that both deliver and receive data are collected.
Backup for System Copy: You use this setting to collect some of the objects into a transport
Request
80). If you update data from ODS to data target. System will generate InfoSource with one prefix name?
Ans: It will generate with prefix name starting with 8 along with InfoSource name.
81). What is an aggregate?
Ans: Aggregates are small or baby cubes. A subset of InfoCube.
Flat Aggregate --when u have more than 15 characteristics for aggregate system will generate that aggregate as flat aggregate to increase performance.
Roll-up--when the data is loaded for second time into cube, we have to roll-up to make that dataavailable in aggregate.
82). What is Line-Item Data, in which scenario u use line item dimension?
Ans: A line item dimension in a fact table does not have the dimension table; it connects directly with the SID table at its sole characteristic. When there is only one characteristic in a dimension, it will eliminate the dimension table. Fact table directly linked to the SID table. When the size of the dimension table is more than 20% size of the fact table we will go for line item dimension
83). You can convert currencies at 2 places?
Ans: One is at update rule level & one at the front-end
84). How can we stop loading data into infocube?
Ans: First you have to find out what is the job name from the monitor screen for this load
In Header Tabstrip in monitor screen . Go to SM37 (job monitoring) in R/3 select this job and from the menu you can delete the job. Job cancellation is not suggestible for delta load.
85). What's the difference between R3 drill down reporting and BW reporting?
These two reporting seem to function similarly with slice and dice. If they function similarly, then that means we don't have to implement BW, just use R3 Drill down reporting tool, am I right?
Ans: The major benefits of reporting with BW over R/3 are in terms of performance and analysis.
1. Performance -- Heavy reporting along with regular OLTP transactions can produce a lot of load both on the R/3 and the database (cpu, memory, disks, etc). Just take a look at the load put on your system during a month end, quarter end, or year-end -- now imagine that occurring even more frequently.
2. Data analysis -- BW uses a Data Warehouse and OLAP concepts for storing and analyzing data, where R/3 was designed for transaction processing. With a lot of work you can get the same analysis out of R/3 but most likely would be easier from a BW
86). What is the Difference between Transfer Rules and Update Rules ?
Ans:
Transfer Rules : Which specifies how the mapping between the Data Source fields with the Infosource fields (So called Communication Structure).
Update Rules : Which specifies how data will be updated into the Data Targets (ODS or InfoCube). (Which internally does some techinical name mapping)
87). In update rules for key figures, what are the return table options for?
Ans: Usually the update rule sends one record to the data target; using this option you can send multiple records to the data target eg. If you get 1 record from the
communication structure using this option you can create multiple records into the data target. For exa mple if we are getting total telephone expenses for the cost center, you can use this to return telephone expenses for each employee (by dividing the total expenses by the number of employees in the cost center) and creating cost record for each employee using ABAP code.
SAP Bw Interview Questions With IBM/HP
1)How we do the SD and MM configuration for BW ?
You need to activate the data sources in R3 system.
You need to maintain the login information for the logical system.sm59 : Choose the RFC destination , BW system, Under logon Security, maintain the user credentials.
Maintain control parameters for data transfer.
Filling in of setup tables SBIW
I feel that these are certain prerequisites.
From an SD perspective, you as a BW consultant should first understand the basic SD process flow on the R3 side. (search the forum for SD process flow and you'll get a wealth of information on the flow and the tables as well as transactions involved in SD).
Next you need to understand the process flow that has been implemented at the clients place. How the SD data flows and what are the integration points with other modules as well as how the integration happens.
This knowledge is essential when modeling your BW design.
From a BW perspective you need to first know all the SD extractors and what information they bring. Next look at all the cubes and ODS for SD.
1. What is the t-code to see log of transport connection?
in RSA1 -> Transport Connection you can collect the Queries and the Role and after this you can transport them (enabling the transport in SE10, import it in STMS
1. RSA1
2. Transport connection (button on the left bar menu)
3. Sap transport -> Object Types (button on the left bar menu)
4. Find Query Elements -> Query
5. Find your query
6. Group necessery object
7. Transport Object (car icon)
8. Release transport (SE10 T-code)
9. load transport (STMS T-code)
2.Lo; mm inventory data source with marker significance?
Marker is as like check point when u upload the data from inventory data source
2lis_03_bx data source for current stock and BF for movement type
after uploading data from BX u should rlise the request in cube or i menn to say compress it then load data from another data source BF and set this updated data to no marker update so marker is use as a check point if u dont do this u getting data missmatch at bex level bcz system get confuse .
(2LIS_03_BF Goods Movement From Inventory Management-- -----Unckeck the no marker update tab)
(2LIS_03_BX Stock Initialization for Inventory Management-- ---select the no marker update check box)
2LIS_03_UM Revaluations ----Uncheck the no marker update tab) in the infopackege of "collaps"
3. How can you navigate to see the error idocs ?
If it is fine check the IDOCs in source system go to BD87->give Ur user ID and date->execute->you can find Red status Idocs select the erroneous Idoc->Rt.click and select Manual process.
You need to Reprocess this IDOC which are RED. For this you can take help of Any of your Team (ALE IDOC Team or BAsis Team)Or Else
youcan push it manually. Just search it in bd87 screen only to Reprocess.
Also, Try to find why this IDocs are stuck there.
4)Difference between v1, v2, v3 jobs in extraction?
V1 Update: when ever we create a transaction in R/3(e.g.,Sales Order) then the entries get into the R/3 Tables(VBAK, VBAP..) and this takes place in V1 Update.
V2 Update: V2 Update starts a few seconds after V1 Update and in this update the values get into Statistical Tables, from where we do the extraction into BW.
V3 Update: Its purely for BW extraction.
But in the Document below, V1, V2 and V3 are defined in a different way. Can You please explain me in detial what exactly V1, V2 and V3 updates means?
5.What are statistical update and document update?
Synchronous Updating (V1 Update)
The statistics update is made synchronously with the document update.
While updating, if problems that result in the termination of the
statistics update occur, the original documents are NOT saved. The cause
of the termination should be investigated and the problem solved.
Subsequently, the documents can be entered again.
Radio button: V2 updating
6.Do you have any idea how to improve the performance of the BW..?
Asynchronous Updating (V2 Update)
With this update type, the document update is made separately from the statistics update. A termination of the statistics update has NO influence on the document update (see V1 Update).
Radio button: Updating in U3 update program
Asynchronous Updating (V3 Update)
With this update type, updating is made separately from the document update. The difference between this update type and the V2 Update lies,however, with the time schedule. If the V3 update is active, then the update can be executed at a later time.
In contrast to V1 and V2 Updates, no single documents are updated. The V3 update is, therefore, also described as a collective update.
7)How can you decide the query performance is slow or fast ?
You can check that in RSRT tcode.
execute the query in RSRT and after that follow the below steps
Goto SE16 and in the resulting screen give table name as RSDDSTAT for BW 3.x and RSDDSTAT_DM for BI 7.0 and press enteryou can view all the details about the query like time taken to execute the query and the timestmaps
8)What is statistical setup and what is the need and why?
Follow these steps to filling the set up table.
1. Go to transaction code RSA3 and see if any data is available related to your DataSource. If data is there in RSA3 then go to transaction code LBWG (Delete Setup data) and delete the data by entering the application name.
2. Go to transaction SBIW --> Settings for Application Specific Datasource --> Logistics --> Managing extract structures --> Initialization --> Filling the Setup table --> Application specific setup of statistical data --> perform setup (relevant application)
3. In OLI*** (for example OLI7BW for Statistical setup for old documents : Orders) give the name of the run and execute. Now all the available records from R/3 will be loaded to setup tables.
4. Go to transaction RSA3 and check the data.
5. Go to transaction LBWE and make sure the update mode for the corresponding DataSource is serialized V3 update.
6. Go to BW system and create infopackage and under the update tab select the initialize delta process. And schedule the package. Now all the data available in the setup tables are now loaded into the data target.
7. Now for the delta records go to LBWE in R/3 and change the update mode for the corresponding DataSource to Direct/Queue delta. By doing this record will bypass SM13 and directly go to RSA7. Go to transaction code RSA7 there you can see green light # Once the new records are added immediately you can see the record in RSA7.
8. Go to BW system and create a new infopackage for delta loads. Double click on new infopackage. Under update tab you can see the delta update radio button..
9. Now you can go to your data target and see the delta record.
9.Why we have construct setup tables?
The R/3 database structure for accounting is much more easier than the Logistical structure.
Once you post in a ledger that is done. You can correct, but that give just another posting.
BI can get information direct out of this (relatively) simple database structure.
In LO, you can have an order with multiple deliveries to more than one delivery addresses. And the payer can also be different.
When 1 item (orderline) changes, this can have its reflection on order, supply, delivery, invoice, etc.
Therefore a special record structure is build for Logistical reports.and this structure now is used for BI.
In order to have this special structre filled with your starting position, you must run a set-up. from that moment on R/3 will keep filling this LO-database.
If you wouldn't run the setup. BI would start with data from the moment you start the filling of LO (with the logistica cocpit)
10.How can you eliminate the duplicate records in TD, MD?Try to check the system logs through SM21 for the same.
11.What use marker in MM?
Marker update is just like check point.
ie it will give the snapshot of the stock on a particular date ie when was the marker updated.
Because we are using Noncumulative keyfigure it will lot of time to calculate the current stock for example at report time. to overcome this we use marker update
Marker updates do not summarize the data.. In inventory management scenarios, we have to calculate opening stock and closing stock on a daily basis. In order to facilitate this, we set a marker which will add and subtract the values for each record.
In the absence of marker update, the data will be added up and will not provide the correct values.
12.Tell me web template?
You get information on where the web template details are stored from the following tables :
RSZWOBJ Storage of the Web Objects
RSZWOBJTXT Texts for Templates/Items/ Views
RSZWOBJXREF Structure of the BW Objects in a Template
RSZWTEMPLATE Header Table for BW HTML Templates
You can check these tables and search for your web template entry . However, If I understand your question correctly , you will have to open the template in the WAD and then make the corrections in the same to correct it.
13.What is dashboard?
A dash board can be created using the web application Designer (WAD) or the visual composer (VC). A dashboard is just a collection of reports, views and links etc in a single view. For e.g. igoogle is a dashboard.
A dashboard is a graphical reporting interface, which displays KPIs (Key Performance Indicators) as charts and graphs. A dashboard is a performance management system
When we look at the all organization measures how they are performing with helicopter view, we need a report that teaches and shows the trend in a graphical display quickly. These reports are called as Dashboard Reports, still we can report these measures individually, but by keeping all measures in a single page, we are creating single access point to the users to view all information available to them. Absolutely this will save lot of precious time, gives clarity on decision that needs to be taken, helps the users to understand the measure(s) trend with business flow creating dashboard
Dashboards : Could be built with Visual Composer & WAD
create your dashboard in BW,
(1) Create all BEx Queries with required variants,tune them perfectly.
(2) Differentiate table queries and graph queries.
(3) Choose the graph type required that meet your requirement.
(4) Draw the layout how the Dashboard page looks like.
(5) Create a web template that has navigational block / selection information.
(6) Keep navigational block fields are common across the measures.
(7) Include the relevant web items into web template.
(8) Deploy the URL/Iview to users through portal/intranet
The steps to be followed in the creation of Dashboard using WAD are summarized as below:
1) Open a New Web template in WAD.
2) Define the tabular layout as per the requirements so as to embed the necessary web items.
3) Place the appropriate web items in the appropriate tabular grids
4) Assign queries to the web items (A Query assigned to a web item is called as a data provider)
5) Care should be taken to ensure that the navigation block’s selection parameters are common across all the BEx queries of the affected dataproviders.
6) Properties of the individual web items are to be set as per the requirements. They can be modified in Properties window or in the HTML code.
7) The URL when this web template is executed should be used in the portal/intranet
14.How can you solve the data mismatch tickets between r/3 and bw?
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.
15. What is thumb rule?
16)What is replacement path tell me one scenario?
http://www.sd- solutions. com/documents/ SDS_BW_Replaceme nt%20Path% 20Variables. html
17.What is difference between PSA & IDOC?
BI7 is PSA used only for Data load from Source System into BW
18). what we do in Business Blue Print Stage?
SAP has defined a business blueprint phase to help extract pertinent information about your company that is necessary for implementation. These blueprints are in the form of questionnaires that are designed to probe for information that uncovers how your company does business. As such, they also serve to document the implementation. Each business blueprint document essentially outlines your future business processes and business requirements. The kinds of questions asked are germane to the particular business function, as seen inthe following sample questions:1) What information do you capture on a purchase order?2) What information is required to complete a purchase order?Accelerated SAP question and answer database:The question and answer database (QADB) is a simple although aging tool designed to facilitate the creation and maintenance of your business blueprint.This database stores the questions and the answers and serves as the heart of your blue print. Customers are provided with a customer input template for each application that collects the data. The question and answer format is standard across applications to facilitate easier use by the project team.Issues database: Another tool used in the blueprinting phase is the issues database. Thisdatabase stores any open concerns and pending issues that relate to the implementation. Centrally storing this information assists in gathering and then managing issues to resolution, so that important matters do not fall through the cracks. You can then track the issues in database, assign them to teammembers, and update the database accordingly.
19). How do we gather the requirements for an Implementation Project?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 useThis process involves one seemingly simple task: Find out exactly what theend users' analysis requirements are, both now and in the future, and buildthe BW system to these requirements. Although simple in concept, in practicegathering and reaching a clear understanding and agreement on a complete setof BW functional requirements is not always so simple.
20) How do we decide what cubes has to be created?
Its depends on your project requirement. Customized cubes are not mandatory for all the projects. If your bussines 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 implemention. 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 scenrio we could'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 asreports.
21) Who used to make the Technical and Functional Specifications?
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.
22) Give me one example of a Functional Specification and explain what information we will get from that?Functional Specs are requirements of the business user.Technical Specs translate these requirements in a technical fashion.Let's say Functional Spec says,1. the user should be able to enter the Key date, Fiscal Year, Fiscal Version.2. The Company variable should be defaulted to USA but then if the user wants to change it, they can check the drop down list and choose other countries.3. The calculations or formulas for the report will be displayed in precision of one decimal point.4. The report should return values for 12 months of data depending on the fiscal year that the user enters Or it should display in quarterly values. Functional specs are also called as Software requirements.Now from this Techinal Spec follows, to resolve each of the line items listed above.1. To give the option of key date, Fiscal year and Fiscal Version – certain Info Obejcts should be availble in the system. If available, then should we create any variables for them - so that they are used as user entry variable. To create any varaibles, what is the approch, where do you do it, what is the technical of the objects you'll use, what'll be the technical name of the objects you'll crete as a result of this report.2. Same explanation goes for the rest. How do you set up the varaible,
3. What changes in properties willu do to get the precision.4. How will you get the 12 months of data.What will be the technical and display name of the report, who'll be authorized to run this report, etc are clearly specified in the technical specs.
23) What is Customization? How do we do in LO?
How to do basic LO extraction for SAP-R3-BW1. Go to transaction code RSA3 and see if any data is available related to your DataSource. If data is there in RSA3 then go to transaction code LBWG (Delete Setup data) and delete the data by entering the application name.2. Go to transaction SBIW --> Settings for Application Specific Datasource --> Logistics --> Managing extract structures --> Initialization --> Filling the Setup table --> Application specific setup of statistical data --> perform setup (relevant application)3. In OLI*** (for example OLI7BW for Statistical setup for old documents : Orders) give the name of the run and execute. Now all the available records from R/3 will be loaded to setup tables.4. Go to transaction RSA3 and check the data.5. Go to transaction LBWE and make sure the update mode for the corresponding DataSource is serialized V3 update.6. Go to BW system and create infopackage and under the update tab select the initialize delta process. And schedule the package. Now all the data available in the setup tables are now loaded into the data target.7.Now for the delta records go to LBWE in R/3 and change the update mode for the corresponding DataSource to Direct/Queue delta. By doing this record will bypass SM13 and directly go to RSA7. Go to transaction code RSA7 there you can see green light # Once the new records are added immediately you can see the record in RSA7.
24) When we use Maintain Data Source, What we do? What we will maintain?
Go to BW system and create a new infopackage for delta loads. Double click on new infopackage. Under update tab you can see the delta update radio button.
25) Tickets and Authorization in SAP Business Warehouse What is tickets? And example?Tickets are the tracking tool by which the user will track the work which we do. It can be a change requests or data loads or what ever. They will of types critical or moderate. Critical can be (Need to solve in 1 day or half a day) depends on the client. After solving the ticket will be closed by informing the client that the issue is solved. Tickets are raised at the time of support project these may be any issues, problems.... .etc. If the support person faces any issues then he will ask/request to operator to raise a ticket.
Operator will raise a ticket and assign it to the respective person. Critical means it is most complicated issues ....depends how you measure this...hope it helps. The concept of Ticket varies from contract to contract in between companies. Generally Ticket raised by the client can be considered based on the priority. Like High Priority, Low priority and so on. If a ticket is of high priority it has to be resolved ASAP. If the ticket is of low> priority it must be considered only after attending to high priority tickets. The typical tickets in a production Support work could be: 1. Loading any of the missing master data attributes/texts. 2. Create ADHOC hierarchies. 3. Validating the data in Cubes/ODS. 4. If any of the loads runs into errors then resolve it. 5. Add/remove fields in any of the master data/ODS/Cube. 6. Data source Enhancement. 7. Create ADHOC reports.
1. Loading any of the missing master data attributes/texts - This would be done by scheduling the infopackages for the attributes/texts mentioned by the client. 2. Create ADHOC hierarchies. - Create hierarchies in RSA1 for the info-object. 3. Validating the data in Cubes/ODS. - By using the Validation reports or by comparing BW data with R/3. 4. If any of the loads runs into errors then resolve it. - Analyze the error and take suitable action. 5. Add/remove fields in any of the master data/ODS/Cube. - Depends upon the requirement 6. Data source Enhancement. 7. Create ADHOC reports. - Create some new reports based on the requirement of client.
26) Change attribute run.
Generally attribute change run is used when there is any change in the master data..it is used for realingment of the master data..Attribute change run is nothing but adjusting the master data after its been loaded from time to time so that it can change or generate or adjust the sid's so that u may not have any problem when loading the trasaction data in to data targets.the detail explanation about Attribute change run.The hierarchy/attribute change run which activates hierarchy and attribute changes and adjusts the corresponding aggregates is devided, into 4 phases:1. Finding all affected aggregates2. set up all affected aggregates again and write the result in the new aggregate table.3. Activating attributes and hierarchies4. rename the new aggregate table. When renaming, it is not possible to execute queries. In some databases, which cannot rename the indexes, the indexes are also created in this phase.
27) Different types of Delta updates?
Delta loads will bring any new or changed records after the last upload.This method is used for better loading in less time. Most of the std SAP data sources come as delta enabled, but some are not. In this case you can do a full load to the ODS and then do a delta from the ODS to the cube. If you create generic datasources, then you have the option of creating a delta onCalday, timestamp or numeric pointer fields (this can be doc number, etc).You'll be able to see the delta changes coming in the delta queue through RSA7 on the R3 side.To do a delta, you first have to initialize the delta on the BW side and then set up the delta.The delta mechanism is the same for both Master data and Transaction data loads.============ ========= ==There are three deltasDirect Delta: With this update mode, the extraction data is transferred with each document posting directly into the BW delta queue. In doing so, each document posting with delta extraction is posted for exactly one LUW in the respective BW delta queues.Queued Delta: With this update mode, the extraction data is collected for the affected application instead of being collected in an extraction queue, and can be transferred as usual with the V3 update by means of an updating collective run into the BW delta queue. In doing so, up to 10000 deltaextractions of documents for an LUW are compressed for each Data Source into the BW delta queue, depending on the application.Non-serialized V3 Update: With this update mode, the extraction data for the application considered is written as before into the update tables with the help of a V3 update module. They are kept there as long as the data is selected through an updating collective run and are processed. However, in contrast to the current default settings (serialized V3 update), the data in the updating collective run are thereby read without regard to sequence from the update tables and are transferred to the BW delta queue.
28) Function modules;1) UNIT_CONVERSION_ SIMPLE and2) MD_CONVERT_MATERIAL _UNITexplain how to use these things, if possible with a well explained example.
The conversion of units of measure is required to convert business measurements into other units. Business measurements encompass physical measurements which are either assigned to a dimension or are nondimensional. Nondimensional measurements are understood as countable measurements(palette, unit..).You differentiate between conversions for which you only need to enter a source and target unit in order to perform conversion and conversions for which specifying these values alone is not sufficient. For the latter, you have to enter a conversion factor which is derived from a characteristic ora characteristic combination (compound characteristic) and the corresponding properties....1. Measurements of lengthConversions within the same dimension ID (T006-DIMID) – for example, length:1 m = 100 cm (linear correlation)*Meter* and *Centimeter* both belong to dimension ID LENGTH.2. Measurements of number associated with measurements of weightConversions involving different dimension IDs – for example, number andweight.1 unit = 25 g (linear correlation)*Unit* has dimension ID AAAADL and *Gram* has dimension ID MASS.ExampleNumber
Unit Number Unit1
Chocolate bar 25 g1 Small carton 12 Chocolate bar1 Large carton 20 Small carton1 Europallet 40 Large carton* Quantity Conversion*
<http://help.sap.com/saphelp_nw2004s/helpdata/en/27/b65c42b4e05542e10000000a1550b0/frameset.htm>* *UseQuantity conversion allows you to convert key figures with units that have different units of measure in the source system into a uniform unit of measure in the BI system.FeaturesThis function enables the conversion of updated data records from the source unit of measure into a target unit of measure, or into different target units of measure, if the conversion is repeated. In terms of functionality, quantity conversion is structured similarly to currency translation.In part it is based on the quantity conversion functionality in SAP NetWeaver Application Server. Simple conversions can be performed between units of measure that belong to the same dimension (such as meters to kilometers, kilograms to grams). You can also perform InfoObject-specific conversions (for example, two palettes (PAL) of material 4711 were ordered and this order quantity has to be converted to the stock quantity *Carton*(CAR) ).Quantity conversion is based on quantity conversion types. The business transaction rules of the conversion are established in the quantity conversion type. The conversion type is a combination of different parameters (conversion factors, source and target units of measure) that determine how the conversion is performed. For more information, see QuantityConversion Types<http://help.sap.com/saphelp_nw2004s/helpdata/en/1c/1b5d427609c153e10000000a1550b0/content.htm>.IntegrationThe quantity conversion type is stored for future use and is available for quantity conversions in the transformation rules for InfoCubes and in the Business Explorer:In the transformation rules for InfoCubes you can specify, for each key figure or data field, whether quantity conversion is performed during the update. In certain cases you can also run quantity conversion in user-defined routines in the transformation rules..In the Business Explorer you can:● Establish a quantity conversion in the query definition.● Translate quantities at query runtime. Translation is more limitedhere than in the query definition.[image: This graphic is explained in the accompanying text]*Quantity Conversion Types*<http://help.sap.com/saphelp_nw2004s/helpdata/en/1c/1b5d427609c153e10000000a1550b0/frameset.htm>DefinitionA quantity conversion type is a combination of different parameters that establish how the conversion is performed. StructureThe parameters that determine the conversion factors are the source and target unit of measure and the option you choose for determining the conversion factors.The decisive factor in defining a conversion type is the way in which you want conversion factors to be determined. Entering source and target quantities is optional.Conversion FactorsThe following options are available:· Using a reference InfoObjectThe system tries to determine the conversion factors from the reference InfoObject you have chosen or from the associated quantity DataStore object.If you want to convert 1000 grams into kilograms but the conversion factors are not defined in the quantity DataStore object, the system cannot perform the conversion, even though this is a very simple conversion.· Using central units of measure (T006)Conversion can only take place if the source unit of measure and target unit of measure belong to the same dimension (for example, meters to kilometers, kilograms to grams, and so on).· Using reference InfoObject if available, central units of measure (T006) if notThe system tries to determine the conversion factors using the quantity DataStore object you have defined. If the system finds conversion factors, it uses these to perform the calculation. If the system cannot determine conversion factors from the quantity DataStore object it tries again usingthe central units of measure.· Using central units of measure (T006) if available, reference InfoObject if notThe system tries to find the conversion factors in the central units of measure table. If the system finds conversion factors it uses these to perform the conversion. If the system cannot determine conversion factors from the central units of measure it tries to find conversion factors that match the attributes of the data record by looking in the quantity DataStore object.The settings that you can make in this regard affect performance and the decision must be strictly based on the data set. If you only want to perform conversions within the same dimension, option 2 is most suitable.If you are performing InfoObject-specific conversions (for example, material-specific conversions) between units that do not belong to the same dimension, option 1 is most suitable.In both cases, the system only accesses one database table. That table contains the conversion factors.With option 3 and option 4, the system tries to determine conversion factors at each stage. If conversion factors are not found in the basic table (T006), the system searches again in the quantity DataStore object, or in reverse.The option you choose should depend on how you want to spread the conversion. If the source unit of measure and target unit of measure belong to the same dimension for 80% of the data records that you want to convert, first try to determine factors using the central units of measure (option4), and accept that the system will have to search in the second table also for the remaining 20%.The *Conversion Factor from InfoObject *option (as with *Exchange Rate from InfoObject* in currency translation types) is only available when you load data. The key figure you enter here has to exist in the InfoProvider and the attribute this key figure has in the data record is taken as the conversionfactor.Source Unit of MeasureThe source unit of measure is the unit of measure that you want to convert. The source unit of measure is determined dynamically from the data record or from a specified InfoObject (characteristic) . In addition, you can specify a fixed source unit of measure or determine the source unit of measure using avariable.When converting quantities in the Business Explorer, the source unit of measure is always determined from the data record.During the data load process the source unit of measure can be determined either from the data record or using a specified characteristic that bears master data.You can use a fixed source unit of measure in planning functions. Data records are converted that have the same unit key as the source unit of measure.The values in input help correspond to the values in table T006 (units of measure).You reach the maintenance for the unit of measure in *SAP Customizing Implementation Guide* (r) *SAP NetWeaver *(r) *General Settings* (r) *Check Units of Measure*.In reporting, you can use a source unit of measure from a variable. The variables that have been defined for InfoObject 0UNIT are used.
Target Unit of MeasureYou have the following options for determining the target unit of measure:· You can enter a fixed target unit of measure in the quantityconversion type (for example, 'UNIT').· You can specify an InfoObject in the quantity conversion type that is used to determine the target unit of measure during the conversion. This is not the same as defining currency attributes where you determine a currency attribute on the *Business Explorer* tab page in characteristic maintenance. With quantity conversion types you determine the InfoObject in the quantity conversion type itself. Under *InfoObject for Determining Unit of Measure*, all InfoObjects are listed that have at least one attribute of type *Unit*. You have to select one of these attributes as the corresponding quantity attribute.· Alternatively, you can determine that the target unit of measure be determined during the conversion. In the Query Designer under the properties for the relevant key figure, you specify either a fixed target unit of measure or a variable to determine the target unit of measure.· Target quantity using InfoSetThis setting covers the same functionality as *InfoObject for Determining Target Quantity*. If the InfoObject that you want to use to determine the target quantity is unique in the InfoSet (it only occurs once in the whole InfoSet), you can enter the InfoObject under *InfoObject for DeterminingTarget Quantity*.You only have to enter the InfoObject in *Target Quantity Using InfoSet* if you want to determine the target quantity using an InfoObject but that occurs more than once in the InfoSet.The InfoSet contains InfoProviders A and B and both A and B contain InfoObject X with a quantity attribute. In this case you have to specify exactly whether you want to use X from A or X from B to determine the target quantity. Field aliases are used in an InfoSet to ensure uniqueness.All the active InfoSets in the system can be displayed using input help. As long as you have selected an InfoSet, you can select an InfoObject. All the InfoObjects with quantity attributes contained in the InfoSet can be displayed using input help.
29) An SAP BW functional consultant is responsible for the following: Key responsibilities include: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) Liase 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 DesignerWeb report development using Web Application.
29. Production support
In production support there will be two kind jobs which you will be doing mostly 1, looking into the data load errors. 2, solving the tickets raised by the user. Data loading involves monitoring process chains, solving the errors related to data load, other than this you will also be doing some enhancements to the present cubes and master data but that done on requirement. User will raise a ticket when they face any problem with the query, like report showing wrong values incorrect data etc.if the system response is slow or if the query run time is high. Normally the production support activities include * Scheduling * R/3 Job Monitoring * B/W Job Monitoring * Taking corrective action for failed data loads. * Working on some tickets with small changes in reports or in AWB objects. The activities in a typical Production Support would be as follows: 1.Data Loading - could be using process chains or manual loads. 2. Resolving urgent user issues - helpline activities 3. Modifying BW reports as per the need of the user. 4. Creating aggregates in Prod system 5. Regression testing when version/patch upgrade is done. 6. Creating adhoc hierarchies. We can perform the daily activities in Production 1. monitoring Dataload failures thru RSMO 2. Monitoring Process Chains Daily/weekly/ monthly 3. Perform Change run Hirerachy 4. Check Aggr's Rollup.
30) How to convert a BeX query Global structure to local structure (Steps involved)
BeX query Global structure to local structureSteps; ***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 inthis 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 tocomfirm changes to all queries. that is how you identify a global structure*
31) What is the use of Define cell in BeX & where it is useful?
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 diferent behaviour that the general one described in your query defininion.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.
32) What is SAP GUI and what use of it?
AP Graphic User Interface:
SAP GUI is the GUI client in SAP R/3's 3-tier architecture of database, application server and client. It is software that runs on a Microsoft Windows, Apple Macintosh or Unix desktop, and allows a user to access SAP functionality in SAP applications such as mySAP ERP and SAP Business Information Warehouse (now called SAP Business Intelligence).
You need the SAP GUI to log on to and to use the SAP systems. Check alsohttp://help.sap.com/saphelp_nw70/helpdata/en/4f/472e42e1ef5633e10000000a155106/frameset.htm
33) What is the RMS Application?
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.
34) Bug resolution for the RMS Application?
3A.
http://rmsitservices.co.uk/upgrade.pdf
35) Development tasks for RMS release work?
The main task isComplete life cycle development of SAP Authorization Roles . This includes participating in the high level, low level, RMS's and technical development of the roles.
36) What is BP Master Data?
BP Master data is nothing but Business partner data used in CRM Master tables
describe the BP Master Data tables, Authorization Objects
A.Basic Table : BUT000 Steps to view this tables:Go to TX (tcode) se16 , specify the table u want ot view in this case is But000 and click on the icon table contents (or enter) and u can find the entries by giving a selection or view the total no of entries.
You can't set an automatic code for BPs. However, you could use a formatted search to bring up the next code, provided that the code you are using has a logical sequence. You can assign this formatted search to the BP Code field and then the user can trigger it (Shift-F2) when they are creating a new BP. If you want to have a separate range for each BP type then the user needs to set the BP type field before using the formatted search.
I've also included this kind of function in an add-on. In this case, the query is still the same but the user leaves the BP Code field blank and the add-on will populate it when the user clicks on the Add button.
Process Flow:1. Configure application components in SAP Solution Manager.In the Business Blueprint, transactions can already be assigned for process steps from the reference model. You can also assign transactions to any additional processes and steps you have defined, and thereby specify how your business processes are to run in the SAP system. Furthermore, you can also edit the Implementation Guide.
2. Use metadata (PI).You specify the necessary metadata for your integration requirements, such as data types, message interfaces, mappings, and so on.
3. Configure integration scenario and integration process (PI).You adapt the defined integration scenarios and integration processes to your specific system landscape. In doing so, you specify, for example, collaboration profiles (communication party, service and communication channel). You can use wizards for the configuration.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a8ffd911-0b01-0010-679e-d47dade98cdd
Tools used for business process:1. BPM2. ARIS etc.
Business Process Management with SAP NetWeaver and ARIS for SAP NetWeaver provides procedure models, methods, technologies and reference content for modeling, configuring, executing and monitoring these business processes.
Process ModelingA process model is an abstraction of a process and describes all the aspects of the process:· Activities: steps that are executed within the process· Roles: users or systems that execute the activities· Artifacts: objects, such as business documents, for example, that are processed by the process
Processes within a company can be modeled on multiple abstraction levels and from numerous different viewpoints. To implement and utilize innovative processes and strategies successfully, you must convert business process views into technical views and relate both views. Typically, different individuals or departments within a company are responsible for modeling processes from the business and technical perspectives. A deciding factor for the success of business process modeling is, therefore, that all those involved have a common understanding of the business processes and “speak the same language”.
Business Process Management in SAP NetWeaver provides a common methodology for all levels of process modeling. This common methodology forms a common reference framework for all project participants and links models for multiple abstraction levels:· Business process models describe the process map and process architecture of a company – from value chain diagrams and event-driven process chains, right up to end-to-end processes. · Process configuration models support the process-driven configuration and implementation of processes.· Process execution models support service-based process execution
37) Describe the BP Master Data, Authorization Objects?
Authorization Objects:
SAP R/3 Authorization ConceptFundamental to SAP R/3 security is the authorization concept. To get an understanding of SAP R/3 security, one needs to thoroughly understand the authorization concept. The authorization concept allows the assignment of broad or finely defined authorizations/permissions for system access. Several authorizations may be required to perform a task such as creating a material master record. Based upon design, these authorizations can be limited to:
Access to the transaction code (TCODE) to create a material master Access to specific material Authorization to work in a particular plant in the system Authorization ObjectAuthorization objects can best be described as locks that limit access to SAP R/3 system objects, such as programs, TCODES and data entry screens. Depending on the SAP R/3 version, there are approximately 800 standard authorizations.
There can be 10 fields in an authorization object, but all 10 fields are not used in all objects. The most common field in an authorization object is the activity field. These are predefined activity codes that reside in a table named TACT. Examples of activity are "01" create or generate, "02" change, "03" read, "04" print or edit message, and "06" delete. The next most common field is an organization field, such as company code or plant.
Authorization objects are classified and cataloged in the system based upon functionality, such as FI (financial accounting) or HR (human resources). These classifications are called object classes.
Developers and programmers can create new authorization objects through the developers' workbench called ABAP Workbench in SAP R/3. ABAP/4 is a 4GL (fourth-generation programming language) that was used to develop all SAP R/3 applications. It stands for Advanced Business Application Programming Language.
AuthorizationsAuthorizations are the keys that can open the authorization objects, and they contain the specific information for field values. For instance, an authorization contains a specific set of values for one or all the fields of a particular authorization object. If a field is not restricted, an authorization will have an asterisk (*) as a field value.
check in following table AGR_TCODES
An example of an authorization is as follows:
Field Value ACTVT (Activity) 01 BUKRS (Company Code) 0010
This particular authorization grants users access to create for company code 0010 the specific object that is locked by the authorization object, such as a purchase order.
The following authorization will grant total access to all the activities for all the company codes:
Field Value ACTVT (Activity) * BUKRS (Company Code) *
38) Tell what is localization?
39) Workflow SAP GUI
40) What is 0Recordmode?
A. 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.
41)What is the difference between filter & Restricted Key Figures? Examples & Steps in BI?
Filter restriction applies to entire query. RKF is restriction applied on a keyfigure.Suppose for example, you want to analyse data only after 2006...showing sales in 2007,2008 against Materials..You have got a keyfigure called Sales in your cube
Now you will put global restriction at query level by putting Fiscyear > 2006 in the Filter.This will make only data which have fiscyear >2006 available for query to process or show.
Now to meet your requirement. ..like belowMaterial Sales in 2007 Sales in 2008M1 200 300M2 400 700You need to create two RKF's.Sales in 2007 is one RKF which is defined on keyfigure Sales restricted by Fiscyear = 2007Similarly,Sales in 2008 is one RKF which is defined on Keyfigure Sales restricted by Fiscyear = 2008Now i think u understood the differenceFilter will make the restriction on query level..Like in above case putting filter Fiscyear>2006 willmake data from cube for yeaers 2001,2002,2003, 2004,2005 ,2006 unavailable to the query for showing up.So query is only left with data to be shown from 2007 and 2008.Within that data.....you can design your RKF to show only 2007 or something like that...
42)How to create condition and exceptions in Bi.7.0? But I know in Bw3.5 version.?
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.
43)The FI Business Flow related to BW. case studies or scenarios
FI FlowBasically there are 5 major topics/areas in FI,1. GL Accounting -related tables are SKA1, SKB1 Master dataBSIS and BSAS are the Transaction Data2. Account Receivables- related to CustomerAll the SD related data when transfered to FI these are created.Related Tables BSID and BSAD3. Account Payables - related VendorAll the MM related documents data when transfered to FI these are createdRelated Tables BSIK and BSAKAll the above six tables data is present in BKPF and BSEG tablesYou can link these tables with the hlp of BELNR and GJAHR and with Dates also.4. Special Purpose Ledger.. which is rarely used.5. Asset ManagmentIn CO there are Profit center AccountingCost center Accounting will be there.
You need to activate the data sources in R3 system.
You need to maintain the login information for the logical system.sm59 : Choose the RFC destination , BW system, Under logon Security, maintain the user credentials.
Maintain control parameters for data transfer.
Filling in of setup tables SBIW
I feel that these are certain prerequisites.
From an SD perspective, you as a BW consultant should first understand the basic SD process flow on the R3 side. (search the forum for SD process flow and you'll get a wealth of information on the flow and the tables as well as transactions involved in SD).
Next you need to understand the process flow that has been implemented at the clients place. How the SD data flows and what are the integration points with other modules as well as how the integration happens.
This knowledge is essential when modeling your BW design.
From a BW perspective you need to first know all the SD extractors and what information they bring. Next look at all the cubes and ODS for SD.
1. What is the t-code to see log of transport connection?
in RSA1 -> Transport Connection you can collect the Queries and the Role and after this you can transport them (enabling the transport in SE10, import it in STMS
1. RSA1
2. Transport connection (button on the left bar menu)
3. Sap transport -> Object Types (button on the left bar menu)
4. Find Query Elements -> Query
5. Find your query
6. Group necessery object
7. Transport Object (car icon)
8. Release transport (SE10 T-code)
9. load transport (STMS T-code)
2.Lo; mm inventory data source with marker significance?
Marker is as like check point when u upload the data from inventory data source
2lis_03_bx data source for current stock and BF for movement type
after uploading data from BX u should rlise the request in cube or i menn to say compress it then load data from another data source BF and set this updated data to no marker update so marker is use as a check point if u dont do this u getting data missmatch at bex level bcz system get confuse .
(2LIS_03_BF Goods Movement From Inventory Management-- -----Unckeck the no marker update tab)
(2LIS_03_BX Stock Initialization for Inventory Management-- ---select the no marker update check box)
2LIS_03_UM Revaluations ----Uncheck the no marker update tab) in the infopackege of "collaps"
3. How can you navigate to see the error idocs ?
If it is fine check the IDOCs in source system go to BD87->give Ur user ID and date->execute->you can find Red status Idocs select the erroneous Idoc->Rt.click and select Manual process.
You need to Reprocess this IDOC which are RED. For this you can take help of Any of your Team (ALE IDOC Team or BAsis Team)Or Else
youcan push it manually. Just search it in bd87 screen only to Reprocess.
Also, Try to find why this IDocs are stuck there.
4)Difference between v1, v2, v3 jobs in extraction?
V1 Update: when ever we create a transaction in R/3(e.g.,Sales Order) then the entries get into the R/3 Tables(VBAK, VBAP..) and this takes place in V1 Update.
V2 Update: V2 Update starts a few seconds after V1 Update and in this update the values get into Statistical Tables, from where we do the extraction into BW.
V3 Update: Its purely for BW extraction.
But in the Document below, V1, V2 and V3 are defined in a different way. Can You please explain me in detial what exactly V1, V2 and V3 updates means?
5.What are statistical update and document update?
Synchronous Updating (V1 Update)
The statistics update is made synchronously with the document update.
While updating, if problems that result in the termination of the
statistics update occur, the original documents are NOT saved. The cause
of the termination should be investigated and the problem solved.
Subsequently, the documents can be entered again.
Radio button: V2 updating
6.Do you have any idea how to improve the performance of the BW..?
Asynchronous Updating (V2 Update)
With this update type, the document update is made separately from the statistics update. A termination of the statistics update has NO influence on the document update (see V1 Update).
Radio button: Updating in U3 update program
Asynchronous Updating (V3 Update)
With this update type, updating is made separately from the document update. The difference between this update type and the V2 Update lies,however, with the time schedule. If the V3 update is active, then the update can be executed at a later time.
In contrast to V1 and V2 Updates, no single documents are updated. The V3 update is, therefore, also described as a collective update.
7)How can you decide the query performance is slow or fast ?
You can check that in RSRT tcode.
execute the query in RSRT and after that follow the below steps
Goto SE16 and in the resulting screen give table name as RSDDSTAT for BW 3.x and RSDDSTAT_DM for BI 7.0 and press enteryou can view all the details about the query like time taken to execute the query and the timestmaps
8)What is statistical setup and what is the need and why?
Follow these steps to filling the set up table.
1. Go to transaction code RSA3 and see if any data is available related to your DataSource. If data is there in RSA3 then go to transaction code LBWG (Delete Setup data) and delete the data by entering the application name.
2. Go to transaction SBIW --> Settings for Application Specific Datasource --> Logistics --> Managing extract structures --> Initialization --> Filling the Setup table --> Application specific setup of statistical data --> perform setup (relevant application)
3. In OLI*** (for example OLI7BW for Statistical setup for old documents : Orders) give the name of the run and execute. Now all the available records from R/3 will be loaded to setup tables.
4. Go to transaction RSA3 and check the data.
5. Go to transaction LBWE and make sure the update mode for the corresponding DataSource is serialized V3 update.
6. Go to BW system and create infopackage and under the update tab select the initialize delta process. And schedule the package. Now all the data available in the setup tables are now loaded into the data target.
7. Now for the delta records go to LBWE in R/3 and change the update mode for the corresponding DataSource to Direct/Queue delta. By doing this record will bypass SM13 and directly go to RSA7. Go to transaction code RSA7 there you can see green light # Once the new records are added immediately you can see the record in RSA7.
8. Go to BW system and create a new infopackage for delta loads. Double click on new infopackage. Under update tab you can see the delta update radio button..
9. Now you can go to your data target and see the delta record.
9.Why we have construct setup tables?
The R/3 database structure for accounting is much more easier than the Logistical structure.
Once you post in a ledger that is done. You can correct, but that give just another posting.
BI can get information direct out of this (relatively) simple database structure.
In LO, you can have an order with multiple deliveries to more than one delivery addresses. And the payer can also be different.
When 1 item (orderline) changes, this can have its reflection on order, supply, delivery, invoice, etc.
Therefore a special record structure is build for Logistical reports.and this structure now is used for BI.
In order to have this special structre filled with your starting position, you must run a set-up. from that moment on R/3 will keep filling this LO-database.
If you wouldn't run the setup. BI would start with data from the moment you start the filling of LO (with the logistica cocpit)
10.How can you eliminate the duplicate records in TD, MD?Try to check the system logs through SM21 for the same.
11.What use marker in MM?
Marker update is just like check point.
ie it will give the snapshot of the stock on a particular date ie when was the marker updated.
Because we are using Noncumulative keyfigure it will lot of time to calculate the current stock for example at report time. to overcome this we use marker update
Marker updates do not summarize the data.. In inventory management scenarios, we have to calculate opening stock and closing stock on a daily basis. In order to facilitate this, we set a marker which will add and subtract the values for each record.
In the absence of marker update, the data will be added up and will not provide the correct values.
12.Tell me web template?
You get information on where the web template details are stored from the following tables :
RSZWOBJ Storage of the Web Objects
RSZWOBJTXT Texts for Templates/Items/ Views
RSZWOBJXREF Structure of the BW Objects in a Template
RSZWTEMPLATE Header Table for BW HTML Templates
You can check these tables and search for your web template entry . However, If I understand your question correctly , you will have to open the template in the WAD and then make the corrections in the same to correct it.
13.What is dashboard?
A dash board can be created using the web application Designer (WAD) or the visual composer (VC). A dashboard is just a collection of reports, views and links etc in a single view. For e.g. igoogle is a dashboard.
A dashboard is a graphical reporting interface, which displays KPIs (Key Performance Indicators) as charts and graphs. A dashboard is a performance management system
When we look at the all organization measures how they are performing with helicopter view, we need a report that teaches and shows the trend in a graphical display quickly. These reports are called as Dashboard Reports, still we can report these measures individually, but by keeping all measures in a single page, we are creating single access point to the users to view all information available to them. Absolutely this will save lot of precious time, gives clarity on decision that needs to be taken, helps the users to understand the measure(s) trend with business flow creating dashboard
Dashboards : Could be built with Visual Composer & WAD
create your dashboard in BW,
(1) Create all BEx Queries with required variants,tune them perfectly.
(2) Differentiate table queries and graph queries.
(3) Choose the graph type required that meet your requirement.
(4) Draw the layout how the Dashboard page looks like.
(5) Create a web template that has navigational block / selection information.
(6) Keep navigational block fields are common across the measures.
(7) Include the relevant web items into web template.
(8) Deploy the URL/Iview to users through portal/intranet
The steps to be followed in the creation of Dashboard using WAD are summarized as below:
1) Open a New Web template in WAD.
2) Define the tabular layout as per the requirements so as to embed the necessary web items.
3) Place the appropriate web items in the appropriate tabular grids
4) Assign queries to the web items (A Query assigned to a web item is called as a data provider)
5) Care should be taken to ensure that the navigation block’s selection parameters are common across all the BEx queries of the affected dataproviders.
6) Properties of the individual web items are to be set as per the requirements. They can be modified in Properties window or in the HTML code.
7) The URL when this web template is executed should be used in the portal/intranet
14.How can you solve the data mismatch tickets between r/3 and bw?
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.
15. What is thumb rule?
16)What is replacement path tell me one scenario?
http://www.sd- solutions. com/documents/ SDS_BW_Replaceme nt%20Path% 20Variables. html
17.What is difference between PSA & IDOC?
BI7 is PSA used only for Data load from Source System into BW
18). what we do in Business Blue Print Stage?
SAP has defined a business blueprint phase to help extract pertinent information about your company that is necessary for implementation. These blueprints are in the form of questionnaires that are designed to probe for information that uncovers how your company does business. As such, they also serve to document the implementation. Each business blueprint document essentially outlines your future business processes and business requirements. The kinds of questions asked are germane to the particular business function, as seen inthe following sample questions:1) What information do you capture on a purchase order?2) What information is required to complete a purchase order?Accelerated SAP question and answer database:The question and answer database (QADB) is a simple although aging tool designed to facilitate the creation and maintenance of your business blueprint.This database stores the questions and the answers and serves as the heart of your blue print. Customers are provided with a customer input template for each application that collects the data. The question and answer format is standard across applications to facilitate easier use by the project team.Issues database: Another tool used in the blueprinting phase is the issues database. Thisdatabase stores any open concerns and pending issues that relate to the implementation. Centrally storing this information assists in gathering and then managing issues to resolution, so that important matters do not fall through the cracks. You can then track the issues in database, assign them to teammembers, and update the database accordingly.
19). How do we gather the requirements for an Implementation Project?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 useThis process involves one seemingly simple task: Find out exactly what theend users' analysis requirements are, both now and in the future, and buildthe BW system to these requirements. Although simple in concept, in practicegathering and reaching a clear understanding and agreement on a complete setof BW functional requirements is not always so simple.
20) How do we decide what cubes has to be created?
Its depends on your project requirement. Customized cubes are not mandatory for all the projects. If your bussines 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 implemention. 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 scenrio we could'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 asreports.
21) Who used to make the Technical and Functional Specifications?
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.
22) Give me one example of a Functional Specification and explain what information we will get from that?Functional Specs are requirements of the business user.Technical Specs translate these requirements in a technical fashion.Let's say Functional Spec says,1. the user should be able to enter the Key date, Fiscal Year, Fiscal Version.2. The Company variable should be defaulted to USA but then if the user wants to change it, they can check the drop down list and choose other countries.3. The calculations or formulas for the report will be displayed in precision of one decimal point.4. The report should return values for 12 months of data depending on the fiscal year that the user enters Or it should display in quarterly values. Functional specs are also called as Software requirements.Now from this Techinal Spec follows, to resolve each of the line items listed above.1. To give the option of key date, Fiscal year and Fiscal Version – certain Info Obejcts should be availble in the system. If available, then should we create any variables for them - so that they are used as user entry variable. To create any varaibles, what is the approch, where do you do it, what is the technical of the objects you'll use, what'll be the technical name of the objects you'll crete as a result of this report.2. Same explanation goes for the rest. How do you set up the varaible,
3. What changes in properties willu do to get the precision.4. How will you get the 12 months of data.What will be the technical and display name of the report, who'll be authorized to run this report, etc are clearly specified in the technical specs.
23) What is Customization? How do we do in LO?
How to do basic LO extraction for SAP-R3-BW1. Go to transaction code RSA3 and see if any data is available related to your DataSource. If data is there in RSA3 then go to transaction code LBWG (Delete Setup data) and delete the data by entering the application name.2. Go to transaction SBIW --> Settings for Application Specific Datasource --> Logistics --> Managing extract structures --> Initialization --> Filling the Setup table --> Application specific setup of statistical data --> perform setup (relevant application)3. In OLI*** (for example OLI7BW for Statistical setup for old documents : Orders) give the name of the run and execute. Now all the available records from R/3 will be loaded to setup tables.4. Go to transaction RSA3 and check the data.5. Go to transaction LBWE and make sure the update mode for the corresponding DataSource is serialized V3 update.6. Go to BW system and create infopackage and under the update tab select the initialize delta process. And schedule the package. Now all the data available in the setup tables are now loaded into the data target.7.Now for the delta records go to LBWE in R/3 and change the update mode for the corresponding DataSource to Direct/Queue delta. By doing this record will bypass SM13 and directly go to RSA7. Go to transaction code RSA7 there you can see green light # Once the new records are added immediately you can see the record in RSA7.
24) When we use Maintain Data Source, What we do? What we will maintain?
Go to BW system and create a new infopackage for delta loads. Double click on new infopackage. Under update tab you can see the delta update radio button.
25) Tickets and Authorization in SAP Business Warehouse What is tickets? And example?Tickets are the tracking tool by which the user will track the work which we do. It can be a change requests or data loads or what ever. They will of types critical or moderate. Critical can be (Need to solve in 1 day or half a day) depends on the client. After solving the ticket will be closed by informing the client that the issue is solved. Tickets are raised at the time of support project these may be any issues, problems.... .etc. If the support person faces any issues then he will ask/request to operator to raise a ticket.
Operator will raise a ticket and assign it to the respective person. Critical means it is most complicated issues ....depends how you measure this...hope it helps. The concept of Ticket varies from contract to contract in between companies. Generally Ticket raised by the client can be considered based on the priority. Like High Priority, Low priority and so on. If a ticket is of high priority it has to be resolved ASAP. If the ticket is of low> priority it must be considered only after attending to high priority tickets. The typical tickets in a production Support work could be: 1. Loading any of the missing master data attributes/texts. 2. Create ADHOC hierarchies. 3. Validating the data in Cubes/ODS. 4. If any of the loads runs into errors then resolve it. 5. Add/remove fields in any of the master data/ODS/Cube. 6. Data source Enhancement. 7. Create ADHOC reports.
1. Loading any of the missing master data attributes/texts - This would be done by scheduling the infopackages for the attributes/texts mentioned by the client. 2. Create ADHOC hierarchies. - Create hierarchies in RSA1 for the info-object. 3. Validating the data in Cubes/ODS. - By using the Validation reports or by comparing BW data with R/3. 4. If any of the loads runs into errors then resolve it. - Analyze the error and take suitable action. 5. Add/remove fields in any of the master data/ODS/Cube. - Depends upon the requirement 6. Data source Enhancement. 7. Create ADHOC reports. - Create some new reports based on the requirement of client.
26) Change attribute run.
Generally attribute change run is used when there is any change in the master data..it is used for realingment of the master data..Attribute change run is nothing but adjusting the master data after its been loaded from time to time so that it can change or generate or adjust the sid's so that u may not have any problem when loading the trasaction data in to data targets.the detail explanation about Attribute change run.The hierarchy/attribute change run which activates hierarchy and attribute changes and adjusts the corresponding aggregates is devided, into 4 phases:1. Finding all affected aggregates2. set up all affected aggregates again and write the result in the new aggregate table.3. Activating attributes and hierarchies4. rename the new aggregate table. When renaming, it is not possible to execute queries. In some databases, which cannot rename the indexes, the indexes are also created in this phase.
27) Different types of Delta updates?
Delta loads will bring any new or changed records after the last upload.This method is used for better loading in less time. Most of the std SAP data sources come as delta enabled, but some are not. In this case you can do a full load to the ODS and then do a delta from the ODS to the cube. If you create generic datasources, then you have the option of creating a delta onCalday, timestamp or numeric pointer fields (this can be doc number, etc).You'll be able to see the delta changes coming in the delta queue through RSA7 on the R3 side.To do a delta, you first have to initialize the delta on the BW side and then set up the delta.The delta mechanism is the same for both Master data and Transaction data loads.============ ========= ==There are three deltasDirect Delta: With this update mode, the extraction data is transferred with each document posting directly into the BW delta queue. In doing so, each document posting with delta extraction is posted for exactly one LUW in the respective BW delta queues.Queued Delta: With this update mode, the extraction data is collected for the affected application instead of being collected in an extraction queue, and can be transferred as usual with the V3 update by means of an updating collective run into the BW delta queue. In doing so, up to 10000 deltaextractions of documents for an LUW are compressed for each Data Source into the BW delta queue, depending on the application.Non-serialized V3 Update: With this update mode, the extraction data for the application considered is written as before into the update tables with the help of a V3 update module. They are kept there as long as the data is selected through an updating collective run and are processed. However, in contrast to the current default settings (serialized V3 update), the data in the updating collective run are thereby read without regard to sequence from the update tables and are transferred to the BW delta queue.
28) Function modules;1) UNIT_CONVERSION_ SIMPLE and2) MD_CONVERT_MATERIAL _UNITexplain how to use these things, if possible with a well explained example.
The conversion of units of measure is required to convert business measurements into other units. Business measurements encompass physical measurements which are either assigned to a dimension or are nondimensional. Nondimensional measurements are understood as countable measurements(palette, unit..).You differentiate between conversions for which you only need to enter a source and target unit in order to perform conversion and conversions for which specifying these values alone is not sufficient. For the latter, you have to enter a conversion factor which is derived from a characteristic ora characteristic combination (compound characteristic) and the corresponding properties....1. Measurements of lengthConversions within the same dimension ID (T006-DIMID) – for example, length:1 m = 100 cm (linear correlation)*Meter* and *Centimeter* both belong to dimension ID LENGTH.2. Measurements of number associated with measurements of weightConversions involving different dimension IDs – for example, number andweight.1 unit = 25 g (linear correlation)*Unit* has dimension ID AAAADL and *Gram* has dimension ID MASS.ExampleNumber
Unit Number Unit1
Chocolate bar 25 g1 Small carton 12 Chocolate bar1 Large carton 20 Small carton1 Europallet 40 Large carton* Quantity Conversion*
<http://help.sap.com/saphelp_nw2004s/helpdata/en/27/b65c42b4e05542e10000000a1550b0/frameset.htm>* *UseQuantity conversion allows you to convert key figures with units that have different units of measure in the source system into a uniform unit of measure in the BI system.FeaturesThis function enables the conversion of updated data records from the source unit of measure into a target unit of measure, or into different target units of measure, if the conversion is repeated. In terms of functionality, quantity conversion is structured similarly to currency translation.In part it is based on the quantity conversion functionality in SAP NetWeaver Application Server. Simple conversions can be performed between units of measure that belong to the same dimension (such as meters to kilometers, kilograms to grams). You can also perform InfoObject-specific conversions (for example, two palettes (PAL) of material 4711 were ordered and this order quantity has to be converted to the stock quantity *Carton*(CAR) ).Quantity conversion is based on quantity conversion types. The business transaction rules of the conversion are established in the quantity conversion type. The conversion type is a combination of different parameters (conversion factors, source and target units of measure) that determine how the conversion is performed. For more information, see QuantityConversion Types<http://help.sap.com/saphelp_nw2004s/helpdata/en/1c/1b5d427609c153e10000000a1550b0/content.htm>.IntegrationThe quantity conversion type is stored for future use and is available for quantity conversions in the transformation rules for InfoCubes and in the Business Explorer:In the transformation rules for InfoCubes you can specify, for each key figure or data field, whether quantity conversion is performed during the update. In certain cases you can also run quantity conversion in user-defined routines in the transformation rules..In the Business Explorer you can:● Establish a quantity conversion in the query definition.● Translate quantities at query runtime. Translation is more limitedhere than in the query definition.[image: This graphic is explained in the accompanying text]*Quantity Conversion Types*<http://help.sap.com/saphelp_nw2004s/helpdata/en/1c/1b5d427609c153e10000000a1550b0/frameset.htm>DefinitionA quantity conversion type is a combination of different parameters that establish how the conversion is performed. StructureThe parameters that determine the conversion factors are the source and target unit of measure and the option you choose for determining the conversion factors.The decisive factor in defining a conversion type is the way in which you want conversion factors to be determined. Entering source and target quantities is optional.Conversion FactorsThe following options are available:· Using a reference InfoObjectThe system tries to determine the conversion factors from the reference InfoObject you have chosen or from the associated quantity DataStore object.If you want to convert 1000 grams into kilograms but the conversion factors are not defined in the quantity DataStore object, the system cannot perform the conversion, even though this is a very simple conversion.· Using central units of measure (T006)Conversion can only take place if the source unit of measure and target unit of measure belong to the same dimension (for example, meters to kilometers, kilograms to grams, and so on).· Using reference InfoObject if available, central units of measure (T006) if notThe system tries to determine the conversion factors using the quantity DataStore object you have defined. If the system finds conversion factors, it uses these to perform the calculation. If the system cannot determine conversion factors from the quantity DataStore object it tries again usingthe central units of measure.· Using central units of measure (T006) if available, reference InfoObject if notThe system tries to find the conversion factors in the central units of measure table. If the system finds conversion factors it uses these to perform the conversion. If the system cannot determine conversion factors from the central units of measure it tries to find conversion factors that match the attributes of the data record by looking in the quantity DataStore object.The settings that you can make in this regard affect performance and the decision must be strictly based on the data set. If you only want to perform conversions within the same dimension, option 2 is most suitable.If you are performing InfoObject-specific conversions (for example, material-specific conversions) between units that do not belong to the same dimension, option 1 is most suitable.In both cases, the system only accesses one database table. That table contains the conversion factors.With option 3 and option 4, the system tries to determine conversion factors at each stage. If conversion factors are not found in the basic table (T006), the system searches again in the quantity DataStore object, or in reverse.The option you choose should depend on how you want to spread the conversion. If the source unit of measure and target unit of measure belong to the same dimension for 80% of the data records that you want to convert, first try to determine factors using the central units of measure (option4), and accept that the system will have to search in the second table also for the remaining 20%.The *Conversion Factor from InfoObject *option (as with *Exchange Rate from InfoObject* in currency translation types) is only available when you load data. The key figure you enter here has to exist in the InfoProvider and the attribute this key figure has in the data record is taken as the conversionfactor.Source Unit of MeasureThe source unit of measure is the unit of measure that you want to convert. The source unit of measure is determined dynamically from the data record or from a specified InfoObject (characteristic) . In addition, you can specify a fixed source unit of measure or determine the source unit of measure using avariable.When converting quantities in the Business Explorer, the source unit of measure is always determined from the data record.During the data load process the source unit of measure can be determined either from the data record or using a specified characteristic that bears master data.You can use a fixed source unit of measure in planning functions. Data records are converted that have the same unit key as the source unit of measure.The values in input help correspond to the values in table T006 (units of measure).You reach the maintenance for the unit of measure in *SAP Customizing Implementation Guide* (r) *SAP NetWeaver *(r) *General Settings* (r) *Check Units of Measure*.In reporting, you can use a source unit of measure from a variable. The variables that have been defined for InfoObject 0UNIT are used.
Target Unit of MeasureYou have the following options for determining the target unit of measure:· You can enter a fixed target unit of measure in the quantityconversion type (for example, 'UNIT').· You can specify an InfoObject in the quantity conversion type that is used to determine the target unit of measure during the conversion. This is not the same as defining currency attributes where you determine a currency attribute on the *Business Explorer* tab page in characteristic maintenance. With quantity conversion types you determine the InfoObject in the quantity conversion type itself. Under *InfoObject for Determining Unit of Measure*, all InfoObjects are listed that have at least one attribute of type *Unit*. You have to select one of these attributes as the corresponding quantity attribute.· Alternatively, you can determine that the target unit of measure be determined during the conversion. In the Query Designer under the properties for the relevant key figure, you specify either a fixed target unit of measure or a variable to determine the target unit of measure.· Target quantity using InfoSetThis setting covers the same functionality as *InfoObject for Determining Target Quantity*. If the InfoObject that you want to use to determine the target quantity is unique in the InfoSet (it only occurs once in the whole InfoSet), you can enter the InfoObject under *InfoObject for DeterminingTarget Quantity*.You only have to enter the InfoObject in *Target Quantity Using InfoSet* if you want to determine the target quantity using an InfoObject but that occurs more than once in the InfoSet.The InfoSet contains InfoProviders A and B and both A and B contain InfoObject X with a quantity attribute. In this case you have to specify exactly whether you want to use X from A or X from B to determine the target quantity. Field aliases are used in an InfoSet to ensure uniqueness.All the active InfoSets in the system can be displayed using input help. As long as you have selected an InfoSet, you can select an InfoObject. All the InfoObjects with quantity attributes contained in the InfoSet can be displayed using input help.
29) An SAP BW functional consultant is responsible for the following: Key responsibilities include: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) Liase 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 DesignerWeb report development using Web Application.
29. Production support
In production support there will be two kind jobs which you will be doing mostly 1, looking into the data load errors. 2, solving the tickets raised by the user. Data loading involves monitoring process chains, solving the errors related to data load, other than this you will also be doing some enhancements to the present cubes and master data but that done on requirement. User will raise a ticket when they face any problem with the query, like report showing wrong values incorrect data etc.if the system response is slow or if the query run time is high. Normally the production support activities include * Scheduling * R/3 Job Monitoring * B/W Job Monitoring * Taking corrective action for failed data loads. * Working on some tickets with small changes in reports or in AWB objects. The activities in a typical Production Support would be as follows: 1.Data Loading - could be using process chains or manual loads. 2. Resolving urgent user issues - helpline activities 3. Modifying BW reports as per the need of the user. 4. Creating aggregates in Prod system 5. Regression testing when version/patch upgrade is done. 6. Creating adhoc hierarchies. We can perform the daily activities in Production 1. monitoring Dataload failures thru RSMO 2. Monitoring Process Chains Daily/weekly/ monthly 3. Perform Change run Hirerachy 4. Check Aggr's Rollup.
30) How to convert a BeX query Global structure to local structure (Steps involved)
BeX query Global structure to local structureSteps; ***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 inthis 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 tocomfirm changes to all queries. that is how you identify a global structure*
31) What is the use of Define cell in BeX & where it is useful?
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 diferent behaviour that the general one described in your query defininion.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.
32) What is SAP GUI and what use of it?
AP Graphic User Interface:
SAP GUI is the GUI client in SAP R/3's 3-tier architecture of database, application server and client. It is software that runs on a Microsoft Windows, Apple Macintosh or Unix desktop, and allows a user to access SAP functionality in SAP applications such as mySAP ERP and SAP Business Information Warehouse (now called SAP Business Intelligence).
You need the SAP GUI to log on to and to use the SAP systems. Check alsohttp://help.sap.com/saphelp_nw70/helpdata/en/4f/472e42e1ef5633e10000000a155106/frameset.htm
33) What is the RMS Application?
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.
34) Bug resolution for the RMS Application?
3A.
http://rmsitservices.co.uk/upgrade.pdf
35) Development tasks for RMS release work?
The main task isComplete life cycle development of SAP Authorization Roles . This includes participating in the high level, low level, RMS's and technical development of the roles.
36) What is BP Master Data?
BP Master data is nothing but Business partner data used in CRM Master tables
describe the BP Master Data tables, Authorization Objects
A.Basic Table : BUT000 Steps to view this tables:Go to TX (tcode) se16 , specify the table u want ot view in this case is But000 and click on the icon table contents (or enter) and u can find the entries by giving a selection or view the total no of entries.
You can't set an automatic code for BPs. However, you could use a formatted search to bring up the next code, provided that the code you are using has a logical sequence. You can assign this formatted search to the BP Code field and then the user can trigger it (Shift-F2) when they are creating a new BP. If you want to have a separate range for each BP type then the user needs to set the BP type field before using the formatted search.
I've also included this kind of function in an add-on. In this case, the query is still the same but the user leaves the BP Code field blank and the add-on will populate it when the user clicks on the Add button.
Process Flow:1. Configure application components in SAP Solution Manager.In the Business Blueprint, transactions can already be assigned for process steps from the reference model. You can also assign transactions to any additional processes and steps you have defined, and thereby specify how your business processes are to run in the SAP system. Furthermore, you can also edit the Implementation Guide.
2. Use metadata (PI).You specify the necessary metadata for your integration requirements, such as data types, message interfaces, mappings, and so on.
3. Configure integration scenario and integration process (PI).You adapt the defined integration scenarios and integration processes to your specific system landscape. In doing so, you specify, for example, collaboration profiles (communication party, service and communication channel). You can use wizards for the configuration.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a8ffd911-0b01-0010-679e-d47dade98cdd
Tools used for business process:1. BPM2. ARIS etc.
Business Process Management with SAP NetWeaver and ARIS for SAP NetWeaver provides procedure models, methods, technologies and reference content for modeling, configuring, executing and monitoring these business processes.
Process ModelingA process model is an abstraction of a process and describes all the aspects of the process:· Activities: steps that are executed within the process· Roles: users or systems that execute the activities· Artifacts: objects, such as business documents, for example, that are processed by the process
Processes within a company can be modeled on multiple abstraction levels and from numerous different viewpoints. To implement and utilize innovative processes and strategies successfully, you must convert business process views into technical views and relate both views. Typically, different individuals or departments within a company are responsible for modeling processes from the business and technical perspectives. A deciding factor for the success of business process modeling is, therefore, that all those involved have a common understanding of the business processes and “speak the same language”.
Business Process Management in SAP NetWeaver provides a common methodology for all levels of process modeling. This common methodology forms a common reference framework for all project participants and links models for multiple abstraction levels:· Business process models describe the process map and process architecture of a company – from value chain diagrams and event-driven process chains, right up to end-to-end processes. · Process configuration models support the process-driven configuration and implementation of processes.· Process execution models support service-based process execution
37) Describe the BP Master Data, Authorization Objects?
Authorization Objects:
SAP R/3 Authorization ConceptFundamental to SAP R/3 security is the authorization concept. To get an understanding of SAP R/3 security, one needs to thoroughly understand the authorization concept. The authorization concept allows the assignment of broad or finely defined authorizations/permissions for system access. Several authorizations may be required to perform a task such as creating a material master record. Based upon design, these authorizations can be limited to:
Access to the transaction code (TCODE) to create a material master Access to specific material Authorization to work in a particular plant in the system Authorization ObjectAuthorization objects can best be described as locks that limit access to SAP R/3 system objects, such as programs, TCODES and data entry screens. Depending on the SAP R/3 version, there are approximately 800 standard authorizations.
There can be 10 fields in an authorization object, but all 10 fields are not used in all objects. The most common field in an authorization object is the activity field. These are predefined activity codes that reside in a table named TACT. Examples of activity are "01" create or generate, "02" change, "03" read, "04" print or edit message, and "06" delete. The next most common field is an organization field, such as company code or plant.
Authorization objects are classified and cataloged in the system based upon functionality, such as FI (financial accounting) or HR (human resources). These classifications are called object classes.
Developers and programmers can create new authorization objects through the developers' workbench called ABAP Workbench in SAP R/3. ABAP/4 is a 4GL (fourth-generation programming language) that was used to develop all SAP R/3 applications. It stands for Advanced Business Application Programming Language.
AuthorizationsAuthorizations are the keys that can open the authorization objects, and they contain the specific information for field values. For instance, an authorization contains a specific set of values for one or all the fields of a particular authorization object. If a field is not restricted, an authorization will have an asterisk (*) as a field value.
check in following table AGR_TCODES
An example of an authorization is as follows:
Field Value ACTVT (Activity) 01 BUKRS (Company Code) 0010
This particular authorization grants users access to create for company code 0010 the specific object that is locked by the authorization object, such as a purchase order.
The following authorization will grant total access to all the activities for all the company codes:
Field Value ACTVT (Activity) * BUKRS (Company Code) *
38) Tell what is localization?
39) Workflow SAP GUI
40) What is 0Recordmode?
A. 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.
41)What is the difference between filter & Restricted Key Figures? Examples & Steps in BI?
Filter restriction applies to entire query. RKF is restriction applied on a keyfigure.Suppose for example, you want to analyse data only after 2006...showing sales in 2007,2008 against Materials..You have got a keyfigure called Sales in your cube
Now you will put global restriction at query level by putting Fiscyear > 2006 in the Filter.This will make only data which have fiscyear >2006 available for query to process or show.
Now to meet your requirement. ..like belowMaterial Sales in 2007 Sales in 2008M1 200 300M2 400 700You need to create two RKF's.Sales in 2007 is one RKF which is defined on keyfigure Sales restricted by Fiscyear = 2007Similarly,Sales in 2008 is one RKF which is defined on Keyfigure Sales restricted by Fiscyear = 2008Now i think u understood the differenceFilter will make the restriction on query level..Like in above case putting filter Fiscyear>2006 willmake data from cube for yeaers 2001,2002,2003, 2004,2005 ,2006 unavailable to the query for showing up.So query is only left with data to be shown from 2007 and 2008.Within that data.....you can design your RKF to show only 2007 or something like that...
42)How to create condition and exceptions in Bi.7.0? But I know in Bw3.5 version.?
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.
43)The FI Business Flow related to BW. case studies or scenarios
FI FlowBasically there are 5 major topics/areas in FI,1. GL Accounting -related tables are SKA1, SKB1 Master dataBSIS and BSAS are the Transaction Data2. Account Receivables- related to CustomerAll the SD related data when transfered to FI these are created.Related Tables BSID and BSAD3. Account Payables - related VendorAll the MM related documents data when transfered to FI these are createdRelated Tables BSIK and BSAKAll the above six tables data is present in BKPF and BSEG tablesYou can link these tables with the hlp of BELNR and GJAHR and with Dates also.4. Special Purpose Ledger.. which is rarely used.5. Asset ManagmentIn CO there are Profit center AccountingCost center Accounting will be there.
Posts
2 comments:
Good job, It helps a lot for job seekers
Post a Comment