Write Optimized DSO The concept of Write Optimized DSO was introduced in BI-7.0.

Write Optimized DSO unlikeStandard DSO has only one relational table, i.e. Active Table and moreover there is no SIDgenerated in Write Optimized DSO, and hence loading the data from Data Source to WriteOptimized DSO takes less time and acuires less disk space. Business Case : Require Data storage for storing detailed level of data with immediate reporting or further updatefacility. No over write functionality required. Limitation of Standard DSO - A standard DSO allows to store detailed level of information, However, activation process is mandatory.- Reporting or further update is not possible until activation is completed. Write Optimized DSO - Properties - Primarily designed for initial staging of source system dataBusiness rules are only applied when the data is updated to additional Info Providers.Stored in at most granular form- Can be used for faster uploadRecords with the same key are not aggregated ,But inserted as new record, as everyrecord has new technical key- Data is available in active version immediately for further ProcessingThere is no change log table and activation queue in it.- Data is saved quickly.Data is stored in it at request level, same as in PSA table.Every record has a new technical key, only inserts.- It is Partitioned on request ID (automatic).It allows parallel load, which saves time for data loading.It can be included in Process chain, and we do not need activation step for it.- It supports archiving. Write-Optimized DSO - Semantic Keys Semantic Key identifies error in incoming records or Duplicate records .Semantic Keys protects Data Quality such that all subsequent Records with same key are writteninto error stack along with incorrect Data Records.To Process the error records or duplicate records , Semantic Group is defined in DTP. Note : if we are sure there are no incoming duplicate or error records, Semantic Groups need not be defined. Write Optimized DSO- Data Flow 1. Construct Data Flow model.2. Create Data source3. Create Transformation4. Create Info Package5. Cr eate DTP Write-Optimized-Settings If we do not check the Check Box "Do not Check Uniqueness of Data ", the data coming fromsource is checked for duplication, i.e, if the same record (semantic keys) already exist in theDSO, then the current load is terminated.If we select the check box , Duplicate records are loaded as a new record. There is no relevanceof semantic keys in this case

When Write Optimized DSO is Recommended ? - For faster data load., DSOs can be configured to be Write optimized - When the access for Source system is for a small duration.- It can be used as a first Staging layer.In cases where delta in Data Source is not enabled, we first load data into WriteOptimized DSO and then delta load can be done to Standard DSO.When we need to load large volume of data into Info Providers, then WO DSO helps inexecuting complex transformations.Write Optimized DSO can be used to fetch history at request level, instead of going toPSA archive. Write

Optimised DSO - Functionality - It contains only one table, i.e. active data table (DSO key: request ID, Packet No, andRecord No)It does not have any change log table and activation queue.Every record in Wrtite Optimized DSO has a new technical key, and delta in it worksrecord wise.In Wrtite Optimized DSO data is stored at request level like in PSA table.In Wrtite Optimized DSO SID is not generated.In Wrtite Optimized DSO Reporting is possible but it is not a good practice as it willeffect the performance of DSO.- In Wrtite Optimized DSO BEx Reporting is switched off.Wrtite Optimized DSO can be included in Info Set or Multiprovider.Due to Wrtite Optimized DSO performance is better during data load as there is noActivation step involved. The system generates a unique technical keyThe technical key in Wrtite Optimized DSO consists of the Request GUID field(0REQUEST), the Data Package field (0DATAPAKID) and the Data Record Number field(0RECORD). Write-Optimized DSO-Points to RememberPoints to Remember :- Generally Write Optimized DSO is not prefered for reporting, but If we want to use it for reporting then it is recommended to defina a semantic in order to ensure the uniqueness of thedata.- Writeoptimized DSOs can force a check of the semantic key for uniqueness when data isstored.If this option is active and if duplicate records are loaded with regard to semantic key,these are logged in the error stack of the Data Transfer Protocol (DTP) for further evaluation.If we need to use error stack in our flow then we need to define the semantic key in theDSO level.Semantic group definition is necessary to do parallel loads. Write-Optimized DSO - Reporting If we want to use write-optimized DataStore object in BEx queries(not preferred):it is recommended to1. Have a semantic key and2. Ensure that the data is unique.Here the Technical key is not visible for reporting, so it looks like any regular DSO Write-Optimized DSO-Useful OSS Notes - OSS 1077308 : In a write-optimized DSO, 0FISCVARNT is treated as a key, eventhough it is only a semantic key.

