F111V SAP (Fields for SAPF111V (PR Payment Program Parameters)) Structure details
Description: Fields for SAPF111V (PR Payment Program Parameters)
Structure field list including key, data, relationships and ABAP select examples
F111V 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 "Fields for SAPF111V (PR Payment Program Parameters)" 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_F111V TYPE F111V.
The F111V table consists of various fields, each holding specific information or linking keys about Fields for SAPF111V (PR Payment Program Parameters) data available in SAP. These include LAUFI (Additional Identification), COPYD (CPU Date of the Run that Serves as a Reference Copy), COPYI (Additional Identification of the Run to be Copied), STATU (Editing Status).. 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 F111V 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 |
| LAUFD | Date on Which the Program Is to Be Run | LAUFD | DATS | 8 | DATUM | ||||
| LAUFI | Additional Identification | LAUFI | CHAR | 6 | LAUFI | ||||
| COPYD | CPU Date of the Run that Serves as a Reference Copy | COPYD | DATS | 8 | DATUM | ||||
| COPYI | Additional Identification of the Run to be Copied | COPYI | CHAR | 6 | LAUFI | ||||
| STATU | Editing Status | STATU_110 | CHAR | 60 | TEXT60 | ||||
| VONLD | Lower Limit for the Run Date Found | VONDT_REGU | DATS | 8 | DATUM | ||||
| BISLD | Upper Limit for the Run Date Being Searched For | BISDT_REGU | DATS | 8 | DATUM | ||||
| ZWELS | List of Payment Methods that Should be Used in a Payment Run | F110_ZWELS | CHAR | 10 | ZWELS | ||||
| NEDAT | Date of the Next Payment Run | PRQ_NEDAT | DATS | 8 | DATUM | ||||
| WDATE | Bill of Exchange Issue Date | WDATE | DATS | 8 | DATUM | ||||
| WFAEL | Bill of Exchange Due Date | WFAEL | DATS | 8 | DATUM | ||||
| XVORL | Indicator: Only Proposal Run? | XVORL | CHAR | 1 | XFELD | ||||
| XFKTV | Indicator: Adjust Date Details | XFKTV_110 | CHAR | 1 | XFELD | ||||
| XSTRF | Indicator: Start immediately | XSTRF | CHAR | 1 | XFELD | ||||
| XMITL | Indicator: Schedule Payment Lists Too | XMITL | CHAR | 1 | XFELD | ||||
| XMITD | Indicator: Schedule Post and Print | XMITD | CHAR | 1 | XFELD | ||||
| XMORE | Indicator: Further details on the detail screen | XMORE | CHAR | 1 | XFELD | ||||
| STRDT | Sched. Start Date | STRDT | DATS | 8 | DATUM | ||||
| STRZT | Planned Start Time | STRZT | TIMS | 6 | UZEIT | ||||
| JNAME | Background job name | BTCJOB | CHAR | 32 | CHAR32 | ||||
| BHOST | Computer on Which the Background Job Is to Be Carried Out | BHOST | CHAR | 20 | MSHOST | ||||
| FDTA | Selection Field - Reorganize FDTA Data | FDTA_REORG | CHAR | 1 | XFELD | ||||
| XTRZN | Indicator: Payment Method Selection Trace for Errors? | PRQ_XTRZN | CHAR | 1 | XFELD | ||||
| XTRZW | Indicator: Payment Method Selection Trace Required? | XTRZW_110 | CHAR | 1 | XFELD | ||||
| XTRBL | Indicator: Is a Trace Required for the Payment Documents? | XTRBL_110 | CHAR | 1 | XFELD | ||||
| XTRZE | Indicator: Payment Method Selection Trace for Errors? | XTRZE_110 | CHAR | 1 | XFELD | ||||
| XTRFA | Indicator: Trace for Due Date Determination? | XTRFA_110 | CHAR | 1 | XFELD | ||||
| MONAT | Fiscal Period | MONAT | NUMC | 2 | MONAT | ||||
| GJAHR | Fiscal Year | GJAHR | NUMC | 4 | GJAHR | GJAHR | GJR | ||
| PROGN | Program Name | PROGN | CHAR | 40 | PROGN | ||||
| LPROG | Program Name | PROGN | CHAR | 40 | PROGN | ||||
| VARI1 | Payment Transaction Variant | FORDVARI | CHAR | 14 | SELSET | ||||
| VARI2 | Payment Transaction Variant | FORDVARI | CHAR | 14 | SELSET | ||||
| VARI3 | Payment Transaction Variant | FORDVARI | CHAR | 14 | SELSET | ||||
| VARI4 | Payment Transaction Variant | FORDVARI | CHAR | 14 | SELSET | ||||
| VARL1 | Payment Transaction Variant | FORDVARI | CHAR | 14 | SELSET | ||||
| VARL2 | Payment Transaction Variant | FORDVARI | CHAR | 14 | SELSET | ||||
| VARL3 | Payment Transaction Variant | FORDVARI | CHAR | 14 | SELSET | ||||
| VARL4 | Payment Transaction Variant | FORDVARI | CHAR | 14 | SELSET | ||||
| INDI | Not More Closely Defined Area, Possibly Used for Patchlevels | CHAR4 | CHAR | 4 | CHAR4 |
| Key field | Non-key field |
How do I retrieve data from SAP structure F111V using ABAP code?
As F111V 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 F111V as there is no data to select.How to access SAP table F111V
Within an ECC or HANA version of SAP you can also view further information about F111V 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