FKKPY_DYNP SAP (Payment Program - Screen Fields) Structure details
Description: Payment Program - Screen Fields
Structure field list including key, data, relationships and ABAP select examples
FKKPY_DYNP 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 "Payment Program - Screen Fields" 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_FKKPY_DYNP TYPE FKKPY_DYNP.
The FKKPY_DYNP table consists of various fields, each holding specific information or linking keys about Payment Program - Screen Fields data available in SAP. These include LAUFI (Identification for the payment run), XSIMU (Simulate Payment Run), COPYD (Date ID), COPYI (Additional identification of the run to be copied).. 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: Cannot Be Enhanced
SAP FKKPY_DYNP 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 ID | LAUFD_KK | DATS | 8 | DATUM | ||||
LAUFI | Identification for the payment run | LAUFI_PAY | CHAR | 5 | LAUFI_PAY | ||||
XSIMU | Simulate Payment Run | XSIMU_PAY | CHAR | 1 | XFELD | ||||
COPYD | Date ID | LAUFD_KK | DATS | 8 | DATUM | ||||
COPYI | Additional identification of the run to be copied | COPYI_PAY | CHAR | 5 | LAUFI_PAY | ||||
EXCEP | Indicator: Only Delete Exceptions? | EXCEP_PAY | CHAR | 1 | XFELD | ||||
XFKTV | Indicator: Adjust Date Details | XFKTV_110 | CHAR | 1 | XFELD | ||||
STATU | Status text | STEXT_KK | CHAR | 60 | TEXT60 | ||||
STATUS1 | Status text | STEXT_KK | CHAR | 60 | TEXT60 | ||||
STATUS2 | Status text | STEXT_KK | CHAR | 60 | TEXT60 | ||||
STRDT | Scheduled Start Date | STRDT_KK | DATS | 8 | SYDATS | ||||
STRZT | Scheduled Start Time | STRZT_KK | TIMS | 6 | SYTIME | ||||
XSTRF | Start Immediately | XSTRF_KK | CHAR | 1 | XFELD | ||||
XVERRSPACE | Payment Method: Processed via Bank Account | XVERRSPACE_KK | CHAR | 1 | XFELD | ||||
XVERRC | Payment Method: Processed With Payment Card | XVERRC_KK | CHAR | 1 | XFELD | ||||
XVERRX | Paymt Method: Processing by Internal Clearing/Deposit Acct | XVERRX_KK | CHAR | 1 | XFELD | ||||
XVERRA | Payment method: Processed by broker/collections agency | XVERRA_KK | CHAR | 1 | XFELD | ||||
XIBAN_S | SWIFT Code Is Required | XIBAN_S_KK | CHAR | 1 | XFELD | ||||
XIBAN_X | IBAN Is Required | XIBAN_X_KK | CHAR | 1 | XFELD |
Key field | Non-key field |
How do I retrieve data from SAP structure FKKPY_DYNP using ABAP code?
As FKKPY_DYNP 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 FKKPY_DYNP as there is no data to select.How to access SAP table FKKPY_DYNP
Within an ECC or HANA version of SAP you can also view further information about FKKPY_DYNP 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