generated in Write Optimized DSO, and hence loading the data from Data Source to WriteOptimized DSO takes less time and acuires less disk space. Business Case : Require Data storage for storing detailed level of data with immediate reporting or further updatefacility. No over write functionality required. Limitation of Standard DSO - A standard DSO allows to store detailed level of information, However, activation process is mandatory.- Reporting or further update is not possible until activation is completed. Write Optimized DSO - Properties - Primarily designed for initial staging of source system dataBusiness rules are only applied when the data is updated to additional Info Providers.Stored in at most granular form- Can be used for faster uploadRecords with the same key are not aggregated ,But inserted as new record, as everyrecord has new technical key- Data is available in active version immediately for further ProcessingThere is no change log table and activation queue in it.- Data is saved quickly.Data is stored in it at request level, same as in PSA table.-

Every record has a new technical key, only inserts.- It is Partitioned on request ID (automatic).It allows parallel load, which saves time for data loading.It can be included in Process chain, and we do not need activation step for it.- It supports archiving. Write-Optimized DSO - Semantic Keys Semantic Key identifies error in incoming records or Duplicate records .Semantic Keys protects Data Quality such that all subsequent Records with same key are writteninto error stack along with incorrect Data Records.To Process the error records or duplicate records , Semantic Group is defined in DTP. Note : if we are sure there are no incoming duplicate or error records, Semantic Groups need not be defined. Write Optimized DSO- Data Flow 1. Construct Data Flow model.2. Create Data source3. Create Transformation4. Create Info Package5. Cr eate DTP Write-Optimized-Settings If we do not check the Check Box "Do not Check Uniqueness of Data ", the data coming fromsource is checked for duplication, i.e, if the same record (semantic keys) already exist in theDSO, then the current load is terminated.If we select the check box , Duplicate records are loaded as a new record. There is no relevanceof semantic keys in this case. When Write Optimized DSO is Recommended ? - For faster data load., DSOs can be configured to be Write optimizedWhen the access for Source system is for a small duration.- It can be used as a first Staging layer.In cases where delta in Data Source is not enabled, we first load data into Write Optimized DSO and then delta load can be done to Standard DSO.When we need to load large volume of data into Info Providers, then WO DSO helps inexecuting complex transformations.Write Optimized DSO can be used to fetch history at request level, instead of going toPSA archive. Write Optimised DSO - Functionality - It contains only one table, i.e. active data table (DSO key: request ID, Packet No, andRecord No)It does not have any change log table and activation queue.Every record in Wrtite Optimized DSO has a new technical key, and delta in it worksrecord wise.In Wrtite Optimized DSO data is stored at request level like in PSA table.In Wrtite Optimized DSO SID is not generated.In Wrtite Optimized DSO Reporting is possible but it is not a good practice as it willeffect the performance of DSO.- In Wrtite Optimized DSO BEx Reporting is switched off.Wrtite Optimized DSO can be included in Info Set or Multiprovider.Due to Wrtite Optimized DSO performance is better during data load as there is noActivation step involved. The system generates a unique technical keyThe technical key in Wrtite Optimized DSO consists of the Request GUID field(0REQUEST), the Data Package field (0DATAPAKID) and the Data Record Number field(0RECORD). Write-Optimized DSO-Points to RememberPoints to Remember :- Generally Write Optimized DSO is not prefered for reporting, but If we want to use it for reporting then it is recommended to defina a semantic in order to ensure the uniqueness of thedata.- Writeoptimized DSOs can force a check of the semantic key for uniqueness when data isstored.If this option is active and if duplicate records are loaded with regard to semantic key,these are logged in the error stack of the Data Transfer Protocol (DTP) for further evaluation.If we need to use error stack in our flow then we need to define the semantic key in theDSO level.Semantic group definition is necessary to do parallel loads.

