VDZNBPI SAP (TR-LO: Payment Postprocessing - Payment Information) Structure details
Description: TR-LO: Payment Postprocessing - Payment Information
Structure field list including key, data, relationships and ABAP select examples
VDZNBPI is a standard SAP Structure so does not store data like a database table does. It can be used to define the fields of other actual tables or to process "TR-LO: Payment Postprocessing - Payment Information" Information within sap ABAP programs.
This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately.
i.e. DATA: wa_VDZNBPI TYPE VDZNBPI.
The VDZNBPI table consists of various fields, each holding specific information or linking keys about TR-LO: Payment Postprocessing - Payment Information data available in SAP. These include BUKRS (Company Code), BELNR (Accounting Document Number), GJAHR (Fiscal Year), BUZEI (Number of Line Item Within Accounting Document).. See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .
Delivery Class:Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Can be enhanced (character-type or numeric)
SAP VDZNBPI structure fields - Full list of fields found in SAP data dictionary
| Field | Description | Data Element | Data Type | length (Dec) | Check table | Conversion Routine | Domain Name | MemoryID | SHLP |
| BSEGKEY | 0 | ||||||||
| BUKRS | Company Code | BUKRS | CHAR | 4 | BUKRS | BUK | C_T001 | ||
| BELNR | Accounting Document Number | BELNR_D | CHAR | 10 | ALPHA | BELNR | BLN | ||
| GJAHR | Fiscal Year | GJAHR | NUMC | 4 | GJAHR | GJAHR | GJR | ||
| BUZEI | Number of Line Item Within Accounting Document | BUZEI | NUMC | 3 | BUZEI | BUZ | |||
| TCODE | Transaction Code | TCODE_BKPF | CHAR | 4 | CHAR4 | ||||
| VALUT | Value date of the item to be cleared | VALUT_EB | DATS | 8 | DATE_EB | ||||
| AZIDT | Bank statement identification | AZIDT_EB | CHAR | 20 | CHAR20 | ||||
| KUKEY | Short key (surrogate) | KUKEY_EB | NUMC | 8 | KUKEY_EB | ||||
| ESNUM | Memo record number (line item number in bank statement) | ESNUM_EB | NUMC | 5 | NUM5 | ||||
| LAUFI | Additional Identification | LAUFI | CHAR | 6 | LAUFI | ||||
| LAUFD | Date on Which the Program Is to Be Run | LAUFD | DATS | 8 | DATUM | ||||
| KUNNR | Customer Numbers | KUNNR | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | KUN | C_KUNNR |
| PARTN | Business Partner | PARTN_EB | CHAR | 55 | CHAR55 | ||||
| WRBTR | Foreign currency amount (different from account cuurency) | FWBTR_EB | CURR | 13(2) | WRTV7 | ||||
| WAERS | Foreign currency key (unequal to account currency) | FWAER_EB | CUKY | 5 | Assigned to domain | WAERS | |||
| DMBTR | Amount in account currency | KWBTR_EB | CURR | 13(2) | WRTV7 | ||||
| HWAER | Account Currency Key | KWAER_EB | CUKY | 5 | Assigned to domain | WAERS | |||
| HBBLZ | Bank number of our bank | UBNKL | CHAR | 15 | BANKL | ||||
| HBLD1 | Bank country key | BANKS | CHAR | 3 | Assigned to domain | LAND1 | BKL | ||
| KTONR | Bank account number | KTONR_EB | CHAR | 18 | BANKN | ||||
| KTOIH | Bank account holder | KTOIH_EB | CHAR | 35 | CHAR35 | ||||
| AZDAT | Statement Date | AZDAT_EB | DATS | 8 | DATEX | DATE_EB | |||
| AZNUM | Statement number | AZNUM_EB | NUMC | 5 | NUM5 | ||||
| EFART | Input Type | EFART_EB | CHAR | 1 | CHAR1 | ||||
| BUDAT | Posting date in the document | BUDAT_EB | DATS | 8 | DATEX | DATE_EB | |||
| VGINT | Posting rule | VGINT_EB | CHAR | 4 | Assigned to domain | VGINT_EB | |||
| BUTXT | Bank posting text | BUTXT_EB | CHAR | 50 | CHAR50 | ||||
| PABKS | Country key of partner bank | PABKS_EB | CHAR | 3 | Assigned to domain | LAND1 | |||
| PABLZ | Bank number of partner bank | PABLZ_EB | CHAR | 15 | BANKK | ||||
| PAKTO | Account number at the partner bank | PAKTO_EB | CHAR | 18 | BANKN | ||||
| RZAWE | Payment Method for This Payment | RZAWE | CHAR | 1 | Assigned to domain | ZLSCH | |||
| TXTVV | Financial Assets Management Information Field | TXTVV_EB | CHAR | 40 | CHAR40 | ||||
| INFO1 | Additional information 1 | INFO1_EB | CHAR | 30 | CHAR30 | ||||
| INFO2 | Additional information 2 | INFO2_EB | CHAR | 30 | CHAR30 | ||||
| VERTT | Contract Type | RANTYP | CHAR | 1 | RANTYP | ||||
| VERTN | Contract Number | RANL | CHAR | 13 | ALPHA | RANL | RAN | ||
| FEBREIDX | Row Index of Internal Tables | SYTABIX | INT4 | 10 | SYST_LONG | ||||
| VWEZW1 | Character field with length 27 | CHAR27 | CHAR | 27 | CHAR27 | ||||
| VWEZW2 | Character field with length 27 | CHAR27 | CHAR | 27 | CHAR27 | ||||
| PIBAN | Partner Bank Account: IBAN | PIBAN_EB | CHAR | 34 | IBAN | ||||
| PASWI | SWIFT code of partner bank | PASWI_EB | CHAR | 11 | SWIFT | ||||
| KKREF | Customer-to-customer reference | REFNR_EB | CHAR | 35 | CHAR35 | ||||
| TRNID | Transaction ID | EB_TRANSID | CHAR | 35 |
| Key field | Non-key field |
How do I retrieve data from SAP structure VDZNBPI using ABAP code?
As VDZNBPI is a database structure and not a table it does not store any data in the SAP data dictionary. The ABAP SELECT statement is therefore not appropriate and can not be performed on VDZNBPI as there is no data to select.How to access SAP table VDZNBPI
Within an ECC or HANA version of SAP you can also view further information about VDZNBPI and the data within it using relevant transactions such asSE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).
Search for further information about these or an SAP related objects