SAP CK_F_CHECK_ORGANI_MEASURES Function Module for
CK_F_CHECK_ORGANI_MEASURES is a standard ck f check organi measures 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 ck f check organi measures FM, simply by entering the name CK_F_CHECK_ORGANI_MEASURES into the relevant SAP transaction such as SE37 or SE38.
Function Group: CKVO
Program Name: SAPLCKVO
Main Program: SAPLCKVO
Appliation area: K
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CK_F_CHECK_ORGANI_MEASURES 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 'CK_F_CHECK_ORGANI_MEASURES'".
EXPORTING
P_BUPER = "
P_GJAHR = "
CHANGING
T_BUKRS_DATA = "
IMPORTING Parameters details for CK_F_CHECK_ORGANI_MEASURES
P_BUPER -
Data type: MBEW-PPRDZOptional: No
Call by Reference: Yes
P_GJAHR -
Data type: MBEW-PDATZOptional: No
Call by Reference: Yes
CHANGING Parameters details for CK_F_CHECK_ORGANI_MEASURES
T_BUKRS_DATA -
Data type: COST_T_BUKRS_DATAOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CK_F_CHECK_ORGANI_MEASURES 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_p_buper | TYPE MBEW-PPRDZ, " | |||
| lv_t_bukrs_data | TYPE COST_T_BUKRS_DATA, " | |||
| lv_p_gjahr | TYPE MBEW-PDATZ. " |
|   CALL FUNCTION 'CK_F_CHECK_ORGANI_MEASURES' " |
| EXPORTING | ||
| P_BUPER | = lv_p_buper | |
| P_GJAHR | = lv_p_gjahr | |
| CHANGING | ||
| T_BUKRS_DATA | = lv_t_bukrs_data | |
| . " CK_F_CHECK_ORGANI_MEASURES | ||
ABAP code using 7.40 inline data declarations to call FM CK_F_CHECK_ORGANI_MEASURES
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 PPRDZ FROM MBEW INTO @DATA(ld_p_buper). | ||||
| "SELECT single PDATZ FROM MBEW INTO @DATA(ld_p_gjahr). | ||||
Search for further information about these or an SAP related objects