Write-Optimized DSO - Reporting If we want to use write-optimized DataStore object in BEx queries(not preferred):it is recommended to1. Have a semantic key and2. Ensure that the data is unique.Here the Technical key is not visible for reporting, so it looks like any regular DSO Write-Optimized DSO-Useful OSS Notes - OSS 1077308 : In a write-optimized DSO, 0FISCVARNT is treated as a key, eventhough it is only a semantic key.- OSS 1007769 : Parallel updating in write-optimized DSOOSS 966002 : Integration of write-opt DSO in DTP error stack - OSS 1054065 : Archiving supports. List of all the important tables used in Sales and Distribution (SD) : VTFA Flow shipping documentsVEPVG Delivery Due Index Sales order : VBAK Header dataVBAP Item dataVBPA Partners in sales order VBKD Sales district dataVBEP D ata related to delivery line items Billing document : VBRK header dataVBRP Item data Shipping : VTTK Shipment header VTTP Shipment itemVTTS Stage in transportVTSP Stage in transport per shipment itemVTPA Shipment partnersVEKP Handling Unit Header TableVEPO Packing: Handling Unit Item (Contents) SD Delivery Documet : LIKP Delivery header LIPS Delivery item Pricing : KONH Conditions header KONP Conditions itemsKONV Procedure ( billing doc or sales order)K OND Contracts : VEDA Contract data Customers KNA1 General DataKNB1 Customer Master Co. Code Data (payment method, reconciliation acct)KNB4 Customer Payment HistoryKNB5 Customer Master Dunning infoKNBK Customer Master Bank DataKNKA Customer Master Credit Mgmt.KNKK Cu stomer Master Credit Control Area Data (credit limits)KNVV Sales Area Data (terms, order probability)KNVI Customer Master Tax Indicator KNVP Partner Function keyKNVD Output typeKNVS Customer Master Ship DataKLPA Customer/Vendor Link Sales Documents VBAKUK VBAK + VBUKVBUK Header Status and Administrative DataVBAK Sales Document Header Data VBKD Sales Document - Business DataVBUP Item StatusVBAP Sales Document - Item DataVBPA PartnersVBFA Document FlowVBEP Sales Document Schedule LineVBBE Sales Requirements: In dividual Record

VD01 Create customer master VD02 Change customer master VD03 Display customer master VD04 Cus tomer account changesVD06 Customer deletion flagXD01 Create Customer (Centrally)XD02 Change Cu stomer (Centrally)XD03 Display Customer (Centrally)XD04 Customer Changes (Centrally)XD05 Block

