SAP RH_SHOW_TASK_PROFILE Function Module for









RH_SHOW_TASK_PROFILE is a standard rh show task 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 rh show task profile FM, simply by entering the name RH_SHOW_TASK_PROFILE into the relevant SAP transaction such as SE37 or SE38.

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



Function RH_SHOW_TASK_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 'RH_SHOW_TASK_PROFILE'"
EXPORTING
INP_PLVAR = "
* INP_START_LINE = 0 "
* INP_END_COLUMN = 0 "
* INP_END_LINE = 0 "
* DISPLAY_ONLY = ' ' "
INP_OTYPE = "
INP_OBJID = "
* INP_ISTAT = '1' "
* INP_SVECT = '1' "
* INP_BEGDA = SY-DATUM "
* INP_ENDDA = '99991231' "
* INP_MAINT = ' ' "
* INP_START_COLUMN = 0 "

EXCEPTIONS
OBJECT_NOT_FOUND = 1 OBJECTTYPE_NOT_ALLOWED = 2
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLRHGB_001 Additional information on / off
EXIT_SAPLRHGB_002 Text Fill Customer-Specific Field
EXIT_SAPLRHGB_003 Header Fill Customer-Specific Field

IMPORTING Parameters details for RH_SHOW_TASK_PROFILE

INP_PLVAR -

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

INP_START_LINE -

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

INP_END_COLUMN -

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

INP_END_LINE -

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

DISPLAY_ONLY -

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

INP_OTYPE -

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

INP_OBJID -

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

INP_ISTAT -

Data type: OBJEC-ISTAT
Default: '1'
Optional: Yes
Call by Reference: No ( called with pass by value option)

INP_SVECT -

Data type: GDSTR-SVECT
Default: '1'
Optional: Yes
Call by Reference: No ( called with pass by value option)

INP_BEGDA -

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

INP_ENDDA -

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

INP_MAINT -

Data type: T77FC-MAINT
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

INP_START_COLUMN -

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

EXCEPTIONS details

OBJECT_NOT_FOUND -

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

OBJECTTYPE_NOT_ALLOWED -

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

Copy and paste ABAP code example for RH_SHOW_TASK_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_inp_plvar  TYPE OBJEC-PLVAR, "   
lv_object_not_found  TYPE OBJEC, "   
lv_inp_start_line  TYPE OBJEC, "   0
lv_inp_end_column  TYPE OBJEC, "   0
lv_inp_end_line  TYPE OBJEC, "   0
lv_display_only  TYPE T77FC-MAINT, "   ' '
lv_inp_otype  TYPE OBJEC-OTYPE, "   
lv_objecttype_not_allowed  TYPE OBJEC, "   
lv_inp_objid  TYPE OBJEC, "   
lv_inp_istat  TYPE OBJEC-ISTAT, "   '1'
lv_inp_svect  TYPE GDSTR-SVECT, "   '1'
lv_inp_begda  TYPE OBJEC-BEGDA, "   SY-DATUM
lv_inp_endda  TYPE OBJEC-ENDDA, "   '99991231'
lv_inp_maint  TYPE T77FC-MAINT, "   SPACE
lv_inp_start_column  TYPE T77FC. "   0

  CALL FUNCTION 'RH_SHOW_TASK_PROFILE'  "
    EXPORTING
         INP_PLVAR = lv_inp_plvar
         INP_START_LINE = lv_inp_start_line
         INP_END_COLUMN = lv_inp_end_column
         INP_END_LINE = lv_inp_end_line
         DISPLAY_ONLY = lv_display_only
         INP_OTYPE = lv_inp_otype
         INP_OBJID = lv_inp_objid
         INP_ISTAT = lv_inp_istat
         INP_SVECT = lv_inp_svect
         INP_BEGDA = lv_inp_begda
         INP_ENDDA = lv_inp_endda
         INP_MAINT = lv_inp_maint
         INP_START_COLUMN = lv_inp_start_column
    EXCEPTIONS
        OBJECT_NOT_FOUND = 1
        OBJECTTYPE_NOT_ALLOWED = 2
. " RH_SHOW_TASK_PROFILE




ABAP code using 7.40 inline data declarations to call FM RH_SHOW_TASK_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 OBJEC INTO @DATA(ld_inp_plvar).
 
 
 
 
 
"SELECT single MAINT FROM T77FC INTO @DATA(ld_display_only).
DATA(ld_display_only) = ' '.
 
"SELECT single OTYPE FROM OBJEC INTO @DATA(ld_inp_otype).
 
 
 
"SELECT single ISTAT FROM OBJEC INTO @DATA(ld_inp_istat).
DATA(ld_inp_istat) = '1'.
 
"SELECT single SVECT FROM GDSTR INTO @DATA(ld_inp_svect).
DATA(ld_inp_svect) = '1'.
 
"SELECT single BEGDA FROM OBJEC INTO @DATA(ld_inp_begda).
DATA(ld_inp_begda) = SY-DATUM.
 
"SELECT single ENDDA FROM OBJEC INTO @DATA(ld_inp_endda).
DATA(ld_inp_endda) = '99991231'.
 
"SELECT single MAINT FROM T77FC INTO @DATA(ld_inp_maint).
DATA(ld_inp_maint) = ' '.
 
 


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!