请问哪位大侠知道SAP系统中AIS（Audit Information System）模块中都有些什么功能吗？

gtsp

请问哪位大侠知道SAP系统中AIS（Audit Information System）模块中都有些什么功能吗？在哪能下载！

[ 本帖最后由 heartsease 于 2006-12-20 22:16 编辑 ]

heartsease

去SAP的官方网站看看

纵横四海

给你找了一个资料：

**************************************************
Here I quote some notes that might help....
**************************************************
Audit Information System (AIS) - installation
Note Number 0100609
Released on 15.02.2001
Release


--------------------------------------------------------------------------------

Symptom


Audit Information System (AIS) - installation

The AIS is a working tool for auditors and is described in Note 77503.


Additional key words

AIS, Audit Infosystem, Audit Info System, Revision, System revision, Auditor


Cause and prerequisites


Solution

Installation of the Audit Information System:

The AIS is a part of the SAP Basis functions in Release 3.1I and as of Release 4.6A. For previous maintenance levels as of 3.0D, you can import the AIS according to the following instructions. Please take care to use the correct transport files depending on your target release.


------------------------------------------------------------------------

1. Import of the AIS

The AIS is stored on SAP service computers (SAPSERV_) under the following path:

~ftp/specific/audit_info

You can download the data with the SAP Workbench Organizer (Correction and Transport System) to your computer.

Carry out the import of the target system in clients 000 as set out in SAP Note 13719.

( ... import client000 transport U168 ... )


For 3.0D, 3.0F, 3.1H and 3.1I only

You can import the AIS into client 000 or into your production client. In case of importing into client 000 you have to copy client-specific objects on the transport order into your production client using Transaction SCC1.


Transport request N31K000038 of current version 1.5.2 of the AIS includes the following files in the directory version1.5.2 :
File Size Date

D000038.N31 833331 May 6 15:51
K000038.N31 314 May 6 15:51
R000038.N31 3173126 May 6 15:51

These files are stored in the zip archive AIS1.5.2.zip .


If you have already installed AIS version 1.5.1, it is sufficient to import transport N31K000038. Steps 2-5 are then no longer required. The important changes for version 1.5.2 compared to previous versions are set out in Note 77503. Users can then decide for themselves whether an Upgrade to 1.5.2 is necessary.


For 4.0B only

You have to import into client 000. There is no need to copy client-specific objects into the production client.


Transport request N40K000069 of the current version 40B.5 of the AIS includes the following files in the directory version40B.5 :
File Size Date

D000069.N40 727.747 Nov. 7, 2000
K000069.N40 197 Nov. 7, 2000
R000069.N40 4.793.974 Nov. 7, 2000

These files are stored in the car archive AIS40B.5.car .



If you have already installed AIS version 4.6, 4.6.1, 4.6.2, 40B.3 or 40B.4 it is sufficient to import transport N40K000069. Steps 2-5 are then no longer required. The important changes for version 40B.5 compared to previous versions are set out in Note 77503. Users can them decide for themselves whether an upgrade to 40B.5 is necessary.


For 4.5B only

You have to import into client 000. There is no need to copy client-specific objects into the production client.


Transport request N45K000129 of the current version 45B.3 of the AIS includes the following files in the directory version45B.3 :
File Size Date

D000129.N45 761.644 Jan 31, 2001
K000129.N45 895 Jan 31, 2001
R000129.N45 5.846.752 Jan 31, 2001

These files are stored in car archive AIS45B.3.car .


If you have already installed AIS version 45B.1 it is sufficient to import transport N45K000129. Steps 2-5 are then no longer required. The important changes for version 45B.2 compared to previous versions are set out in Note 77503. Users can them decide for themselves whether an upgrade to 45B.3 is necessary.


For all correction levels

The object list is stored in the same directory in the file

objlst.txt

By using this before the import you can check which objects are to be imported.

In the file

readme.txt

there is a brief description of the AIS transport files.

------------------------------------------------------------------------

2. Import queries


For Releases 3.0D, 3.0F, 3.1H and 3.1I only

Start Transaction SECR in the target client with the function
-> Extras -> Installation -> Import Queries


The selection screen for the import of queries is called up. All necessary parameters are set as default.

Execute the program.


Using the user-defined transport system, the following query data is transferred:

User group AU
Function area/Query/Var AUBR/AB/SAP&AUDIT

AUDD/AD/SAP&AUDIT
AUKD/AK/SAP&AUDIT
AUSD/AS/SAP&AUDIT
AUSD/AT/SAP&AUDIT



To transfer the queries of Asset Accounting for user group AM you should observe the release notes for Release 3.0B:
-> Financial Accounting -> Asset Accounting -> New Information System



For Release 4.*B only

After a release upgrade from Release 3.x to Release 4.y it is necessary for you to covert the query objects (queries, functional areas, user groups). If you have not yet made this conversion, you receive the following message when calling up queries:

AQ898 "Execute conversion first".


This error message is also issued if a new installation of an R/3 System has been carried out based on Release 4.y.

In this case refer to Note 92124 on the conversion of the queries.


For all correction levels

