1e-DART26-NotPag

1

Data Retention ToolD A R T 2.6Data for Tax Audits

Peter SchiwekSolution Management Financials, SAP AG

[email protected]/15/2008

mailto:[email protected]

2

© SAP 2008 / DART 2.6 /Page 2

Topics

Evaluate View File

Data Detector / Extract Splitter

Customer Enhancements

Authorization Objects

Application Help

Enhancements in 2.6

The Concept

Extract Data

Source Extract Display / Print

Source Extract Export to View File

Checksums / Control Totals

Other Functions

3

© SAP 2008 / DART 2.6 /Page 3

DART 2.6See SAP Note1 173 540

DART 2.6See SAP Note1 173 540

DART2.6 Functional Enhancements in 2.6

Choice of extraction languageExtract balances of G/L account(GLT0 or FAGLFLEXT)Extract splitter logdisplay records from view file using ALVProcessing based solely onextract of metadata (TXW_META)Data formatting for view file in temporaryareas on the databaseReworking of segment structuresNew data segments for financial statementstructuresSetting segments to inactive (for U.S. template only)

Enhanced segment number rangesJob scheduling for archive exports/importsDART connection with Schedule Manager

4

© SAP 2008 / DART 2.6 /Page 4

DART2.6 Data Catalog of Enhancements to 2.6

Transaction KeyKTOSLFIGENTXW_BSET

Tax Accounts Determination“New Segment”FIDETXW_T030K

GEN

GEN

GEN

GEN

GEN

Set

Proportional cumulative revaluation on replacement valueAUFWV

Proportional revaluation for the year on replacement valueAUFWL

Proportional cumul. revaluation on ordinary depreciationAUFNV

Proportional revaluation of annual ordinary dep.AUFNLAMTXW_AS_PRV

Asset locationSTORTAMTXW_ANLZ

Cumulative revaluation on the replacement valueKAUFW

Cumulative revaluation of ordinary depreciationKAUFN

Proportional cumulative revaluation on replacement valueAUFWV

Planned revaluation on replacement valueAUFWP

Proportional revaluation for the year on replacement valueAUFWL

Proportional cum. revaluation on ordinary depreciationAUFNV

Planned revaluation of accumulated ordinary depreciationAUFNP

Proportional revaluation of annual ordinary dep.AUFNLAMTXW_ANLC

Investment support keyINVSLAMTXW_ANLB

Account Number of Vendor or CreditorLIFNR

Inventory numberINVNRAMTXW_ANLA

Appl. MeaningFieldSegment

5

© SAP 2008 / DART 2.6 /Page 5


Name of Person who Created the ObjectERNAM

Date on which the record was createdERDATFIGENTXW_BANK


Date on which the record was createdERDATSDGENTXW_BI_HD


Date on which the record was createdERDATCOGENTXW_PROJ

Date on which the record was createdERDATAMGENTXW_ANLA


DE

GEN

GEN

GEN

GEN

GEN

Set


Date on which the record was createdERDATSDTXW_VBKD


Date on which the record was createdERDATSDTXW_SD_HD


Date on which the record was createdERDATSDTXW_DL_HD


Date on which the record was createdAEDATMMTXW_MM_POH

Name of Person who Created the ObjectERNAMMMTXW_MAT

Date on which the record was createdERDATAMTXW_ANLB

Appl.


MeaningFieldSegment

6

© SAP 2008 / DART 2.6 /Page 6


Names for trip activity types2 FieldsTVDETXW_T706R

Names for Travel Expense Types42 FieldsTVDETXW_T706B5

DE

DE

DE

Set

To provide a clearer overview, only the segments and the number of new fields are listed here.

Names for enterprise-specific trip types3 FieldsTVTXW_T706X

Texts for Absence Types (PS Separation Allowance)4 FieldsTVTXW_T706T_ABWH

Names for statutory trip types14 FieldsTVTXW_T706G

Appl. MeaningFieldSegment

7

© SAP 2008 / DART 2.6 /Page 7

Legal Requirements Around the Globe

Germany: §§ 146, 147 of German Fiscal Code“GDPdU” enactment of 07/16/2001

Switzerland: Decree by theFederal Department of Finance (FDF)on electronically transferred dataand information of 01/30/2002(“ElDI-V”)

Austria: §§ 131 and 132 of theAustrian Fiscal Code (BAO)

France: Contrôle Fiscal desComptabilités Informatisées (CFCI)

UK: Application of specialcheck ABAPS by HM Customs & Excise

USA: IRS Revenue Procedure 98-25

Various other countries: . . .

Note also the amendment bill of EU directive 77/799/EWG by the European Council regardingthe mutual cooperation between the relevant authorities of the member states in the area ofdirect tax (in particular article 6a).

Concerning Austria, see also SAP Notes 450166 and 546853.

8

© SAP 2008 / DART 2.6 /Page 8

DART2.6 InternationalPortugal (Country Component XX-CSC-PT)

Requirements according to Portuguese law, Portaria nº 321-A/2007:

Portugal requires that files are in a legally prescribed XML formatSAF-T-PT (Standard Audit File – Tax – Portugal)

The SAP solution consists of an additional report for DART.

For details, see SAP Notes 1082823 and 1128119 (including further references).

9

© SAP 2008 / DART 2.6 /Page 9

DART2.6 InternationalPoland (Country Component XX-CSC-PL)

The requirements and the SAP solution are described in SAP Note 1071929.

The export is made using familiar DART tools (Viewer and Extract Splitter).

The following defined views are provided for the Viewer:PL_CUST Customer master dataPL_VEND Vendor master dataPL_FI_HD_F FI documentsPL_MM_HD_F MM documentsPL_SD_HD_F SD documentsPL_PKWiU Material classification data

Certain Customizing segments must be exported along with the Extract Splitter.

10

© SAP 2008 / DART 2.6 /Page 10

SAP Solution: Data Retention Tool

D A R TSource Extract

Transaction Data

Transaction Data

...

Master Data

Master Data

Meta Data

Consistent data, prepared to meet therequirements of a tax auditor

Assessment: “Tax-relevant data”

SAP Online DatabaseSAP Online Database

DARTView File (+ Meta File)

Data provided in- SAP

Audit Format -

Views

DART allows you to regularly extract and store data from ERP systems. DART provides toolsfor the flexible evaluation of the data stored. A typical function is the export of sequential files.

DART provides support for the export of data in SAP Audit Format. The DART functionsthereby appeal to internal and external auditors alike.

DART resulted from an initiative from the Americas SAP User Group (ASUG) to satisfy U.S.legal requirements (IRS Revenue Procedure 98-25), which correspond to the transfer to datamedium in Germany.As part of an ASUG working group, several SAP customers defined the basic types of data thatare relevant to taxation.

SAP put this into practice technically by creating the DART tool. The tool has been created sothat it can be enhanced.

In this way, DART interprets to some extent the concept “relevant to taxation.”

Every taxpayer must decide what additional data may be needed in a tax audit, and mustconfigure DART accordingly. SAP cannot give any guarantee that the standard version ofDART is sufficient for full compliance with the legal requirements.

11

© SAP 2008 / DART 2.6 /Page 11

Viewdatei

Metadaten

Customizing Data

Stammdaten

Transaction Data

Metadaten

Customizing Data

Stammdaten

Transaction Data

Meta Data

Customizing Data

Master Data

