SAP Net Weaver 400s BI 7.0For more information, visit the Business Intelligence homepage.

Transcription

1 Applies to: SAP Net Weaver 400s BI 7.0For more information, visit the Business Intelligence homepage. Summary This paper provides the step by step procedure on how to archive data in ODS/InfoCube using ADK method. The purpose is to explain detailed technical procedure of ADK archiving, deleting and reloading archived data in the InfoProvider. For archiving, we need to create the logical file and physical file for each InfoCube/DSO based on some parameters using Archiving Object. Persons who want to understand stepwise implementation of SAP BI ADK archiving and reloading of archived data will be benefited from this paper. Author: Manoranjan Pandey Company: Tata Consultancy Services Ltd. Created on: 13 July 2009 Author Bio The author has been associated with Tata Consultancy Services Ltd. for 1.5 year with 5 years experience in SAP BIW and has been working in the Utilities domain since then. He has been involved in an end-to-end implementation of SAP BI 7.0 for a renowned client in this domain. In this time of association with this project, he was able to gain knowledge in couple of issues related to BI Archiving such as design, implementation etc SAP AG 1

2 Table of Contents Business Scenario... 3 Solution Benefits... 3 How and where to create logical file :... 4 How to create data archiving process... 7 Process for Reloading the Archived Data in SAP BI System Related Content Disclaimer and Liability Notice SAP AG 2

3 Business Scenario In one BI system, the volume of data increases constantly. Constant changes to business and legal requirements mean that this data must be available for longer. In effect, the cost for process, personnel and technology grow. Since keeping a large volume of data in the system affects performance and increases administration efforts. So we can remove this data from our data targets store it into other data storage and reload to the system whenever required. Thus we can increase memory space and the retrieval performance of the data at query runtime. Solution Benefits The main advantage of ADK archiving is it is a SAP-standard BW solution which is a comprehensive procedure for writing, deleting, and storing BW data. Hence, consistency of the archived data is guaranteed. It allows the use of a blend of cost-effective data storage media. It is platform independent and handles structural changes in the definition of BW elements. It has easy-to-use front end. Moreover, it offers reduction in resource consumption. The hardware costs for hard drives on the BI side where the online data will be stored, is reduced if the archiving solution is in place. Below are BW relevant features of ADK: Handling structural changes: Since the ADK is storing metadata of the archived data as well as the data itself, it is capable of retrieving the archived data even after structural changes have been made. This data is not converted to the new structure, but simply displayed in the new structure. Platform independency: The ADK can handle different code pages (ASCII, EBCDIC, and UNICODE) and number formats. Data compression: The archived data can be compressed up to 5 times of the original data volume. Archiving Information System (SAP-AS).The archived data can be displayed with the Archiving Information System. In BW, the customer has to define the Info Structures for the respective archiving objects, and fill them manually within AS customizing. Administration via transaction SARA: The scheduling, monitoring and management of the archiving session can be performed with the standard transaction SARA SAP AG 3

4 How and where to create logical file : Step 1: Go to transaction code FILE in BI, click on Logical File Path Definition and select Archive Global Path as shown below: Step 2: Click on Assignment of Physical Paths to Logical Path 2009 SAP AG 4

5 Step 3: Select the WINDOWS NT and display. This will show the physical path where archive files store SAP AG 5

6 Step 4: To create our own/new Logical File, select Logical File Name Definition, Cross-Client and New Entries Step 5: Enter the following details as shown below- Logical File: ZXXXX Physical File: Parameter_<MONTH>_<DAY>.txt Data Format: ASC Application Area: Select the respective area (like SD, FI, MM, etc.) Logical Path: Select the existing path ARCHIVE_GLOBAL_PATH and the save finally SAP AG 6

7 How to create data archiving process Step 6: To create Data Archiving Process, go to transaction code RSA1 in BI system, right click on the DSO/InfoCube, click on Create Data Archiving Process 2009 SAP AG 7

8 Step 7: System will assign the archiving object name for the DSO/InfoCube. In the General Settings tab, check the box ADK-Based Archiving. Step 8: In the Selection Profile tab, select the Characteristic for Time Slices as a Time Characteristic and select and move left respective InfoObjects on which we need to archive data based upon selection criteria SAP AG 8

