SAP CRM_ISM_BUPA_EVENT_SCRNC Function Module for
CRM_ISM_BUPA_EVENT_SCRNC is a standard crm ism bupa event scrnc 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 crm ism bupa event scrnc FM, simply by entering the name CRM_ISM_BUPA_EVENT_SCRNC into the relevant SAP transaction such as SE37 or SE38.
Function Group: CRM_BUPA_ISM_DIALOG
Program Name: SAPLCRM_BUPA_ISM_DIALOG
Main Program: SAPLCRM_BUPA_ISM_DIALOG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CRM_ISM_BUPA_EVENT_SCRNC 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 'CRM_ISM_BUPA_EVENT_SCRNC'".
EXPORTING
I_ACTION = "Action
I_VARTP_OLD = "
I_VARTP_NEW = "
IMPORTING Parameters details for CRM_ISM_BUPA_EVENT_SCRNC
I_ACTION - Action
Data type: BUS000FLDS-CHAR1Optional: No
Call by Reference: Yes
I_VARTP_OLD -
Data type: TBZ3N-VARTPOptional: No
Call by Reference: Yes
I_VARTP_NEW -
Data type: TBZ3N-VARTPOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CRM_ISM_BUPA_EVENT_SCRNC 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_action | TYPE BUS000FLDS-CHAR1, " | |||
lv_i_vartp_old | TYPE TBZ3N-VARTP, " | |||
lv_i_vartp_new | TYPE TBZ3N-VARTP. " |
  CALL FUNCTION 'CRM_ISM_BUPA_EVENT_SCRNC' " |
EXPORTING | ||
I_ACTION | = lv_i_action | |
I_VARTP_OLD | = lv_i_vartp_old | |
I_VARTP_NEW | = lv_i_vartp_new | |
. " CRM_ISM_BUPA_EVENT_SCRNC |
ABAP code using 7.40 inline data declarations to call FM CRM_ISM_BUPA_EVENT_SCRNC
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 CHAR1 FROM BUS000FLDS INTO @DATA(ld_i_action). | ||||
"SELECT single VARTP FROM TBZ3N INTO @DATA(ld_i_vartp_old). | ||||
"SELECT single VARTP FROM TBZ3N INTO @DATA(ld_i_vartp_new). | ||||
Search for further information about these or an SAP related objects