FTW1A – Extract Data (Source Extract)

Transaction Data

ERP Online DatabaseERP Online Database

FTWH – Data Extract Views

View File( + Meta File )

- SAP Audit Format -

FTWNDisplay View Log

ADKADKArchiving DataArchiving Data

1

2


DART2.6 The Process

Storage SystemFile System

The basic technical installation and configuration process can be completed in a matter ofdays. Sufficient disk space has to be provided, and a solution for long-term file storage must bedecided.

DART should also be integrated into a company's general archiving strategy.

12

© SAP 2008 / DART 2.6 /Page 12

Starting point:Financial Accounting

DART extracts documents from Financial Accounting with the associatedpreceding and follow-on documents

DART2.6 Audit Track – Outgoing from FI

Company codeFiscal yearPeriods

FI

SD

MM

. . .

AM

Valuation area

Documents fromMaterials Management

Documents fromSales and Distribution

Cost Accounting

Asset Accounting

CO

DART’s default settings allow you to select data for extraction from many ERP components.DART uses Financial Accounting (FI) documents as its starting point, allowing you to extractdata from the related documents .

The data extraction utility extracts data from the ERP applications you specify, and createssequential files containing transaction and master data from these applications .

13

© SAP 2008 / DART 2.6 /Page 13

DART2.6 Extraction (Example)

Valuation conditionsANEKAM documentheader

COFISFI/CO reconciliation posting

Asset value fields

Asset assignments

Cost center

Internal order

WBS element

Profit center

Asset

Customer

Supplier

Plant

ANEPAM document item

ANEAProportional values

BKPFFI document header

BSEGFI document item

PAYRFI payment transfer

EKKOMM purchasing document

EKPOPurchasing documentitem

COBKCO document header

COEPCO document item

LIKPSD deliveryheader

LIPSDelivery item

VBAKSD document

VBAPSales document item

VBPASales documentpartner Selection criteria

Transaction data

Master data

Key

VBRKSD billingheader

VBRPBilling item

KONVPricing conditions

GLT0G/L accountbalanceKNC1Customer balances

LFC1Supplier balances

Product

MKPFMM document header

MSEGMM document item

Address

Company code,

years, periods

Valuation area

14

© SAP 2008 / DART 2.6 /Page 14

DART2.6 Data Scope = Country-Specific

5 segments138 fields

170 segments2,132 fields



US DE

All

ExtendedData Volumeas of 2.6

Up to now, data scopes for the United States and Germany have been defined as "US" and"DE" respectively.

Multinational companies that needed to cover requirements from both countries, needed tocreate the data extract twice. With the new data scope "all", the system extracts all segmentsattached to DART.

The different combination of check-relevant data according to country requirements must becarried out in the view.

You can only select the new data scope in the company-code-specific Customizing of theTXW_C_BUKRS maintenance view. Existing settings are not affected and data is still extracteddepending on the country code of the company code.

15

© SAP 2008 / DART 2.6 /Page 15

DART2.6 AccessingSAP Menu / Trans. FTW0

Now additionalposition in the

menu.See SAP Note

1262693

Accessing DARTFrom the SAP Easy Access menu choose:Tools AdministrationAdministration Data Retention Tool

orFrom the ERP SAP Easy Access menu, choose:Accounting Financial Accounting General LedgerPeriodic Processing Data Retention Tool(Refer to SAP Note 1262693)

orEnter program name FTW0 and choose Enter.

16

© SAP 2008 / DART 2.6 /Page 16

DART2.6 OverviewSegment Catalog

SAP Note582583

contains thesegment catalog

for 2.6

The segment catalog includes the standard and the customer-specific segments including thereference tables and the application allocation in DART.

It is possible to display the field catalog either independently for all segments or by branchingfrom the segment catalog. You can branch from the segment catalog directly to the ABAP DataDictionary by double-clicking the segment name or reference table. The field catalog alsodisplays fields of the standard segments defined individually for the customer. If any are found,they are selected in the Included column.

In the field catalog, the program displays those segment fields for which the reference field isnot filled. This means that there is no 1:1 relationship between the database field and thesegment field. This field is therefore filled by a special DART logic.

Example:In segment TXW_FI_POS, the field catalog does not display any reference for the Month field.The reason for this is that the Month field in the database is not a field in reference table BSEG.Instead, it is a field in table BKPF (segment TXW_FI_HD). To improve the readability of thedata in segment TXW_FI_POS, the Month field has been added to this segment and is alsofilled by the DART logic during the extraction run.

In the header, both catalogs include the version number of the DART version installed in thesystem.

17

© SAP 2008 / DART 2.6 /Page 17

DART2.6 OverviewField Catalog

SAP Note582583

contains thefield catalog for

2.6

The segment catalog includes the standard and the customer-specific segments including thereference tables and the application allocation in DART.

It is possible to display the field catalog either independently for all segments or by branchingfrom the segment catalog. You can branch from the segment catalog directly to the ABAP DataDictionary by double-clicking the segment name or reference table. The field catalog alsodisplays fields of the standard segments defined individually for the customer. If any are found,they are selected in the Included column.

In the field catalog, the program displays those segment fields for which the reference field isnot filled. This means that there is no 1:1 relationship between the database field and thesegment field. This field is therefore filled by a special DART logic.

Example:In segment TXW_FI_POS, the field catalog does not display any reference for the Month field.The reason for this is that the Month field in the database is not a field in reference table BSEG.Instead, it is a field in table BKPF (segment TXW_FI_HD). To improve the readability of thedata in segment TXW_FI_POS, the Month field has been added to this segment and is alsofilled by the DART logic during the extraction run.

In the header, both catalogs include the version number of the DART version installed in thesystem.

18

© SAP 2008 / DART 2.6 /Page 18

DART2.6 Extract Data

Viewdatei

Metadaten

Customizing Data

Stammdaten

Transaction Data

Metadaten

Customizing Data

Stammdaten

Transaction Data

Meta Data

Customizing Data

Master Data


Transaction Data






1

2




19

© SAP 2008 / DART 2.6 /Page 19

TableAfter Deletion

TableBefore Deletion

DART2.6 Delete Index FieldsTable: TXW_C_STRC, KEY2 - KEY5

RTXWDELI

Before

After

In table TXW_C_STRC, index key fields KEY2 - KEY5 might still be filled with values. If that isthe case, that would result in unnecessary structuring and storing of index records during dataselection (FTW1A).

Index records are no longer needed as of DART 2.4.

The new report, RTXWDELI, deletes the key fields KEY2 - KEY5 in table TXW_C_STRC.

You have to call this report manually.

20

© SAP 2008 / DART 2.6 /Page 20

DART2.6 Setting Segments to InactiveTable: V_TXW_C_SKIP_SEG

FTW1A – Extract Data


SKIP_SEG?

yes

no

New Functionin 2.6

Using table V_TXW_C_SKIP_SEGyou can exclude segments in theDART segment catalog fromprocessing (extraction).

Currently this option is availableonly for the US template.

21

© SAP 2008 / DART 2.6 /Page 21

DART2.6 ConfigurationFile Directories

A directory set is a group of one or more directories used for storing all the sequential filescreated for a single data extract. A directory set definition lists the possible data volumes for adata extract and maps those data volumes to physical directories.

22

© SAP 2008 / DART 2.6 /Page 22

DART2.6 ConfigurationData Extraction

