SAP FKK_CR_CHECK_READ_DATA Function Module for









FKK_CR_CHECK_READ_DATA is a standard fkk cr check read data 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 cr check read data FM, simply by entering the name FKK_CR_CHECK_READ_DATA into the relevant SAP transaction such as SE37 or SE38.

Function Group: FKCHKREP
Program Name: SAPLFKCHKREP
Main Program: SAPLFKCHKREP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function FKK_CR_CHECK_READ_DATA 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_CR_CHECK_READ_DATA'"
EXPORTING
* IX_USE_KEY = "Checkbox
* I_CHECK_KEY = "Key structure for checks repository
* IX_USE_OPBEL = "Checkbox
* I_OPBEL = "Number of a Contract Accounts Receivable and Payable Document
* IX_GET_ALL = "Checkbox
* IX_GET_LAST = "Checkbox
* IX_LOCKED = "

IMPORTING
E_CHECK_DATA = "Repository For Checks

TABLES
* ET_CHECK2P = "Check Repository: Additional Payees
* ET_CHECKD2 = "Check Management: Partial Encashments
* ET_ALL_KEYS = "Key structure for checks repository

EXCEPTIONS
WRONG_CALL = 1 NO_ENTRY_FOUND = 2
.



IMPORTING Parameters details for FKK_CR_CHECK_READ_DATA

IX_USE_KEY - Checkbox

Data type: XFELD
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_CHECK_KEY - Key structure for checks repository

Data type: FKKCRKEY
Optional: Yes
Call by Reference: No ( called with pass by value option)

IX_USE_OPBEL - Checkbox

Data type: XFELD
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_OPBEL - Number of a Contract Accounts Receivable and Payable Document

Data type: OPBEL_KK
Optional: Yes
Call by Reference: No ( called with pass by value option)

IX_GET_ALL - Checkbox

Data type: XFELD
Optional: Yes
Call by Reference: No ( called with pass by value option)

IX_GET_LAST - Checkbox

Data type: XFELD
Optional: Yes
Call by Reference: No ( called with pass by value option)

IX_LOCKED -

Data type: XFELD
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for FKK_CR_CHECK_READ_DATA

E_CHECK_DATA - Repository For Checks

Data type: FKKCR
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for FKK_CR_CHECK_READ_DATA

ET_CHECK2P - Check Repository: Additional Payees

Data type: DFKKCR2P
Optional: Yes
Call by Reference: Yes

ET_CHECKD2 - Check Management: Partial Encashments

Data type: DFKKCRDOC2
Optional: Yes
Call by Reference: Yes

ET_ALL_KEYS - Key structure for checks repository

Data type: FKKCRKEY
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

WRONG_CALL -

Data type:
Optional: No
Call by Reference: Yes

NO_ENTRY_FOUND -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FKK_CR_CHECK_READ_DATA 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:
lt_et_check2p  TYPE STANDARD TABLE OF DFKKCR2P, "   
lv_ix_use_key  TYPE XFELD, "   
lv_wrong_call  TYPE XFELD, "   
lv_e_check_data  TYPE FKKCR, "   
lt_et_checkd2  TYPE STANDARD TABLE OF DFKKCRDOC2, "   
lv_i_check_key  TYPE FKKCRKEY, "   
lv_no_entry_found  TYPE FKKCRKEY, "   
lt_et_all_keys  TYPE STANDARD TABLE OF FKKCRKEY, "   
lv_ix_use_opbel  TYPE XFELD, "   
lv_i_opbel  TYPE OPBEL_KK, "   
lv_ix_get_all  TYPE XFELD, "   
lv_ix_get_last  TYPE XFELD, "   
lv_ix_locked  TYPE XFELD. "   

  CALL FUNCTION 'FKK_CR_CHECK_READ_DATA'  "
    EXPORTING
         IX_USE_KEY = lv_ix_use_key
         I_CHECK_KEY = lv_i_check_key
         IX_USE_OPBEL = lv_ix_use_opbel
         I_OPBEL = lv_i_opbel
         IX_GET_ALL = lv_ix_get_all
         IX_GET_LAST = lv_ix_get_last
         IX_LOCKED = lv_ix_locked
    IMPORTING
         E_CHECK_DATA = lv_e_check_data
    TABLES
         ET_CHECK2P = lt_et_check2p
         ET_CHECKD2 = lt_et_checkd2
         ET_ALL_KEYS = lt_et_all_keys
    EXCEPTIONS
        WRONG_CALL = 1
        NO_ENTRY_FOUND = 2
. " FKK_CR_CHECK_READ_DATA




ABAP code using 7.40 inline data declarations to call FM FKK_CR_CHECK_READ_DATA

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.

 
 
 
 
 
 
 
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!