WPLFBK SAP (Extended LFBK structure (planned changes)) Structure details
Description: Extended LFBK structure (planned changes)
Structure field list including key, data, relationships and ABAP select examples
WPLFBK 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 "Extended LFBK structure (planned changes)" 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_WPLFBK TYPE WPLFBK.
The WPLFBK table consists of various fields, each holding specific information or linking keys about Extended LFBK structure (planned changes) data available in SAP. These include UTIME (Time of Last Change), AENNR (Change Number), CHGFLAG (POS interface: flag for certain field changes), MANDT (Client).. 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: Not classified
SAP WPLFBK 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 |
| DATUM | POS interface: date | WJDPOSDAT | DATS | 8 | DATUM | ||||
| UTIME | Time of Last Change | UTIME | TIMS | 6 | UZEIT | ||||
| AENNR | Change Number | AENNR | CHAR | 12 | Assigned to domain | AENNR | AENNR | AEN | |
| CHGFLAG | POS interface: flag for certain field changes | WJDPOSFLAG | CHAR | 1 | X | ||||
| MANDT | Client | MANDT | CLNT | 3 | T000 | MANDT | |||
| LIFNR | Account Number of Vendor or Creditor | LIFNR | CHAR | 10 | LFA1 | ALPHA | LIFNR | LIF | KRED_C |
| BANKS | Bank country key | BANKS | CHAR | 3 | T005 | LAND1 | BKL | ||
| BANKL | Bank Keys | BANKK | CHAR | 15 | BANKK | BNK | |||
| BANKN | Bank account number | BANKN | CHAR | 18 | BANKN | ||||
| BKONT | Bank Control Key | BKONT | CHAR | 2 | BKONT | ||||
| BVTYP | Partner Bank Type | BVTYP | CHAR | 4 | BVTYP | ||||
| XEZER | Indicator: Is there collection authorization ? | XEZER | CHAR | 1 | XFELD | ||||
| BKREF | Reference specifications for bank details | BKREF | CHAR | 20 | CHAR20 | ||||
| KOINH | Account Holder Name | KOINH_FI | CHAR | 60 | KOINH | ||||
| .INCLU--AP | 0 | ||||||||
| EBPP_ACCNAME | User-Defined Name of Bank Details | EBPP_ACCNAME | CHAR | 40 | EBPP_ACCNAME | ||||
| EBPP_BVSTATUS | Status of Bank Details in Biller Direct | EBPP_BVSTATUS | CHAR | 1 | EBPP_BVSTATUS | ||||
| .INCLU--AP | 0 | ||||||||
| KOVON | Bank Details Valid From | KOVON | DATS | 8 | DATUM | ||||
| KOBIS | Bank details valid to | KOBIS | DATS | 8 | DATUM |
| Key field | Non-key field |
How do I retrieve data from SAP structure WPLFBK using ABAP code?
As WPLFBK 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 WPLFBK as there is no data to select.How to access SAP table WPLFBK
Within an ECC or HANA version of SAP you can also view further information about WPLFBK 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