SAP RHPP_R_PROFILE_READ Function Module for Read requirements profile









RHPP_R_PROFILE_READ is a standard rhpp r profile read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read requirements profile 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 rhpp r profile read FM, simply by entering the name RHPP_R_PROFILE_READ into the relevant SAP transaction such as SE37 or SE38.

Function Group: RHPP
Program Name: SAPLRHPP
Main Program: SAPLRHPP
Appliation area: H
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function RHPP_R_PROFILE_READ 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 'RHPP_R_PROFILE_READ'"Read requirements profile
  EXPORTING
*  BEGDA = SY-DATUM "Start Date
*  ENDDA = SY-DATUM "End Date
*  WITH_STEXT = 'X' "
*  WITH_QK_INFO = 'X' "
*  CHECK_NOTE = ' ' "

TABLES
   OBJECTS =  "
*  ERR_OBJECTS =  "
   PROFILE =  "

EXCEPTIONS
   NO_AUTHORITY = 1    WRONG_OTYPE = 2    OBJECT_NOT_FOUND = 3    UNDEFINED = 4
.



IMPORTING Parameters details for RHPP_R_PROFILE_READ

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)

WITH_STEXT -

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

WITH_QK_INFO -

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

CHECK_NOTE -

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

TABLES Parameters details for RHPP_R_PROFILE_READ

OBJECTS -

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

ERR_OBJECTS -

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

PROFILE -

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

EXCEPTIONS details

NO_AUTHORITY -

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

WRONG_OTYPE - Unauth. object type

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

OBJECT_NOT_FOUND - Object does not exist

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

UNDEFINED -

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

Copy and paste ABAP code example for RHPP_R_PROFILE_READ 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_begda  TYPE HRP1000-BEGDA, "   SY-DATUM
lt_objects  TYPE STANDARD TABLE OF HRSOBID, "   
lv_no_authority  TYPE HRSOBID, "   
lv_endda  TYPE HRP1000-ENDDA, "   SY-DATUM
lt_err_objects  TYPE STANDARD TABLE OF HRSOBID, "   
lv_wrong_otype  TYPE HRSOBID, "   
lt_profile  TYPE STANDARD TABLE OF HRPE_PROFQ, "   
lv_with_stext  TYPE CHAR1, "   'X'
lv_object_not_found  TYPE CHAR1, "   
lv_undefined  TYPE CHAR1, "   
lv_with_qk_info  TYPE CHAR1, "   'X'
lv_check_note  TYPE CHAR1. "   ' '

  CALL FUNCTION 'RHPP_R_PROFILE_READ'  "Read requirements profile
    EXPORTING
         BEGDA = lv_begda
         ENDDA = lv_endda
         WITH_STEXT = lv_with_stext
         WITH_QK_INFO = lv_with_qk_info
         CHECK_NOTE = lv_check_note
    TABLES
         OBJECTS = lt_objects
         ERR_OBJECTS = lt_err_objects
         PROFILE = lt_profile
    EXCEPTIONS
        NO_AUTHORITY = 1
        WRONG_OTYPE = 2
        OBJECT_NOT_FOUND = 3
        UNDEFINED = 4
. " RHPP_R_PROFILE_READ




ABAP code using 7.40 inline data declarations to call FM RHPP_R_PROFILE_READ

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 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.
 
 
 
 
DATA(ld_with_stext) = 'X'.
 
 
 
DATA(ld_with_qk_info) = 'X'.
 
DATA(ld_check_note) = ' '.
 


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!