9 Step 9: In the Semantic Group tab, select and move the InfoObjects fro right to left for which we want to archive the data. Step 10: In the last tab ADK, enter the newly created logical file name, maintain the Archiving File Size, select Delete Job as Not Scheduled. This will not allow system to delete the data automatically from data target SAP AG 9

10 Step 11: After creating and maintaining an Archiving Object for a DSO/InfoCube, next job is to archive the data. Go to transaction code SARA, give the Archiving Object name, and click on Write. Step 12: To create a variant, enter a variant name start with ZXXXX and click on Maintain SAP AG 10

11 Step 13: In the pop-up window, select For All Selection Screens. Step 14: in the tab Primary Time Restrictions, maintain the details as below: 2009 SAP AG 11

12 Step 15: In the tab Further Restrictions, give the details if we want to archive the data on certain selection condition. Step 16: Click on to go back from transaction, system will pop-up a window, click on Yes to save. Step 17: Enter the variant Meaning i.e., text SAP AG 12

13 Step 18: Click on Start Date SAP AG 13

14 Step 19: Click on Immediate and SAVE. Step 20: Click on Spool Params. Step 21: Enter the Output Device and press Enter button. Step 22: Click on Execute SAP AG 14

15 Step 23: Press the Job button to see the job overview. Step 24: After archiving the data, we need to delete the data from respective DSO/InfoCube. The delete program first read the data from the archive files and then deletes it from data base. For doing this activity, go to transaction SARA. Enter the Archiving Object name and click on Delete. Step 25: Click on Archive Selection SAP AG 15

16 Step 26: Select the archived file and press Enter SAP AG 16

17 Step 27: Click on Start Date and click on Immediate and SAVE. Step 28: Click on Spool Parameters, enter the Output Device name and press Enter SAP AG 17

18 Step 29: Click on Execute button. Data is deleted successfully. Step 30: To see the archive data, go to AL11 and double click on the name of directory SAP AG 18

19 Process for Reloading the Archived Data in SAP BI System Once the data has been archived on the application server it is stored externally by basis team on separate magnetic tapes and other storage devices. Whenever such data is again required for reporting the basis team can bring it back on application server easily. Once it is on the application server it can be reloaded into a separate data target which is a copy of the original info-provider. S A P A SAP BI Data Print Lists r c h i v Meta data for external retrieval (PBS Indices, DocID) e L I n There are two different methods to reload the archived info provider data- reload data into different data target or reload into the same InfoProvider. It is recommended that we reload the archived data into the copy of the original InfoProvider. It allows the reloaded data to remain physically separate from any existing data. This allows for easier verification of the reloaded archive data because the data is isolated in its own InfoProvider. We also can combine reloaded data with current data via multi providers for better query performance because of the system s parallel query processing functionality. Data should be reloaded into the same info-provider only in emergency cases, in which wrong data was archived due to error in customizing or during document selection. Therefore, data should only be reloaded immediately after the erroneous archiving session. If we reload the data, later we may end up with inconsistencies in the database SAP AG 19

20 Method 1: Reload Data into Different Data Target (copy of original data target with same Structure) Step 1: Go to transaction RSA1, right click on the original DSO and click Copy SAP AG 20

21 Step 2: Save the DSO as Local Object and Activate it. Step 3: Create Transformation from the original DSO to the copied DSO SAP AG 21

22 Step 4: Activate the transformation. Step 5: Now create DTP for the copied DSO SAP AG 22

23 Step 6: Select the settings as below and click on Filter to make the selection for which we want to reload the archived data. Step 7: Click on Change Selection and enter the range of value and then press Enter SAP AG 23

24 Step 8: Save and activate the DTP and then click on Execute. Step 9: See the status in Details tab (Green). We can check and display the data in the copied DSO SAP AG 24

25 Method 2: Reload the data into the same InfoProvider. Step 1: Go to transaction SARA and select/enter the archiving object name as shown below. Step 2: In the menu, select Go To and click Reload SAP AG 25

26 Step 3: Press Enter to continue. Step 4: Select Archive Selection and maintain Variant Attribute SAP AG 26

27 Step 5: Check the box and press Enter SAP AG 27

28 Step 6: Maintain the Start Date and Spool Parameters SAP AG 28

29 Step 7: Click on Execute button to start the reload process. We can check and display the data in the original DSO SAP AG 29

30 Related Content For more information, visit the Business Intelligence homepage SAP AG 30

31 Disclaimer and Liability Notice This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document SAP AG 31