SAP Function Modules
FKK_SAMPLE_0630 SAP Function module
FKK_SAMPLE_0630 is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.
See here to view full function module documentation and code listing, simply by entering the name FKK_SAMPLE_0630 into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
FKML
Released Date:
Not Released
Processing type: Normal fucntion module
Pattern for FM FKK_SAMPLE_0630 - FKK SAMPLE 0630
CALL FUNCTION 'FKK_SAMPLE_0630' "
EXPORTING
i_srt1 = " fkkpy_srt1 Sort key for paid group
i_fkkvkp = " fkkvkp Contract account data for payment transactions
i_gpshad = " fkk_gpshad Payee data (including bank account)
i_bnka_bus = " bnka Payee bank data
i_bnka_hb = " bnka House bank data
i_t012 = " t012 House bank data
i_t012k = " t012k House bank account data
i_fkkclbt = " fkkclbt Amounts paid
i_fkkopk = " fkkopk Bank line item generated by payment program
i_payh = " payh Payment data
* i_dpayc = " dpayc Administrative Data for Payment Run
* i_exception_data = SPACE " boole-boole Indicator: Payment Exception?
* i_para = " fkkpy_para Payment Program - Parameters
* i_basics = " fkk_mad_basics Mass Activities: Global Values for All Mass Activities
IMPORTING
e_0630 = " fkkpy_0630 Additional payment data
e_commit_required = " boolean COMMIT WORK is Necessary
TABLES
t_fkkcl = " fkkpy_0630_items Payment Program: Structure for Event 0630 (Items)
. " FKK_SAMPLE_0630
ABAP code example for Function Module FKK_SAMPLE_0630
The ABAP code below is a full code listing to execute function module FKK_SAMPLE_0630 including all data declarations. The code uses 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 original method of declaring data variables up front. 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).
| ld_e_0630 | TYPE FKKPY_0630 , |
| ld_e_commit_required | TYPE BOOLEAN , |
| it_t_fkkcl | TYPE STANDARD TABLE OF FKKPY_0630_ITEMS,"TABLES PARAM |
| wa_t_fkkcl | LIKE LINE OF it_t_fkkcl . |
DATA(ld_i_srt1) = 'Check type of data required'.
DATA(ld_i_fkkvkp) = 'Check type of data required'.
DATA(ld_i_gpshad) = 'Check type of data required'.
DATA(ld_i_bnka_bus) = 'Check type of data required'.
DATA(ld_i_bnka_hb) = 'Check type of data required'.
DATA(ld_i_t012) = 'Check type of data required'.
DATA(ld_i_t012k) = 'Check type of data required'.
DATA(ld_i_fkkclbt) = 'Check type of data required'.
DATA(ld_i_fkkopk) = 'Check type of data required'.
DATA(ld_i_payh) = 'Check type of data required'.
DATA(ld_i_dpayc) = 'Check type of data required'.
DATA(ld_i_exception_data) = some text here
DATA(ld_i_para) = 'Check type of data required'.
DATA(ld_i_basics) = 'Check type of data required'.
"populate fields of struture and append to itab
append wa_t_fkkcl to it_t_fkkcl. . CALL FUNCTION 'FKK_SAMPLE_0630' EXPORTING i_srt1 = ld_i_srt1 i_fkkvkp = ld_i_fkkvkp i_gpshad = ld_i_gpshad i_bnka_bus = ld_i_bnka_bus i_bnka_hb = ld_i_bnka_hb i_t012 = ld_i_t012 i_t012k = ld_i_t012k i_fkkclbt = ld_i_fkkclbt i_fkkopk = ld_i_fkkopk i_payh = ld_i_payh * i_dpayc = ld_i_dpayc * i_exception_data = ld_i_exception_data * i_para = ld_i_para * i_basics = ld_i_basics IMPORTING e_0630 = ld_e_0630 e_commit_required = ld_e_commit_required TABLES t_fkkcl = it_t_fkkcl . " FKK_SAMPLE_0630
IF SY-SUBRC EQ 0. "All OK ENDIF.
ABAP code to compare 7.40 inline data declaration with original syntax
The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.
DATA:
| ld_e_0630 | TYPE FKKPY_0630 , |
| ld_i_srt1 | TYPE FKKPY_SRT1 , |
| it_t_fkkcl | TYPE STANDARD TABLE OF FKKPY_0630_ITEMS , |
| wa_t_fkkcl | LIKE LINE OF it_t_fkkcl, |
| ld_e_commit_required | TYPE BOOLEAN , |
| ld_i_fkkvkp | TYPE FKKVKP , |
| ld_i_gpshad | TYPE FKK_GPSHAD , |
| ld_i_bnka_bus | TYPE BNKA , |
| ld_i_bnka_hb | TYPE BNKA , |
| ld_i_t012 | TYPE T012 , |
| ld_i_t012k | TYPE T012K , |
| ld_i_fkkclbt | TYPE FKKCLBT , |
| ld_i_fkkopk | TYPE FKKOPK , |
| ld_i_payh | TYPE PAYH , |
| ld_i_dpayc | TYPE DPAYC , |
| ld_i_exception_data | TYPE BOOLE-BOOLE , |
| ld_i_para | TYPE FKKPY_PARA , |
| ld_i_basics | TYPE FKK_MAD_BASICS . |
ld_i_srt1 = 'Check type of data required'.
"populate fields of struture and append to itab
append wa_t_fkkcl to it_t_fkkcl.
ld_i_fkkvkp = 'Check type of data required'.
ld_i_gpshad = 'Check type of data required'.
ld_i_bnka_bus = 'Check type of data required'.
ld_i_bnka_hb = 'Check type of data required'.
ld_i_t012 = 'Check type of data required'.
ld_i_t012k = 'Check type of data required'.
ld_i_fkkclbt = 'Check type of data required'.
ld_i_fkkopk = 'Check type of data required'.
ld_i_payh = 'Check type of data required'.
ld_i_dpayc = 'Check type of data required'.
ld_i_exception_data = some text here
ld_i_para = 'Check type of data required'.
ld_i_basics = 'Check type of data required'.
SAP Documentation for FM FKK_SAMPLE_0630
In this event, you can store information on the payment that is to be
output on the payment medium, but which is not automatically recorded
...See here for full SAP fm documentation
Contribute (Add Comments)
Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name FKK_SAMPLE_0630 or its description.