WPLFB5 SAP (Extended LFB5 structure (planned changes)) Structure details
Description: Extended LFB5 structure (planned changes)
Structure field list including key, data, relationships and ABAP select examples
WPLFB5 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 LFB5 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_WPLFB5 TYPE WPLFB5.
The WPLFB5 table consists of various fields, each holding specific information or linking keys about Extended LFB5 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 WPLFB5 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 |
| BUKRS | Company Code | BUKRS | CHAR | 4 | LFB1 | BUKRS | BUK | C_T001 | |
| MABER | Dunning Area | MABER | CHAR | 2 | T047M | MABER | |||
| MAHNA | Dunning Procedure | MAHNA | CHAR | 4 | T047A | MAHNA | |||
| MANSP | Dunning block | MANSP | CHAR | 1 | T040S | MANSP | |||
| MADAT | Last dunned on | MADAT | DATS | 8 | DATUM | ||||
| MAHNS | Dunning level | MAHNS_D | NUMC | 1 | MAHNS | ||||
| LFRMA | Account number of the dunning recipient | LFRMA | CHAR | 10 | LFA1 | ALPHA | LIFNR | ||
| GMVDT | Date of the legal dunning proceedings | GMVDT | DATS | 8 | DATUM | ||||
| BUSAB | Dunning clerk | BUSAB_MA | CHAR | 2 | T001S | BUSAB |
| Key field | Non-key field |
How do I retrieve data from SAP structure WPLFB5 using ABAP code?
As WPLFB5 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 WPLFB5 as there is no data to select.How to access SAP table WPLFB5
Within an ECC or HANA version of SAP you can also view further information about WPLFB5 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