SAP BW Questions - Some Real Question

1. Differences b/w 3.0 and 3. !. Differences b/w 3. and B" #.0 3. $an %ou e&'lain a life c%cle in brief (. Difference b/w table ) structure . Ste's of *+ ,. Ste's of *"S #. Ste's of -eneric .. W/at is inde& and /ow do %ou increase 'erformance usin- t/em 0. 1ow do %ou load deltas into +DS and cube 10. 2&am'le of errors w/ile loadin- data and /ow do u resol3e t/em 11. 1ow do %ou maintain wor4 /istor% until a tic4et is closed 1!. W/at is reconciliation 13. W/at is t/e met/odolo-% u use before im'lementation 1(. W/at are t/e role ) res'onsibilities w/en %ou are in im'lementation and w/ile in su''ort also 5a6or Differences between Sa' Bw 3. ) sa'B" #.0 3ersion 1. In Infosets now you can include Infocubes as well. 2. The Remodeling transaction helps you add new key figure and characteristics and handles historical data as well without much hassle. This is only for info cube. 3. The BI accelerator (for now only for infocubes helps in reducing !uery run time by almost a factor of 1" # 1"". This BI accl is a separate bo$ and would cost more. %endors for these would be &' or IB(. ). The monitoring has been impr*oed with a new portal based cockpit. +hich means you would need to ha*e an ,' guy in ur pro-ect for implementing the portal . / 0. 1earch functionality has impro*ed.. 2ou can search any ob-ect. 3ot like 3.0 4. Transformations are in and routines are pass5. 2es6 you can always re*ert to the old transactions too. 7. The 8ata +arehousing +orkbench replaces the 9dministrator +orkbench. :. ;unctional enhancements ha*e been made for the 8ata1tore ob-ect/ 3ew type of 8ata1tore ob-ect ,nhanced settings for performance optimi<ation of 8ata1tore ob-ects. =. The transformation replaces the transfer and update rules. 1". 3ew authori<ation ob-ects ha*e been added

