White Paper for Archiving in SAP BI - United Biscuits

8/10/2019 White Paper for Archiving in SAP BI - United Biscuits

http://slidepdf.com/reader/full/white-paper-for-archiving-in-sap-bi-united-biscuits 1/25

How to Archive in SAP BI

White Paper Version 1.0 – October 2008



How to archive in SAP BI

Confidential Page 2 of 25

Document Control

Change Record

Date Author Version Change ReferenceOctober 7,2008

Rohit Parti 1.0 No previous document





TABLE OF CONTENTS

1. Business Scenario................................................................................................................ 4

2. Solution Approach to the Business Scenario ........................................................................ 4

3. Archiving strategy in the SAP BI System .............................................................................. 5

4. Archive Process – An Overview ........................................................................................... 6

5. SAP BI Data Targets in Scope for Archiving ......................................................................... 7

6. Prerequisites for Archiving .................................................................................................... 7

7. Considerations for Archiving ODS Data. ............................................................................... 7

8. System in scope for Feasibility ............................................................................................. 7

9. Step-By-Step Archive Process ............................................................................................. 8

10. Conclusion ......................................................................................................................... 25





1. Business Scenario

“The rapid increase in transaction data has created an enormous administration workload and leads to longerdata-processing times in the SAP BI Application area. We need to find a solution where in we can achieveconsiderable performance improvement in reporting and efficient utilization of database resources.”

2. Solution Approach to the Business Scenario

The best possible solution approach to the above problem would be to ARCHIVE the historical data that is notcurrently being used in reporting and store it in a safe storage from where it can be retrieved back as in whenrequired for reporting or auditing purposes.





3. Introduction to archiving strategy in the SAP BI System

Data archiving in the SAP BI system allows you to archive data from InfoCubes and ODS objects.The tool used is the Archiving Development Kit (ADK). The ADK is already used in many mySAP.comcomponents to develop archiving solutions. The ADK provides the runtime environment required for archiving.

The first step is to read the data from the data targets and use the ADK to write it to the archive files. Thesearchive files are stored in a local directory.

The ADK also enables you to export archive files from your local file system to external third-party data stores.In UB, the third party data store is ‘Common Store’.

Properties of the ADK

Has already been integrated into many mySAP.com components It is platform-independent and release-independent Is able to handle structural changes Has a central archive administration (SARA)

Can be used in conjunction with third party archiving and storage systems Supports statistics and indexing Indexing takes place using the Archive Information System (SAP-AS)

Figure 1.0: ADK Integration in BI





4. Archive Process – An Overview

The archiving process in the SAP BI system is divided into three stages:

1. Writing data to the archive2. Deleting archived data from the data sources.3. Reloading the data from the archives into the SAP BI system

Figure 2.0: Archiving Process Overview





5. SAP BI Data Targets in Scope for Archiving

The current scope for Archiving of BI data targets as part of feasibility study that is being carried out is: -

InfoCube – Create any cube having relevant data in it for archiving.

Operational Data Store (ODS) – Create an ODS object having relevant data in it for archiving

6. Prerequisites for Archiving

Logical File Name

This is the actual defined physical path where all archived data files will reside.It is maintained on transaction code: FILE.For more information on define this you can go to the following LINK

Compression

For archiving data from the cube, the cube should be fully compressed. The source table of the archive datawould then be the ‘E’ table of the cube. The ‘F’ table i.e. the fact table would have zero records in it.

7. Considerations for Archiving ODS Data.

For ODS objects, the system only deletes the data from the Active Data table. The Change Log remainsunchanged.

With ODS objects, it is therefore particularly important that the archived data area is protected againstdata being reloaded into the ODS object. If this were not the case, when the data is activated, not only

would new entries be generated in the Active Data table, but a real update would also be generated inthe Change Log and updated into the connected data targets.

8. System in scope for Feasibility

The system in scope for carrying out the feasibility of archiving in SAP BI application area was SAP BI 7.0having the SP12 installed.





9. Step-By-Step Archive Process

1) Check theexistingnumber ofrecords in the‘E’ table as thecube iscompressed.

(TCODE – SE16)

2) Total numberof records inthe ‘E’ Facttable of thecube are13,500,912

3) Check thecontents of the‘F’ fact table.

4) Numbers ofrecords arezero as thecube iscompressed

so ‘F’ tablehas no recordsin it.

5) Check thecompressionstatus in theCube, as thisis one of theprerequisitesof Cube





Archiving.

6) Create ArchiveProcess

On context menu ofthe InfoCube, select‘Create ArchiveProcess’




Confidential Page 10 of25

7) General SettingsTab

No changes made tothis tab as we are notusing the Nearlinestorages.

8) Selection ProfileTab

Choose the timecharacteristics to beused by the archivingobject from the dropdown box