To be able to work with query data, your must enter your user name in the user groups AU and AM (Transaction SQ03).

------------------------------------------------------------------------

3. Import drill-down reports

Start Transaction SECR in the target client with the function
-> Extras -> Installation -> Import drill-down report


You should import the following drill-down reports:
Report type Report
Balance sheet key figures RFRRS02 01 0SAPAUDIT Export to Baetge
RFRRS02 01 0SAPAUDIT Balance sheet key
figures
Balance display RFRRS10 01 0SAPAUDIT Export to audit agent


Each of the drill-down reports is imported in the logon language. If you are working with more than one language, repeat this step for each language.

------------------------------------------------------------------------

4. User master records for auditors

AIS users need a user master record with display authorizations from several components.

The necessary authorizations can be found in the following SAP profiles (amongst others)
A_ANZ, F_ANZ, M_ANZ, S_A.SHOW, ...


To be able to carry out evaluations with drill-down reporting, the following authorization must be assigned:

Object class Controlling
Object CO: Interactive drilldown reports
Authorization nnn
Fields Activity "03,16,25,61,L0,L1,L2"
Applic. class for drill-down "*"
Report "*"
Table name "*"

The AIS is protected by the transaction code start authorization for authorization object S_TCODE.

You must also assign an authorization for Transactions SECR and 0REP to the users, in addition to the above-mentioned profiles.

For the system audit more comprehensive authorizations are sometimes necessary. Extend the transaction code start authorization as and when needed. There is at present no 'generate' function.

You can display the quantity of the transactions and programs entered in the AIS with Transaction SECR function 'Find program'.

------------------------------------------------------------------------

5. Activate customer enhancement for the export of query results with field information

This activity is only neccessary if your company uses external audit systems which use this interface to analyze financial documents (up to now ACL).


The auditors need selected data from the SAP database to perform stochastic checks.


The query offers an open interface to export data to external analysis tool.


There may be an extensive amount of both basis data as well as selected data. Therefore you need an optimized interface. The structure definition and the field descriptions should also be exported.


The query offers a user exit (SQUE0001, ABAP/4-Query: Private file) which runs just after the data selection.


With the AIS you obtain a suitable include module, RXQUEU00, to export the data: "Private file at the application server"


This include module only performs the export for query user group 'AU' (3.0/3.1) or /SAPQUERY/AU (4.0).

If you would also like to use the file format for other queries, you can deactivate the corresponding query in a copy of the APAP include RXQUEU00. You will find this IF statement following the line containing "* Deactivate this line"


Activate the user exit by assigning the include module to the SAP enhancement SQUE0001 using Transaction CMOD.

If you want to transfer the user exit via transport into the production system, subsequently use Transaction SE38 to generate the main program SAPLXQUE of the user exit function module EXIT_RSAQEXCE_001 (refer to Note 182699 Audit Info System Download of Query data, UserExit).


The data to be exported are stored in TEMSE; this is a storage area for temporary data. The auditors need the following authorization to access the TEMSE datasets:

Object class Basis: Administration ( BC_A )
Object TemSe: Actions on TemSe objects ( S_TMS_ACT )
Field Value
STMSACTION TemSe: Action ID for authorizations
*
STMSOWNER TemSe: Generic object name for authorizations (with '*')
AUDIT_*
STMSOBJECT TemSe: Owner group for authorizations
OWN


Usage of Transaction CMOD
(Project Management of SAP Enhancements)


-Call transaction CMOD.
You get to the screen Project Management (Entry screen)
.Project SQUE0001 (Choose a project name)
.choose Create

You get to the screen Attributes
.Shorttext AIS Private file at the application server
.choose Save
.Development class nnnn (Choose a development class)
.go back to entry screen

.choose SAP enhancements ->Change
.Enhancement SQUE0001
.choose Save
.go back to entry screen

.choose Enhancement components ->Change
.select with double click EXIT_RSAQEXCE_001
.go down to last page of program
.select with double click include zxqueu01

.Message Include ZXQUEU01 does not exist.
Should the include be created?
.choose yes
.choose proceed

.Title AIS Private file at the application server
.Type I
.Component F
.choose Save

.Development class nnnn (same as above)

.choose Source code
.enter include rxqueu00.
.choose Save

.go back to entry screen
.choose Activate project

Additional information.

6. On the SAP service computers (SAPSERV_), in the above-mentioned directory you will find the file

feedback.rtf
containing a questionnaire regarding the Audit Information System. You
are requested to inform SAP of any comments or suggestions you may have about the AIS by filling in this questionnaire.

7. The AIS is an independent component. Existing objects have, in some instances, been enhanced (for example, through system variants for reports), but otherwise remain unchanged. With the object list, you can check prior to the import whether customer-specific modifications have in fact been influenced.

8. The subsequent transport of the AIS from a final preparation system into a production system can be achieved by the direct import of the above-mentioned transport request.

9. Only for Releases 3.0D, 3.0F, 3.1H und 3.1I: You also have to copy report system variants for a client copy. Check SAPNet Note 41475 for details. To copy the system variants after the client copy has finished follow this note and use the transport request of the AIS as a template for Transaction SCC1.

10. You must import the Audit Information System again following an upgrade.

