Sand dna nearline for sap net weaver bw 7.0
Upcoming SlideShare
Loading in...5
×
 

Sand dna nearline for sap net weaver bw 7.0

on

  • 311 views

 

Statistics

Views

Total Views
311
Views on SlideShare
311
Embed Views
0

Actions

Likes
0
Downloads
13
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Sand dna nearline for sap net weaver bw 7.0 Sand dna nearline for sap net weaver bw 7.0 Document Transcript

  • SAP COMMUNITY NETWORK scn.sap.com© 2012 SAP AG 1SAND/DNA Nearline for SAPNetWeaver BW 7.0Applies to:SAND/DNA Nearline for SAP NetWeaver BW 7.0SummaryThis document is a tutorial which provides hand-on introduction to the following aspects of SAND/DNANearline for SAP NetWeaver BW 7.0 and the SAP NLS (Nearline Storage) interface.• Basic Nearline functionality:o Nearlining and reloading of Infocubeso Query access to Nearline dataAuthor(s): Ram TomarCompany: Bajaj Hindusthan Ltd..Created on: 04 June 2013Author BioRam Tomar has completed his Master in Computer Application from U.P TechnicalUniversity.She has 6 years of SAP experience. She has been working on SAP NW BI since 5years. Apart from SAP BI she has experience in SAP ABAP and hands on experiencein SAP QM modules.
  • SAND/DNA Nearline for SAP NetWeaver BW 7.0SAP COMMUNITY NETWORK scn.sap.com© 2012 SAP AG 2Table of ContentsIntroduction .........................................................................................................................................................3Topics..............................................................................................................................................................3Activating Data Archiving Process for an Infocube ............................................................................................3Nearlining Data from an Infocube.......................................................................................................................6Reloading Nearline Data into SAP Netweaver BW ..........................................................................................10Accessing Nearline Data using SAP Business Explorer (BEx) ........................................................................13Related Content................................................................................................................................................15Copyright...........................................................................................................................................................16
  • SAND/DNA Nearline for SAP NetWeaver BW 7.0SAP COMMUNITY NETWORK scn.sap.com© 2012 SAP AG 3IntroductionNearline Storage (NLS) is a type of Data Archiving Process.Using the NLS, you can archive and store transaction data from InfoCubes and DataStore objects.The data archiving process consists of three main steps:... 1. Creating the archive file/near-line object2. Storing the archive file in near-line storage3. Deleting the archived data from the databaseA data archiving process is always assigned to one specific InfoProvider and has the same name as thisInfoProvider. It can be created retrospectively for an existing InfoProvider that is already filled with data.Nearline storage is recommended for the data that is still in use. Storing historical data in near-line storagereduces the data volume on Info providers; however the data is available for BEx queries.Topics• Basic Nearline functionality:o Nearlining and reloading of Infocubeso Query access to Nearline dataActivating Data Archiving Process for an InfocubeThe objective is to activate a Data Archiving Process (DAP) for the InfoCube ZEDU98I and to determine theparameters of this DAP. Assume that the data will be moved to nearline storage ("nearlined") on a yearlybasis starting with the year 1990. It should be possible to nearline data for different company codesindependently.Step 1Use the LISTCUBE transaction to verify the contents of the InfoCube for all years.Figure 1: Content of Infocube View slide
  • SAND/DNA Nearline for SAP NetWeaver BW 7.0SAP COMMUNITY NETWORK scn.sap.com© 2012 SAP AG 4Verify the data for the earliest year, 1990.Figure 2: Verify Infocube DataStep 2Start the RSDAP transaction and enter your InfoProvider name in the field provided.Figure 3 : Create Data Archiving ProcessStart editing (creating) the new Data Archiving Process.On the first tab, uncheck the ‘ADK-Based Archiving’ option and specify the general nearline connectioninformation as shown in Figure 4.Select Time slice Archiving as shown in Figure 4.Figure 4 : Nearline connection infoStep 3 View slide
  • SAND/DNA Nearline for SAP NetWeaver BW 7.0SAP COMMUNITY NETWORK scn.sap.com© 2012 SAP AG 5Nearline connection information also needs to be specified on the Nearline Storage tab (depending on thesupport package level installed). The technical details for communication with the nearline provider must bespecified on this tab as well, as shown in Figure 5.Figure 5 : Nearline Connection detailsSave the Data Archiving Process.Step 4On the Selection Profile tab, define the characteristics that will determine the "slice" of data to be saved tonearline storage. As we want to nearline on a yearly basis, "Calendar Year/Month" is used as the primarypartitioning characteristic; as we want to be able to nearline different company codes independently,"Company code" is selected as an additional partitioning characteristic.The Semantic Group tab is optional and depends on the requirement.Figure 6 : Defining characteristic of the Nearline sliceActivate the DAP.Successful activation can be verified by looking at the entry for the Active Version, which should be set toExecutable = Edited Version.Figure 7 : Activated DAP
  • SAND/DNA Nearline for SAP NetWeaver BW 7.0SAP COMMUNITY NETWORK scn.sap.com© 2012 SAP AG 6Nearlining Data from an InfocubeObjective is to move data for the year 1990 in the InfoCube ZEDUnnI to nearline storage. This is done usingan Archiving Request from the Manage screen for the InfoCube.Step 1After the Data Archiving Process is activated, a new Archiving tab appears in the Manage screen for theInfoCube. As no Archiving Request has been created at this point, no Archiving Request information isdisplayed.Figure 8 : Archiving TabAll Archiving Request information for this specific InfoProvider will be available on this grid.Step 2Create a new Archiving Request by clicking the Archiving Request.Determination of the nearline slice is based on a relative time calculation. As we want to nearline a completeyear in our example, we set the value of the “Only Complete” field to “Year(s)”. This ensures that theArchiving Request nearlines complete years. In order to nearline the year 1990, we have to determine theoffset from the system date when the Archiving Request is created. In 2012, we would choose all datarecords older than 21 years. This results in an Archiving Request specifying that the Calendar Year / Monthmust be less than or equal to December 1990.Settings on the "Further Restrictions" tab should be ignored in this exercise.In the Process Flow Control section, adjust the "Continue Processing Until Target Status" setting to carry outthe Archiving Request only up to the point where the request is generated. This means that the ArchivingRequest will not actually be executed in this step, which simply defines the slice.Select to start it In Background (or In Dialog as you will only generate the request but not yet execute it) andchoose the button that does not simulate as shown in the Figure 9.
  • SAND/DNA Nearline for SAP NetWeaver BW 7.0SAP COMMUNITY NETWORK scn.sap.com© 2012 SAP AG 7Figure 9 : Defining the Data to be NearlinedStep 3Going back to the Archiving tab on the Manage screen, you can see some of the relevant Archiving Requestmetadata:Figure 10 : Archiving RequestClick the button in the Lock Status field to start executing the Archiving Request. On the dialog box thatappears, under Action, choose to continue until Status 70. This covers the complete loop, including datadeletion in SAP NetWeaver BW. Start the job in the Background.Figure 11 : Continue until archive request is completed
  • SAND/DNA Nearline for SAP NetWeaver BW 7.0SAP COMMUNITY NETWORK scn.sap.com© 2012 SAP AG 8The overall status of the job is displayed along with corresponding metadata on the grid showing allArchiving Requests.Figure 12 : Active requestYou can access the corresponding nearline data via the adjoint nearline provider with the $N suffix. In thisexample, this is the InfoCube ZEDUnnI$N.Figure 13 : Data in Nearline ProviderCompare this to the values from Figure 2, the results should be the same.The grid also shows that we have nearlined 363 records in one data package, using roughly 126 kilobytes inthe database as shown in Figure 14.Figure 14 : Info of Active JobStep 4
  • SAND/DNA Nearline for SAP NetWeaver BW 7.0SAP COMMUNITY NETWORK scn.sap.com© 2012 SAP AG 9Use the listcube transaction to verify that the data for the year 1990 has been deleted from SAP NetWeaverBW.Figure 15 : Verify data deletion from BI Infocube
  • SAND/DNA Nearline for SAP NetWeaver BW 7.0SAP COMMUNITY NETWORK scn.sap.com© 2012 SAP AG 10Reloading Nearline Data into SAP Netweaver BWObjective is to reload nearline data back into SAP NetWeaver BW.Step 1Identify and select the Archiving Request used to nearline the data of company code 4000 for the year 1991.In the example, this is the request with the SID 243.Figure 16: Archived RequestsClick the button in the Status field to trigger the reload. Reload the data in the background.Figure 17: Reload the DataThe reload request appears in the list of all requests in the Archiving tab, after the grid is refreshed. Thecorresponding Archiving Request is set to a status of yellow as shown in Figure 18.
  • SAND/DNA Nearline for SAP NetWeaver BW 7.0SAP COMMUNITY NETWORK scn.sap.com© 2012 SAP AG 11Figure 18: Reload Request in the Requests ListThe reload involves three phases: copy, verify and delete.When the reload has finished, all requestsdisplayed on the grid once again have a status green:Figure 19: Completion of Reload RequestThe reloaded slice of data is now not available via the adjoint nearline provider. Because it has beenreloaded, it is available only from the online provider:Figure 20: Reloaded Data Available via Online Provider
  • SAND/DNA Nearline for SAP NetWeaver BW 7.0SAP COMMUNITY NETWORK scn.sap.com© 2012 SAP AG 12The reloaded data appears as a new APO request in the list of data load requests.Figure 21: Reloaded Data as APO Request in Request ListThis request is not yet compressed, as can be seen from the list. It must be compressed before this dataslice can be nearlined again.
  • SAND/DNA Nearline for SAP NetWeaver BW 7.0SAP COMMUNITY NETWORK scn.sap.com© 2012 SAP AG 13Accessing Nearline Data using SAP Business Explorer (BEx)Objective is to access nearline data using a BEx Query.Step 1Start the BEx Query Designer (BW 7 Version) and create a new query on the InfoCube as shown inFigure 22.Figure 22: New BEx QueryCheck the data: only the online data of the InfoCube will be visible.Step 2In order to see the nearline data as well, use theRSRT transaction to adjust the query properties.Figure 23: Adjust the Query PropertiesIn the query properties window, click to check the “Read Near-Line Storage As Well” option box.
  • SAND/DNA Nearline for SAP NetWeaver BW 7.0SAP COMMUNITY NETWORK scn.sap.com© 2012 SAP AG 14Figure 24: Read Near-Line Storage as WellStep 3The complete result set, merging online and nearline data, is displayed.Figure 25: Complete Result SetThis is similar to the results now shown in BEx.
  • SAND/DNA Nearline for SAP NetWeaver BW 7.0SAP COMMUNITY NETWORK scn.sap.com© 2012 SAP AG 15Related ContentSAND websiteSAP BI ArchivingNLS Best Practices
  • SAND/DNA Nearline for SAP NetWeaver BW 7.0SAP COMMUNITY NETWORK scn.sap.com© 2012 SAP AG 16Copyright© Copyright 2012 SAP AG. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9,iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States and/or other countries.Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks ofCitrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, MassachusettsInstitute of Technology.Java is a registered trademark of Oracle Corporation.JavaScript is a registered trademark of Oracle Corporation, used under license for technology invented and implemented by Netscape.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentionedherein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, andother Business Objects products and services mentioned herein as well as their respective logos are trademarks or registeredtrademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.All other product and service names mentioned are the trademarks of their respective companies. Data contained in this documentserves informational purposes only. National product specifications may vary.These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAPGroup") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors oromissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in theexpress warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting anadditional warranty.