F 1

Set the indicator for every transaction data source you wish to make available to the user. Forexample, if you set the indicator for Material documents (MM), then the Extract data screendisplays a Material documents (MM) indicator, allowing the user to include MM transaction datain the extraction.

23

© SAP 2008 / DART 2.6 /Page 23

DART2.6 ConfigurationData Extraction

F 1

Master dataFlag the Standard cost center hierarchies to include standard cost center hierarchies forselected controlling areas to be extracted. These can only be viewed with the Data extractbrowser.Likewise if you set the indicator for Standard profit center hierarchies, you can extract profitcenter hierarchies for selected controlling areas that can only be viewed with the Data extractbrowser.Setting the Joint Venture Accounting master data indicator enables the user to select masterdata from the Joint Venture Accounting application in the Change Settings for Data Extractionscreen. This field is displayed to the user as set by default.

Other dataSetting the Extract customer-defined data sources indicator includes this field in the Extract datascreen. It is displayed to the user as set by default. Setting this indicator allows the user to extractthe data as defined by the segments that you or someone else have added to DART.

24

© SAP 2008 / DART 2.6 /Page 24

DART2.6 Extract DataSelection

DARTSource Extract

New Function in2.6

The data extraction utility extracts data from the ERP applications you specify, and createssequential files containing transaction and master data from these applications.

DART’s default settings allow you to select data for extraction from many ERP components.DART uses Financial Accounting (FI) documents as its starting point, allowing you to extract datafrom related documents.

The data extraction utility:Converts numeric fields to charactersCan compress data when creating the sequential file by ignoring trailing blanks (blanks at theend of the data in a field) in the source dataCan include checksums for each of the segments included in the extractThese checksums allow you to verify the integrity of the sequential file.Can include control totals for data extracted from FI or other applicationsThese control total values allow you to verify that the correct data had been extracted, or thatdata had not changed in the database since an extraction.Extracts descriptive metadata in the requested language (TXW_META).

25

© SAP 2008 / DART 2.6 /Page 25

DART2.6 Extract DataLogs

DARTSource Extract

The system extracts data into one or more sequential files. If the data extracted exceeds thatwhich can fit into the maximum file size specified in configuration, then the system createsseveral sequential files. It displays information on the resulting sequential file(s), and statisticalinformation on the segments in it.

26

© SAP 2008 / DART 2.6 /Page 26


DARTSource Extract

27

© SAP 2008 / DART 2.6 /Page 27


DARTSource Extract

28

© SAP 2008 / DART 2.6 /Page 28

DART2.6 Source Extract Analysis Display / print

Viewdatei

Metadaten

Customizing Data

Stammdaten

Transaction Data

Metadaten

Customizing Data

Stammdaten

Transaction Data

Meta Data

Customizing Data

Master Data


Transaction Data






1

2




29

© SAP 2008 / DART 2.6 /Page 29

DART2.6 Source Extract AnalysisData Extract Log -Browser

DARTSource Extract

TXW_FI_HD + TXW_META

Although the data extracts containing the extracted data are in a text format, they are notintended for direct reading with a text editor or a spreadsheet program. We recommend thatyou use the Extract Browser tool to view data in the extract.

The data is formatted for ALV display in the data extract browser solely using the metadatabelonging to this source extract.

The contents of currency fields are always displayed with two decimal places.

30

© SAP 2008 / DART 2.6 /Page 30

DART2.6 Source Extract AnalysisBrowser

DARTSource Extract

TXW_META

TXW_FI_HD + TXW_META

NewFunctions

in 2.6

Although the data extracts containing the extracted data are in a text format, they are notintended for direct reading with a text editor or a spreadsheet program. We recommend thatyou use the Extract Browser tool to view data in the extract.



As of DART 2.6, the following DART functions are now included in transaction FTWF – DataExtract Browser:- Delete extract- Export to archive- Import from archiveAs a result, these functions are available using the Schedule Manager.

Errors can occur when you export DART files to the archive or import DART files from thearchive. If an error occurs during background processing, you can influence the systembehavior using the parameters- New Export/Import of Files- Partial Export/Import of FilesAlso see the field help (F1 help).

31

© SAP 2008 / DART 2.6 /Page 31

DART2.6 Source Extract AnalysisBrowser

The display for the extract contents has been switched to user-friendly ALV technology.

From the browser, the data for an extract can be displayed in a prepared list (for example, theTXW_FI_HD segment). You can use the list to sort, group and total data, and it thereforeresults in a significant improvement compared to the previous file list.

32

© SAP 2008 / DART 2.6 /Page 32

DART2.6 View Definition I

DART enables you to select and group data from your financial records into views. Viewscombine selected fields from multiple segments in an extract. Views can be designed to meetparticular IDRs. With views you can query multiple extracts at a time.

33

© SAP 2008 / DART 2.6 /Page 33

DART2.6 View Definition II

Joins can also bemaintained

manually, wherenecessary

> 1200 join conditionscan be called

(table TXW_C_RELA )

In a relational database system, a join is a combination of data records from two or moretables. In a similar fashion, in DART, a join refers to combining data records from two or moresegments in an extract.

Table TXW_C_RELA is used to deliver the options for linking between DART segments. Youcan use transaction FTWYR to modify segment relationships later.

This dependency is now available as entry support for DART users with the definition of viewsin transaction FTWY. As a consequence, the user is no longer obliged to know therelationships, but is now able to select them from the existing inventory.

You can use the new function in transaction FTWY by choosing the pushbuttons Relations andSelect Join Conditions.

It is still possible to maintain view definitions manually in the previous form.

34

© SAP 2008 / DART 2.6 /Page 34

DART2.6 View Definition III

Specifying the Fields to Include in the View ReportYou can add multiple fields from the same segment at the same time, by choosing SelectFields, selecting the segment name, and then checking the box next to the fields you wish toinclude in the report.

Specifying Additional Selection Conditions for Filtering RecordsYou may specify additional selection conditions to filter the data included in the view report. Forexample, you may wish to retrieve only documents of a certain document type.

35

© SAP 2008 / DART 2.6 /Page 35

DART2.6 View Definition IV

The Activate View function is used to generate the query program for this view.

Views are generated based on the ABAP Dictionary (DDIC) in the current ERP system.Therefore a view can only reflect fields that are known to the ABAP Dictionary. The currentlevel of the ABAP Dictionary also determines the format of the fields.

36

© SAP 2008 / DART 2.6 /Page 36

DART2.6 Maintain Segment Relationships

Definition of relationships betweenTXW_FI_POS FI Document ItemTXW_FI_HD FI Document Header

There is a match when the following field contents are identical:MANDT ClientBUKRS Company CodeBELNR Document NumberGJAHR Fiscal Year

Previously, it was only possible to make entries or changes to relationships (tableTXW_C_RELA) using the general table maintenance transactions (SM30-31).

Now transaction FTWYR – Maintain Segment Relationships makes it possible to enter orchange data only in table TXW_C_RELA, but with the same range of functions.Using authorization object S_TCODE – Transaction Code Check at Transaction Start, youcan separately control maintenance of relationships.

37

© SAP 2008 / DART 2.6 /Page 37

DART2.6 Source ExtractDisplay / Print

DARTSource Extract

This utility executes the report defined by the view, displaying data from the fields andsegments defined by the view.

38

© SAP 2008 / DART 2.6 /Page 38

