SAP ISM_CB_MSD_JKEP_REQUIRED Function Module for IS-M/SD: Check Whether Schedule Line Required for Update
ISM_CB_MSD_JKEP_REQUIRED is a standard ism cb msd jkep required SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-M/SD: Check Whether Schedule Line Required for Update 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 ism cb msd jkep required FM, simply by entering the name ISM_CB_MSD_JKEP_REQUIRED into the relevant SAP transaction such as SE37 or SE38.
Function Group: JI_CIRCBOOK_UPDATE
Program Name: SAPLJI_CIRCBOOK_UPDATE
Main Program: SAPLJI_CIRCBOOK_UPDATE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISM_CB_MSD_JKEP_REQUIRED 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 'ISM_CB_MSD_JKEP_REQUIRED'"IS-M/SD: Check Whether Schedule Line Required for Update.
EXPORTING
IS_TJD57 = "IS-M/SD: Circulation Audit Report Types for Editions
IMPORTING
EV_XREQUIRED = "
IMPORTING Parameters details for ISM_CB_MSD_JKEP_REQUIRED
IS_TJD57 - IS-M/SD: Circulation Audit Report Types for Editions
Data type: TJD57Optional: No
Call by Reference: Yes
EXPORTING Parameters details for ISM_CB_MSD_JKEP_REQUIRED
EV_XREQUIRED -
Data type: XFELDOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISM_CB_MSD_JKEP_REQUIRED 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_is_tjd57 | TYPE TJD57, " | |||
| lv_ev_xrequired | TYPE XFELD. " |
|   CALL FUNCTION 'ISM_CB_MSD_JKEP_REQUIRED' "IS-M/SD: Check Whether Schedule Line Required for Update |
| EXPORTING | ||
| IS_TJD57 | = lv_is_tjd57 | |
| IMPORTING | ||
| EV_XREQUIRED | = lv_ev_xrequired | |
| . " ISM_CB_MSD_JKEP_REQUIRED | ||
ABAP code using 7.40 inline data declarations to call FM ISM_CB_MSD_JKEP_REQUIRED
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