11. Remodeling of Info'ro*iders supports you in Information >ifecycle (anagement. 12 The 8ata 1ource/ There is a new ob-ect concept for the 8ata 1ource. ?ptions for direct access to data ha*e been enhanced. ;rom BI6 remote acti*ation of 8ata 1ources is possible in 19' source systems. 13.There are functional changes to the 'ersistent 1taging 9rea 1).BI supports real#time data ac!uisition. 10 19' B+ is now known formally as BI (part of 3et +ea*er 2"")s . It implements the ,nterprise 8ata +arehousing (,8+ . The new features@ (a-or differences include/ a Renamed ?81 as 8ata1tore. b Inclusion of +rite#optimi<ed 8ata1tore which does not ha*e any change log and the re!uests do need any acti*ation c Anification of Transfer and Apdate rules d Introduction of Bend routineB and B,$pert RoutineB e 'ush of C(> data into BI system (into '19 without 1er*ice 9'I or 8elta Dueue f Introduction of BI accelerator that significantly impro*es the performance. g >oad through '19 has become a must. I am not too sure about this. It looks like we would not ha*e the option to bypass the '19 2es6 14. >oad through '19 has become a mandatory. 2ou canEt skip this6 and also there is no I8ocs transfer method in BI 7.". 8T' (8ata Transfer 'rocess replaced the Transfer and Apdate rules. 9lso in the Transformation now we can do B1tart Routine6 ,$pert Routine and ,nd RoutineB. 8uring data load. 7ew features in B" # com'ared to earlier 3ersions8 i. 3ew data flow capabilities such as 8ata Transfer 'rocess (8T' 6 Real time data 9c!uisition (R89 . ii. ,nhanced and Fraphical transformation capabilities such as 8rag and Relate options. iii. ?ne le*el of Transformation. This replaces the Transfer Rules and Apdate Rules i*. 'erformance optimi<ation includes new BI 9ccelerator feature. *. Aser management (includes new concept for analysis authori<ations for more fle$ible BI end user authori<ations. GGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGG 2. Homplete life#cycle implementation of 19' B+6 which includes data modeling6 data e$traction6 data loading6 reporting and support. ('19 .

GGGGGGGGGGGGGGGGGGGGGGGGGGGGGG 39. +hen they refer to the full life cycle itIs 919' methodology which 19' recommends to follow for all its pro-ects. 1. 'ro-ect preparation. 2. Business Blueprint. 3. Reali<ation. ). ;it#Fap 9nalysis 0.Fo#>i*e 'hase. 3ormally in the first phase all the management guys will sit with in a discussion. In the second phase u will get a functional spec n basing on that u will ha*e a technical spec. In the third phase u will actually implement the pro-ect and finally u after testing u will deploy it for production i.e. Fo#li*e. 2ou might fall under and get in*ol*ed in the reali<ation phase. If itIs a supporting pro-ect u will come into picture only after successful deployment. GGGGGGGGGGGGGGGGGGGGGGGGGGG 09. >? e$traction is one stop shop for all the logistics e$tractions. >? data sources come as a part of the business content in B+. +e need to transfer them from the BHT and then acti*ate them from 8 *ersion to the acti*e %ersion 9. Fo to the tcode ## R190 #### Transfer the desired data source. 9nd then >B+, to maintain the e$tract structure >B+F ## to delete the setup tables #### why...J ?>IKB+ ## 1tatistical initiali<ation. >B+D ### To delete the e$tractor !ueue 1(13 ## to delete the update !ueue. >B+f ## to get the log. ItIs always recommended to ha*e the Dueued delta as an update method6 since it uses the collecti*e run to schedule all the changed records. ?nce the initial run is o*er set the delta method Dueued to periodic for further delta load +hy..J +e need to delete the setup tables since we need to delete the data that is already in them and also because we will change the ,1 by adding the re!uired fields from the R@3 communication structure. +e can also select and hide the fields here... 9ll the fields in blue are mandatory... If the re!uired fields are not a*ailable we will go for the 81 enhancements.

GGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGG 49. >I1 uses information structures to e$tract the data .it comes under the application specific customer generated e$tractions. The range is """ to ===. "#)== is for 19' structures n 0"" to === are for customer defined. +e need to consider the two cases if itIs the 19' defined r the customer defined. >etIs see the 19' defined first/ Tcode ## >B+" gi*e the information structure and select the option display settings to know the status .if u select the generate data source option it will throw an error saying that u cannot create in the 1ap name range. 2ou select the option the setup en*ironment settings it will create the two tables n one structure with the naming con*ention .. 2>I1Lapplication no LBI+1 62>I1Lappl 3o LBI+2 and 2>I1 Lappl noLBI+1 These two structures are used to enable the delta records interchangebaly ### we will come to know this in the table T(HBI+ . Then go to >B+1 to change the *ersion .. >B+2 to setup the no update update method .. now you do the full load and after that go >B+1 change the *ersion and then go to >B+2 to setup the delta update n the periodic -ob . 3ow you can load the delta updates . If its in the case of the user defined / 2ou need to create the I1 (H1: ### create the I1 (H1=## change (H2" ## dispaly (H21##(H2266(H236(H2)6(H206(H24 folwing to craete the update rules . Then Tcode >B+" gi*e the I1 name and sel setup lis en*ironment it will craete the the two tables n the structure .. 2ou can use ?(?1 to fill the tables n u do the full upload then u need to setup the delta by sel the steup delta ..

2ou can set whether the delta is enabled are not using the option acti*ate @deacti*ate delta Both in cases you need while migrating the data you need to lock the setup tables to pre*ent users from entering the transactions 1,1) ... and after completion u need to unlock. But >? is preferred to >I1 in all aspects. >? pro*ides the I1 up to the le*el of detail . ,nhanced performance and also deletion of setup tables after updation which we ne*er do in >I1. GGGGGGGGGGGGGGGGGGGGGGGGGGGG 79. +e opt for generic e$traction whene*er the desired datasource is not a*ailable in business content or if it is already used and we need to regenerate it . when u want to e$tract the data from table6 *iew6 infoset6 function module we use generic e$traction. In generic we create our own datasource and acti*ate it . 1teps / 1.Tcode is R1?2 2.Fi*e the datasource name and designate it to a particular application component. 3. Fi*e the short medium and long desc mandatory. ). Fi*e the table @ ;m @*iew @infoset. 0. and continue which leads to a detail screen in which you can always hide6 select 6in*ersion 6 field only options are a*ailable. &I8, is used to hide the fields .. it will not transfer the data from r@3 to B+ 1,>,HT ## the fields are a*ailable in the selection screen of the info package while u schedule it . I3%,R1I?3 is for key figs which will operate with E#1E and nullify the *alue . ?nce the data source is generated you can e$tract the data using it . 9nd now to speak about the delta ... we ha*e... "calday6 3umeric pointer6 and time stamp. "calday ## is to be run only once a day that to at the end of the day and with a range of 0 min. 3umeric 'ointer ## is to be used for the tables where it allows only appending of records 9na no change... e.g./ H9T18B &Rtime managing table . Timestamp/ using this you can always delta as many times as possible with an upper limit. +hene*er there 1/1 relation you use the *iew and 1/ m you use ;(. GGGGGGGGGGGGGGGGGGGGGGGGGGGG :9. I38,C/ They are used to impro*e the performance of data retrie*al while e$ecuting the !ueries or work books the moment when we e$ecute and once we place the *alues in 1election criteria at that time the inde$es will act as retrie*al point of data... 9nd it will fetch the data in a faster manner...

Must common e$ample if you can obeser*e any book which has inde$es .. This inde$es will gi*e a e$act location of each topic based on this * can easily go to that particulur page and we will continue our thing<. 1imilar mannner in the data le*el the inde$es are act in B+ side... GGGGGGGGGGGGGGGGGGGGGGGGGGGGG =9. Time stamp error. sol/ acti*ate the data source and replicate the data source and load. 2. 8ata error in '19. sol/ (odify the in '19 error data and load. 3. R;H connection failed. sol/ raise the ticket to B91I1 team to pro*ide the connection. ). 1hort dump error. sol/ delete the re!uest and load once again. a >oads can be failed due to the in*alid characters b Han be because of the deadlock in the system c Han be becuase of pre*iuos load failure 6 if the load is dependant on other loads d Han be because of erreneous records e Han be because of R;H connections.....(sol/ raise the ticket to B91I1 team to pro*ide the connection f Han be because of missing master data. g Han be because of no data found in the source system h In*alid characters while loading. +hen you are loading data then you may get some special characters like NOPQ...e.t.c..then B+ will throw an error like In*alid characters..then you need to go through this R1RH transaction and enter all the In*alid chars and e$ecute..it will store this data in R19>>?+,8H&9R table..Then reload the data..2ou wonEt get any error because now these are eligible chars..done by R1RH. i 9>,R,(?T, user is locked 3ormally6 9>,R,(?T, gets locked due to a sm0= R;H destination entry ha*ing the incorrect password. 2ou should be about to get a list of all sm0= R;H destinations using 9>,R,(?T, by using transaction se14 to search field R;H?'TI?31 for a *alue of BKAG9>,R,(?T,B. 2ou will need to look for this information in any e$ternal R@3 instances that call the instance in which 9>,R,(?T, is getting locked as well. - >ower case letters not allowed. look at your infoob-ect description/ >owercase >etters allowed k e$traction -ob aborted in r3 It might ha*e got cancelled due to running for more than the e$pected time6 or may be cancelled by R@3 users if it is hampering the performance. l datasource not replicated If the new 8ata1ource is created in the source system6 you should replicate this 8ata1ource in EdialogE mode. 8uring the replication6 you can decide whether this 8ata1ource should be replicated as the 3.$ 8ata1ource or as the new 8ata1ource. If you do not run the replication in EdialogE mode6 the 8ata1ource is not replicated. m ?81 9cti*ation ,rror ?81 acti*ation errors can occur mainly due to following reasons

1. In*alid characters (O like characters 2. In*alid data *alues for units@currencies etc 3. In*alid *alues for data types of char S key figures. ). ,rror in generating 1I8 *alues for some data GGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGG 1"9 Ticket is nothing but an issue or a process error which need to be addressed. There are two types of tickets. K ito tickets # which are usually generated by the system automatically when a process fails. ;or e$ample6 when a process chain fails to run it will generate an into ticket which we need to address and find the fault. K non#ito tickets # which are the issues which the client face and which are forwarded for correction or alternati*e action. If youEre using Remedy for tickets6 unfortunately itEs not possible. But this depends on the software you are using6 ask your admin. GGGGGGGGGGGGGGGGGGGGGGGGGGG 119 Reconciliation is nothing but the comparison of the *alues between B+ target data with the 1ource system data like R@36 M8 edwards6?racle6,HH or 1H( or 1R(. In general this process is taken N 3 places one is comparing the info pro*ider data with R@3 data6 Hompare the Duery display data with R@3 or ?81 data and Hhecking the data a*ailable in info pro*ider key figure with '19 key figure *alues GGGGGGGGGGGGGGGGGGGG 129 919' (ethodology 1. 'ro-ect 'reparation6 in which the pro-ect team is identified and mobili<ed6 the pro-ect standards are defined6 and the pro-ect work en*ironment is set upT 2. Blueprint6 in which the business processes are defined and the business blueprint document is designedT 3. Reali<ation6 in which the system is configured6 knowledge transfer occurs6 e$tensi*e unit testing is completed6 and data mappings and data re!uirements for migration are definedT ). ;inal 'reparation6 in which final integration testing6 stress testing6 and con*ersion testing are conducted6 and all end users are trainedT and 0. Fo#>i*e and 1upport6 in which the data is migrated from the legacy systems6 the new system is acti*ated6 and post#implementation support is pro*ided GGGGGGGGGGGGGGGGGGGGGGGG

139 Responsibilities of an implementation pro-ect... ;or e$6 >ets say If its a fresh implementation of BI or for that matter you are implementing 19'... ;irst and foremost will be your re!uirements gathering from the client. 8epending upon the re!uirements you will create a business blueprint of the pro-ect which is the entire process from the start to the end of an implementation... 9fter the blue print phase sign off we start off with the reali<ation phase where the actual de*elopment happens... In our e$ample after installing the necessary soft wares6 patches for BI we need to discuss with the end users who are going to use the system for inputs like how they want a report to look like and what are the Rey 'erformance Indicators (R'I for the reports etc.6 basically its a !uestion and answer session with the business users... 9fter collecting those in formations the de*elopment happens in the de*elopment ser*ers... 9fter the de*elopment comes to an end the same ob-ects are tested in !uality ser*ers for any bugs6 errors etc.6 +hen all the tests are done we mo*e all the ob-ects to the production en*ironment and test it again whether e*erything works fine... The Fo#>i*e of the pro-ect happens where the actually postings happen from the users and reports are generated based on those inputs which will be a*ailable as an analytical report for the management to take decisions... The responsibilities *ary depending on the re!uirement... Initially the business analyst will interact with the end users@managers etc.6 then on the re!uirements the software consultants do the de*elopment6 testers do the testing and finally the go#li*e happens... +hat are the ob-ects that we perform in a production 1upport pro-ectJ In production 1upport Fenerally most of the pro-ect they will work on monitoring area for their loads(R3@ 3?3 19' to 8ata Targets (B+ and depending up the pro-ect to pro-ect it *aries because some of them using the 'HEs and 1ome of them using ,*ent Hhains. 1o its 8epends up on the 'ro-ect to pro-ect *aries. +hat are the different transactions that we use fre!uently in 'roduction support pro-ectJ 'l< e$plain them in detail. Fenerally In 'roduction 1upport 'ro-ect6 we will use the check the loads by using R1(? for monitoring the loads and we will rectify the errors in that by using step by step analysis. The consultant is re!uired to ha*e access to the following transactions in R3. 1. 1T22 2. 1(37 3. 1(0: ). 1(01

0. R197 4. 1(13 9uthori<ations for the following transactions are re!uired in B+ 1. R191 2. 1(37 3. 1T22 ). 1T") 0. 1,3: 4. 1,37 7. 1(12 :. R1RH =. 1(01 1". R1R% The 'rocess Hhain (aintenance (transaction R1'H is used to define6 change and *iew process chains. Apload (onitor (transaction R1(? or R1RD (if the re!uest is known The +orkload (onitor (transaction 1T"3 shows important o*erall key performance indicators (R'Is for the system performance The ?1 (onitor (transaction 1T"4 gi*es you an o*er*iew on the current H'A6 memory6 I@? and network load on an application ser*er instance. The database monitor (transaction 1T") checks important performance indicators in the database6 such as database si<e6 database buffer !uality and database indices. The 1D> trace (transaction 1T"0 records all acti*ities on the database and enables you to check long runtimes on a 8B table or se*eral similar accesses to the same data. The 9B9' runtime analysis (transaction 1,3" The Hache (onitor (accessible with transaction R1RH9H&, or from R1RT shows among other things the cache si<e and the currently cached !ueries. The ,$port@Import 1hared buffer determines the cache si<eT it should be at least )"(B.