DART2.6 Source ExtractDisplay / Print

The display has been switched to user-friendly ALV technology.

39

© SAP 2008 / DART 2.6 /Page 39

DART2.6 Source ExtractChange Layout

After a view is defined, you can influence the list layout that is determined by the viewdefinition. To do so, in transaction FTWH, choose the Change Layout function the first time theview is displayed using ALV.

You determine the layout type using the Save Layout function:- User-specific yes/no As default (initial variant) yes/no- User-independent yes/no As default (initial variant) yes/no

When you analyze DART extract data using transaction FTWH, after you select the view, theLayout Name field appears on the selection screen.Using the view-related layouts that you defined in advance, you can determine the appearanceof the list screen in which the resulting DART data is displayed.

If a layout (user-independent or user-specific) is classified as an initial variant, then it acts as adefault value.

Layouts have an effect only when you choose Display/print. If you choose the export function,then the data volume is determined by the view definition alone.

40

© SAP 2008 / DART 2.6 /Page 40

DART2.6 Source ExtractLayout Selection

41

© SAP 2008 / DART 2.6 /Page 41

DART2.6 Source ExtractTotaling

Based on your specifications for totals and groups in the view definition (FTWY), totals rowsare displayed in the list when you choose output type Display/print.

Note:When ALV processing is used:If totals are calculated and grouped together in a view, certain ALV functions provide incorrectresults,such as, calculation of totals, mean values, or subtotals.

Note:When exporting:The system includes the totals records in the exported data.

If you want to use the export functions to transfer DART data to ACL/IDEA for furtherprocessing, do not specify totaling and grouping in the views (FTWY) you use for this.

42

© SAP 2008 / DART 2.6 /Page 42

DART2.6 Source ExtractTotals Only

When you execute a view (FTWH), if the Totals Only indicator is set, then no single records areoutput.

This indicator is set automatically if the Limit view output to totals only indicator was set in theview definition (FTWY).You cannot change this decision when executing the view (FTWH).

43

© SAP 2008 / DART 2.6 /Page 43

DART2.6 Source ExtractSelection Conditions

When you define views (FTWY), you can already enter selection criteria for the later dataselection.

Each field of the segments processed in the view can be designated as a selection field.The fields you specify for a selection do not have to be contained in the list layout as viewfields.

A field that was specified as a selection condition in the view definition can also (in parallel) bespecified as an input field on the selection screen of the view query.When the view is executed (FTWH), values entered directly on the selection screen are givenprecedence.

44

© SAP 2008 / DART 2.6 /Page 44

DART2.6 Source ExtractSeveral Extracts

DARTSource Extract

Using multiple selection for the Source Extract field, you can analyze multiple data extracts inone view.As an example, you could create an annual report out of four quarterly extracts.

The specifications regarding segments and fields in the view ensure that only data with thesame structure is included in the analysis.

Note: For segment structures with cumulative fields (such as, balance carryforward), theanalysis includes only the chronologically most recent value for the field.

45

© SAP 2008 / DART 2.6 /Page 45

DART2.6 Use Additional Source Extracts I

DARTSource Extract

Example

Transaction DataExtract created quarterly

Master Data/TablesExtract created once at endof fiscal year

If you need to create the DART source extract in the middle of the year, it may not makebusiness sense to include the respective explanatory master data and tables in the extraction.Exclude the master data from program runs that are performed mid-year.

At the end of the year, create an extract set in a separate run, containing just the master data(here, 1000_2006_Tables).

46

© SAP 2008 / DART 2.6 /Page 46

DART2.6 Use Additional Source Extracts II

Create a view containing the transaction data and master data.For example:

TXW_FI_HD FI Document HeaderTXW_FI_POS FI Document ItemTXW_DOCTYP Document TypeTXW_POSTKY Posting Key

47

© SAP 2008 / DART 2.6 /Page 47

DART2.6 Use Additional Source Extracts III

DARTTransaction Data

DARTMaster Data

In the analysis of the transaction data, include the extract set with the master data in theassignment.

48

© SAP 2008 / DART 2.6 /Page 48

DART2.6 Use Additional Source Extracts IV

The list result shows the actual fields of the extract, complete with an explanation:- Document Type, Description- Posting Key, Name of posting key

49

© SAP 2008 / DART 2.6 /Page 49

DART2.6 Source Extract Export to View file

Viewdatei

Metadaten

Customizing Data

Stammdaten

Transaction Data

Metadaten

Customizing Data

Stammdaten

Transaction Data

Meta Data

Customizing Data

Master Data


Transaction Data






1

2




50

© SAP 2008 / DART 2.6 /Page 50

DART2.6 Source ExtractExport to View File

DARTView file ( + Meta File )

DARTSource Extract

Functionimproved in

2.6

The data specified in a view is read from the source extract and stored in a view data area forfuture reports.

For each view file created in this way, the system generates a metadata file for later analysis bymeans of ALV display (…_MT). These MT files are internal SAP data areas and cannot beexported.The metadata for the SAP Audit Format are stored in the first 8 records of the view file.

As of DART 2.6, the data for a view file is formatted and prepared in temporary areas on thedatabase.In contrast to the previous method (data combined and prepared in main memory, max. 2 – 8GB), you can now process large data volumes without difficulty.

51

© SAP 2008 / DART 2.6 /Page 51

DART2.6 Source ExtractAppend to File

DARTSource Extract

View File2006_Q1

View File2006_Q2

Using the Append to file function, you can merge DART data from different source extracts intoone view file.This can be useful, for example, if the source extracts are created quarterly, but you want theview analysis to be cumulative for the year.In that case, you just need to have the system read the source extract for each new quarterand append it to the existing view file.

When the Append to file function is used, the program internally compares the existingstructure to the structure being appended. The function is not performed unless the twostructures are the same.

Each export is documented in a separate row in the view log. However, the report itselfnormally relates to the complete dataset.

52

© SAP 2008 / DART 2.6 /Page 52

DART2.6 Evaluate View File

Viewdatei

Metadaten

Customizing Data

Stammdaten

Transaction Data

Metadaten

Customizing Data

Stammdaten

Transaction Data

Meta Data

Customizing Data

Master Data


Transaction Data






1

2




53

© SAP 2008 / DART 2.6 /Page 53

DART2.6 Evaluate View FileView Log


This utility allows you to obtain a log of DART jobs that were executed on your system, and inwhich files they were created.

54

© SAP 2008 / DART 2.6 /Page 54

DART2.6 Evaluate View FileView Log . . .


View data that you created once can be used in analyses as often as you wish.

ALV reportingUsing ALV functions, you can filter, sort and group data. The use of totals and subtotalsprovides a quick overview.

Display fileThis method of display shows the raw data.

Export to local fileWhen you use this function, the view data is copied from the file system of the applicationsystem to the local presentation server (PC).The SAP Audit data format (industry standard) enables you to easily continue processing datausing common auditing tools, such as ACL or IDEA.

The view data can be transferred to an external storage system using SAP ArchiveLink.Note: After this transfer, the metadata description is no longer available to provide a user-friendly display.

55

© SAP 2008 / DART 2.6 /Page 55

3rd Party Audit SoftwareA C L (Audit Command Language)

“SAP Audit Format” for the transfer to data medium

In collaboration with the auditing software providers

A C L Services Ltd., Vancouver BC, Canada, http://www.acl.com

