SAP RHPP_SHOW_PROFILE Function Module for
RHPP_SHOW_PROFILE is a standard rhpp show profile 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 rhpp show profile FM, simply by entering the name RHPP_SHOW_PROFILE 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): Normal Function Module
Update:

Function RHPP_SHOW_PROFILE 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_SHOW_PROFILE'".
EXPORTING
* PLVAR = "Plan Version
* OBJECTMANAGER = ' ' "
* NO_PUBLISHING = ' ' "
* OBJECT_AUTHORITY = 'X' "Indicator: Authorization
* OTYPE = 'P ' "Object type
* OBJID = "Object ID
* BEGDA = SY-DATUM "Start Date
* ENDDA = '99991231' "End Date
* MAINTAIN = 'X' "
* COMMIT_FLG = 'X' "
* FIRST_DYNNR = "
* FIRST_REPID = "
IMPORTING
LAST_OTYPE = "
LAST_OBJID = "
CHANGING
* CHANGED_WITHOUT_COMMIT = "
EXCEPTIONS
NO_AUTHORITY = 1 NOT_FOUND = 2
IMPORTING Parameters details for RHPP_SHOW_PROFILE
PLVAR - Plan Version
Data type: P1000-PLVAROptional: Yes
Call by Reference: No ( called with pass by value option)
OBJECTMANAGER -
Data type: CHAR1Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
NO_PUBLISHING -
Data type: CHAR1Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
OBJECT_AUTHORITY - Indicator: Authorization
Data type: HRRHAS-AUTHYDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
OTYPE - Object type
Data type: P1000-OTYPEDefault: 'P '
Optional: Yes
Call by Reference: No ( called with pass by value option)
OBJID - Object ID
Data type: OBJEC-REALOOptional: Yes
Call by Reference: No ( called with pass by value option)
BEGDA - Start Date
Data type: P1000-BEGDADefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
ENDDA - End Date
Data type: P1000-ENDDADefault: '99991231'
Optional: Yes
Call by Reference: No ( called with pass by value option)
MAINTAIN -
Data type: CHAR1Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
COMMIT_FLG -
Data type: HRRHAP-COMMIT_FLGDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
FIRST_DYNNR -
Data type: SY-DYNNROptional: Yes
Call by Reference: No ( called with pass by value option)
FIRST_REPID -
Data type: SY-REPIDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RHPP_SHOW_PROFILE
LAST_OTYPE -
Data type: P1000-OTYPEOptional: No
Call by Reference: No ( called with pass by value option)
LAST_OBJID -
Data type: OBJEC-REALOOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for RHPP_SHOW_PROFILE
CHANGED_WITHOUT_COMMIT -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_AUTHORITY - No Authorization
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_FOUND - Object Not Found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RHPP_SHOW_PROFILE 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 P1000-PLVAR, " | |||
| lv_last_otype | TYPE P1000-OTYPE, " | |||
| lv_no_authority | TYPE P1000, " | |||
| lv_changed_without_commit | TYPE P1000, " | |||
| lv_objectmanager | TYPE CHAR1, " ' ' | |||
| lv_no_publishing | TYPE CHAR1, " ' ' | |||
| lv_object_authority | TYPE HRRHAS-AUTHY, " 'X' | |||
| lv_otype | TYPE P1000-OTYPE, " 'P ' | |||
| lv_not_found | TYPE P1000, " | |||
| lv_last_objid | TYPE OBJEC-REALO, " | |||
| lv_objid | TYPE OBJEC-REALO, " | |||
| lv_begda | TYPE P1000-BEGDA, " SY-DATUM | |||
| lv_endda | TYPE P1000-ENDDA, " '99991231' | |||
| lv_maintain | TYPE CHAR1, " 'X' | |||
| lv_commit_flg | TYPE HRRHAP-COMMIT_FLG, " 'X' | |||
| lv_first_dynnr | TYPE SY-DYNNR, " | |||
| lv_first_repid | TYPE SY-REPID. " |
|   CALL FUNCTION 'RHPP_SHOW_PROFILE' " |
| EXPORTING | ||
| PLVAR | = lv_plvar | |
| OBJECTMANAGER | = lv_objectmanager | |
| NO_PUBLISHING | = lv_no_publishing | |
| OBJECT_AUTHORITY | = lv_object_authority | |
| OTYPE | = lv_otype | |
| OBJID | = lv_objid | |
| BEGDA | = lv_begda | |
| ENDDA | = lv_endda | |
| MAINTAIN | = lv_maintain | |
| COMMIT_FLG | = lv_commit_flg | |
| FIRST_DYNNR | = lv_first_dynnr | |
| FIRST_REPID | = lv_first_repid | |
| IMPORTING | ||
| LAST_OTYPE | = lv_last_otype | |
| LAST_OBJID | = lv_last_objid | |
| CHANGING | ||
| CHANGED_WITHOUT_COMMIT | = lv_changed_without_commit | |
| EXCEPTIONS | ||
| NO_AUTHORITY = 1 | ||
| NOT_FOUND = 2 | ||
| . " RHPP_SHOW_PROFILE | ||
ABAP code using 7.40 inline data declarations to call FM RHPP_SHOW_PROFILE
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_plvar). | ||||
| "SELECT single OTYPE FROM P1000 INTO @DATA(ld_last_otype). | ||||
| DATA(ld_objectmanager) | = ' '. | |||
| DATA(ld_no_publishing) | = ' '. | |||
| "SELECT single AUTHY FROM HRRHAS INTO @DATA(ld_object_authority). | ||||
| DATA(ld_object_authority) | = 'X'. | |||
| "SELECT single OTYPE FROM P1000 INTO @DATA(ld_otype). | ||||
| DATA(ld_otype) | = 'P '. | |||
| "SELECT single REALO FROM OBJEC INTO @DATA(ld_last_objid). | ||||
| "SELECT single REALO FROM OBJEC INTO @DATA(ld_objid). | ||||
| "SELECT single BEGDA FROM P1000 INTO @DATA(ld_begda). | ||||
| DATA(ld_begda) | = SY-DATUM. | |||
| "SELECT single ENDDA FROM P1000 INTO @DATA(ld_endda). | ||||
| DATA(ld_endda) | = '99991231'. | |||
| DATA(ld_maintain) | = 'X'. | |||
| "SELECT single COMMIT_FLG FROM HRRHAP INTO @DATA(ld_commit_flg). | ||||
| DATA(ld_commit_flg) | = 'X'. | |||
| "SELECT single DYNNR FROM SY INTO @DATA(ld_first_dynnr). | ||||
| "SELECT single REPID FROM SY INTO @DATA(ld_first_repid). | ||||
Search for further information about these or an SAP related objects