SAP Function Modules

CCL_DISB_BI_EXECUTE SAP Function module - Execute Disbursement Using BI







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

Associated Function Group: FVD_MD_DISBURSEMENT
Released Date: Not Released
Processing type: Remote-Enabled
remote enabled module settings


Pattern for FM CCL_DISB_BI_EXECUTE - CCL DISB BI EXECUTE





CALL FUNCTION 'CCL_DISB_BI_EXECUTE' "Execute Disbursement Using BI
  EXPORTING
*   ctu = 'X'                   " apqi-putactive
*   mode = 'N'                  " apqi-putactive
*   update = 'L'                " apqi-putactive
*   group =                     " apqi-groupid
*   user =                      " apqi-userid
*   keep =                      " apqi-qerase
*   holddate =                  " apqi-startdate
*   nodata = '/'                " apqi-putactive
    i_s_disb_data_all =         " ccl_disb_data_all  Data Fields from Contract + Other Data Fields for Screen 400
    ddispo_004 =                " bdcdata-fval  BDC Field Value
    sbust_008 =                 " bdcdata-fval  BDC Field Value
    pauspro_010 =               " bdcdata-fval  BDC Field Value
    vcbtr_022 =                 " char0016      Character string - 16 user-defined characters
    bcwhr_011 =                 " char0016      BDC Field Value
    vdxincl_006 = 'X'           " bdcdata-fval
    banks_029 =                 " bdcdata-fval
  IMPORTING
    subrc =                     " syst-subrc
* TABLES
*   messtab =                   " bdcmsgcoll
    .  "  CCL_DISB_BI_EXECUTE

ABAP code example for Function Module CCL_DISB_BI_EXECUTE





The ABAP code below is a full code listing to execute function module CCL_DISB_BI_EXECUTE 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_subrc  TYPE SYST-SUBRC ,
it_messtab  TYPE STANDARD TABLE OF BDCMSGCOLL,"TABLES PARAM
wa_messtab  LIKE LINE OF it_messtab .


SELECT single PUTACTIVE
FROM APQI
INTO @DATA(ld_ctu).


SELECT single PUTACTIVE
FROM APQI
INTO @DATA(ld_mode).


SELECT single PUTACTIVE
FROM APQI
INTO @DATA(ld_update).


SELECT single GROUPID
FROM APQI
INTO @DATA(ld_group).


SELECT single USERID
FROM APQI
INTO @DATA(ld_user).


SELECT single QERASE
FROM APQI
INTO @DATA(ld_keep).


SELECT single STARTDATE
FROM APQI
INTO @DATA(ld_holddate).


SELECT single PUTACTIVE
FROM APQI
INTO @DATA(ld_nodata).

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

DATA(ld_ddispo_004) = some text here

DATA(ld_sbust_008) = some text here

DATA(ld_pauspro_010) = some text here
DATA(ld_vcbtr_022) = 'Check type of data required'.
DATA(ld_bcwhr_011) = 'Check type of data required'.

DATA(ld_vdxincl_006) = some text here

DATA(ld_banks_029) = some text here

"populate fields of struture and append to itab
append wa_messtab to it_messtab. . CALL FUNCTION 'CCL_DISB_BI_EXECUTE' EXPORTING * ctu = ld_ctu * mode = ld_mode * update = ld_update * group = ld_group * user = ld_user * keep = ld_keep * holddate = ld_holddate * nodata = ld_nodata i_s_disb_data_all = ld_i_s_disb_data_all ddispo_004 = ld_ddispo_004 sbust_008 = ld_sbust_008 pauspro_010 = ld_pauspro_010 vcbtr_022 = ld_vcbtr_022 bcwhr_011 = ld_bcwhr_011 vdxincl_006 = ld_vdxincl_006 banks_029 = ld_banks_029 IMPORTING subrc = ld_subrc * TABLES * messtab = it_messtab . " CCL_DISB_BI_EXECUTE
IF SY-SUBRC EQ 0. "All OK 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_subrc  TYPE SYST-SUBRC ,
ld_ctu  TYPE APQI-PUTACTIVE ,
it_messtab  TYPE STANDARD TABLE OF BDCMSGCOLL ,
wa_messtab  LIKE LINE OF it_messtab,
ld_mode  TYPE APQI-PUTACTIVE ,
ld_update  TYPE APQI-PUTACTIVE ,
ld_group  TYPE APQI-GROUPID ,
ld_user  TYPE APQI-USERID ,
ld_keep  TYPE APQI-QERASE ,
ld_holddate  TYPE APQI-STARTDATE ,
ld_nodata  TYPE APQI-PUTACTIVE ,
ld_i_s_disb_data_all  TYPE CCL_DISB_DATA_ALL ,
ld_ddispo_004  TYPE BDCDATA-FVAL ,
ld_sbust_008  TYPE BDCDATA-FVAL ,
ld_pauspro_010  TYPE BDCDATA-FVAL ,
ld_vcbtr_022  TYPE CHAR0016 ,
ld_bcwhr_011  TYPE CHAR0016 ,
ld_vdxincl_006  TYPE BDCDATA-FVAL ,
ld_banks_029  TYPE BDCDATA-FVAL .


SELECT single PUTACTIVE
FROM APQI
INTO ld_ctu.


"populate fields of struture and append to itab
append wa_messtab to it_messtab.

SELECT single PUTACTIVE
FROM APQI
INTO ld_mode.


SELECT single PUTACTIVE
FROM APQI
INTO ld_update.


SELECT single GROUPID
FROM APQI
INTO ld_group.


SELECT single USERID
FROM APQI
INTO ld_user.


SELECT single QERASE
FROM APQI
INTO ld_keep.


SELECT single STARTDATE
FROM APQI
INTO ld_holddate.


SELECT single PUTACTIVE
FROM APQI
INTO ld_nodata.

ld_i_s_disb_data_all = 'Check type of data required'.

ld_ddispo_004 = some text here

ld_sbust_008 = some text here

ld_pauspro_010 = some text here
ld_vcbtr_022 = 'Check type of data required'.
ld_bcwhr_011 = 'Check type of data required'.

ld_vdxincl_006 = some text here

ld_banks_029 = some text here

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name CCL_DISB_BI_EXECUTE or its description.