SAP FSBP_BUPA_EVENT_FCODE Function Module for
FSBP_BUPA_EVENT_FCODE is a standard fsbp bupa event fcode 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 fsbp bupa event fcode FM, simply by entering the name FSBP_BUPA_EVENT_FCODE into the relevant SAP transaction such as SE37 or SE38.
Function Group: FS_BP_BDT_EVENTS
Program Name: SAPLFS_BP_BDT_EVENTS
Main Program: SAPLFS_BP_BDT_EVENTS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function FSBP_BUPA_EVENT_FCODE 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 'FSBP_BUPA_EVENT_FCODE'".
EXPORTING
* I_FCODE = "
* I_CRSFIELD = "
* I_CRSLINE = "
IMPORTING
E_XHANDLE = "
IMPORTING Parameters details for FSBP_BUPA_EVENT_FCODE
I_FCODE -
Data type: TBZ4-FCODEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_CRSFIELD -
Data type: BUS000TBFL-TBFLDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_CRSLINE -
Data type: SY-LILLIOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FSBP_BUPA_EVENT_FCODE
E_XHANDLE -
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FSBP_BUPA_EVENT_FCODE 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_fcode | TYPE TBZ4-FCODE, " | |||
lv_e_xhandle | TYPE C, " | |||
lv_i_crsfield | TYPE BUS000TBFL-TBFLD, " | |||
lv_i_crsline | TYPE SY-LILLI. " |
  CALL FUNCTION 'FSBP_BUPA_EVENT_FCODE' " |
EXPORTING | ||
I_FCODE | = lv_i_fcode | |
I_CRSFIELD | = lv_i_crsfield | |
I_CRSLINE | = lv_i_crsline | |
IMPORTING | ||
E_XHANDLE | = lv_e_xhandle | |
. " FSBP_BUPA_EVENT_FCODE |
ABAP code using 7.40 inline data declarations to call FM FSBP_BUPA_EVENT_FCODE
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."SELECT single FCODE FROM TBZ4 INTO @DATA(ld_i_fcode). | ||||
"SELECT single TBFLD FROM BUS000TBFL INTO @DATA(ld_i_crsfield). | ||||
"SELECT single LILLI FROM SY INTO @DATA(ld_i_crsline). | ||||
Search for further information about these or an SAP related objects