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 ElementName of the column in Trustpair file
LFA1-NAME1company_name
LFA1-LAND1company_registration_country_code
LFA1-STCD1 / LFA1-STCD2company_registration
LFA1-STCEGtax_number
LFA1-KRAUSduns
TIBAN-IBANiban
LFBK-BANKNbank_account_number
BNKA-SWIFTbic_code
BNKA-RCCODErouting_number
LFBK-BKONTcontrol_key
LFA1-LIFNRsupplier_id
LFA1-LOEVMsupplier_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 elementName of the column in the Trustpair file
LFA1-NAME1company_name
LFA1-LAND1company_registration_country_code
LFA1-STCD1 / LFA1-STCD2company_registration
LFA1-STCEGtax_number
LFA1-KRAUSduns
TIBAN-IBANiban
LFBK-BANKNbank_account_number
BNKA-SWIFTbic_code
BNKA-RCCODErouting_number
LFBK-BKONTcontrol_key
LFA1-LIFNRsupplier_id
LFA1-LOEVMsupplier_status
BSIK-DMBTRamount
BSIK-WAERSpayment_currency
N/A (calculated element, must be pending)payment_status
BSIK-AUGBLpayment_id
BSIK-AUGDTexecution_date
BSIK-BELNRinvoice_id
BSIK-XBLNRinvoice_number
PAYP-IDbatch_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 elementName of the column in the Trustpair file
LFA1-NAME1company_name
LFA1-LAND1company_registration_country_code
LFA1-STCD1 / LFA1-STCD2company_registration
LFA1-STCEGtax_number
LFA1-KRAUSduns
TIBAN-IBANiban
LFBK-BANKNbank_account_number
BNKA-SWIFTbic_code
BNKA-RCCODErouting_number
LFBK-BKONTcontrol_key
LFA1-LIFNRsupplier_id
LFA1-LOEVMsupplier_status
BSAK-DMBTRamount
BSAK-WAERSpayment_currency
N/A (calculated element, must be paid)payment_status
BSAK-AUGBLpayment_id
BSAK-AUGDTexecution_date
BSAK-BELNRinvoice_id
BSAK-XBLNRinvoice_number
PAYP-IDbatch_id