SAP FKCK_ESCH_POST Function Module for Check Escheatment: Posting
FKCK_ESCH_POST is a standard fkck esch post SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check Escheatment: Posting processing and below is the pattern details for this FM, 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 fkck esch post FM, simply by entering the name FKCK_ESCH_POST into the relevant SAP transaction such as SE37 or SE38.
Function Group: FKCH_ESCH_POST
Program Name: SAPLFKCH_ESCH_POST
Main Program: SAPLFKCH_ESCH_POST
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FKCK_ESCH_POST 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 'FKCK_ESCH_POST'"Check Escheatment: Posting.
EXPORTING
IT_CHECKS = "Posting of Check Escheatment: Check Data
IV_BUKRS = "Company Code
IV_ESCHRC = "Receiver Code for Check Escheatment
IV_WAERS = "Currency Key
IV_FIKEY = "Reconciliation Key for General Ledger
IV_BUDAT = "Posting Date in the Document
IV_BLDAT = "Document Date in Document
* IX_UPDATE_TASK = ' ' "Indicator: Update Task
* IX_SIMU = ' ' "Indicator: Simulation
IMPORTING
ET_DFKKCRESCH_CHG = "Check Register: Escheatment Data
ET_MESSAGES = "Table with BAPI Return Information
EX_ERROR = "Indicator: Errors Occurred
IMPORTING Parameters details for FKCK_ESCH_POST
IT_CHECKS - Posting of Check Escheatment: Check Data
Data type: FKKCRESCH_POST_CHECK_TOptional: No
Call by Reference: Yes
IV_BUKRS - Company Code
Data type: BUKRSOptional: No
Call by Reference: Yes
IV_ESCHRC - Receiver Code for Check Escheatment
Data type: ESCHRC_KKOptional: No
Call by Reference: Yes
IV_WAERS - Currency Key
Data type: WAERSOptional: No
Call by Reference: Yes
IV_FIKEY - Reconciliation Key for General Ledger
Data type: FIKEY_KKOptional: No
Call by Reference: Yes
IV_BUDAT - Posting Date in the Document
Data type: BUDAT_KKOptional: No
Call by Reference: Yes
IV_BLDAT - Document Date in Document
Data type: BLDATOptional: No
Call by Reference: Yes
IX_UPDATE_TASK - Indicator: Update Task
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: Yes
IX_SIMU - Indicator: Simulation
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FKCK_ESCH_POST
ET_DFKKCRESCH_CHG - Check Register: Escheatment Data
Data type: DFKKCRESCH_TOptional: No
Call by Reference: Yes
ET_MESSAGES - Table with BAPI Return Information
Data type: BAPIRETTABOptional: No
Call by Reference: Yes
EX_ERROR - Indicator: Errors Occurred
Data type: XFELDOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FKCK_ESCH_POST 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_it_checks | TYPE FKKCRESCH_POST_CHECK_T, " | |||
| lv_et_dfkkcresch_chg | TYPE DFKKCRESCH_T, " | |||
| lv_iv_bukrs | TYPE BUKRS, " | |||
| lv_et_messages | TYPE BAPIRETTAB, " | |||
| lv_ex_error | TYPE XFELD, " | |||
| lv_iv_eschrc | TYPE ESCHRC_KK, " | |||
| lv_iv_waers | TYPE WAERS, " | |||
| lv_iv_fikey | TYPE FIKEY_KK, " | |||
| lv_iv_budat | TYPE BUDAT_KK, " | |||
| lv_iv_bldat | TYPE BLDAT, " | |||
| lv_ix_update_task | TYPE XFELD, " SPACE | |||
| lv_ix_simu | TYPE XFELD. " SPACE |
|   CALL FUNCTION 'FKCK_ESCH_POST' "Check Escheatment: Posting |
| EXPORTING | ||
| IT_CHECKS | = lv_it_checks | |
| IV_BUKRS | = lv_iv_bukrs | |
| IV_ESCHRC | = lv_iv_eschrc | |
| IV_WAERS | = lv_iv_waers | |
| IV_FIKEY | = lv_iv_fikey | |
| IV_BUDAT | = lv_iv_budat | |
| IV_BLDAT | = lv_iv_bldat | |
| IX_UPDATE_TASK | = lv_ix_update_task | |
| IX_SIMU | = lv_ix_simu | |
| IMPORTING | ||
| ET_DFKKCRESCH_CHG | = lv_et_dfkkcresch_chg | |
| ET_MESSAGES | = lv_et_messages | |
| EX_ERROR | = lv_ex_error | |
| . " FKCK_ESCH_POST | ||
ABAP code using 7.40 inline data declarations to call FM FKCK_ESCH_POST
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.| DATA(ld_ix_update_task) | = ' '. | |||
| DATA(ld_ix_simu) | = ' '. | |||
Search for further information about these or an SAP related objects