ISB_EDT_AND_COSTING_CHECK_INIT SAP Function module - IS-B: Überprüfen der Starteinstellungen bei FDÜ mit Kalkulation

ISB_EDT_AND_COSTING_CHECK_INIT is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name ISB_EDT_AND_COSTING_CHECK_INIT into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: JBF1
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM ISB_EDT_AND_COSTING_CHECK_INIT - ISB EDT AND COSTING CHECK INIT

CALL FUNCTION 'ISB_EDT_AND_COSTING_CHECK_INIT' "IS-B: Überprüfen der Starteinstellungen bei FDÜ mit Kalkulation
  EXPORTING
*   sav_prot_name =             " char40        Character 40-Stellen
    fdu_start_mode =            "
    fdu_start_test =            "
    calc_do =                   "
    repid =                     " kcdsm-repid
  IMPORTING
    calc_test =                 " jbikapd-jtestl
    new_edt_run =               " char1         Einstelliges Kennzeichen
  EXCEPTIONS
    FDU_TEST_CALC_REAL = 1      "
    FDU_TYPE_NO_CALC = 2        "
    FDU_ERKRS_NOT_SET = 3       "
    .  "  ISB_EDT_AND_COSTING_CHECK_INIT

ABAP code example for Function Module ISB_EDT_AND_COSTING_CHECK_INIT

The ABAP code below is a full code listing to execute function module ISB_EDT_AND_COSTING_CHECK_INIT including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_calc_test  
 
 TYPE JBIKAPD-JTESTL
,
ld_new_edt_run  
 
 TYPE CHAR1
.


DATA(ld_sav_prot_name) = 'Check type of data required'.

DATA(ld_fdu_start_mode) = 'some text here'.

DATA(ld_fdu_start_test) = 'some text here'.

DATA(ld_calc_do) = 'some text here'.
 

SELECT single REPID 
  FROM KCDSM 
  INTO @DATA(ld_repid).

.

CALL FUNCTION 'ISB_EDT_AND_COSTING_CHECK_INIT'
  EXPORTING
*   sav_prot_name =              ld_sav_prot_name
    fdu_start_mode =             ld_fdu_start_mode
    fdu_start_test =             ld_fdu_start_test
    calc_do =                    ld_calc_do
    repid =                      ld_repid
  IMPORTING
    calc_test =                  ld_calc_test
    new_edt_run =                ld_new_edt_run
  EXCEPTIONS
    FDU_TEST_CALC_REAL =         1
    FDU_TYPE_NO_CALC =           2
    FDU_ERKRS_NOT_SET =          3
    .  "  ISB_EDT_AND_COSTING_CHECK_INIT

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_calc_test
 
 TYPE JBIKAPD-JTESTL ,
ld_sav_prot_name
 
 TYPE CHAR40 ,
ld_new_edt_run
 
 TYPE CHAR1 ,
ld_fdu_start_mode
 
 TYPE STRING ,
ld_fdu_start_test
 
 TYPE STRING ,
ld_calc_do
 
 TYPE STRING ,
ld_repid
 
 TYPE KCDSM-REPID .


ld_sav_prot_name = 'Check type of data required'.
ld_fdu_start_mode = 'some text here'.
ld_fdu_start_test = 'some text here'.
ld_calc_do = 'some text here'.

SELECT single REPID 
  FROM KCDSM 
  INTO ld_repid.