SAP FKK_POST_SETTLEMENT_POSITION Function Module for
FKK_POST_SETTLEMENT_POSITION is a standard fkk post settlement position 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 post settlement position FM, simply by entering the name FKK_POST_SETTLEMENT_POSITION into the relevant SAP transaction such as SE37 or SE38.
Function Group: FKKEXC
Program Name: SAPLFKKEXC
Main Program: SAPLFKKEXC
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function FKK_POST_SETTLEMENT_POSITION 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_POST_SETTLEMENT_POSITION'".
EXPORTING
* I_COMMIT = 'X' "Commit Work
* I_SIMU = ' ' "Simulation
IT_EXTITEMS = "
IT_PAYKEYS = "
IMPORTING
ET_POSTEDDOC = "Table Type for ICM_FICA_DOC
ET_MESSAGES = "Return Parameter(s)
EXCEPTIONS
PROCESS_ERROR = 1
IMPORTING Parameters details for FKK_POST_SETTLEMENT_POSITION
I_COMMIT - Commit Work
Data type: BOOLE-BOOLEDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_SIMU - Simulation
Data type: BOOLE-BOOLEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
IT_EXTITEMS -
Data type: FKK_COMM_ITEM_TOptional: No
Call by Reference: No ( called with pass by value option)
IT_PAYKEYS -
Data type: FKK_PAYKY_LIST_TOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FKK_POST_SETTLEMENT_POSITION
ET_POSTEDDOC - Table Type for ICM_FICA_DOC
Data type: ICM_FICA_DOC_TOptional: No
Call by Reference: No ( called with pass by value option)
ET_MESSAGES - Return Parameter(s)
Data type: BAPIRET2_TOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
PROCESS_ERROR - Process Error
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FKK_POST_SETTLEMENT_POSITION 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_i_commit | TYPE BOOLE-BOOLE, " 'X' | |||
| lv_et_posteddoc | TYPE ICM_FICA_DOC_T, " | |||
| lv_process_error | TYPE ICM_FICA_DOC_T, " | |||
| lv_i_simu | TYPE BOOLE-BOOLE, " SPACE | |||
| lv_et_messages | TYPE BAPIRET2_T, " | |||
| lv_it_extitems | TYPE FKK_COMM_ITEM_T, " | |||
| lv_it_paykeys | TYPE FKK_PAYKY_LIST_T. " |
|   CALL FUNCTION 'FKK_POST_SETTLEMENT_POSITION' " |
| EXPORTING | ||
| I_COMMIT | = lv_i_commit | |
| I_SIMU | = lv_i_simu | |
| IT_EXTITEMS | = lv_it_extitems | |
| IT_PAYKEYS | = lv_it_paykeys | |
| IMPORTING | ||
| ET_POSTEDDOC | = lv_et_posteddoc | |
| ET_MESSAGES | = lv_et_messages | |
| EXCEPTIONS | ||
| PROCESS_ERROR = 1 | ||
| . " FKK_POST_SETTLEMENT_POSITION | ||
ABAP code using 7.40 inline data declarations to call FM FKK_POST_SETTLEMENT_POSITION
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 BOOLE FROM BOOLE INTO @DATA(ld_i_commit). | ||||
| DATA(ld_i_commit) | = 'X'. | |||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_simu). | ||||
| DATA(ld_i_simu) | = ' '. | |||
Search for further information about these or an SAP related objects