SAP RHPE_POPUP_CLASSIFICATION Function Module for Dialog Box: Qualification Group









RHPE_POPUP_CLASSIFICATION is a standard rhpe popup classification SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Dialog Box: Qualification Group processing and below is the pattern details for this FM, 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 rhpe popup classification FM, simply by entering the name RHPE_POPUP_CLASSIFICATION into the relevant SAP transaction such as SE37 or SE38.

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



Function RHPE_POPUP_CLASSIFICATION 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 'RHPE_POPUP_CLASSIFICATION'"Dialog Box: Qualification Group
EXPORTING
PLVAR = "Plan Version
* OBJID = "Object ID
* BEGDA = SY-DATUM "Start Date
* ENDDA = SY-DATUM "End Date
* BASE_OTYPE = "
* BASE_OBJID = "
* MAINTAIN = ' ' "
* X1 = 30 "
* Y1 = 1 "

IMPORTING
MODIFIED = "

TABLES
* NEW_OBJECTS = "

EXCEPTIONS
NOT_FOUND = 1 WRONG_DATE = 2
.



IMPORTING Parameters details for RHPE_POPUP_CLASSIFICATION

PLVAR - Plan Version

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

OBJID - Object ID

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

BEGDA - Start Date

Data type: HRP1000-BEGDA
Default: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)

ENDDA - End Date

Data type: HRP1000-ENDDA
Default: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)

BASE_OTYPE -

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

BASE_OBJID -

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

MAINTAIN -

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

X1 -

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

Y1 -

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

EXPORTING Parameters details for RHPE_POPUP_CLASSIFICATION

MODIFIED -

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

TABLES Parameters details for RHPE_POPUP_CLASSIFICATION

NEW_OBJECTS -

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

EXCEPTIONS details

NOT_FOUND - Not Found

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

WRONG_DATE - Error in date

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

Copy and paste ABAP code example for RHPE_POPUP_CLASSIFICATION 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_plvar  TYPE HRP1000-PLVAR, "   
lv_modified  TYPE SY-INPUT, "   
lv_not_found  TYPE SY, "   
lt_new_objects  TYPE STANDARD TABLE OF HROBJECT, "   
lv_objid  TYPE HRP1000-OBJID, "   
lv_wrong_date  TYPE HRP1000, "   
lv_begda  TYPE HRP1000-BEGDA, "   SY-DATUM
lv_endda  TYPE HRP1000-ENDDA, "   SY-DATUM
lv_base_otype  TYPE HRP1000-OTYPE, "   
lv_base_objid  TYPE HRP1000-OBJID, "   
lv_maintain  TYPE SY-INPUT, "   ' '
lv_x1  TYPE SY-CUCOL, "   30
lv_y1  TYPE SY-CUROW. "   1

  CALL FUNCTION 'RHPE_POPUP_CLASSIFICATION'  "Dialog Box: Qualification Group
    EXPORTING
         PLVAR = lv_plvar
         OBJID = lv_objid
         BEGDA = lv_begda
         ENDDA = lv_endda
         BASE_OTYPE = lv_base_otype
         BASE_OBJID = lv_base_objid
         MAINTAIN = lv_maintain
         X1 = lv_x1
         Y1 = lv_y1
    IMPORTING
         MODIFIED = lv_modified
    TABLES
         NEW_OBJECTS = lt_new_objects
    EXCEPTIONS
        NOT_FOUND = 1
        WRONG_DATE = 2
. " RHPE_POPUP_CLASSIFICATION




ABAP code using 7.40 inline data declarations to call FM RHPE_POPUP_CLASSIFICATION

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 HRP1000 INTO @DATA(ld_plvar).
 
"SELECT single INPUT FROM SY INTO @DATA(ld_modified).
 
 
 
"SELECT single OBJID FROM HRP1000 INTO @DATA(ld_objid).
 
 
"SELECT single BEGDA FROM HRP1000 INTO @DATA(ld_begda).
DATA(ld_begda) = SY-DATUM.
 
"SELECT single ENDDA FROM HRP1000 INTO @DATA(ld_endda).
DATA(ld_endda) = SY-DATUM.
 
"SELECT single OTYPE FROM HRP1000 INTO @DATA(ld_base_otype).
 
"SELECT single OBJID FROM HRP1000 INTO @DATA(ld_base_objid).
 
"SELECT single INPUT FROM SY INTO @DATA(ld_maintain).
DATA(ld_maintain) = ' '.
 
"SELECT single CUCOL FROM SY INTO @DATA(ld_x1).
DATA(ld_x1) = 30.
 
"SELECT single CUROW FROM SY INTO @DATA(ld_y1).
DATA(ld_y1) = 1.
 


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!