SAP HR_BEN_DISPLAY_SAVING_PLAN Function Module for









HR_BEN_DISPLAY_SAVING_PLAN is a standard hr ben display saving plan 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 hr ben display saving plan FM, simply by entering the name HR_BEN_DISPLAY_SAVING_PLAN into the relevant SAP transaction such as SE37 or SE38.

Function Group: HRBEN00ENROLLMENT
Program Name: SAPLHRBEN00ENROLLMENT
Main Program:
Appliation area: P
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function HR_BEN_DISPLAY_SAVING_PLAN 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 'HR_BEN_DISPLAY_SAVING_PLAN'"
EXPORTING
* CURRENT_PLAN_SELEC = "
* EVENT_DESCRIPTION = "
* ITS_COMPATIBLE = ' ' "
REACTION = "

IMPORTING
NEW_PLAN_SELEC = "
ITS_EXIT = "
SUBRC = "

TABLES
PLAN_OFFER = "
BEN_OFFER = "
INV_OFFER = "
* CURRENT_BEN_SELEC = "
* CURRENT_INV_SELEC = "
* NEW_BEN_SELEC = "
* NEW_INV_SELEC = "
ERROR_TABLE = "
.



IMPORTING Parameters details for HR_BEN_DISPLAY_SAVING_PLAN

CURRENT_PLAN_SELEC -

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

EVENT_DESCRIPTION -

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

ITS_COMPATIBLE -

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

REACTION -

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

EXPORTING Parameters details for HR_BEN_DISPLAY_SAVING_PLAN

NEW_PLAN_SELEC -

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

ITS_EXIT -

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

SUBRC -

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

TABLES Parameters details for HR_BEN_DISPLAY_SAVING_PLAN

PLAN_OFFER -

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

BEN_OFFER -

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

INV_OFFER -

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

CURRENT_BEN_SELEC -

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

CURRENT_INV_SELEC -

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

NEW_BEN_SELEC -

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

NEW_INV_SELEC -

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

ERROR_TABLE -

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

Copy and paste ABAP code example for HR_BEN_DISPLAY_SAVING_PLAN 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:
lt_plan_offer  TYPE STANDARD TABLE OF RPBEN_OC, "   
lv_new_plan_selec  TYPE RPBEN_SC, "   
lv_current_plan_selec  TYPE RPBEN_SC, "   
lv_its_exit  TYPE C, "   
lt_ben_offer  TYPE STANDARD TABLE OF RPBENOBF, "   
lv_event_description  TYPE RPBENEVENT, "   
lv_subrc  TYPE SY-SUBRC, "   
lt_inv_offer  TYPE STANDARD TABLE OF RPBENOIV, "   
lv_its_compatible  TYPE C, "   ' '
lv_reaction  TYPE SY-MSGTY, "   
lt_current_ben_selec  TYPE STANDARD TABLE OF RPBENSBF, "   
lt_current_inv_selec  TYPE STANDARD TABLE OF RPBENSIV, "   
lt_new_ben_selec  TYPE STANDARD TABLE OF RPBENSBF, "   
lt_new_inv_selec  TYPE STANDARD TABLE OF RPBENSIV, "   
lt_error_table  TYPE STANDARD TABLE OF RPBENERR. "   

  CALL FUNCTION 'HR_BEN_DISPLAY_SAVING_PLAN'  "
    EXPORTING
         CURRENT_PLAN_SELEC = lv_current_plan_selec
         EVENT_DESCRIPTION = lv_event_description
         ITS_COMPATIBLE = lv_its_compatible
         REACTION = lv_reaction
    IMPORTING
         NEW_PLAN_SELEC = lv_new_plan_selec
         ITS_EXIT = lv_its_exit
         SUBRC = lv_subrc
    TABLES
         PLAN_OFFER = lt_plan_offer
         BEN_OFFER = lt_ben_offer
         INV_OFFER = lt_inv_offer
         CURRENT_BEN_SELEC = lt_current_ben_selec
         CURRENT_INV_SELEC = lt_current_inv_selec
         NEW_BEN_SELEC = lt_new_ben_selec
         NEW_INV_SELEC = lt_new_inv_selec
         ERROR_TABLE = lt_error_table
. " HR_BEN_DISPLAY_SAVING_PLAN




ABAP code using 7.40 inline data declarations to call FM HR_BEN_DISPLAY_SAVING_PLAN

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 SUBRC FROM SY INTO @DATA(ld_subrc).
 
 
DATA(ld_its_compatible) = ' '.
 
"SELECT single MSGTY FROM SY INTO @DATA(ld_reaction).
 
 
 
 
 
 


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!