SAP developed the data description standard“SAP Audit Format”.

Since 1998, this function is delivered with the SAP“Audit Information System“ ( A I S ).DART supports the “SAP Audit Format” since 2001.

3rd Party Audit SoftwareDigitalTax Audit

3rd Party Audit Software

A C L

I D E A

Data provided in- SAP Audit Format -

DARTView File

A C L (Audit Command Language)

http://www.acl.com

56

© SAP 2008 / DART 2.6 /Page 56

3rd Party Audit SoftwareA C L (Audit Command Language)

SAP Audit Format enables very easy transfer to evaluation programs such as ACL and IDEA.

At the request of external auditors, the SAP Audit Format was agreed upon a few years agoby SAP and the manufacturers of ACL and IDEA to enable data transfer at the touch of abutton.

The views also have a descriptive eight-line intention with field and format descriptions that canbe interpreted by ACL and IDEA.

57

© SAP 2008 / DART 2.6 /Page 57

3rd Party Audit SoftwareI D E A (Interactive Data Extraction and Analysis)

“SAP Audit Format” for the transfer to data medium

In collaboration with the auditing software providers

I D E A, CaseWare Internat. Inc. Toronto, http://www.caseware.com

SAP developed the data description standard“SAP Audit Format”.

Since 1998, this function is delivered with the SAP“Audit Information System“ ( A I S ).DART supports the “SAP Audit Format” since 2001.

3rd Party Audit SoftwareDigitalTax Audit

3rd Party Audit Software

A C L

I D E A

DARTView File

Data provided in- SAP Audit Format -

I D E A (Interactive Data Extraction and Analysis)

http://www.caseware.com

58

© SAP 2008 / DART 2.6 /Page 58

3rd Party Audit SoftwareI D E A (Interactive Data Extraction and Analysis)

SAP Audit Format enables very easy transfer to evaluation programs such as ACL and IDEA.

At the request of external auditors, the SAP Audit Format was agreed upon a few years agoby SAP and the manufacturers of ACL and IDEA to enable data transfer at the touch of abutton.

The views also have a descriptive eight-line intention with field and format descriptions that canbe interpreted by ACL and IDEA.

59

© SAP 2008 / DART 2.6 /Page 59

SAP Audit FormatAs Easy As It Gets …

3rd party audit software3rd

party

Once the data has been stored in a local directory on the internal auditor's PC, it can easily beprocessed further using auditing software.

ACLThe wizard for data transfers proposes the Private SAP Data Format for automatic datatransfers.

IDEAThe wizard for data transfers proposes the SAP/AIS Import File format for automatic datatransfers.

Microsoft ExcelWhen converting the DART data, Excel interprets almost all data fields correctly. The first eightlines can be omitted in the import.

Other Auditing ToolsThe user is free to choose the data structure for the data records generated by DART. Thisenables every software provider to make its software compatible with the SAP Audit Format.

60

© SAP 2008 / DART 2.6 /Page 60

DART2.6 Source ExtractData Detector

DART Source Extract DART View file

When you have defined a special view for the data transfer, it is often useful to provide moresegments as explanations of this view to the tax auditor.

Example :If you defined a view using a document header and items,

- TXW_FI_HD Document header- TXW_FI_POS Document items

the Asset master data and the Company code master, for example, are explanatory segments.- TXW_ANLA Asset master data- TXW_COMPC Company code master- etc.

The associated data detector outputs the data in SAP Audit Format without requiring you tocreate a special view for the extract.

The environment for a view is determined on the basis of the details about possiblerelationships stored in table TXW_C_RELA.


61

© SAP 2008 / DART 2.6 /Page 61

DART2.6 Source ExtractData Detector


The log display can be used to view the result of the program run Detector for Associated Data.Data callup is possible at any time.

62

© SAP 2008 / DART 2.6 /Page 62

DART2.6 Source ExtractExtract Splitter

DART Source Extract DART View File

In The extract splitter is an independent program that is provided for transferring data in asimilar way to view creation for data transfer. It automatically generates a view file in the SAP-AIS format for transferring data for each segment contained in the DART extract.

No special definition of DART views is required for this. Consequently, this program simplifiesthe user’s task if the tax auditor wants to have nearly all segments transferred.

It is possible to deselect individual segments from the extract on the selection screen.

You can only access a DART extract using an SAP System. (For more detailed information,see SAP Note 522167).

By placing the extract contents in view files using SAP Audit Format, however, you can usethird-party programs (such as Notepad, Excel, ACL, IDEA) to access the data for analysis atany time.


63

© SAP 2008 / DART 2.6 /Page 63


DART2.6 Source ExtractExtract Splitter

NewFunctionin 2.6

The log display can be used to view the result of the program run Data Extract Splitter. Datacallup is possible at any time.



64

© SAP 2008 / DART 2.6 /Page 64

DART2.6 Checksums / Control Totals


FTW1A – Extract data

FTWE / FTWE1Verify FI control totals /Verify all FI control totals

FTWDVerify data checksums

FTWF - Data extract browser

Control Totals (TXW_CHKSUM)

Calculate data checksums

DART offers three options during creating, managing, and using checksums and control totals:

Data Checksums (determine data integrity)During the creation of the extract (FTW1A), the Calculate Data Checksums indicator must be set.For each extracted segment, the system calculates a checksum by adding all bytes. These values are transferredas a technical segment (TXW_DIRSG2) to the DART source extract.The analysis program FTWD determines these checksums once again at runtime. The system compares thesevalues with the checksums created during the creation of the extract and displays the results in a log.

Control Totals (content check)A key figure field can be specified for each data segment (FTWQ). This field must be a numeric field.During the creation of the extract (FTW1A), the system adds the values for each key figure field and writes the totalto the segment TXW_CHKSUM.The control totals are displayed in the log of the extract creation (FTW1A).You can call these control totals separately by choosing Data Extract Browser Goto Control Totals(transaction FTWF).

FI Control Totals (reconciliation)Using programmed logic (FTWE/FTWE1), the system compares accounting values from the DART source extractwith the online data. The log displays the following values for each company code and fiscal year:- Posting period- Account type (A/D/K/S)- FI document totals- G/L account balancesThe reconciliation is without errors, if both of the following are true:

The document amounts agree with the G/L account balancesThe totals from the DART source extract agree with the totals from the online dataset

65

© SAP 2008 / DART 2.6 /Page 65

FTWLDisplay

extract log

S_P6D_40000026Associated

data detector

TXW_META

View_META

DART2.6 Metadata

DARTSource Extract

FTWYDefine data

extract viewsFTWH

Data extractviews

SAPSAPDDICDDIC

ViewCatalog

S_P6D_40000027Data extract

splitter

FTWFData extract

browser

DART View file

FTWNDisplay

view logFunction

Improved in2.6

FTW1A – Extract DataWhen a DART source extract is created, the system stores descriptive data (metadata) for all structuresand fields of this extract in the DART segment TXW_META.The metadata is formatted based on the ABAP Dictionary in the system at the time of the extraction.

FTWY – Define Data Extract ViewsThe view is defined independently of an extract. The system uses the ABAP Dictionary (DDIC) informationof an analysis system as the basis for the definition.

The following options are available for analyzing a DART source extract:o FTWH – Data Extract Views

You perform the analysis using a predefined view. If the source extract was generated in an SAPsystem other than the analysis system, keep in mind the following:

