Page Comparison

The position analysis module "VAT Audit" replicates tax-relevant documents from the SAP database to a local AMANA database using the Java connector JCo, a local AMANA database, in order to be able to carry out analyses.

On the VAT-Audit side, the AMANA interface DataGate takes care of reading and writing the data; on the SAP side, an RFC_READ_TABLE module adapted by AMANA is used.

The BAPI (Business Application Programming Interface) "RFC_READ_TABLE" included in the SAP installation is used to read and transfer SAP database tables. The width of the data records is limited to 512 characters.

It was initially considered to use this standard module, but its implementation is useless for accurate and performant analysis of document data; one would be faced with the challenge of extracting a large number of records in chunks via the interface and reassembling them on the client side. Amana consulting GmbH has modified the ABAP source code of the RFC_READ_TABLE in such a way that data records of up to 2 KB can be transferred.

Furthermore, features such as the support of an order-by-clause have been implemented. The AMANA module is given its own name and function group; it does not conflict with the original if both functions are used in parallel.

This document describes how to install the AMANA BAPI in the SAP system in order to communicate with the VAT-Audit.

1. Initial situation

• Install AMANA ABAP "Z_READ_TABLE_RFC" on all SAP servers (see '2.Installation of the module Z_RFC_READ_TABLE

• (technical) SAP account with read rights for access via JavaConnector (JCo) to at least the following SAP tables:
  

  Master data	Transaction data
  KNA1 LFA1	BKPF BSEG BSEC BSET

  
  

  Note
  An extension of the list may result from new examinations.

  
  

2. Installation of the module Z_RFC_READ_TABLE

In order to be able to access the module Z_RFC_READ_TABLE developed by AMANA from the external system VAT-Audit, several settings and configurations are necessary on the SAP servers involved. First, a function group is created and finally the actual module is configured and activated.

SE80: Creating a function group

For the BAPI delivered by AMANA, a function group must be selected on the SAP server. For AMANA programmes, a new group can be created under transaction SE80. For Customer, the prefixes Y and Z are reserved and must be used. The group is created as a local object.

SE37: Creating the BAPI

In the SAP GUI, transaction SE37 is called to create the AMANA module Z_RFC_READ_TABLE. Another name can also be chosen for the module, but this must be done in coordination with AMANA, as this name is the essential agreement through which the two systems VAT Audit and SAP communicate. The module is assigned to the function group Z_AMANA.

SE37 Configuration of the BAPI

Nach dem Anlegen der Funktion werden die Reiter des Subdialogs nacheinander mit Werten befüllt. Grundeinstellungen (a), Eingabeparameter (b), Ausgabeparameter (c) Tabellen (d), Ausnahmen (e) und nicht zuletzt der Quellcode (f) müssen dem SAP-System bekannt gemacht werden.

a) On the first tab of the sub-dialogue, "Properties", the option "Remote capable module" is selected.

b) The import parameters of the function are stored on the second tab "Import":

c)The original module was extended by the export parameter RECORD_COUNT, which only counts the data records when the input parameter is set.

d) The tables used are configured in the "Tables" tab. The main differences to the original RFC are the new order-by-clause and the structure of the output table: TBL2048 instead of TAB512.

e) The function throws various exceptions, which are specified in the "Exceptions" tab:

f) Finally, the source code of the AMANA implementation is copied into the input field of the Source Code tab. Existing code is overwritten. Then the function is activated via the icon in the toolbar.

3. SAP-User

A technical SAP user is required for the data extract.

The following permissions are required.

• DDIF_FIELDINFO_GET (Functional building block)
• RFC1 (Function group)
• RFCPING (Functional building block)
• RFC_GET_FUNCTION_INTERFACE (Functional building block)
• RFC_METADATA_GET (Functional building block)
• SDIFRUNTIME (Function group)
• SYST (Function group)
• Z_AMANA (Function group)

In addition, a reading authorisation for the examination-relevant tables (siehe see 1. Initial situation).

4. Connection test

On the AMANA side of the interface, the VAT audit is informed about the JCO connection. The authorised user logs into the VAT-Audit (VAT@GTC) and switches to the connection parameter dialogue under the settings tab. There he stores the connection data for the (technical) SAP user who is allowed to replicate the document data via the RFC.

Besides user name and password, the parameters host, instance number, client ID (client) and the SAP router are the decisive entries.

The button "Extended connection test" leads to the dialogue in which you can address the RFC.

Connection test

In the extended connection test of the AMANA application, one can address both the original RFC and the Z_RFC_READ_TABLE adapted by AMANA. The input parameters QUERY_TABLE and DELIMITER are supported. The number of returned records is limited to 100, so that the connection test can also be performed against large database tables.