SAP FKK_PYFORM_GET_NUMBER Function Module for
FKK_PYFORM_GET_NUMBER is a standard fkk pyform get number SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for fkk pyform get number FM, simply by entering the name FKK_PYFORM_GET_NUMBER into the relevant SAP transaction such as SE37 or SE38.
Function Group: FKZ3
Program Name: SAPLFKZ3
Main Program: SAPLFKZ3
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FKK_PYFORM_GET_NUMBER pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'FKK_PYFORM_GET_NUMBER'".
EXPORTING
* I_APPLK = "Application Area
* I_RESERVE = "
IMPORTING
E_NRZAS = "Payment Form Number
IMPORTING Parameters details for FKK_PYFORM_GET_NUMBER
I_APPLK - Application Area
Data type: FKKKO-APPLKOptional: Yes
Call by Reference: No ( called with pass by value option)
I_RESERVE -
Data type: BOOLE-BOOLEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FKK_PYFORM_GET_NUMBER
E_NRZAS - Payment Form Number
Data type: DFKKZR-NRZASOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FKK_PYFORM_GET_NUMBER Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_e_nrzas | TYPE DFKKZR-NRZAS, " | |||
| lv_i_applk | TYPE FKKKO-APPLK, " | |||
| lv_i_reserve | TYPE BOOLE-BOOLE. " |
|   CALL FUNCTION 'FKK_PYFORM_GET_NUMBER' " |
| EXPORTING | ||
| I_APPLK | = lv_i_applk | |
| I_RESERVE | = lv_i_reserve | |
| IMPORTING | ||
| E_NRZAS | = lv_e_nrzas | |
| . " FKK_PYFORM_GET_NUMBER | ||
ABAP code using 7.40 inline data declarations to call FM FKK_PYFORM_GET_NUMBER
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.| "SELECT single NRZAS FROM DFKKZR INTO @DATA(ld_e_nrzas). | ||||
| "SELECT single APPLK FROM FKKKO INTO @DATA(ld_i_applk). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_reserve). | ||||
Search for further information about these or an SAP related objects