SAP BANK_API_IFPP_GENERATE_APPL Function Module for
BANK_API_IFPP_GENERATE_APPL is a standard bank api ifpp generate appl 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 bank api ifpp generate appl FM, simply by entering the name BANK_API_IFPP_GENERATE_APPL into the relevant SAP transaction such as SE37 or SE38.
Function Group: BANK_API_IF_PP
Program Name: SAPLBANK_API_IF_PP
Main Program: SAPLBANK_API_IF_PP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function BANK_API_IFPP_GENERATE_APPL 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 'BANK_API_IFPP_GENERATE_APPL'".
EXPORTING
I_APPLCATG = "Application Type in Parallel Processing
* I_FLG_TRANSPORT = 'X' "
* I_CORRNO = "Request/Task
* I_FLG_CUST_APPL = 'X' "
I_TAPPLCATG = "Description of a Parallel Processing Application
* I_APPLPARAMTYPE = "Name of DDIC Structure of Application-Specific Parameters
* I_PARAMTABNAME = "DDIC Table Type Name for Appl.- Specific Package Data
* I_LOGOBJ = "Application log: Object name (Application code)
I_PREFIX = "
I_FPOOL = "
* I_NAME' ' = "Namespace
* I_RNG_METHODS = "
EXCEPTIONS
APPL_EXISTS = 1 FMOD_GEN_ERROR = 2 TRANSPORT_ORDER_FAILED = 3
IMPORTING Parameters details for BANK_API_IFPP_GENERATE_APPL
I_APPLCATG - Application Type in Parallel Processing
Data type: BANK_DTE_PP_PAAPPLCATGOptional: No
Call by Reference: Yes
I_FLG_TRANSPORT -
Data type: XFELDDefault: 'X'
Optional: Yes
Call by Reference: Yes
I_CORRNO - Request/Task
Data type: TRKORROptional: Yes
Call by Reference: Yes
I_FLG_CUST_APPL -
Data type: XFELDDefault: 'X'
Optional: Yes
Call by Reference: Yes
I_TAPPLCATG - Description of a Parallel Processing Application
Data type: BANK_DTE_PP_TPAAPLLCATGOptional: No
Call by Reference: Yes
I_APPLPARAMTYPE - Name of DDIC Structure of Application-Specific Parameters
Data type: BANK_DTE_PP_APPLPARAMTYPEOptional: Yes
Call by Reference: Yes
I_PARAMTABNAME - DDIC Table Type Name for Appl.- Specific Package Data
Data type: BANK_DTE_PP_PACKPARAMTYPEOptional: Yes
Call by Reference: Yes
I_LOGOBJ - Application log: Object name (Application code)
Data type: BALOBJ_DOptional: Yes
Call by Reference: Yes
I_PREFIX -
Data type: CHAR20Optional: No
Call by Reference: Yes
I_FPOOL -
Data type: RS38L-AREAOptional: No
Call by Reference: Yes
I_NAMESPACE - Namespace
Data type: RS38L-NAMESPACEOptional: Yes
Call by Reference: Yes
I_RNG_METHODS -
Data type: BANK_RNG_PP_METHODSOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
APPL_EXISTS -
Data type:Optional: No
Call by Reference: Yes
FMOD_GEN_ERROR -
Data type:Optional: No
Call by Reference: Yes
TRANSPORT_ORDER_FAILED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for BANK_API_IFPP_GENERATE_APPL 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_appl_exists | TYPE BANK_DTE_PP_PAAPPLCATG, " | |||
lv_i_flg_transport | TYPE XFELD, " 'X' | |||
lv_i_corrno | TYPE TRKORR, " | |||
lv_i_flg_cust_appl | TYPE XFELD, " 'X' | |||
lv_i_tapplcatg | TYPE BANK_DTE_PP_TPAAPLLCATG, " | |||
lv_fmod_gen_error | TYPE BANK_DTE_PP_TPAAPLLCATG, " | |||
lv_i_applparamtype | TYPE BANK_DTE_PP_APPLPARAMTYPE, " | |||
lv_transport_order_failed | TYPE BANK_DTE_PP_APPLPARAMTYPE, " | |||
lv_i_paramtabname | TYPE BANK_DTE_PP_PACKPARAMTYPE, " | |||
lv_i_logobj | TYPE BALOBJ_D, " | |||
lv_i_prefix | TYPE CHAR20, " | |||
lv_i_fpool | TYPE RS38L-AREA, " | |||
lv_i_namespace | TYPE RS38L-NAMESPACE, " | |||
lv_i_rng_methods | TYPE BANK_RNG_PP_METHODS. " |
  CALL FUNCTION 'BANK_API_IFPP_GENERATE_APPL' " |
EXPORTING | ||
I_APPLCATG | = lv_i_applcatg | |
I_FLG_TRANSPORT | = lv_i_flg_transport | |
I_CORRNO | = lv_i_corrno | |
I_FLG_CUST_APPL | = lv_i_flg_cust_appl | |
I_TAPPLCATG | = lv_i_tapplcatg | |
I_APPLPARAMTYPE | = lv_i_applparamtype | |
I_PARAMTABNAME | = lv_i_paramtabname | |
I_LOGOBJ | = lv_i_logobj | |
I_PREFIX | = lv_i_prefix | |
I_FPOOL | = lv_i_fpool | |
I_NAMESPACE | = lv_i_namespace | |
I_RNG_METHODS | = lv_i_rng_methods | |
EXCEPTIONS | ||
APPL_EXISTS = 1 | ||
FMOD_GEN_ERROR = 2 | ||
TRANSPORT_ORDER_FAILED = 3 | ||
. " BANK_API_IFPP_GENERATE_APPL |
ABAP code using 7.40 inline data declarations to call FM BANK_API_IFPP_GENERATE_APPL
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.DATA(ld_i_flg_transport) | = 'X'. | |||
DATA(ld_i_flg_cust_appl) | = 'X'. | |||
"SELECT single AREA FROM RS38L INTO @DATA(ld_i_fpool). | ||||
"SELECT single NAMESPACE FROM RS38L INTO @DATA(ld_i_namespace). | ||||
Search for further information about these or an SAP related objects