SAP CVIV_BUPA_EVENT_FCODE_CBYREF Function Module for Function Modules to handle Fcode
CVIV_BUPA_EVENT_FCODE_CBYREF is a standard cviv bupa event fcode cbyref SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Function Modules to handle Fcode 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 cviv bupa event fcode cbyref FM, simply by entering the name CVIV_BUPA_EVENT_FCODE_CBYREF into the relevant SAP transaction such as SE37 or SE38.
Function Group: CVI_FS_UI_VEND_CBYREF_ENH
Program Name: SAPLCVI_FS_UI_VEND_CBYREF_ENH
Main Program: SAPLCVI_FS_UI_VEND_CBYREF_ENH
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CVIV_BUPA_EVENT_FCODE_CBYREF 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 'CVIV_BUPA_EVENT_FCODE_CBYREF'"Function Modules to handle Fcode.
EXPORTING
I_FCODE = "GUI Function Code
IMPORTING
E_XHANDLE = "
IMPORTING Parameters details for CVIV_BUPA_EVENT_FCODE_CBYREF
I_FCODE - GUI Function Code
Data type: TBZ4-FCODEOptional: No
Call by Reference: Yes
EXPORTING Parameters details for CVIV_BUPA_EVENT_FCODE_CBYREF
E_XHANDLE -
Data type: CLIKEOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CVIV_BUPA_EVENT_FCODE_CBYREF 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 CLIKE. " |
|   CALL FUNCTION 'CVIV_BUPA_EVENT_FCODE_CBYREF' "Function Modules to handle Fcode |
| EXPORTING | ||
| I_FCODE | = lv_i_fcode | |
| IMPORTING | ||
| E_XHANDLE | = lv_e_xhandle | |
| . " CVIV_BUPA_EVENT_FCODE_CBYREF | ||
ABAP code using 7.40 inline data declarations to call FM CVIV_BUPA_EVENT_FCODE_CBYREF
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). | ||||
Search for further information about these or an SAP related objects