SAP RH_PM_RECLASS_RULES_GET Function Module for









RH_PM_RECLASS_RULES_GET is a standard rh pm reclass rules get 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 rh pm reclass rules get FM, simply by entering the name RH_PM_RECLASS_RULES_GET into the relevant SAP transaction such as SE37 or SE38.

Function Group: RHBC_2
Program Name: SAPLRHBC_2
Main Program:
Appliation area: H
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function RH_PM_RECLASS_RULES_GET 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 'RH_PM_RECLASS_RULES_GET'"
  EXPORTING
   PD_PLVAR =  "
*  PD_OTYPE = 'BU' "
   PD_OBJID =  "
*  PD_BEGDA = '19000101' "
*  PD_ENDDA = '99991231' "
*  PD_ISTAT = '1' "
*  PD_OPEN_RULES =  "
*  PD_ACTIVATED_RULES = 'X' "

TABLES
*  PT_1506_NEG_INT =  "
*  PT_1506_NEG_EXT =  "
*  PT_1506_POS_INT =  "
*  PT_1506_POS_EXT =  "

EXCEPTIONS
   NOTHING_FOUND = 1
.



IMPORTING Parameters details for RH_PM_RECLASS_RULES_GET

PD_PLVAR -

Data type: P1000-PLVAR
Optional: No
Call by Reference: Yes

PD_OTYPE -

Data type: P1000-OTYPE
Default: 'BU'
Optional: Yes
Call by Reference: Yes

PD_OBJID -

Data type: P1000-OBJID
Optional: No
Call by Reference: Yes

PD_BEGDA -

Data type: P1000-BEGDA
Default: '19000101'
Optional: Yes
Call by Reference: Yes

PD_ENDDA -

Data type: P1000-ENDDA
Default: '99991231'
Optional: Yes
Call by Reference: Yes

PD_ISTAT -

Data type: P1000-ISTAT
Default: '1'
Optional: Yes
Call by Reference: Yes

PD_OPEN_RULES -

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

PD_ACTIVATED_RULES -

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

TABLES Parameters details for RH_PM_RECLASS_RULES_GET

PT_1506_NEG_INT -

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

PT_1506_NEG_EXT -

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

PT_1506_POS_INT -

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

PT_1506_POS_EXT -

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

EXCEPTIONS details

NOTHING_FOUND -

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

Copy and paste ABAP code example for RH_PM_RECLASS_RULES_GET 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_pd_plvar  TYPE P1000-PLVAR, "   
lv_nothing_found  TYPE P1000, "   
lt_pt_1506_neg_int  TYPE STANDARD TABLE OF P1506, "   
lv_pd_otype  TYPE P1000-OTYPE, "   'BU'
lt_pt_1506_neg_ext  TYPE STANDARD TABLE OF P1506, "   
lv_pd_objid  TYPE P1000-OBJID, "   
lt_pt_1506_pos_int  TYPE STANDARD TABLE OF P1506, "   
lv_pd_begda  TYPE P1000-BEGDA, "   '19000101'
lt_pt_1506_pos_ext  TYPE STANDARD TABLE OF P1506, "   
lv_pd_endda  TYPE P1000-ENDDA, "   '99991231'
lv_pd_istat  TYPE P1000-ISTAT, "   '1'
lv_pd_open_rules  TYPE SY-BINPT, "   
lv_pd_activated_rules  TYPE SY-BINPT. "   'X'

  CALL FUNCTION 'RH_PM_RECLASS_RULES_GET'  "
    EXPORTING
         PD_PLVAR = lv_pd_plvar
         PD_OTYPE = lv_pd_otype
         PD_OBJID = lv_pd_objid
         PD_BEGDA = lv_pd_begda
         PD_ENDDA = lv_pd_endda
         PD_ISTAT = lv_pd_istat
         PD_OPEN_RULES = lv_pd_open_rules
         PD_ACTIVATED_RULES = lv_pd_activated_rules
    TABLES
         PT_1506_NEG_INT = lt_pt_1506_neg_int
         PT_1506_NEG_EXT = lt_pt_1506_neg_ext
         PT_1506_POS_INT = lt_pt_1506_pos_int
         PT_1506_POS_EXT = lt_pt_1506_pos_ext
    EXCEPTIONS
        NOTHING_FOUND = 1
. " RH_PM_RECLASS_RULES_GET




ABAP code using 7.40 inline data declarations to call FM RH_PM_RECLASS_RULES_GET

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 PLVAR FROM P1000 INTO @DATA(ld_pd_plvar).
 
 
 
"SELECT single OTYPE FROM P1000 INTO @DATA(ld_pd_otype).
DATA(ld_pd_otype) = 'BU'.
 
 
"SELECT single OBJID FROM P1000 INTO @DATA(ld_pd_objid).
 
 
"SELECT single BEGDA FROM P1000 INTO @DATA(ld_pd_begda).
DATA(ld_pd_begda) = '19000101'.
 
 
"SELECT single ENDDA FROM P1000 INTO @DATA(ld_pd_endda).
DATA(ld_pd_endda) = '99991231'.
 
"SELECT single ISTAT FROM P1000 INTO @DATA(ld_pd_istat).
DATA(ld_pd_istat) = '1'.
 
"SELECT single BINPT FROM SY INTO @DATA(ld_pd_open_rules).
 
"SELECT single BINPT FROM SY INTO @DATA(ld_pd_activated_rules).
DATA(ld_pd_activated_rules) = '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!