11. For the status management, the Test Workbench functions are used, while the Test Workbench uses functions of the Implementation Guide. In particular, status records are stored under IMG project 900. This project is normally generated automatically. If this is not the case, you can use report RSCATINI of the Test Workbench to create project 900.

12. When you import version 1.5.1 and 1.5.2 into a system with a maintenance level prior to 3.1H, a generation error is displayed on screen RSAUDITA 0001 (Field OBJSUB-WORKFLOW does not exist). This error is corrected in a later AIS version. The affected function is not required by AIS users. The error can therefore be ignored.

13. As of R/3 Release 4.0 you must import AIS into client 000 so that only the SAP system variants of reports which were delivered with the AIS are available. If you import into another client, you will receive a whole series of transport errors.

14. Is there a way that I can check to see if the the AIS query user exit is installed?
Call up Transaction CMOD
Use the F4-Help for field 'Project'
Choose 'Infosystem' if needed
Expand all selections if needed
Enter 'SQUE0001' into extra selection field 'SAP Enhancement Exitname' and proceed
You'll get the project containing this exit

Mark radiobutton 'Attributes' and choose function 'Display' to view the status (active/inactive) of the project.

Mark radiobutton 'Enhancement Components' and choose function 'Display' (depending on the correction level you have to choose the function 'Change')
Doubleclick on line 'Functionexit EXIT_RSAQEXCE_001'
If needed, choose function 'Source Code'
Scroll down to the end
Doubleclick on line 'INCLUDE ZXQUEU01.'
Now you should see a line 'include rxqueu00.'. This indicated the AIS
query user exit.


Source code corrections



Related notes

0013719 Preliminary transports to customers (note for customers)
0077503 Audit Information System (AIS)
0128256 Audit info system: Missing English texts
0129170 Audit Info System Download of Query data
0162971 Audit Information System (AIS) 3.x 4.0 4.5: version history
0182699 Audit Information System (AIS): Download of Query data (user
0187483 Audit Information System: Incomplete activity group
0197137 Audit Info System Query Download from EBCDIC server
0376779 RSQUEU01: Missing FM "F4IF_INT_TABLE_VALUE_REQUEST"
0414365 A4012, 'Subobject not found'

heartsease

我这里也找到些：
Archive Information System

Use

The Archive Information System (AS) is generic tool for implementing searches in data archives and is fully integrated into the SAP Data Archiving environment. The search for and display of data follows rules set in the Archive Information Structures, which the user can define and fill with data from the archive.



In this documentation, the terms archive information structure, information structure and infostructure are used synonymously.

Features

The archive information system includes the following components:

Archive Retrieval Configurator (ARC)

The ARC enables you to create archive information structures with the help of field catalogs, and to fill the structures with data from the archive. The archive information structure, which represents a kind of archive index, provides the basis for archive data reporting.

Archive Explorer

The Archive Explorer enables fast searches of archived data. It does this by accessing the archive information structures that have been created and stored in transparent database tables using the Archive Retrieval Configurator. Furthermore, the Archive Explorer allows direct accesses of individual data objects in the archive, which can then be displayed in both technical and application-specific views.

Using the Archive Information System

Purpose

This process describes the step-by-step procedures for using the Archive Information System (AS). The individual steps are in introduced the order in which the user would normally execute them.



Reloading archived data can lead to problems with the Archive Information System, as the available information structures are not updated automatically. For more information, see Procedure for Reloaded Archives.

Process Flow

Check available information structures
First you should check if an information structure already exists that you could use for reporting. You can then change this information structure to suit your needs. If there is no information structure available that you can use, you can create a new one.

Create the information structure
You define the information structure to be used for archive reporting. In doing this, you specify which source fields from the archive are copied to which fields in the information structure. You do this with the help of application-specific field catalogs, which are included in the features of the Archive Information System.

An information structure is only ever valid for one archiving object. Several information structures can be defined for one archiving object. For more information, see Creating Information Structures

Activate the Information Structure
After you have created an information structure, you need to activate it. Alternatively you can use a standard information structure, provided that it fits your requirements.

At this stage, the system generates a transparent database table and the reporting program. For more information, see Activating Information Structures

Fill the Information Structure
During an archiving delete run all (activated) archive information structures belonging to an archiving object are filled automatically. Also the Archive Development Kit (ADK) transfers all data records found in the archive to the AS interface. From the defined infostructure, the AS filters the data from the data records transferred and enters it in a transparent database table together with an access key. This table serves as the basis for later searches.

As well as the automatic fill using the delete program, an information structure can also be filled later for already available archives. This can be useful if you want to report data that was already archived or if you have changed the fields of an information structure. For more information, see Filling Information Structures.

Report Information Structures
Use the Archive Explorer function to specify the archiving object and the information structure from which you want to report. In the selection screen, where necessary, specify the display parameters for the archived data. Select a data object from the list of data objects and, where possible, specify the view in which it is to be displayed. For more information, see Reporting Information Structures.



As well as standard reporting, there is also a special ad-hoc reporting function available that enables direct reporting from archives. Here, there is no need to fill the archive information structure with data from the archive.