SAP SAMPLE_PROCESS_0BANK010 Function Module for









SAMPLE_PROCESS_0BANK010 is a standard sample process 0bank010 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 sample process 0bank010 FM, simply by entering the name SAMPLE_PROCESS_0BANK010 into the relevant SAP transaction such as SE37 or SE38.

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



Function SAMPLE_PROCESS_0BANK010 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 'SAMPLE_PROCESS_0BANK010'"
  EXPORTING
   I_APPLCATG =  "Application Type in Parallel Processing
   I_STR_PARAM =  "Parameters to Demonstrate Use of Parallel Processing
   I_PARAMNAME =  "Name of an ABAP Dictionary Object
   I_STR_PACKAGE_KEY =  "Key to a Package Template

 IMPORTING
   E_LIMIT_HIGH =  "Number of an Object in Parallel Processing (Key)
   E_LIMIT_LOW =  "Number of an Object in Parallel Processing (Key)
   E_TAB_OBJKEY =  "Object Key
   E_CNT_PACKAGES =  "Number of Packages
   E_STR_PACKPARAM =  "
   E_FLG_NO_PACKAGE =  "
   E_PACKDEFCATG =  "Package Definition Category

EXCEPTIONS
   NOT_FOUND = 1    FAILED = 2
.



IMPORTING Parameters details for SAMPLE_PROCESS_0BANK010

I_APPLCATG - Application Type in Parallel Processing

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

I_STR_PARAM - Parameters to Demonstrate Use of Parallel Processing

Data type:
Optional: No
Call by Reference: Yes

I_PARAMNAME - Name of an ABAP Dictionary Object

Data type: DDOBJNAME
Optional: No
Call by Reference: Yes

I_STR_PACKAGE_KEY - Key to a Package Template

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

EXPORTING Parameters details for SAMPLE_PROCESS_0BANK010

E_LIMIT_HIGH - Number of an Object in Parallel Processing (Key)

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

E_LIMIT_LOW - Number of an Object in Parallel Processing (Key)

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

E_TAB_OBJKEY - Object Key

Data type: BANK_TAB_OBJKEY
Optional: No
Call by Reference: Yes

E_CNT_PACKAGES - Number of Packages

Data type: BANK_DTE_PP_CNT_PACKAGES
Optional: No
Call by Reference: Yes

E_STR_PACKPARAM -

Data type:
Optional: No
Call by Reference: Yes

E_FLG_NO_PACKAGE -

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

E_PACKDEFCATG - Package Definition Category

Data type: BANK_DTE_PP_PACKDEFCATG
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NOT_FOUND -

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

FAILED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SAMPLE_PROCESS_0BANK010 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_not_found  TYPE STRING, "   
lv_i_applcatg  TYPE BANK_DTE_PP_PAAPPLCATG, "   
lv_e_limit_high  TYPE BANK_DTE_PP_OBJNO, "   
lv_failed  TYPE BANK_DTE_PP_OBJNO, "   
lv_e_limit_low  TYPE BANK_DTE_PP_OBJNO, "   
lv_i_str_param  TYPE BANK_DTE_PP_OBJNO, "   
lv_i_paramname  TYPE DDOBJNAME, "   
lv_e_tab_objkey  TYPE BANK_TAB_OBJKEY, "   
lv_e_cnt_packages  TYPE BANK_DTE_PP_CNT_PACKAGES, "   
lv_i_str_package_key  TYPE BANK_STR_PP_PACKAGEKEY, "   
lv_e_str_packparam  TYPE BANK_STR_PP_PACKAGEKEY, "   
lv_e_flg_no_package  TYPE XFELD, "   
lv_e_packdefcatg  TYPE BANK_DTE_PP_PACKDEFCATG. "   

  CALL FUNCTION 'SAMPLE_PROCESS_0BANK010'  "
    EXPORTING
         I_APPLCATG = lv_i_applcatg
         I_STR_PARAM = lv_i_str_param
         I_PARAMNAME = lv_i_paramname
         I_STR_PACKAGE_KEY = lv_i_str_package_key
    IMPORTING
         E_LIMIT_HIGH = lv_e_limit_high
         E_LIMIT_LOW = lv_e_limit_low
         E_TAB_OBJKEY = lv_e_tab_objkey
         E_CNT_PACKAGES = lv_e_cnt_packages
         E_STR_PACKPARAM = lv_e_str_packparam
         E_FLG_NO_PACKAGE = lv_e_flg_no_package
         E_PACKDEFCATG = lv_e_packdefcatg
    EXCEPTIONS
        NOT_FOUND = 1
        FAILED = 2
. " SAMPLE_PROCESS_0BANK010




ABAP code using 7.40 inline data declarations to call FM SAMPLE_PROCESS_0BANK010

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!