‘Characteristics forTime Slices’.Optionally you candrag to include anyadditional partitioningtime characteristicfrom the InfoObjectslist.





9) Semantic GroupTab

Select a characteristic

for grouping data onthe archive file.

10) ADK Tab

Enter the Logical FileName and check ‘StartAutomatically radiobutton under ‘DeleteJobs’. Suggestion:

Leave the ‘Archive FileSize’ textboxes empty.If specified, the archiveobject will be writtenand split according tothe maximum sizeentered in MB. E.g. Ifyou need to archive a100 mb data, and youspecified 50 under‘Maximum Size in MB’,there’ll be 2 archivefiles each with a size

of 50 mb, archived





11) Activate thearchivingprocess.

Check the contextmenu (right click on

the InfoProvider), themenu should now beenhanced withadditional function-‘Manage ADK Archive’and ‘Data ArchivingProcess’

12) Manage ADKArchive

Select ‘Manage ADKArchive’. This takesyou to transactioncode SARA

Archiving Data(Manually)

Click on Write buttonCreate a variant(Cannot be reused –

One variant perarchiving Object)Click on Maintainbutton

13) You can run thearchive manuallyhere orotherwise usethe processchain





14) MaintainVariants formanual write job.

Continue and makethe following inputsaccording to yourarchiving object

Click on Next Screen

button

Click the

button





In the variant attributesscreen –

Fill the ‘Meaning’ textarea with a meaningfulname of the variant.

Click on the Savebutton twice.

15) ‘Start Date’button

Click on ‘Start Date’button – Schedule to

start immediatelyClick on ‘SpoolParams’ button andthe accept spoolprinting parameters.

16) See logs





17) Manage theInfoProvider

Notice an extra tab –Archiving whichcontains all archivingrelated functions.Here you can monitorthe progress, see howmany records werearchived per file, howmuch space the filesutilize, archivingcriteria, archivingsession number,release hangingprocesses & see thelast action of anarchiving object.

HINTS: Icons on theArchiving tab.This indicates that therequest# 188 062 hascompleted archivingand data is nowremoved from theInfoProvider.

This indicates that therequest# 188 043 hascompletedsuccessfully reloadingback the archived datato the InfoProvider.

18) ArchivingSessions

Click on ‘Management’





button of Transactioncode SARAArchiving session willindicate incompleteeven though jobfinished because thearchived data has not

yet been deleted.

19) Deleting Datafrom an infoprovider

Back on the ADK(SARA), click on‘Delete’ button

Archive Selection

Click ‘ArchiveSelection’ button. Thisis to select whicharchiving session youneed to delete its data(there can be morethan 1)Click on Continue





20) Execute &monitor the ‘Job’





21) Check number ofrecords in ‘E’fact table after

the deleteprogram has run.

The number of recordsshould decrease fromthe E table as some ofthe contents are nowarchived.





The number of recordsare reduced.

Records beforearchiving– 13,500912

Records afterarchiving – 12,446,809

22) Check for theArchive status inthe manage tabof the cube.

23) SARAManagement

Back on SARA, click

on ManagementSession maintainsgreen status if data issuccessfully archivedand removed from theinfoprovider

24) Reloading data

Reloading Archiveddata back to BI(Strictly on exceptional

cases)

Back on SARA, go tomenu bar -> Goto ->Reload





Click continue on thismessage.

25) Create a variantfor reloadingdata into thecube.

26) Enter adescription forthe Reloadvariant.





27) Maintain variant

Save (twice) and backon SARA -> select

28) ArchiveSelection

Click on ‘ArchiveSelection’ and selectthe file to be reloaded(can be more than 1file)

29) Execute &Monitor the job

30) See Logs









31) Data is nowreloaded into theCube ☺☺☺☺

32) Number ofrecords added tothe F table of thecube

33) Check for load

status inArchiving tab.

If reload is successfulstatus will be green





34) Check contentsof ‘E’ fact tableafter the reloadjob hasexecuted.

The number of recordsremains the same.

35) Check thecontents of the‘F’ fact table.

The numbers ofrecords haveincreased in the ‘F’

fact table as thereloaded archivecontents have beentransferred to the ‘F’fact table.





10. Conclusion

The above steps depict the way archiving is carried out in the SAP BI system. The below mentionedstatistics of archiving run show the number of records in the two cube fact tables (F and E) as follows: -

Table Name Number of Records before Archiving Number of Records after Reloading

/BIC/FZCOPAACTD 0 1,054,103

/BIC/EZCOPAACTD 13,500,912 12,446,809

The above result of the table content shows that the archived contents when reloaded are placed in the ‘F’fact table of the cube.

The total number of records for reporting remains the same when the reload program is run.

Documents

White Paper for Archiving in SAP BI - United Biscuits