Escorts in Nungambakkam Phone 8250092165 Enjoy 24/7 Escort Service Enjoy Your...
Â
Mantala DAB:exporter presentation
1. Standardized audit steps for SAPÂŽ R/3â˘
with dab:exporter + ACLTM
DAB
Mass data extraction from SAPÂŽ R/3â˘
Standardized, pre-defined audit check routines
Implemented in the ACLTM Audit Software
2. Agenda
⢠Definitions
⢠Overview of the dab:exporter
â Installation
â Advantages
â System requirements
⢠Integrated standardized auditing with dab:exporter and ACLTM
â dab:exporter vs. SAPÂŽ Built-in download tools
â Outstanding advantages by using the dab:exporter
⢠Concept resume dab:exporter and dab:scripts
â Risk-based screening
â Day-to-day business support
⢠Standardized, pre-defined audit routines
â Modules / Packages
â Examples
⢠Digital audit process supported by the tools from dab:GmbH
⢠Conclusions
3. Definitions
⢠ACLTM
â Audit tool which we use for analyzing data
⢠dab:exporter
â Windows tool for downloading tables from SAPÂŽ R/3⢠: for any amount of records, no performance
impact, just read-only authorization required
â automated â integrated - standardized
⢠dab: scripts
â 170 pre-defined audit steps for SAPÂŽ R/3â˘
â Procurement, Accounts Payable, Accounts Receivable, Sales & Distribution, KPI Analysis
â dab: scripts including the dab: catalog
⢠SAPŽ table know-how
⢠Table and field catalog with all tables and fields which are necessary for performing the audit steps
4. Introduction
⢠A single interface for several different source systems
â SAPÂŽ R/3⢠, Microsoft Navision, Oracle
â ⌠open-ended
⢠A single interface for several different target formats
â ACLTM , CSV, etc.
â ⌠open-ended
⢠Extracting huge amounts of data e.g. from SAPÂŽ R/3â˘
â User needs just read-only access to the data
â Highest security standards by using the authorization concept of SAPÂŽ
â No timeouts when downloading very big tables with lots of records
â No negative performance impact on the SAPÂŽ system when downloading!
⢠Data Conversion into an analyzable data format
â No manual data import into ACLTM necessary
â No manual table or field definition needed
5. dab:exporter - Installation
ď¨ Implementation of a function module on
the SAPÂŽ server (âRFCâ â remote function
module)
ď¨ The function module is based on an official
SAPÂŽ recommendation
ď¨ It just takes about 10-15 minutes to be
implemented
ď¨ Installation of the dab:exporter Windows
client on the users/auditors laptop
(Installation time 5 minutes)
ďŽ If a corresponding user account in SAPÂŽ is
already available, the software can be
immediately put to use
ďŽ User needs just read-only permissions - access
to the data always takes place in a reading-
only modus
6. dab:exporter â Advantages
Outstanding advantages:
â Download of SAPÂŽ tables
â No negative performance impact on
the SAPÂŽ system
â No timeouts even when downloading
big tables with millions of records
â Logging- and validation mechanisms
â It is possible to use the Windows task
scheduler to schedule downloads
â Pre-defining necessary tables and
fields needed to perform the analyses
â The interface is read-only. The data in
the source system can not be
changed
â dab:exporter is also prepared for
unicode SAPÂŽ systems
â âDownload once â analyze oftenâ
â Select certain fields of a table, or set
filter to restrict the amount of data
7. dab:exporter - System requirements
⢠Client
â Windows 2000 / Windows XP
â Microsoft .NET Framework
⢠Server (SAPŽ System)
â SAPÂŽ Release >= 4.5
â Function module has to be set to âremote-enabledâ
â The solution is also suitable for Unicode systems
⢠Technical difficulties
â None so far
8. dab:exporter - Validation and Logging
Performance Report
Export Report â Table Structure
Export Progress
Export Report â System Comparison
9. dab:exporter vs. built-in SAPÂŽ download
mechanisms
⢠SE16
â Transaction times out when downloading big tables
â Available target data formats require a lot of manual work when importing it into ACLTM
â Special authorization needed for using SE16
⢠QuickViews (Transaction SQVI)
â QuickViews are just implemented locally, no standardization possible
â No possibility to pre-define tables and fields needed for certain audit steps
â Same download problems like when using SE16
The dab:exporter in combination withdab:scripts makes it possible to centralize the
allocation of standardized table-, download- and audit-know-how, but still allowing
to use the solutions locally for example when doing audits abroad. Built-in SAPÂŽ
mechanisms do not allow such an approach.
10. Advantages of the dab:exporter
⢠Automation
â Table- and field comparison (do all necessary tables and fields exist in the source system)
â Download
⢠Standardization
â Standardization of download and data format makes it possible to standardize the audit steps
â table catalogue (dab: catalog) contains all necessary SAPÂŽ tables and fields; it can be maintained
centrally
â Pre-defined Audit steps (dab: scripts) are also maintained centrally
⢠Integration
â Seamless integration into ACLTM
â SAPÂŽ table know-how, download know-how and audit know-how are brought together in one
solution
⢠Usability
â Easy to use, a wizard helps you to prepare the downloads
â Advanced users still can use techniques like filters, SQL Statements or manual field selections
13. Risk-based screening â Example: one-time
vendors
⢠Periodical screening of several fields
of risk
â Identifying risk fields
â Planning audits based on potential
risk fields
â Reporting
14. Audit check routine packages (dab:scripts)
- Overview
⢠Over hundred of ready-to-run tests for SAPŽ data, available also as bundle for certain SAPŽ modules
â Procurement (about 50 audit steps)
â Vendor management incl. Accounts Payable (about 40 audit steps)
â Customer management incl. Accounts Receivables (about 40 audit steps)
â Sales and Distribution (about 40 audit steps)
⢠Packages which are currently under development:
â Marketing
â Plant Maintenance
⢠Package contains
â Audit steps
â English manual (technical documentation as well as business background)
â Key Performance Indicators (if possible)
â Results usually contain materiality, user information, information about SAPÂŽ transactions
15. Audit check routine packages (dab:scripts)
â Examples I
⢠Procurement (Examples)
â Outline Agreements
â Price Analysis
â One-time-vendors
⢠Accounts Payable (Examples)
â Double Payments
â Unusual Posting Times
â Manual Payments
â Invoices without Purchase Order
16. Audit check routine packages (dab:scripts)
â Examples II
⢠Accounts Receivables
â Credit limit changes
â Down Payments
â Open items
⢠Human Resources (Examples)
â Bank account matches
â Bank account duplicates
⢠Masterdata (Examples)
â Master data creation
â Master data changes
â Duplicates on Bank accounts
20. Overview about data analysis with ACLTM
dab: Daten - Analysen & Beratung GmbHmartin.riedl@dab-gmbh.de, stefan.wenig@dab-gmbh.de 20
The dab:exporter allows you to export data from SAPÂŽ;
it converts the data automatically into ACLTM format
Once downloaded,
you can start
immediately with
analyzing the data
in ACLTM , no
manual
adjustments
needed!
21. Conclusions
⢠Benefits from a Management perspective
â Support when planning audits
â Establish a global, risk-based screening
â Establish a benchmarking system based on KPIs (Key Performance
Indicators)
â High-level management reporting
⢠Benefits from an Operational perspective
â Seamless integration from KPI to transaction level (detail records)
â The solution supports the daily business of internal auditors
22. Conclusions
⢠Download mass data (big tables) from SAPŽ, without having a performance impact
on the SAPÂŽ system
â Extract one â analyze often. Because of analyzing the data locally on your laptop, there
is no performance impact on the SAPÂŽ system, no matter how complex the analyzes are
or how long they will take
â Examples
⢠Successful download of 120 Gigabytes of ACLTM data from one SAPŽ system in total
⢠Successful download of tables with more than 200 millions of records
⢠Use the windows task scheduler to use time-slots when the system is not busy
⢠Convert the data into ACLTM format automatically
â Seamless integration: Download from SAPÂŽ, double-click the ACLTM project, run the
audit steps
â No manual importing work necessary anymore, all key fields have the same length, are
named correctly and have the correct data type
⢠A single interface for several source systems and target data formats
â Data from more than one system (SAPÂŽ, Microsoft Navision, Oracle etc.) can be put
together in one single ACLTM project
â Target formats ACLTM , CSV, GDPdU (Suggested data format by German Tax Law)
23. Conclusions
⢠Pre-defined SAPŽ audit steps are standardized
â Synergy effects: The very same script / audit step can be applied to SAPÂŽ systems and
SAPÂŽ data all over the world, no matter if they are located in the UK, Germany, China, or
Brasil
â High level of transparency because of the detailed English manual
⢠Audit steps contain a lot of know-how
â SAPÂŽ know-how: Required tables, fields and relations are pre-defined
â Business know-how: The ready-to-run tests are based on the daily examination work of
internal and financial auditors or certified public accounts
⢠Increase effectiveness and efficiency of your audit mechanisms
â Select audit steps which answer exactly your questions (effectiveness)
â Reach your goals with less manual effort (efficiency)
â Still, it is no âauditing by check listâ, the flexibility is guaranteed, and also the auditors
creativity will never be redundant