customer (centrally)XD06 Mark customer for deletion (centr.)XD07 Change Customer Account GroupX D99 Customer master mass maintenanceXDN1 Maintain Number Ranges (Customer) SALES ORDER VA00 Initial Sales MenuVA01 Create Sales Order VA02 Change Sales Order VA03 Display Sales Order VA05 List of Sales OrdersVA07 Compare Sales Purchasing (Order) PRODUCTION PLANNING AND CONTROL CO01 Create production order with materialCO01S Adding simulation order CO02 Change Production O rder CO02S Change simulation order CO03 Display Production Order CO03S Display simulation order C O04 Print Production OrdersCO05 Collective Release of Production OrdersCO06 Backorder ProcessingC O07 Create order without a materialCO08 Create Production order with sales order CO09 Availability Ov erviewCO1F Create confirmation of prod. order CO1L Confirmation: List of requestsCO1P Predefined co nfirmation processesCO1V Confirmation: Fast entry of time tick CO10 Create Production order with proj ectCO11 Enter Time TicketCO11N Single Screen Entry of ConfirmationCO12 Collective Entry of Confir mationsCO13 Cancel confirmation of production order CO14 Display confirmation of production order C O15 Enter Production order ConfirmationCO16 Conf.: Postprocessing error recordsCO16N Reprocessing ConfirmationCO17 Enter confirmation with referenceCO1 9 Enter Time EventCO20 Orders acc. to Order Numbers CO21 Orders for MaterialCO22 Orders for the MRP controller CO23 Orders for the production scheduler CO24 Missing Parts InfoSystCO26 Order information systemCO27 Picking listCO28 Choose individual object listsCO30 Standard trigger pointsCO31 Create standard trigger pointCO32 Change standard trigger pointCO33 Display standard trigger pointCO40 Converting Planned Order CO41 Collective Conversion of Planned OrdersCO42 Act. Overhead: Prod.Order Ind.ProCO43 Act. Overhead: Prod.Order Col.ProCO 44 Mass processing of ordersCO46 Order progress reportCO47 Change comparisonCO51 Send Process MessagesCO52 Evaluate Process DataCO53 Control Recipe Monitor CO54 Message Monitor CO55 Wor klist for Maintaining PI SheetsCO56 Display PI SheetCO57 Create Message ManuallyCO58 Maintain PI SheetCO59 Delete PI SheetCO60 Find PI SheetCO62 Delete Process MessagesCO63 Evaluate Deletion LogsCO64 Worklist for Completing PI SheetsCO67 Worklist for Checking PI SheetsCO68 MiniApp PI S heet Mon -> ListCO69 Create Message AutomaticallyCO78 Archiving ordersCO8A Preset. CoProducts; Post-processingCO8B Preset. Co-Products; PostprocessingCO80 Number range maintenance: AUF_RUECK CO81 Number assignment: routing to order CO82 Number ranges for ordersCO83 Number range maintenance: RESBCO88 Act. Settlement: Prod./Pr ocess Order CO99 Set Status "Closed"MD04 Display Stock/Requirements SituationMF65 Stock Transfer for Reservation (Goods Movement)MF68 Log for Pull List (Goods Movement)MB1A Goods Withdrawal (ie Goods issue)MB1B Transfer PostingMB1C Other Goods ReceiptsMB31 Goods Receipt for Productio n Order COHV Mass processingCOMAC Collective Availability Check MATERIAL MASTER IH09 Display MaterialMM01 Create MaterialMM02 Change MaterialMM03 Display MaterialMM04 Dis play Material Change DocumentsMM06 Flag Material for DeletionMM11 Schedule Creation of Material MM12 Schedule Changing of MaterialMM13 Activate Planned ChangesMM14 Display Planned Changes MM15 Display Changes (Migration)MM16 Schedule Material for DeletionMM18 Activate Planned Chan gesMM19 Display Material & at Key DateMM50 List Extendable MaterialsMMBE Stock OverviewMMI 1 Create Operating SuppliesMMN1 Create Non-Stock MaterialMMS1 Create ServiceMMU1 Create NonValuated MaterialMB21 Create ReservationMB22 Change ReservationMB23 Display ReservationMB24 Reservations by MaterialMB25 Reservations by Account AssignmentMB1C Other Goods ReceiptsMB52 Warehouse Stock MB90 Output Processing for Material DocumentsMBRL Return Delivery per Material DocumentMB1B Transfer PostingMIBC ABC Analysis for Cycle CountingMI03 Display Physical Invent ory DocumentMI06 Display Inventory Count