- In the analysis system, both the release level of the system and the DART release level must be thesame as or higher than the release level in the system where the extract was created.

- Customer-defined segments and/or fields must be known in the analysis system. (If necessary, enterthem in the ABAP Dictionary beforehand). See also SAP Note 407847.

o S_P6D_40000027 – Data Extract SplitterS_P6D_40000026 – Associated Data DetectorFTWF – Data Extract -BrowserFTWL – Display Data Extract LogFor storing or displaying data, these programs use only the metadata from the DART source extract.

FTWN – Display View LogWhen a view file is stored, the descriptive data for this file is formatted and then stored in a parallel file(…_MT).For later evaluations using transaction FTWN, only this metadata is then needed.

66

© SAP 2008 / DART 2.6 /Page 66

DART2.6 ArchiveLink

Viewdatei

Metadaten

Customizing Data

Stammdaten

Transaction Data

Metadaten

Customizing Data

Stammdaten

Transaction Data

Meta Data

Customizing Data

Master Data

Transaction Data

Storage-SystemFile System


FunctionImproved in

2.6

FTWF - Data extract browserFTWL - Display extract logFTWN - Display view logS_P6D_40000025

- Display extract splitter log

NewFunctionin 2.6

ArchiveLink is the interface from an SAP system to external archiving systems (such as, opticalstorage systems).

DART supports this interface which enables you to archive data extracts and data view files(inlcuding metadata).

You can easily export these files to an archive or import them from an archive.

67

© SAP 2008 / DART 2.6 /Page 67

DART2.6 Connection to Schedule Manager

Data extract browserFTWFRTXWQU01

Verify all FI control totalsFTWE1RTXWCHK4

Verify extract consistencyRTXWCHK3

Verify data checksumsFTWDRTXWCHK2

Verify FI control totalsFTWERTXWCHK11

Verify FI control totalsRTXWCHK10

Extract dataFTW1ARTXWCF02

Table: SCMAPROGRAMS Schedule ManagerIndex of Registered SAP Programs

NewFunctionin 2.6

Schedule Manager

By providing a high degree of automation, Schedule Manager simplifies the processes ofdefining, scheduling, executing, and monitoring periodically recurring tasks.

If you have a large number of organizational units (such as company codes), it is beneficial toautomate your DART process using the Schedule Manager.

The following programs are linked with the Schedule Manager starting from DART Version 2.6:FTW1A Extract DataFTWF Data Extract BrowserFTWE Verify FI Control TotalsFTWE1 Verify All FI Control TotalsFTWD Verify Checksums

See also:Transaction SCMA, Help -> Application Help -> Schedule Manager

68

© SAP 2008 / DART 2.6 /Page 68

FI – DocumentsBKPFBKPF Doc. headerDoc. header

recordsrecords

BSEGBSEG Line itemsLine items_ __ _ independent of ledgerindependent of ledger

BSEG_ADDBSEG_ADD Line itemsLine itemsL0L0 Leading LedgerLeading LedgerL1L1 Subledger 1Subledger 1LnLn Subledger nSubledger n

DART2.6 Extract DataFI Documents Related to Ledgers

ERP Online DatabaseERP Online DatabaseFI DocumentsFI Documents

DARTSource Extract

Customizing

?

( Ledger L1 )BKPF TXW_FI_HDBSEG TXW_FI_POSBSEG_ADD TXW_FI_POS

FAGLFLEXA TXW_FI_NGL_POS

BKPF TXW_FI_HDBSEG TXW_FI_POS

yes no

FTW1A – Extract Data

FAGLFLEXAFAGLFLEXA Line itemsLine itemsL0L0 Leading LedgerLeading LedgerL1L1 Subledger 1Subledger 1LnLn Subledger nSubledger n

Entry View

General Ledger View

New General Ledger Accounting, Parallel Accounting

New General Ledger Accounting (FI-GL (new)) allows you to perform parallel accounting bymanaging several parallel ledgers for different accounting principles. During posting, you canhave data posted to all ledgers, to a specified selection of ledgers, or to a single ledger.

Documents that affect all ledgers are stored in table BSEG.Documents that affect only a particular ledger are stored in table BSEG_ADD.

FI-GL (new) thereby makes it possible to reflect tax valuation in any given ledger. You canspecify the ledger containing the tax data in the data extraction (transaction FTW1A). If you donot enter a ledger, the system uses the leading ledger.

When the extract is created, the system first extracts the documents that affect all ledgers(BSEG). Depending on whether you made an entry for the Ledger selection parameter, thesystem also extracts the line items that are assigned to that ledger (BSEG_ADD).See also SAP note 873125.

In new General Ledger Accounting, additional line items can be created for zero balanceclearing of balancing units (such as segments). The data gained by this document split is thegeneral ledger view. This data is stored in table FAGLFLEXA.

During the data extraction, the system extracts the document data of the general ledger view(FAGLFLEXA TXW_FI_NGL_POS) in parallel to the document data of the entry view.See also SAP note 904525.

69

© SAP 2008 / DART 2.6 /Page 69

DART2.6 Extract DataNew General Ledger Accounting or Classic G/L?


DARTSource Extract

The Extract only classic GLindicator is not displayed

in the standard system.If you need this function,

contact SAP using ausing a customer message

(component CA-GTF-DRT).

Customizing

?

FAGLFLEXT TXW_BBACC GLT0 TXW_BBACC

FTW1A

yes no

NewFunctionin 2.6

Customizing

The Extract only classic GL indicator is intended only for users who have migrated from classicGeneral Ledger Accounting to new General Ledger Accounting (FI-GL (new)).

An additional parameter in the start screen of the extraction program (transaction FTW1A)controls whether the G/L account balances are extracted from table FAGLFLEXT of new GeneralLedger Accounting or from GLT0 of classic General Ledger Accounting.

It could be necessary to access the data in GLT0 after the date of the migration, if you still have togenerate DART extracts for a time period before the migration.

As a user, you then have to decide on the classic extraction method or the new General LedgerAccounting extraction method, depending on the fiscal year that is being extracted. Note that thenew parameter is not displayed on the start screen unless a migration method is set up.

Caution: To improve performance, the extraction program supports only one selection method forthe G/L account balances in each run. Therefore, you should ensure that the company codes tobe extracted in one run also have the same migration date. It is not possible to combine companycodes in one extraction run if the FI data should be read for one from table FAGLFLEXT and foranother from GLT0.

SAP Note 1270903 (Status: For pilot customers only)

70

© SAP 2008 / DART 2.6 /Page 70

DART2.6 Configure Data SegmentsEnhanced Segment Number Ranges

xxx

xxx

Ct ToFromMaint.Trans.

Range

FTWQMD

FTWQTD

- / -

- / -

- / -

- / -

Customer range: Master data

Customer range: Transaction data

Customer range: Master data

Customer range: Transaction data

SAP range: Master data

SAP range: Transaction data

009999009000D

499999

299999

000999

008999

000899

300000D n

100000C n

000900C

001000B

000001A

Each DART segment is assignedinternally to a unique segmentnumber.When a new segment is created, thesystem automatically assigns thesegment number.There are separate number rangesfor customer enhancements.

?

C n 100000 - 299999D n 300000 - 499999

C 000900 - 000999D 009000 - 009999

yes no

Enhanced Number RangeActive

NewFunctionin 2.6

