EMC iewpoint for SAP Data Retention Tool Module ersion 2.0 ADMINISTRATION MANUAL P/N 300-003-423 RE A01 EMC Corporation Corporate Headquarters: Hopkinton, MA 01748-9103 1-508-435-1000 www.emc.com
Copyright 2006 EMC Corporation. All rights reserved. Published February, 2006 EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROIDED AS IS. EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. All other trademarks used herein are the property of their respective owners. ii EMC iewpoint for SAP CDART Module Administration Manual
Contents Preface... v Chapter 1 Chapter 2 Chapter 3 Introducing iewpoint for SAP CDART Module Introduction... 1-2 iewpoint CDART Module... 1-3 Scope... 1-5 Customizing SAP DART... 1-7 Menu navigation... 1-7 Customer specific fields... 1-9 Data source... 1-9 Archiving object /PBS/DART... 1-10 CDART Archiving Archiving data with iewpoint modules... 2-2 Preparations... 2-2 Generate archive index... 2-3 Select archive... 2-5 Select archive automatically... 2-5 Delete old run... 2-5 All documents / process sequential number intervals... 2-6 Merge... 2-6 Long term problem... 2-7 Postprocessing programs... 2-7 Archive tool... 2-8 Deletion tool... 2-9 Data Extraction EMC iewpoint for SAP CDART Module Administration Manual iii
Contents Disk space requirement... 3-2 DART version... 3-3 Settings... 3-3 Create an extract... 3-3 Further processing of the extract... 3-4 iv EMC iewpoint for SAP CDART Module Administration Manual
Preface As part of an effort to improve and enhance the performance and capabilities of its product line, EMC from time to time releases revisions of its hardware and software. Therefore, some functions described in this manual may not be supported by all revisions of the software or hardware currently in use. For the most up-to-date information on product features, refer to your product release notes. If a product does not function properly or does not function as described in this manual, please contact your EMC representative. iewpoint Functionality Audience This document describes how to administer the various components that make up EMC iewpoint for SAP Data Retention Tool (CDART) Module. EMC s technology allows you to effectively manage your application data by providing the ability to define the access, retention, and service level requirements for any business transaction at each point in its lifecycle. This guide is part of the iewpoint documentation set, and is intended for use by anyone administering the iewpoint for SAP CDART Module. It is assumed that the installer has a working knowledge of SAP Basis, and has the appropriate levels of responsibilities to perform the tasks described. EMC iewpoint for SAP CDART Module Administration Manual v
Preface Related Documentation Be sure to review the EMC iewpoint for SAP Release Notes for the most up-to-date information on product features. The following list of related documents are available on the EMC iewpoint for SAP Documentation CD that was delivered with your EMC iewpoint SAP software CD. Both the release notes and documentation CD can be found at: http://powerlink.emc.com Introductory EMC iewpoint for SAP Documentation CD EMC iewpoint for SAP Release Notes Installation EMC iewpoint for SAP Modules Installation Manual EMC iewpoint for SAP Analyzer Plus Installation and User Manual EMC iewpoint for SAP BW Analyzer Installation Manual EMC iewpoint for SAP Construction and Maintenance Installation Manual EMC iewpoint for SAP Fiscal Year Reporter Module Installation and User Manual Miscellaneous EMC iewpoint for SAP Material Master Data, Batches, Special Stocks, and BOMs Module Modification Manual Administrative EMC iewpoint for SAP Controlling Line Items Module Administration Manual EMC iewpoint for SAP Financial Accounting and Material Documents Module Administration Manual EMC iewpoint for SAP Purchasing Module Administration Manual EMC iewpoint for SAP Sales and Distribution Module Administration Manual EMC iewpoint for SAP Production Orders Module Administration Manual EMC iewpoint for SAP Agency Business Module Administration Manual EMC iewpoint for SAP Construction and Maintenance Module Administration Manual vi EMC iewpoint for SAP CDART Module Administration Manual
Preface EMC iewpoint for SAP Costing-Based Profitability Analysis Module Administration Manual EMC iewpoint for SAP Master Data Changes Module Administration Manual EMC iewpoint for SAP Data Retention Tool Module Administration Manual EMC iewpoint for SAP Contract Account Documents Module Administration Manual EMC iewpoint for SAP HR Archiving Objects Module Administration Manual EMC iewpoint for SAP Material Ledger Documents Module Administration Manual EMC iewpoint for SAP Material Master Data, Batches, Special Stocks, and BOMs Module Administration Manual EMC iewpoint for SAP Controlling Orders Module Administration Manual EMC iewpoint for SAP Profit Center Line Items Module Administration Manual EMC iewpoint for SAP Plant Maintenance Module Administration Manual EMC iewpoint for SAP Production Orders Module Administration Manual EMC iewpoint for SAP Process Orders Module Administration Manual EMC iewpoint for SAP Project Systems Module Administration Manual EMC iewpoint for SAP Line Items Module Administration Manual EMC iewpoint for SAP Special Ledger Module Administration Manual EMC iewpoint for SAP Warehouse Management Module Administration Manual EMC iewpoint for SAP Custom Module Administration Manual User EMC iewpoint for SAP Analyzer Plus Installation and User Manual EMC iewpoint for SAP Analyzer Lite Installation and User Manual EMC iewpoint for SAP CDART Module Administration Manual vii
Preface EMC iewpoint for SAP Analyzer BW User Manual EMC iewpoint for SAP Controlling Line Items Module User Manual EMC iewpoint for SAP Financial Accounting and Material Documents Module User Manual EMC iewpoint for SAP Purchasing Module User Manual EMC iewpoint for SAP Sales and Distribution Module User Manual EMC iewpoint for SAP Production Orders Module User Manual EMC iewpoint for SAP Modules Utilities User Manual EMC iewpoint for SAP Agency Business Module User Manual EMC iewpoint for SAP Construction and Maintenance Module User Manual EMC iewpoint for SAP Costing-Based Profitability Analysis Module User Manual EMC iewpoint for SAP Master Data Changes Module User Manual EMC iewpoint for SAP Contract Account Documents Module User Manual EMC iewpoint for SAP HR Archiving Objects Module User Manual EMC iewpoint for SAP Material Ledger Documents Module User Manual EMC iewpoint for SAP Material Master Data, Batches, Special Stocks, and BOMs Module User Manual EMC iewpoint for SAP Controlling Orders Module User Manual EMC iewpoint for SAP Profit Center Line Items Module User Manual EMC iewpoint for SAP Plant Maintenance Module User Manual EMC iewpoint for SAP Production Orders Module User Manual EMC iewpoint for SAP Process Orders Module User Manual EMC iewpoint for SAP Project Systems Module User Manual EMC iewpoint for SAP Special Ledger Module User Manual EMC iewpoint for SAP Export Interface for Special Ledger Data User Manual EMC iewpoint for SAP Warehouse Management Module User Manual viii EMC iewpoint for SAP CDART Module Administration Manual
Preface EMC iewpoint for SAP Fiscal Year Reporter Module Installation and User Manual Conventions Used in This Guide EMC uses the following conventions for notes, cautions, warnings, and danger notices. Note: A note presents information that is important, but not hazard-related.! CAUTION A caution contains information essential to avoid data loss or damage to the system or equipment. The caution may apply to hardware or software. WARNING A warning contains information essential to avoid a hazard that can cause severe personal injury, death, or substantial property damage if you ignore the warning. DANGER A danger notice contains information essential to avoid a hazard that will cause severe personal injury, death, or substantial property damage if you ignore the message. Typographical Conventions EMC uses the following type style conventions in this guide: bold User actions (what the user clicks, presses, or selects) Interface elements (button names, dialog box names) Names of keys, commands, programs, scripts, applications, utilities, processes, notifications, system calls, services, applications, and utilities in text italic Book titles New terms in text Emphasis in text Courier Prompts System output Filenames Pathnames URLs Syntax when shown in command line or other examples EMC iewpoint for SAP CDART Module Administration Manual ix
Preface Courier, bold User entry Options in command-line syntax Courier italic Arguments in examples of command-line syntax ariables in examples of screen or file output ariables in pathnames <> Angle brackets for parameter values (variables) supplied by user. [] Square brackets for optional values. ertical bar symbol for alternate selections. The bar means or.... Ellipsis for nonessential information omitted from the example. Where to Get Help EMC support, product, and licensing information can be obtained as follows. Product information For documentation, release notes, software updates, or for information about EMC products, licensing, and service, go to the EMC Powerlink website (registration required) at: http://powerlink.emc.com Technical support For technical support, go to EMC WebSupport on Powerlink. To open a case on EMC WebSupport, you must be a WebSupport customer. Information about your site configuration and the circumstances under which the problem occurred is required. Your Comments Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Please send your opinion of this guide to: techpub_comments@emc.com x EMC iewpoint for SAP CDART Module Administration Manual
Invisible Body Tag 1 Introducing iewpoint for SAP CDART Module This chapter includes these topics: Introduction...1-2 iewpoint CDART Module...1-3 Scope...1-5 Customizing SAP DART...1-7 Introducing iewpoint for SAP CDART Module 1-1
Introducing iewpoint for SAP CDART Module Introduction The iewpoint modules are constructed in modular form and cover the application modules FI, SD, MM, CO, etc. with a special program package for exactly this application. You can easily see from the name which iewpoint module belongs to which SAP module: FI, SD, MM, CO, etc. All iewpoint modules have in common that they can be easily installed in the SAP R/3 system via the SAP transport utilities "tp" and "SAINT". Installation details of the iewpoint modules are in the EMC iewpoint for SAP Modules Installation Manual. This administration manual was written to make construction and administration of the iewpoint CDART Module as easy as possible. At first, data archiving with transaction SARA is discussed; the second topic is the iewpoint index construction from the SAP archive files. The EMC iewpoint for SAP Modules Utilities User Manual contains additional module information. 1-2 EMC iewpoint for SAP CDART Module Administration Manual
Introducing iewpoint for SAP CDART Module iewpoint CDART Module Due to the new GDPdU (principles of data access) the German tax authority can ask for a data extract on which the business records are stored for evaluation purposes. It is called the Z3 scenario in the SAP environment. The access type Z3 to current data and archive data represents the essential requirements of a tool which should extract tax relevant data to a data medium, store the data for the storage period and provide the data to the tax authority in case of a tax audit. The SAP Data Retention Tool (DART) can be considered as a solution attempt besides the tools SAP BW, SAP queries, ABAP reports in the SAP environment. Figure 1-1, Data flow SAP DART, shows the SAP DART data flow. Figure 1-1 Data flow SAP DART The DART can be used immediately as it is included in the SAP standard installation and no further software license fees are charged. DART enables the SAP customer to extract data in a predefined volume and store it on external data media or on a file server for the legal storage period. In case of an audit, views can be made to the data extracts which correspond to the requirements of the tax authority regarding the volume and period. Principally, the DART concept allows the possibility of providing archive data by reloading them into temporary tables (not in the original tables) for the extract generation. This is the reason why it is not recommended in practice. One reason is that the restorable tables iewpoint CDART Module 1-3
Introducing iewpoint for SAP CDART Module are incomplete. Another reason is that if data from posting periods far back is to be extracted huge sizes of data are created as nearly all archive files can contain documents concerned by the extract. This is why the SAP standard recommends to generate the extract stocks before starting the archiving procedure. Figure 1-2, Data flow iewpoint CDART, shows the iewpoint CDART data flow. Figure 1-2 Data flow iewpoint CDART iewpoint has extended the SAP-DART concept in a way that the SAP ADK files for DART extract runs are integrated to avoid a temporary reloading of archive data into the database. The data access can be executed via indices generated with the CDART Tool. Due to the integration of SAP ADK files the archive concept does not have to be changed at the iewpoint customers. Furthermore, the iewpoint concept has two essential advantages. On the one hand, the database can be kept performing by a consequent archiving and on the other hand, permanent storage capacity has not to be provided for the temporary storage of extract stocks until they will be used. The stocks can be created 'On Demand'. 1-4 EMC iewpoint for SAP CDART Module Administration Manual
Introducing iewpoint for SAP CDART Module Scope iewpoint supplements the SAP standard tool DART with its tool with a solution for archive data to be processed. The processing logic of the SAP standard remains untouched. Only the handling of the archive data is different for CDART. Table 1-1, CDART transaction data, gives an overview of the transaction data, which may be affected by archiving and which can be extracted from the archive using CDART. All other segments have a master record character (master data, transaction figures) or are not affected by archiving (e.g., Customizing data). This data is only extracted from the database. Table 1-1 CDART transaction data Original Segment structure DART Description ANEK TXW_AD_HD Asset document header ANEP TXW_AD_POS Asset document item AFRU TXW_AFRU Order confirmation AFC TXW_AFC Order operation ANLE TXW_ANLE Asset origin from line items ANLK TXW_ANLK Asset origin from cost element ANLP TXW_ANLP Asset periodic sizes ANEA TXW_ANEA Shared values of attachment document Items BRK TXW_BI_HD Billing document header BRP TXW_BI_POS Billing document item BSET TXW_BSET Document segment tax data KON TXW_CONDPR Pricing conditions (billing documents) COSP TXW_CO_COST_TOTALS Controlling object: total cost COSS TXW_CO_COST_TOTOLS Controlling object: total cost COBK TXW_CO_HD CO document header Scope 1-5
Introducing iewpoint for SAP CDART Module Table 1-1 CDART transaction data (continued) Original Segment structure DART Description COEP TXW_CO_POS CO document item COBK TXW_CO_SHD CO document header Secondary posting COEP TXW_CO_SPOS CO document item Secondary posting LIKP TXW_DL_HD Delivery document header LIPS TXW_DL_POS Delivery document item EIKP TXW_EIKP Export/Import header data EIPO TXW_EIPO Export/Import item data BKPF TXW_FI_HD FI document header BSIK TXW_FI_OP Open item FI BSIS TXW_FI_OP Open item FI BSID TXW_FI_OP Open item FI BSEG TXW_FI_POS FI document item MKPF TXW_MM_HD MM document header EKKO TXW_MM_POH MM order header EKPO TXW_MM_POP MM purchase order item MSEG TXW_MM_POS MM document item COFIS TXW_RC_POS FI/CO settlement item BAK TXW_SD_HD Sales document header BAP TXW_SD_POS Sales document item BPA TXW_SD_PRT SD Partner BKD TXW_BKD Sales document: sales data 1-6 EMC iewpoint for SAP CDART Module Administration Manual
Introducing iewpoint for SAP CDART Module Customizing SAP DART Furthermore, iewpoint describes the definitions which are necessary to use the iewpoint functionality concerning the archive data within the Data Retention Tool. The basic settings which have to be made for the DART tool remain untouched. Please refer to the general SAP DART documentation which is in directory \doku on your installation CD. In addition, we refer to the SAP OSS system which provides the latest notes on the DART tool under the component name CA-GTF-DRT. Menu navigation From release 4.6 the navigation has completely changed due to the implementation of the SAP Easy Access technique. This has also its effects on the transactions in the environment of the iewpoint modules. The delivery of the iewpoint CDART Module contains the area menu /PBS/DART. From this menu, you have to generate now an activity group (4.6B) respectively a role (from 4.6C) which then can be integrated into the user master. You can create an activity group/role directly from the Easy Access menu, as shown in Figure 1-3, Create a role. Figure 1-3 Create a role You are free to choose the name of the activity group/role; the name can also be within the iewpoint namespace (we recommend '/PBS/DART'). The iewpoint range menu for CDART is then transferred by pressing the function key 'Transfer menus from area menus' by indicating the corresponding iewpoint menu name '/PBS/DART'. During the transfer, the system query for the resolution of the range menu is to be answered with 'yes'. The role/activity group created this way can now be integrated in the corresponding user master (transaction SU01). Customizing SAP DART 1-7
Introducing iewpoint for SAP CDART Module Then the following Easy Access menu is displayed within the user menu, as shown in Figure 1-4, Enter the role /PBS/DART. Figure 1-4 Enter the role /PBS/DART The CDART menu, shown in Figure 1-5, Menu CDART, is essentially identical with the one of the SAP standard DART. In addition, there is the option 'Generate index archive data'. iewpoint transactions are only those which can be called via the menu either with 'Extract data', 'Generate index archive data' or 'Check FI control totals'. Selecting all other menu options, the SAP original programs are called. Figure 1-5 Menu CDART 1-8 EMC iewpoint for SAP CDART Module Administration Manual
Introducing iewpoint for SAP CDART Module Customer specific fields The list of fields which are considered for the extraction, can be extended by the customer. The additional fields will be appended in the corresponding segments of the Data Dictionary. The extraction programs in the SAP original and in the iewpoint CDART transfer the fields automatically in case they are fields with the type character. Other fields such as amounts are prepared according to the currency in the character format. This can be done by calling individual routines in special user exits. Should this case emerge, changes of the coding from the SAP original can be easily taken over into CDART. The function modules, which correspond to the user exits in the SAP standard are called names at PBS /PBS/DART_EXIT_SAPLTXW2_001 and /PBS/DART_EXIT_SAPLTXW2_002. In principle, all modifications executed in the SAP DART can be transferred to the iewpoint version. It is the customer s responsibility to transfer them. When implementing an update from iewpoint, the customer has to integrate the modifications again, if necessary. Data source In the menu generate index archive data you can set under the menu option customizing - data source if the archive data should be imported via the existing iewpoint Modules or via the archive indices which can be generated in the product CDART. If the corresponding entry does not exists in the table CDART is preferred as data source. For maintaining the table enter CSD, CFI and CMM per client and per module name and put a checkmark in the column iewpoint (= iewpoint Module) or DART (= index of the iewpoint CDART) as shown in Figure 1-6, Selection of the data source. Figure 1-6 Selection of the data source The indices of the other modules cannot be used by CDART. Customizing SAP DART 1-9
Introducing iewpoint for SAP CDART Module When using the indices of the modules you can only extract the document types listed in Table 1-2, CDART extracted document types, via CDART. Table 1-2 CDART extracted document types Module Module name Type CFI Financial accounting documents FI_DOCUMNT CFI Material documents MM_MATBEL CSD Sales documents SD_BAK CSD Deliveries R_LIKP CSD Billing documents SD_BRK CMM Orders MM_EKKO For the extract of other document types the indices must be built directly in the CDART. Note: For the extract of other document types ( as for example CO cost totals) indices are necessary which are not included in the modules. If you want to take into account also archive data during the extract of these document types the indices for all archiving objects must be built in the CDART. Archiving object /PBS/DART The indices are stored via the archiving object /PBS/DART. With transaction SARA a logical file name is assigned via Customizing > archiving object specific customizing. In the delivery of iewpoint the ARCHIE_DATA_FILE is set. This value can be customer-specifically changed. The path must be created in the file system and a read and write authorization must exist on the operating system level. 1-10 EMC iewpoint for SAP CDART Module Administration Manual
Invisible Body Tag 2 CDART Archiving This chapter includes these topics: Archiving data with iewpoint modules...2-2 Generate archive index...2-3 Archive tool...2-8 Deletion tool...2-9 CDART Archiving 2-1
CDART Archiving Archiving data with iewpoint modules To be able to consider the archive data performing within the extraction, the programs need the index information on the location of the archive data. The indices have to be constructed before executing the DART extraction. If the iewpoint Modules are not used, the indices which are necessary for the archive access are created with the index generation programs included in CDART. However, the indices are not identically with the indices of the modules. During the index generation applications should be made one after another. You only have to generate the indices of those modules which should also be extracted in the DART. The index generation can be started via an own menu, either from the menu option Utilities > Generate index archive data or directly with transaction /PBS/DART_SETUP. Within the menu the complete functionality is provided to index, activate and manage the archive data supported by iewpoint, as shown in Figure 2-1, Creation of the menu 'generate index archive data'. Figure 2-1 Creation of the menu generate index archive data Preparations All indices are stored in the archiving object /PBS/DART. The most important prerequisite is that the path assigned to this archiving object is stored in the file system and that there is enough disk space for the writing of the indices, as described in Archiving object /PBS/DART on page 1-10. Each indexed SAP ADK File requires an additional disk space of 5 percent of the space which is needed by a physic ADK file. 2-2 EMC iewpoint for SAP CDART Module Administration Manual
CDART Archiving Generate archive index ia the menu option Index > generate index you access on overview of the archiving objects which are to be processed. Traffic lights are used to show whether it is necessary to generate indices for each corresponding archiving object. A red traffic light shows that the archiving object has not been archived yet. It is not necessary to act. In case the traffic light is green all existing archive data was indexed, as shown in Figure 2-2, Construction of the menu 'Generate index archive date'. Figure 2-2 Construction of the menu Generate index archive date Indices must only be generated for objects which show a yellow traffic light. By clicking in the line you go to the index generation program and the missing generation can be made up. Figure 2-2, Construction of the menu 'Generate index archive date', shows an example of the menu. In this case no asset records have been have been archived, this is why a red traffic light is displayed. In the Generate archive index 2-3
CDART Archiving archiving object SD_BRK a yellow traffic light is displayed i.e. the index generation is incomplete. After accessing to the index generation program and after the regeneration this traffic light would also switch to green. The CDART extraction of the data should only be carried out when all traffic lights are green or red. In other cases the archive data which is not yet indicated cannot be taken into account during the extraction. For your information about the nature of the indices use the function key marked with i". ia a popup the indicated table fields of the archiving object are displayed. A general survey of the indices can be reached via transaction SE16 and via entering the name of the table /PBS/DART_INDEX. The table entries are not allowed to be changed without informing iewpoint. The index generation program can also be called via Utilities > generate index directly. The archiving object must in this case however be entered manually. A control via the display of the traffic lights about the completeness of the indices is missing. Figure 2-3, Delimitations for run 'Generate archive index', displays the selection screen. Figure 2-3 Delimitations for run Generate archive index 2-4 EMC iewpoint for SAP CDART Module Administration Manual
CDART Archiving In the following the delimitations and their effects are described. Select archive In this option you can select manually the archiving runs created with transaction SARA for SAP archive object FI_DOCUMNT. Clicking the button SAP archives all corresponding SAP archiving runs are displayed which were created from the date entered (from...). The requested SAP archiving runs can be selected now. The system checks if this run has not already been loaded into the iewpoint archive, and displays an error message if this is the case, as shown in Figure 2-4, Error messages. Figure 2-4 Error messages Select archive automatically If you want to process all documents from a certain date without having to select each SAP archive individually, please use this parameter. If there are SAP archives among them, which you have already archived during a previous run, they are not indexed to the iewpoint archive a second time. This function automates the load runs and can be scheduled as a background job by using a selection variant. Delete old run If you have already carried out several load runs and you want to delete one or more of these runs, you can press the button Run to display a list of the previous load runs. Now you can mark and delete the load runs you want. With the same method you can also delete complete SAP archiving runs from the iewpoint Module. Generate archive index 2-5
CDART Archiving All documents / process sequential number intervals In general, the button All documents... should be selected to ensure that all documents in the SAP archiving run are indexed. SAP release lower than 4.6: If the paging area in the system profile for the sorting of indexes is for example set too low, this leads to the termination SYSTEM_NO_MORE_PAGING. If this error occurs, the system parameter should be extended. From SAP release 4.6 a directory is assigned for sorting with the system parameter DIR_SORTTMP. This can be extended in a 32-bit operating system to avoid any sorting problems. It is the best for the processing time and the handling of jobs to define the system in a way that all documents of an archiving run can be processed during a run of the index generation program. If that is not possible, you can also execute several runs with a limited number of documents. In this case, select the second option Sequential number interval... and specify the documents to be processed in the two following fields. If you want to process 100,000 documents in each run, please enter in the first run from 1 to 100,000, in the second run from 100,001 to 200,000 etc. Note: The function that the program automatically recognizes if a selected SAP archive has already been processed is switched off if the interval delimitation is used. Neither is a check regarding an overlapping of intervals carried out. Merge In the CDART the index is kept in ADK files. This is why a new ADK number corresponds to each run of the index generation program. Figure 2-5 Above: Before the 1st run Below: Proposal for merge run In the beginning of the index compilation the button new archive is active. From the first run the proposal merge with archive" with the ADK run number of the previous run is displayed, as shown in Figure 2-5, Above: Before the 1st run Below: Proposal for merge 2-6 EMC iewpoint for SAP CDART Module Administration Manual
CDART Archiving run. The indices of the previous run are taken over into the succeeding run. This merge operation is described as merge. Long term problem The merger takes more time the more runs are executed. In order to reduce the runtimes activate the button 'new archive'. This action creates a second index stock, which is not merged with the first one. The reading routines of CDART can read several index stocks in parallel. We recommend to start a new index stock once a year for example. Postprocessing programs The index generation program starts 2 postprocessing programs if the corresponding buttons are active. ia 'create management indices' control records are written in the database which are necessary for the access to the generated indices. Using 'Delete previous run' the ADK File which does not contain current index sets any more is deleted. Both postprocessing programs can also be started manually via the menu bar 'Utilities'. Generate archive index 2-7
CDART Archiving Archive tool After the run of the index generation program with its post processing programs the generation is finished and the archive can be accessed. The data is then taken into account during the CDART extraction. To get a technical view on the indexes created, you can use the archive tool. It is also called via the menu bar Utilities. In the first line you can choose the index. ia F4 aid you get the description of the index number respectively you can choose the desired index from a list. As an alternative to the index list you can have the job logs displayed. In case of the index list you can start from upper/higher values by entering the key, as shown in Figure 2-6, Starting screen of the archive tool. Figure 2-6 Starting screen of the archive tool 2-8 EMC iewpoint for SAP CDART Module Administration Manual
CDART Archiving Deletion tool Using the option delete index in the menu bar Utilities you can access the deletion tool for the index records, as shown in Figure 2-7, Selection possibilities for the deletion tool. Figure 2-7 Selection possibilities for the deletion tool By selecting the first line all initial runs belonging to the index run which can be selected on the right via the button 'Run' are deleted. This option is activated automatically by the index generation program if the postprocessing program 'Delete initial run' is active. By selecting the second line an overview is displayed after the program has been started displaying all generated index runs. You can delete load runs from this list. This can be sensible when you wish to recreate the indices. Note: The index records are deleted physically. When deleting a run involuntarily all generation runs for the archiving object concerned must be repeated. Deletion tool 2-9
CDART Archiving 2-10 EMC iewpoint for SAP CDART Module Administration Manual
Invisible Body Tag 3 Data Extraction This chapter includes these topics: Disk space requirement...3-2 DART version...3-3 Further processing of the extract...3-4 Data Extraction 3-1
Data Extraction Disk space requirement The extraction program executes only one archive access for each document due to performance reasons. Tables which should be processed later according to the program logic of the SAP DART, have to be stored temporarily. For this purpose, the DART path is used in the extraction program. Therefore, during the creation of the path it has to be considered that the path has to be large enough. The temporary files are deleted at the end of the program. The disk space for the extract stock to be created can be determined via the iewpoint menu with Configuration? File size worksheet (for further information please refer to the SAP manual). As the disk space for the above mentioned temporary files has to be added during the extraction from the archive, we recommend that you take twice the value which was defined via the worksheet and to provide it for the generation of the extract stock. In general, the full capacity is not needed, it represents only an upper limit. 3-2 EMC iewpoint for SAP CDART Module Administration Manual
Data Extraction DART version The product CDART is supplied depending on the SAP release according to the latest version. The extracted structures correspond to the latest DART version. Among previous DART versions the CDART software cannot be run, as there might dictionary objects be missing and the programs are not compelled. The DART version can be determined via transaction SE11 and the display of the type group DART1. There the DART release is placed as a variable as a fixed value. Settings ia the menu option settings for data extracts technical settings on the one hand (for example file name, file size) are made and on the other hand it is determined which document types are taken into account during the extract. Only those document types are displayed for selection in the extract program in which the settings had been selected before. For a detailed description of the setting possibilities see SAP documentation. For CDART only the button data reloaded from archives in the register transaction data sub-option additional transaction data. This button must be active in order to take into account archive data. Only then you have to set the button extract archive data via iewpoint. Create an extract If all definitions have been made in the customizing of the DART, the extracts can be created via the menu option Utilities? Extract data. If the button Extract archive data via iewpoint is selected, the archive data is automatically selected via the index data of the corresponding iewpoint Module and transferred to the extract stock. DART version 3-3
Data Extraction Further processing of the extract The extracted data can be called with the DART extract browser of SAP which can be called, displayed and checked via the menu under Information system. iew data can be exported from the extracts which can be made available to an auditor for further evaluation (the so-called Z3 access). The auditor can process the exported data with special auditing software (e.g. Winidea) on his own PC. If you want to evaluate the CDART extracts outside the SAP system on your PC we refer to the iewpoint module IDA (independent DART access). IDA is not contained in the program package CDART. As further processing of the extracts is completely outside the iewpoint CDART Module we refer to the corresponding SAP documentation for further information, as shown in Figure 3-1, Selection screen for the data extract. Figure 3-1 Selection screen for the data extract 3-4 EMC iewpoint for SAP CDART Module Administration Manual