SAP FIDT_BUPA_EVENT_SCRNC Function Module for OBSOLETE









FIDT_BUPA_EVENT_SCRNC is a standard fidt 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 for OBSOLETE 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 fidt bupa event scrnc FM, simply by entering the name FIDT_BUPA_EVENT_SCRNC into the relevant SAP transaction such as SE37 or SE38.

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



Function FIDT_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 'FIDT_BUPA_EVENT_SCRNC'"OBSOLETE
EXPORTING
I_ACTION = "Single-Character Indicator
I_VARTP_OLD = "BDT: Screen Sequence Category
I_VARNR_OLD = "BDT: Screen Sequence
I_POSNR_OLD = "Item Number (for Sequence)
I_VARTP_NEW = "BDT: Screen Sequence Category
I_VARNR_NEW = "BDT: Screen Sequence
I_POSNR_NEW = "Item Number (for Sequence)
.



IMPORTING Parameters details for FIDT_BUPA_EVENT_SCRNC

I_ACTION - Single-Character Indicator

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

I_VARTP_OLD - BDT: Screen Sequence Category

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

I_VARNR_OLD - BDT: Screen Sequence

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

I_POSNR_OLD - Item Number (for Sequence)

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

I_VARTP_NEW - BDT: Screen Sequence Category

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

I_VARNR_NEW - BDT: Screen Sequence

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

I_POSNR_NEW - Item Number (for Sequence)

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

Copy and paste ABAP code example for FIDT_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_varnr_old  TYPE TBZ3N-VARNR, "   
lv_i_posnr_old  TYPE TBZ3K-POSNR, "   
lv_i_vartp_new  TYPE TBZ3N-VARTP, "   
lv_i_varnr_new  TYPE TBZ3N-VARNR, "   
lv_i_posnr_new  TYPE TBZ3K-POSNR. "   

  CALL FUNCTION 'FIDT_BUPA_EVENT_SCRNC'  "OBSOLETE
    EXPORTING
         I_ACTION = lv_i_action
         I_VARTP_OLD = lv_i_vartp_old
         I_VARNR_OLD = lv_i_varnr_old
         I_POSNR_OLD = lv_i_posnr_old
         I_VARTP_NEW = lv_i_vartp_new
         I_VARNR_NEW = lv_i_varnr_new
         I_POSNR_NEW = lv_i_posnr_new
. " FIDT_BUPA_EVENT_SCRNC




ABAP code using 7.40 inline data declarations to call FM FIDT_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 VARNR FROM TBZ3N INTO @DATA(ld_i_varnr_old).
 
"SELECT single POSNR FROM TBZ3K INTO @DATA(ld_i_posnr_old).
 
"SELECT single VARTP FROM TBZ3N INTO @DATA(ld_i_vartp_new).
 
"SELECT single VARNR FROM TBZ3N INTO @DATA(ld_i_varnr_new).
 
"SELECT single POSNR FROM TBZ3K INTO @DATA(ld_i_posnr_new).
 


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!