Mapping columns between SAP and Trustpair
Many of Trustpair's customers use SAP as an ERP.
In the following sections, you can find the exact mapping between the SAP columns and Trustpair columns to fit the requirements described in the last sections.
Mapping the VMF (Vendor Master File)
The third-party repository file is used to extract the information needed for the ongoing audit of vendors. It is an aggregation of data from different SAP tables.
The tables used are :
- LFA1 - Vendor Master (General Section)
- LFBK - Vendor Master (Bank Details)
- TIBAN - IBAN
- BNKA - Bank master record
Here is the correspondence of the fields of the Trustpair file and the SAP elements :
| SAP ABAP Data Element | Name of the column in Trustpair file |
|---|---|
| LFA1-NAME1 | company_name |
| LFA1-LAND1 | company_registration_country_code |
| LFA1-STCD1 / LFA1-STCD2 | company_registration |
| LFA1-STCEG | tax_number |
| LFA1-KRAUS | duns |
| TIBAN-IBAN | iban |
| LFBK-BANKN | bank_account_number |
| BNKA-SWIFT | bic_code |
| BNKA-RCCODE | routing_number |
| LFBK-BKONT | control_key |
| LFA1-LIFNR | supplier_id |
| LFA1-LOEVM | supplier_status |
Mapping the pending payments
The pending payments file is used to extract the information necessary for the ongoing analysis of scheduled transfers to vendors. It is an aggregation of data from different SAP tables.
This file completes the vendor data with the history of payments pending bank settlement.
The tables used are :
- LFA1 - Vendor Master (General Section)
- LFBK - Vendor Master (Bank Details)
- TIBAN - IBAN
- BNKA - Bank master record
- BSIK - Accounting: Secondary Index for Vendors
- PAYP - Payment program - data on paid item
NB : The file contains a functional field whose content does not correspond directly to a value stored in SAP. This is the payment_status which, in the case of pending payments, must be filled in with the value pending.
Here the correspondence of the fields of the Trustpair file and the SAP elements :
| SAP ABAP Data element | Name of the column in the Trustpair file |
|---|---|
| LFA1-NAME1 | company_name |
| LFA1-LAND1 | company_registration_country_code |
| LFA1-STCD1 / LFA1-STCD2 | company_registration |
| LFA1-STCEG | tax_number |
| LFA1-KRAUS | duns |
| TIBAN-IBAN | iban |
| LFBK-BANKN | bank_account_number |
| BNKA-SWIFT | bic_code |
| BNKA-RCCODE | routing_number |
| LFBK-BKONT | control_key |
| LFA1-LIFNR | supplier_id |
| LFA1-LOEVM | supplier_status |
| BSIK-DMBTR | amount |
| BSIK-WAERS | payment_currency |
| N/A (calculated element, must be pending) | payment_status |
| BSIK-AUGBL | payment_id |
| BSIK-AUGDT | execution_date |
| BSIK-BELNR | invoice_id |
| BSIK-XBLNR | invoice_number |
| PAYP-ID | batch_id |
Mapping the payment history
The payment history file is used to extract the information needed at the start of the project for the initial audit.
It is an aggregation of data from different SAP tables.
This file completes the vendor data with the history of payments made to vendors.
The tables used are :
- LFA1 - Vendor Master (General Section)
- LFBK - Vendor Master (Bank Details)
- TIBAN - IBAN
- BNKA - Bank master record
- BSAK - Accounting: Secondary Index for Vendors (Cleared Items)
- PAYP - Payment program - data on paid item
NB : The file contains a functional field whose content does not correspond directly to a value stored in SAP. This is the payment_status which, in the case of payment history, must be filled in with the value paid.
Here the correspondence of the fields of the Trustpair file and the SAP elements :
| SAP ABAP Data element | Name of the column in the Trustpair file |
|---|---|
| LFA1-NAME1 | company_name |
| LFA1-LAND1 | company_registration_country_code |
| LFA1-STCD1 / LFA1-STCD2 | company_registration |
| LFA1-STCEG | tax_number |
| LFA1-KRAUS | duns |
| TIBAN-IBAN | iban |
| LFBK-BANKN | bank_account_number |
| BNKA-SWIFT | bic_code |
| BNKA-RCCODE | routing_number |
| LFBK-BKONT | control_key |
| LFA1-LIFNR | supplier_id |
| LFA1-LOEVM | supplier_status |
| BSAK-DMBTR | amount |
| BSAK-WAERS | payment_currency |
| N/A (calculated element, must be paid) | payment_status |
| BSAK-AUGBL | payment_id |
| BSAK-AUGDT | execution_date |
| BSAK-BELNR | invoice_id |
| BSAK-XBLNR | invoice_number |
| PAYP-ID | batch_id |
Updated 3 months ago