SAP BCA_BL_1000 Function Module for Initialization of a Work Package









BCA_BL_1000 is a standard bca bl 1000 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Initialization of a Work Package 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 bca bl 1000 FM, simply by entering the name BCA_BL_1000 into the relevant SAP transaction such as SE37 or SE38.

Function Group: BCA_FKK_BILL_MASS_RUN
Program Name: SAPLBCA_FKK_BILL_MASS_RUN
Main Program: SAPLBCA_FKK_BILL_MASS_RUN
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function BCA_BL_1000 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 'BCA_BL_1000'"Initialization of a Work Package
  EXPORTING
*  I_APPLCATG =  "
*  I_LIMIT_LOW =  "
*  I_LIMIT_HIGH =  "
*  I_XRESTART =  "
*  I_STR_PACKATTR =  "
*  I_CNT_PACKAGES =  "
*  I_FLG_ABORTED =  "
*  I_PROGN =  "
*  I_PROGDATE =  "
*  I_PROGNO =  "
*  I_CURRSTARTNO =  "
*  I_XSIMULATION =  "
*  I_CURRSTEPNO =  "
*  I_STR_APPLPARAM =  "
*  I_STR_PACKAGE_KEY =  "
.



IMPORTING Parameters details for BCA_BL_1000

I_APPLCATG -

Data type: BANK_DTE_PP_PAAPPLCATG
Optional: Yes
Call by Reference: Yes

I_LIMIT_LOW -

Data type: BANK_DTE_PP_OBJNO
Optional: Yes
Call by Reference: Yes

I_LIMIT_HIGH -

Data type: BANK_DTE_PP_OBJNO
Optional: Yes
Call by Reference: Yes

I_XRESTART -

Data type: XFELD
Optional: Yes
Call by Reference: Yes

I_STR_PACKATTR -

Data type:
Optional: Yes
Call by Reference: Yes

I_CNT_PACKAGES -

Data type: BANK_DTE_PP_CNT_PACKAGES
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_FLG_ABORTED -

Data type: XFELD
Optional: Yes
Call by Reference: Yes

I_PROGN -

Data type: BANK_DTE_PP_PROGN
Optional: Yes
Call by Reference: Yes

I_PROGDATE -

Data type: BANK_DTE_PP_PROGDATE
Optional: Yes
Call by Reference: Yes

I_PROGNO -

Data type: BANK_DTE_PP_PROGNO
Optional: Yes
Call by Reference: Yes

I_CURRSTARTNO -

Data type: BANK_DTE_PP_RUNSTARTNO
Optional: Yes
Call by Reference: Yes

I_XSIMULATION -

Data type: BANK_DTE_PP_XSIMULRUN
Optional: Yes
Call by Reference: Yes

I_CURRSTEPNO -

Data type: BANK_DTE_PP_STEPNO
Optional: Yes
Call by Reference: Yes

I_STR_APPLPARAM -

Data type: BCA_STR_BL_DOC_PPF
Optional: Yes
Call by Reference: Yes

I_STR_PACKAGE_KEY -

Data type: BANK_STR_PP_PACKAGEKEY
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for BCA_BL_1000 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_i_applcatg  TYPE BANK_DTE_PP_PAAPPLCATG, "   
lv_i_limit_low  TYPE BANK_DTE_PP_OBJNO, "   
lv_i_limit_high  TYPE BANK_DTE_PP_OBJNO, "   
lv_i_xrestart  TYPE XFELD, "   
lv_i_str_packattr  TYPE XFELD, "   
lv_i_cnt_packages  TYPE BANK_DTE_PP_CNT_PACKAGES, "   
lv_i_flg_aborted  TYPE XFELD, "   
lv_i_progn  TYPE BANK_DTE_PP_PROGN, "   
lv_i_progdate  TYPE BANK_DTE_PP_PROGDATE, "   
lv_i_progno  TYPE BANK_DTE_PP_PROGNO, "   
lv_i_currstartno  TYPE BANK_DTE_PP_RUNSTARTNO, "   
lv_i_xsimulation  TYPE BANK_DTE_PP_XSIMULRUN, "   
lv_i_currstepno  TYPE BANK_DTE_PP_STEPNO, "   
lv_i_str_applparam  TYPE BCA_STR_BL_DOC_PPF, "   
lv_i_str_package_key  TYPE BANK_STR_PP_PACKAGEKEY. "   

  CALL FUNCTION 'BCA_BL_1000'  "Initialization of a Work Package
    EXPORTING
         I_APPLCATG = lv_i_applcatg
         I_LIMIT_LOW = lv_i_limit_low
         I_LIMIT_HIGH = lv_i_limit_high
         I_XRESTART = lv_i_xrestart
         I_STR_PACKATTR = lv_i_str_packattr
         I_CNT_PACKAGES = lv_i_cnt_packages
         I_FLG_ABORTED = lv_i_flg_aborted
         I_PROGN = lv_i_progn
         I_PROGDATE = lv_i_progdate
         I_PROGNO = lv_i_progno
         I_CURRSTARTNO = lv_i_currstartno
         I_XSIMULATION = lv_i_xsimulation
         I_CURRSTEPNO = lv_i_currstepno
         I_STR_APPLPARAM = lv_i_str_applparam
         I_STR_PACKAGE_KEY = lv_i_str_package_key
. " BCA_BL_1000




ABAP code using 7.40 inline data declarations to call FM BCA_BL_1000

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!