Beginning in DART 2.6, you can extend the segment number range for managing customer-specific DART segments.Transaction data (old) 000900 – 000999 (new) 100000 – 299999Master data (old) 009000 – 009999 (new) 300000 – 499999

The system works with the enhanced number range if the parameter EXT_SN_RANGE is set(SE16, table TXW_C_GLO).

You can set up and change the number range using the following transactions:FTWQTD = Maintain number range object TXW_SN_TD Transaction DataFTWQMD = Maintain number range object TXW_SN_MD Master Data

You need to switch to the enhanced number range if you want to define more than 100customer-specific transaction segments and more than 1000 customer-specific master datasegments in your DART application.

Another reason for using the enhanced number range is if you want to ensure that segmentenhancements are unique within a distributed system landscape. This is necessary if you wantto evaluate the DART extracts centrally. See the next page also.

Also see SAP Note 1234641 (Enhanced Segment Number Ranges with Customizing).

71

© SAP 2008 / DART 2.6 /Page 71

DART2.6 Configure Data SegmentsEnhanced Segment Number Ranges

Instance 3 Instance 2

Instance 1

Instance 4CentralAnalysisSystem

Development Client 002C n 100000 - 119999D n 300000 - 319999


C n = Customer range: Transaction dataD n = Customer range: Mater data


Scenario:Decentralized Processing

In a distributed system landscape, maintenance of customer-specific segments can bedecentralized.To make a central analysis of the DART data extracts possible at a later time, the DARTsegment numbers must be unique in the entire system landscape.

You need to specify the number interval that is allowed for each instance.

In each instance, you need to maintain the assigned number interval:- FTWQTD = Maintain number range object TXW_SN_TD Transaction Data- FTWQMD = Maintain number range object TXW_SN_MD Master Data

New DART segments are set up within an instance as applicable across clients.For maintaining these new DART segments, it is useful to specify a development client (in theexample, client 002).You must then also maintain the number range objects for the enhanced segment numberrange in this client.

Also keep in mind that when you create new segments, the naming of the segment structuremust be unique within the entire system landscape.

72

© SAP 2008 / DART 2.6 /Page 72

DART2.6 Configure Data SegmentsModification of Segment Structures

AfterBefore

Improvements in: F1 HelpF4 HelpList HeadersImproved

Functions in2.6

73

© SAP 2008 / DART 2.6 /Page 73

DART2.6 Data Segment for Fin. Statement StructureTransparent Tables

As of DART 2.6

Before

AdjustedSegmentsas of 2.6

Previous SituationThe data of the financial statement structures were stored in the transparent tables T011/T011T and in the non-transparent cluster table RFDT.Tables T011/T011T contain only a list of the existing financial statement structures, whereas the cluster tableRFDT contains:- Items in the Financial Statement - (RF011P)- Assignment of Balance Sheet Line Item to Account - (RF011Z)- Financial statement item - functional area – (RF011F)- Item Change after Balance Change – (RF011V)- Financial Statement Item Allocation - Set Name – (RF011S)- Financial Statement Item Texts – (RF011Q)- Timestamp for Fin. Stmt Items – (FIBSC_ERGSL_TSTAMP)

The result of this non-transparent storage is that financial statement structures cannot be delivered using BC Sets(Business Configuration Sets). This fact alone makes a conversion to transparent data storage a necessity.

New Situation (These transparent tables are used as of ERP 2004)- FAGL_011PC - Fin. Statement Structure: Items in Fin. Statement Structure- FAGL_011ZC - Fin. Statement Structure: Assignment FS Items - G/L Account- FAGL_011FC - Fin. Statement Structure: Assignment FS Item - Funct. Areas- FAGL_011SC - Fin. Statement Struct.: Assignment Fin. Stmnt Item: Setname- FAGL_011VC - Fin. Statement Structure: Contra Items- FAGL_011QT - Fin. Statement Structure: Text for Fin. Statement Items- FAGL_011TC - Fin. Statement Structure: Timestamp for Fin. Stmt Items

We also took this opportunity to remove some limitations that existed up to now on the financial statementstructures, including the following:- The limit of a maximum of 10 hierarchy levels- The limit of a maximum of 99 subitems per financial statement item

74

© SAP 2008 / DART 2.6 /Page 74

DART Customer Enhancements

Adding a Database Field as a Data Source for Extraction

Related SegmentExists?

Yes No

Add a Field to an Existing Segment Add a Segment to DART

Extend Structure in Dictionary

NewSourceTable?

NumericField?

End

ProgramFunction ExitFTXW0001

Yes

Yes

No

No

Add a Dictionary Structure

End

Create a NewDART

Segment

ProgramFunction ExitFTXW0002

1.

2.

3.

DART supplies a large set of predefined segments. These include multiple segments for manyof the major ERP application areas.

The set of segments that are defined in DART determines which data can be extracted withDART, meaning that you can only extract and retain data for segments that are defined inDART.

If you wish to configure DART to extract data from additional tables or fields, that is, from tablesor fields not included in the SAP-provided set of segments, then you need to add segments orexpand the existing segments.

75

© SAP 2008 / DART 2.6 /Page 75

DART Customer Enhancements1. DDIC Enhancement

You must first create an ABAP Data Dictionary structure to correspond to the data segmentyou wish to add to DART. The Data Dictionary structure must contain all the fields you wish toinclude in the data segment in DART.

76

© SAP 2008 / DART 2.6 /Page 76

DART Customer Enhancements2. DART Enhancement

You have to create a new segment for the data that you want to add.

An ABAP Data Dictionary structure corresponding to the data segment you wish to add toDART must exist. The Data Dictionary structure must contain all the fields you wish to includein the data segment in DART.

77

© SAP 2008 / DART 2.6 /Page 77

DART Customer Enhancements3. User Exit

!Sample Code

An ABAP Data Dictionary structure corresponding to the data segment you wish to add toDART must exist. The Data Dictionary structure must contain all the fields you wish to includein the data segment in DART.

In addition, you must define the segment in DART. You can do so in parallel to creating thefunction exit.

78

© SAP 2008 / DART 2.6 /Page 78

DART Customer Enhancements3. User Exit

You must program this function exit to read and extract the data for the segment you areadding to DART.

79

© SAP 2008 / DART 2.6 /Page 79

DART ConfigurationCustomer-Defined Data

F 1

80

© SAP 2008 / DART 2.6 /Page 80

DART2.6 Authorization Objects

Class Object Activity Val. 1 Val. 2 Transaction

AAAB S_TCODE Transaction codecheck at transaction start

T-Code - all -

AAAB F_TXW_RA Retrieve data from archive CoCd FTWBFTWJ

AAAB F_TXW_TF Data extracts 01, 03, 06,24, 25

CoCd FTW1A, FTWC, FTWD,FTWE, FTWE1, FTWF,FTWH, FTWK, FTWL,FTWM, FTWN, FTWY,S_P6D_40000025,S_P6D_40000026,S_P6D_40000027

AAAB F_TXW_TFCF Data extract configuration 02 FTWP, FTWQ

AAAB F_TXW_TV Data view queries 03, 06, 24,25, 61

CoCd Authoriz.Group

FTWH, FTWN, FTWY

AAAB F_TXW_TVCF Data view configuration 02, 03 FTWY, FTWI, FTWYR

AAAB F_TXW_TVC2 Data view configuration,with authorization group

