SAP HR_BEN_READ_MISCEL_PLANS Function Module for









HR_BEN_READ_MISCEL_PLANS is a standard hr ben read miscel plans 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 read miscel plans FM, simply by entering the name HR_BEN_READ_MISCEL_PLANS into the relevant SAP transaction such as SE37 or SE38.

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



Function HR_BEN_READ_MISCEL_PLANS 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_READ_MISCEL_PLANS'"
  EXPORTING
   PERNR =  "
*  DESIRED_CURRENCY =  "
*  DESIRED_PERIO =  "
*  PERIO_DATE =  "
*  FILL_DETAILS = 'X' "
   REACTION =  "
*  BAREA =  "
*  PLTYP =  "
*  BPLAN =  "
*  BEGDA = '18000101' "
*  ENDDA = '99991231' "
*  LOGICVIEW = 'X' "
*  INCLUDE_LOCKED = 'X' "
*  CONSIDER_OVR = 'X' "

 IMPORTING
   SUBRC =  "

TABLES
*  PP0377 =  "
   EX_MISC_PLANS =  "
   ERROR_TABLE =  "
.



IMPORTING Parameters details for HR_BEN_READ_MISCEL_PLANS

PERNR -

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

DESIRED_CURRENCY -

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

DESIRED_PERIO -

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

PERIO_DATE -

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

FILL_DETAILS -

Data type: C
Default: 'X'
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)

BAREA -

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

PLTYP -

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

BPLAN -

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

BEGDA -

Data type: P0377-BEGDA
Default: '18000101'
Optional: Yes
Call by Reference: No ( called with pass by value option)

ENDDA -

Data type: P0377-ENDDA
Default: '99991231'
Optional: Yes
Call by Reference: No ( called with pass by value option)

LOGICVIEW -

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

INCLUDE_LOCKED -

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

CONSIDER_OVR -

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

EXPORTING Parameters details for HR_BEN_READ_MISCEL_PLANS

SUBRC -

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

TABLES Parameters details for HR_BEN_READ_MISCEL_PLANS

PP0377 -

Data type: P0377
Optional: Yes
Call by Reference: Yes

EX_MISC_PLANS -

Data type: RPBEN_DE
Optional: No
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_READ_MISCEL_PLANS 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_pernr  TYPE P0377-PERNR, "   
lv_subrc  TYPE SY-SUBRC, "   
lt_pp0377  TYPE STANDARD TABLE OF P0377, "   
lv_desired_currency  TYPE T5UD3-CURRE, "   
lv_desired_perio  TYPE T549R-ZEINH, "   
lv_perio_date  TYPE T549Q-BEGDA, "   
lv_fill_details  TYPE C, "   'X'
lv_reaction  TYPE SY-MSGTY, "   
lv_barea  TYPE P0377-BAREA, "   
lt_ex_misc_plans  TYPE STANDARD TABLE OF RPBEN_DE, "   
lv_pltyp  TYPE P0377-SUBTY, "   
lt_error_table  TYPE STANDARD TABLE OF RPBENERR, "   
lv_bplan  TYPE P0377-BPLAN, "   
lv_begda  TYPE P0377-BEGDA, "   '18000101'
lv_endda  TYPE P0377-ENDDA, "   '99991231'
lv_logicview  TYPE C, "   'X'
lv_include_locked  TYPE C, "   'X'
lv_consider_ovr  TYPE C. "   'X'

  CALL FUNCTION 'HR_BEN_READ_MISCEL_PLANS'  "
    EXPORTING
         PERNR = lv_pernr
         DESIRED_CURRENCY = lv_desired_currency
         DESIRED_PERIO = lv_desired_perio
         PERIO_DATE = lv_perio_date
         FILL_DETAILS = lv_fill_details
         REACTION = lv_reaction
         BAREA = lv_barea
         PLTYP = lv_pltyp
         BPLAN = lv_bplan
         BEGDA = lv_begda
         ENDDA = lv_endda
         LOGICVIEW = lv_logicview
         INCLUDE_LOCKED = lv_include_locked
         CONSIDER_OVR = lv_consider_ovr
    IMPORTING
         SUBRC = lv_subrc
    TABLES
         PP0377 = lt_pp0377
         EX_MISC_PLANS = lt_ex_misc_plans
         ERROR_TABLE = lt_error_table
. " HR_BEN_READ_MISCEL_PLANS




ABAP code using 7.40 inline data declarations to call FM HR_BEN_READ_MISCEL_PLANS

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 PERNR FROM P0377 INTO @DATA(ld_pernr).
 
"SELECT single SUBRC FROM SY INTO @DATA(ld_subrc).
 
 
"SELECT single CURRE FROM T5UD3 INTO @DATA(ld_desired_currency).
 
"SELECT single ZEINH FROM T549R INTO @DATA(ld_desired_perio).
 
"SELECT single BEGDA FROM T549Q INTO @DATA(ld_perio_date).
 
DATA(ld_fill_details) = 'X'.
 
"SELECT single MSGTY FROM SY INTO @DATA(ld_reaction).
 
"SELECT single BAREA FROM P0377 INTO @DATA(ld_barea).
 
 
"SELECT single SUBTY FROM P0377 INTO @DATA(ld_pltyp).
 
 
"SELECT single BPLAN FROM P0377 INTO @DATA(ld_bplan).
 
"SELECT single BEGDA FROM P0377 INTO @DATA(ld_begda).
DATA(ld_begda) = '18000101'.
 
"SELECT single ENDDA FROM P0377 INTO @DATA(ld_endda).
DATA(ld_endda) = '99991231'.
 
DATA(ld_logicview) = 'X'.
 
DATA(ld_include_locked) = 'X'.
 
DATA(ld_consider_ovr) = 'X'.
 


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!