KJCCSJ3_BI01_JP_BB_EXE_DO SAP Function module - Reestimation: Execution for All Relevant Cycles

KJCCSJ3_BI01_JP_BB_EXE_DO 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 KJCCSJ3_BI01_JP_BB_EXE_DO into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM KJCCSJ3_BI01_JP_BB_EXE_DO - KJCCSJ3 BI01 JP BB EXE DO

CALL FUNCTION 'KJCCSJ3_BI01_JP_BB_EXE_DO' "Reestimation: Execution for All Relevant Cycles
  EXPORTING
    x_anlage =                  " eanl-anlage
  IMPORTING
    y_upd_ieabl =               " isu2a_ieabl
  CHANGING
    xy_max_inst =               " isu2a_inst_struc  Installation Structure of an Installation from Billing View
    xy_max_ieabl =              " isu2a_ieabl   Meter readings
    xy_max_ieablg =             " isu2a_ieablg  MR reasons
  EXCEPTIONS
    GENERAL_FAULT = 1           "               General Error
    .  "  KJCCSJ3_BI01_JP_BB_EXE_DO

ABAP code example for Function Module KJCCSJ3_BI01_JP_BB_EXE_DO

The ABAP code below is a full code listing to execute function module KJCCSJ3_BI01_JP_BB_EXE_DO 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_y_upd_ieabl  
 
 TYPE ISU2A_IEABL
.


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

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

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

SELECT single ANLAGE 
  FROM EANL 
  INTO @DATA(ld_x_anlage).

.

CALL FUNCTION 'KJCCSJ3_BI01_JP_BB_EXE_DO'
  EXPORTING
    x_anlage =                   ld_x_anlage
  IMPORTING
    y_upd_ieabl =                ld_y_upd_ieabl
  CHANGING
    xy_max_inst =                ld_xy_max_inst
    xy_max_ieabl =               ld_xy_max_ieabl
    xy_max_ieablg =              ld_xy_max_ieablg
  EXCEPTIONS
    GENERAL_FAULT =              1
    .  "  KJCCSJ3_BI01_JP_BB_EXE_DO

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "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_xy_max_inst
 
 TYPE ISU2A_INST_STRUC ,
ld_y_upd_ieabl
 
 TYPE ISU2A_IEABL ,
ld_x_anlage
 
 TYPE EANL-ANLAGE ,
ld_xy_max_ieabl
 
 TYPE ISU2A_IEABL ,
ld_xy_max_ieablg
 
 TYPE ISU2A_IEABLG .


ld_xy_max_inst = 'Check type of data required'.

SELECT single ANLAGE 
  FROM EANL 
  INTO ld_x_anlage.

ld_xy_max_ieabl = 'Check type of data required'.
ld_xy_max_ieablg = 'Check type of data required'.