FA S PBIBW QA / 1. Where do we used number range buffering? Codes SE27 and SNRO2. what are the different cases in which update rules can be copied?3. what are the different types of queries?4. what is query view and query definition?5. what is query template?6. what is the difference between drill down and slice n dice?7. what is result set query and infoset query?8. what are jump queries?9. what is drill up and drill across and how is drill across done?10. what is an infoset and what the difference to it in BI 7?11. what are the three scenarios for ods reporting?12. what is an info catalog?13. what are free characteristics and filters?14. what are the difference between restricted key figures and filters?15. what is the use of formula in BW?16. what are advance query techniques in BW?17. what is exception reporting?18. what is reporting agent?19. what is a variable and different types of variables and what is the use of variables?20. at what times will currencies be translated?21. what is the use of user exists?22. what is query management?23. what are the techniques to improve query performance?24. what is query monitor? Is it useful for aggregates, if so how?25. what are the query modes available in BW?26. what is an aggregate and what is the use of it?27. how are aggregated updated and when is it recommended to use aggregates?28. what are the conditions and factors to be taken into account while creating aggregates?29. what are the different strategies for creating an aggregate?30. how aggregates can be optimized?31. what is a profile generator and what is the use of it?32. what is the difference between authorization and authorization objects?33. what is Bex map?34. what is web reporting and what are the benefits of using it?35. what are the differences of bex and web reporting?36. what is bex web application designer?37. what type of servers are required to allow web reporting in SAP BW?38. what is web reporting template?39. what does data changes aggregates update program do?40. what is the aim of aggregates and in what case can you not create aggregates?41. where can data be filtered in SAP BW?42. What are the variables used in Bex reporting?43. What are the different Processing Types?

44. What is the replacing path Process Type? What is the input for Replacing path process type?45. How do you create a Generic data source?46. What are the function modules?47. Types of Deltas?48. what are the Generic delta types?49. Explain V3 Update?50. What is Cell definition?51. How do you Transport objects from Development to Quality? IMP52. What is Navigation Attribute? What are the tables will create while creating Navigationalattribute?53. What are the tables for Master data in BW?54. What are the tables will create while creating Info Object?55. What are the tables will create while creating Info Cube?56. Explain your Landscape? Examples?57. Explain Implementation Methodologies?58. ABAP reports?59. What are the tables for SD in R/3?60. how many Process Chains you are used?61. What are the issues Faced while loading data?62. What are the custom cubes you used?63. How many users your company have?64. What are the queries you have created?65. What are the characteristics, key figures involved in query?66. On what basis you assign Characteristics to Dimensions?67. What is Plan data and where it will sit?68.HOw to creat a report on one column where we stored both sales Report ?69.How to strat & STOP PROCESS CHAIN70: LOWER CASE & UPPER CASE ?71: WHY WE GO FOR GENERIC EXTRACTION ? WHICH CASE ? IF THE DATA WILLBE IN 3 TABLES & WE HAVE TO EXRTACT THE DATA FROM TWO FIELDS THENWHAT TO DO ?72: ENHNACEMENT CASE WHICH LOGIC APPLY BY YOU ?73: HOW MANY REPORTS /INFOCUBE /INFOSOURSE / DSO CREATED BY YOU ?74: BASED OPEN 2LIS_11_VAHDR WHAT ARE THE REPORT U ARE CREATED ?75: WHY WE GO FOR CEREATING INDEX ? HOW TO KNOW THAT IT'S THE TIME TOCREAT THE INDEX ? why index not other Compress/ ?76: HOW TO ROLE AUTHORIZEID SAP BI ?77:WHAT IS EARLY INITIALZE DELTA ?78: Wht is best for

reporting Infocube or Dso ? why ?79: How many tables are in dso ? standard dso / direct dso / write optimized dso ?80: Selective Deletion /Repair full request / Repet delta /Reverse Posting /?81: if the data is loaded in sapbw /sap bi & i want to serach the pericular year data ? where tosearch ?82 : Data is loading from sap bi/bw if in extraction stage it fails / How to rectify ? whr tosearchh ?