SAP FEB_2_IMMO_LASTSCHR Function Module for
FEB_2_IMMO_LASTSCHR is a standard feb 2 immo lastschr 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 feb 2 immo lastschr FM, simply by entering the name FEB_2_IMMO_LASTSCHR into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVZO
Program Name: SAPLFVZO
Main Program: SAPLFVZO
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FEB_2_IMMO_LASTSCHR 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 'FEB_2_IMMO_LASTSCHR'".
EXPORTING
I_FEBEP = "
I_FEBKO = "
I_TCODE = "
I_AUGLV = "
IMPORTING
E_MSGID = "
E_MSGTY = "
E_MSGV1 = "
E_MSGV2 = "
E_MSGV3 = "
E_SUBRC = "
E_MSGNO = "
E_MSGV4 = "
TABLES
T_FEBCL = "
T_FEBRE = "
T_FTCLEAR = "
T_FTPOST = "
IMPORTING Parameters details for FEB_2_IMMO_LASTSCHR
I_FEBEP -
Data type: FEBEPOptional: No
Call by Reference: No ( called with pass by value option)
I_FEBKO -
Data type: FEBKOOptional: No
Call by Reference: No ( called with pass by value option)
I_TCODE -
Data type: SY-TCODEOptional: No
Call by Reference: No ( called with pass by value option)
I_AUGLV -
Data type: T041A-AUGLVOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FEB_2_IMMO_LASTSCHR
E_MSGID -
Data type: SY-MSGIDOptional: No
Call by Reference: No ( called with pass by value option)
E_MSGTY -
Data type: SY-MSGTYOptional: No
Call by Reference: No ( called with pass by value option)
E_MSGV1 -
Data type: SY-MSGV1Optional: No
Call by Reference: No ( called with pass by value option)
E_MSGV2 -
Data type: SY-MSGV2Optional: No
Call by Reference: No ( called with pass by value option)
E_MSGV3 -
Data type: SY-MSGV3Optional: No
Call by Reference: No ( called with pass by value option)
E_SUBRC -
Data type: SY-SUBRCOptional: No
Call by Reference: No ( called with pass by value option)
E_MSGNO -
Data type: SY-MSGNOOptional: No
Call by Reference: No ( called with pass by value option)
E_MSGV4 -
Data type: SY-MSGV4Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for FEB_2_IMMO_LASTSCHR
T_FEBCL -
Data type: FEBCLOptional: No
Call by Reference: No ( called with pass by value option)
T_FEBRE -
Data type: FEBREOptional: No
Call by Reference: No ( called with pass by value option)
T_FTCLEAR -
Data type: FTCLEAROptional: No
Call by Reference: No ( called with pass by value option)
T_FTPOST -
Data type: FTPOSTOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FEB_2_IMMO_LASTSCHR 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_e_msgid | TYPE SY-MSGID, " | |||
| lv_i_febep | TYPE FEBEP, " | |||
| lt_t_febcl | TYPE STANDARD TABLE OF FEBCL, " | |||
| lv_e_msgty | TYPE SY-MSGTY, " | |||
| lv_i_febko | TYPE FEBKO, " | |||
| lt_t_febre | TYPE STANDARD TABLE OF FEBRE, " | |||
| lv_e_msgv1 | TYPE SY-MSGV1, " | |||
| lv_i_tcode | TYPE SY-TCODE, " | |||
| lt_t_ftclear | TYPE STANDARD TABLE OF FTCLEAR, " | |||
| lv_e_msgv2 | TYPE SY-MSGV2, " | |||
| lv_i_auglv | TYPE T041A-AUGLV, " | |||
| lt_t_ftpost | TYPE STANDARD TABLE OF FTPOST, " | |||
| lv_e_msgv3 | TYPE SY-MSGV3, " | |||
| lv_e_subrc | TYPE SY-SUBRC, " | |||
| lv_e_msgno | TYPE SY-MSGNO, " | |||
| lv_e_msgv4 | TYPE SY-MSGV4. " |
|   CALL FUNCTION 'FEB_2_IMMO_LASTSCHR' " |
| EXPORTING | ||
| I_FEBEP | = lv_i_febep | |
| I_FEBKO | = lv_i_febko | |
| I_TCODE | = lv_i_tcode | |
| I_AUGLV | = lv_i_auglv | |
| IMPORTING | ||
| E_MSGID | = lv_e_msgid | |
| E_MSGTY | = lv_e_msgty | |
| E_MSGV1 | = lv_e_msgv1 | |
| E_MSGV2 | = lv_e_msgv2 | |
| E_MSGV3 | = lv_e_msgv3 | |
| E_SUBRC | = lv_e_subrc | |
| E_MSGNO | = lv_e_msgno | |
| E_MSGV4 | = lv_e_msgv4 | |
| TABLES | ||
| T_FEBCL | = lt_t_febcl | |
| T_FEBRE | = lt_t_febre | |
| T_FTCLEAR | = lt_t_ftclear | |
| T_FTPOST | = lt_t_ftpost | |
| . " FEB_2_IMMO_LASTSCHR | ||
ABAP code using 7.40 inline data declarations to call FM FEB_2_IMMO_LASTSCHR
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 MSGID FROM SY INTO @DATA(ld_e_msgid). | ||||
| "SELECT single MSGTY FROM SY INTO @DATA(ld_e_msgty). | ||||
| "SELECT single MSGV1 FROM SY INTO @DATA(ld_e_msgv1). | ||||
| "SELECT single TCODE FROM SY INTO @DATA(ld_i_tcode). | ||||
| "SELECT single MSGV2 FROM SY INTO @DATA(ld_e_msgv2). | ||||
| "SELECT single AUGLV FROM T041A INTO @DATA(ld_i_auglv). | ||||
| "SELECT single MSGV3 FROM SY INTO @DATA(ld_e_msgv3). | ||||
| "SELECT single SUBRC FROM SY INTO @DATA(ld_e_subrc). | ||||
| "SELECT single MSGNO FROM SY INTO @DATA(ld_e_msgno). | ||||
| "SELECT single MSGV4 FROM SY INTO @DATA(ld_e_msgv4). | ||||
Search for further information about these or an SAP related objects