SAP FMSNRULE_GET_LIFE_CYCLE_MAIN Function Module for









FMSNRULE_GET_LIFE_CYCLE_MAIN is a standard fmsnrule get life cycle main 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 fmsnrule get life cycle main FM, simply by entering the name FMSNRULE_GET_LIFE_CYCLE_MAIN into the relevant SAP transaction such as SE37 or SE38.

Function Group: FMWH
Program Name: SAPLFMWH
Main Program: SAPLFMWH
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function FMSNRULE_GET_LIFE_CYCLE_MAIN 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 'FMSNRULE_GET_LIFE_CYCLE_MAIN'"
EXPORTING
IP_FIKRS = "
IP_GJAHR = "

TABLES
* T_FMSNRULE = "
T_FMSNRULE_LIFE_NESTED = "
* R_VFIPEX = "
* R_VFONDS = "
* R_VFICTR = "
* R_DATAB = "
* R_AENNAME = "
* R_DBACTION = "
* R_TACTION = "
.



IMPORTING Parameters details for FMSNRULE_GET_LIFE_CYCLE_MAIN

IP_FIKRS -

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

IP_GJAHR -

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

TABLES Parameters details for FMSNRULE_GET_LIFE_CYCLE_MAIN

T_FMSNRULE -

Data type: FMSNRULE
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_FMSNRULE_LIFE_NESTED -

Data type: FMWH_T_FMSNRULE_LIFE_NESTED
Optional: No
Call by Reference: No ( called with pass by value option)

R_VFIPEX -

Data type: RANGE_C24
Optional: Yes
Call by Reference: No ( called with pass by value option)

R_VFONDS -

Data type: RANGE_C10
Optional: Yes
Call by Reference: No ( called with pass by value option)

R_VFICTR -

Data type: RANGE_C16
Optional: Yes
Call by Reference: No ( called with pass by value option)

R_DATAB -

Data type: RANGE_C16
Optional: Yes
Call by Reference: No ( called with pass by value option)

R_AENNAME -

Data type: RANGE_C12
Optional: Yes
Call by Reference: No ( called with pass by value option)

R_DBACTION -

Data type: RANGE_C1
Optional: Yes
Call by Reference: No ( called with pass by value option)

R_TACTION -

Data type: RANGE_C1
Optional: Yes
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for FMSNRULE_GET_LIFE_CYCLE_MAIN 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_ip_fikrs  TYPE FM01-FIKRS, "   
lt_t_fmsnrule  TYPE STANDARD TABLE OF FMSNRULE, "   
lv_ip_gjahr  TYPE FMUDRULE-GJAHR, "   
lt_t_fmsnrule_life_nested  TYPE STANDARD TABLE OF FMWH_T_FMSNRULE_LIFE_NESTED, "   
lt_r_vfipex  TYPE STANDARD TABLE OF RANGE_C24, "   
lt_r_vfonds  TYPE STANDARD TABLE OF RANGE_C10, "   
lt_r_vfictr  TYPE STANDARD TABLE OF RANGE_C16, "   
lt_r_datab  TYPE STANDARD TABLE OF RANGE_C16, "   
lt_r_aenname  TYPE STANDARD TABLE OF RANGE_C12, "   
lt_r_dbaction  TYPE STANDARD TABLE OF RANGE_C1, "   
lt_r_taction  TYPE STANDARD TABLE OF RANGE_C1. "   

  CALL FUNCTION 'FMSNRULE_GET_LIFE_CYCLE_MAIN'  "
    EXPORTING
         IP_FIKRS = lv_ip_fikrs
         IP_GJAHR = lv_ip_gjahr
    TABLES
         T_FMSNRULE = lt_t_fmsnrule
         T_FMSNRULE_LIFE_NESTED = lt_t_fmsnrule_life_nested
         R_VFIPEX = lt_r_vfipex
         R_VFONDS = lt_r_vfonds
         R_VFICTR = lt_r_vfictr
         R_DATAB = lt_r_datab
         R_AENNAME = lt_r_aenname
         R_DBACTION = lt_r_dbaction
         R_TACTION = lt_r_taction
. " FMSNRULE_GET_LIFE_CYCLE_MAIN




ABAP code using 7.40 inline data declarations to call FM FMSNRULE_GET_LIFE_CYCLE_MAIN

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 FIKRS FROM FM01 INTO @DATA(ld_ip_fikrs).
 
 
"SELECT single GJAHR FROM FMUDRULE INTO @DATA(ld_ip_gjahr).
 
 
 
 
 
 
 
 
 


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!