...
In the process, the transaction data and master data are taken from SAP by the AMANA DataGate and transferred to the VAT audit. The data is validated by individually designed audits and assigned to employees for processing once any anomalies have been identified. The facts are then evaluated. Depending on the situation, the document is corrected in SAP, the task is forwarded or a positive confirmation is issued. In any case, however, the so-called task is evaluated at the end. This completed process supports the compliance claims and inevitably leads to cleansed pre-announcement data.
Import von Daten
start import
The import of the data basis for the VAT audit is started in the area "VAT audit - SAP interface" by pressing the button Import. The interface copies, in the following order, the contents of the tables FI_BSEG, FI_LFA1, FI_BSET, FI_BKPF, FI_BSEC, FI_KNA1 into the separately created database. Changes in the data in the VAT audit do not lead to changes in the data in the SAP/ERP system. Entries in tables FI_LFA1, FI_KNA1 are only copied for the master data if a reference to it exists from the transaction data, so that master data that is not required is not copied.
restrict import
It is possible to restrict the import in advance by certain filter criteria. The setting for this is entered in the connection parameter of the respective SAP server under "Settings - Connection parameters - ERP server - Filter criteria".
...
| Note | ||
|---|---|---|
| ||
EQUAL_TO NOT_EQUAL_TO GREATER_THAN LESS_THAN GREATER_OR_EQUAL LESS_OR_EQUAL IN NOT_IN BETWEEN, NOT_BETWEEN LIKE NOT_LIKE |
Examples: "BLART NOT_EQUAL_TO 'WA'" or "BLART NOT_IN ('WA', 'WE')" = Document types WA and WE are excluded and not used in the import process.
A maximum of 2000 characters can be entered. Multiple statements are possible with separation by a newline.
Audits
The transaction data are now subjected to the previously created audits to verify their accuracy.
...