02, 03 Authoriz.Group

FTWY

For a complete overview of the authorizations checked in DART transactions (including basic authorizations),use transaction SU22 (package FTW1).

F_TXW_TV Data view queriesEspecially for smaller businesses, the provision of a view file on the application server increases the time and effortrequired by the tax auditor. Therefore, an option was created in the view system log display to copy a view file fromthe application server to the local presentation server (PC).

This function is protected by the F_TXW_TV authorization and activity 24 that already exists (archive the view filewith ArchiveLink).

Activity 61 (export view report in file) refers to the export to the file system on the application server.

F_TXW_TVC2 Data view configuration, with authorization groupThis authorization object is an enhancement of authorization F_TXW_TVCF.You can use it to set up view protection for views of a certain user group.

The system performs the authorization check based on authorization object F_TXW_TVC2 only if the followingparameter is set in table TXW_C_GLO:PARM_NAME AUTH_VIEW_DEFPARM_VALUE AUTHGRPThis parameter is not set in the standard system.

You can use authorization groups to limit view queries to certain views.=> F_TXW_TV

Starting in DART 2.5, you can extend this organization to include the view definition.=> F_TXW_TVC2

81

© SAP 2008 / DART 2.6 /Page 81

DART2.6 Authorization Objectsfor View Maintenance

FTWYDefine data extract views

Required Authorization:

F_TXW_TVCF

This authorization is required to display or change dataview definitions.

Activity02 Change data view definition03 Display data view definition

FTWHData extract views


F_TXW_TV

This authorization is required to execute data viewqueries.

Activity03 Display or print data view report06 Delete view query file24 Archive view file via ArchiveLink25 Retrieve archived view file via ArchiveLink61 Export data view report to a file

Authorization GroupYou can create authorization groups that identify userswith common authorizations.

Company Code


F_TXW_TVC2

This authorization object is an enhancement ofauthorization F_TXW_TVCF.You can use it to set up create/change protection forviews of a certain user group.

Activity! Enter the same data as in F_TXW_TVCF02 Change data view definition03 Display data view definition

Authorization GroupYou can create authorization groups that identify userswith common authorizations.

You can limit view queries (FTWH) to certain viewsusing authorization groups.Starting in DART 2.5, you can also add theview definition (FTWY) to this organization.

82

© SAP 2008 / DART 2.6 /Page 82


The system performs the authorizationcheck based on authorization objectF_TXW_TVC2only if the following parameter is set intable TXW_C_GLO:

PARM_NAME AUTH_VIEW_DEFPARM_VALUE AUTHGRP

This parameter is not set in thestandard system.

83

© SAP 2008 / DART 2.6 /Page 83


Views available without restriction

1SAP_FI01 AuthGr „_„1SAP_FI02 AuthGr „_„1SAP_FI03 AuthGr „_„1SAP_FI04 AuthGr „_„

Views of authorization group IR

Z_IR_BEL01 AuthGr „IR„Z_IR_BEL05 AuthGr „IR„Z_IR_AUSL AuthGr „IR„

Views of authorization group TA

Z_TA_BEL01 AuthGr „TA„Z_TA_UMS AuthGr „TA„Z_TA_VERB AuthGr „TA„Z_TA_DUPL AuthGr „TA„

FTWY

Maintain authorization groups

User Authorizations FTWY, Online Reaction

Object Activity Auth.Group

FTWYOnline Reaction (*)

F_TXW_TVCF

F_TXW_TVC2

02, 03

02, 03

No authorization for viewmaintenance

F_TXW_TVCF

F_TXW_TVC2

02, 03

02, 03 ’_’

Maintenance authorization forviews- without auth. group

F_TXW_TVCF

F_TXW_TVC2

02, 03

02, 03 ’_’, IR

Maintenance authorization forviews- without auth. group- with auth. group IR

(*) Parameter AUTH_VIEW_DEF AUTHGRP is set.

SAP Note 1056005 Authorization groups for view definitionsSAP Note 1050841, n) DART Version 2.5

84

© SAP 2008 / DART 2.6 /Page 84

DART Application Help

85

© SAP 2008 / DART 2.6 /Page 85

http://service.sap.com/dart Data Retention Toolhttp://service.sap.com/gdpdu Tax Reduction Law (Germany)http://service.sap.com/ais Audit Information System

Automated Data Analysis for Tax on Sales / Purchaseshttp://service.sap.com/erp SAP Tax Audit SAP ERP Financials SAP Corporate Governance Tax Audit

Media Library

Quick Links

http://service.sap.com/dart

http://service.sap.com/gdpdu

http://service.sap.com/ais

http://service.sap.com/erp

86

© SAP 2008 / DART 2.6 /Page 86

http://www.dsag.de/fileadmin/media/Leitfaeden/080919_Handlungsempfehlung-GDPdU.pdf(23 MB)

Recommendations Made by DSAG (German SAP User Group)

for Applying GDPdU

http://www.dsag.de/fileadmin/media/Leitfaeden/080919_Handlungsempfehlung-GDPdU.pdf

87

© SAP 2008 / DART 2.6 /Page 87

Experiences with DART

Since 1998, U.S. law (IRS Revenue Procedure 98-25) requiresthat the access method correspond to the transfer to a datamedium.

DART has been successfully deployed by many customers inthe United States since 1998.

Setup requires little effort.

DART is only suitable for SAP systems.

88

© SAP 2008 / DART 2.6 /Page 88

Important SAP Notes Regarding DART

Data Retention Tool (Component CA-GTF-DRT )

099 914 Installation of DART

390 184 Support for data export in SAP Audit Format

491 141 DART 2.0 Data scope defined for Germany

622 095 DART 2.1

582 583 DART – Release strategy (incl. DART data catalog)

627 148 Archiving of extracts

663 077 DART versus GDPdU conformity

670 447 SAP data archiving and GDPdU

668 943 DART 2.2

702 511 DART 2.3

810 014 DART 2.4

945 615 DART – Standard views

1 050 841 DART 2.5

1 173 540 DART 2.6

1 262 693 DART in SAP menu

89

© SAP 2008 / DART 2.6 /Page 89

Contacts at SAP

Project Lead SAP AG/Solution Management Financials:Peter Schiwek, SAP AG [email protected]

Inquiries to SAP HR (for example, about HR Interface Toolbox):Dr. Michael Wulf, SAP AG [email protected]

Inquiries regarding SAP R/2:Rainer Brust, SAP AG [email protected]

Inquiries regarding data archiving:Georg Fischer, SAP AG [email protected]

General consulting (StSenkG/GDPdU/DART)Lars Gartenschläger, LGD [email protected]






90

© SAP 2008 / DART 2.6 /Page 90

Thank you!

91

© SAP 2008 / DART 2.6 /Page 91

Copyright 2008 SAP AGAll 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 changedwithout prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned and associated logos displayedare the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This documentcontains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy,and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, orother items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties ofmerchantability, fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitationshall not apply in cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durchSAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.

Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind.

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Services sowie diedazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähnten Namenvon Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken. Produkte können länderspezifische Unterschiede aufweisen.

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmtenGeschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht dieRichtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, wederausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zwecksowie für die Gewährleistung der Nichtverletzung geltenden Rechts.

SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendungdieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.

Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinkszugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen überInternetseiten Dritter ab.

Alle Rechte vorbehalten.