SAP RH_POSITION_PLAN_SHOW Function Module for Display Staff Assignments
RH_POSITION_PLAN_SHOW is a standard rh position plan show SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Display Staff Assignments 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 rh position plan show FM, simply by entering the name RH_POSITION_PLAN_SHOW into the relevant SAP transaction such as SE37 or SE38.
Function Group: RHGC
Program Name: SAPLRHGC
Main Program:
Appliation area: H
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RH_POSITION_PLAN_SHOW 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_POSITION_PLAN_SHOW'"Display Staff Assignments.
EXPORTING
ACT_PLVAR = "
* ACT_OTYPE = ' ' "
ACT_OBJID = "
* ACT_BEGDA = SY-DATUM "
* ACT_ENDDA = '99991231' "
* ACT_ISTAT = '1' "
* ACT_SVECT = '1' "
* ACT_MAINT = ' ' "
* DISPLAY_ONLY = ' ' "
EXCEPTIONS
ORG_UNIT_NOT_VALID = 1 PLVAR_NOT_FOUND = 2 WEGID_NOT_FOUND = 3 STRUCTURE_ERROR = 4
IMPORTING Parameters details for RH_POSITION_PLAN_SHOW
ACT_PLVAR -
Data type: OBJEC-PLVAROptional: No
Call by Reference: No ( called with pass by value option)
ACT_OTYPE -
Data type: OBJEC-OTYPEDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
ACT_OBJID -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ACT_BEGDA -
Data type: OBJEC-BEGDADefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
ACT_ENDDA -
Data type: OBJEC-ENDDADefault: '99991231'
Optional: Yes
Call by Reference: No ( called with pass by value option)
ACT_ISTAT -
Data type: OBJEC-ISTATDefault: '1'
Optional: Yes
Call by Reference: No ( called with pass by value option)
ACT_SVECT -
Data type: GDSTR-SVECTDefault: '1'
Optional: Yes
Call by Reference: No ( called with pass by value option)
ACT_MAINT -
Data type: T77FC-MAINTDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
DISPLAY_ONLY -
Data type: T77FC-MAINTDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ORG_UNIT_NOT_VALID -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PLVAR_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WEGID_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
STRUCTURE_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RH_POSITION_PLAN_SHOW 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_act_plvar | TYPE OBJEC-PLVAR, " | |||
| lv_org_unit_not_valid | TYPE OBJEC, " | |||
| lv_act_otype | TYPE OBJEC-OTYPE, " ' ' | |||
| lv_plvar_not_found | TYPE OBJEC, " | |||
| lv_act_objid | TYPE OBJEC, " | |||
| lv_wegid_not_found | TYPE OBJEC, " | |||
| lv_act_begda | TYPE OBJEC-BEGDA, " SY-DATUM | |||
| lv_structure_error | TYPE OBJEC, " | |||
| lv_act_endda | TYPE OBJEC-ENDDA, " '99991231' | |||
| lv_act_istat | TYPE OBJEC-ISTAT, " '1' | |||
| lv_act_svect | TYPE GDSTR-SVECT, " '1' | |||
| lv_act_maint | TYPE T77FC-MAINT, " ' ' | |||
| lv_display_only | TYPE T77FC-MAINT. " ' ' |
|   CALL FUNCTION 'RH_POSITION_PLAN_SHOW' "Display Staff Assignments |
| EXPORTING | ||
| ACT_PLVAR | = lv_act_plvar | |
| ACT_OTYPE | = lv_act_otype | |
| ACT_OBJID | = lv_act_objid | |
| ACT_BEGDA | = lv_act_begda | |
| ACT_ENDDA | = lv_act_endda | |
| ACT_ISTAT | = lv_act_istat | |
| ACT_SVECT | = lv_act_svect | |
| ACT_MAINT | = lv_act_maint | |
| DISPLAY_ONLY | = lv_display_only | |
| EXCEPTIONS | ||
| ORG_UNIT_NOT_VALID = 1 | ||
| PLVAR_NOT_FOUND = 2 | ||
| WEGID_NOT_FOUND = 3 | ||
| STRUCTURE_ERROR = 4 | ||
| . " RH_POSITION_PLAN_SHOW | ||
ABAP code using 7.40 inline data declarations to call FM RH_POSITION_PLAN_SHOW
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_act_plvar). | ||||
| "SELECT single OTYPE FROM OBJEC INTO @DATA(ld_act_otype). | ||||
| DATA(ld_act_otype) | = ' '. | |||
| "SELECT single BEGDA FROM OBJEC INTO @DATA(ld_act_begda). | ||||
| DATA(ld_act_begda) | = SY-DATUM. | |||
| "SELECT single ENDDA FROM OBJEC INTO @DATA(ld_act_endda). | ||||
| DATA(ld_act_endda) | = '99991231'. | |||
| "SELECT single ISTAT FROM OBJEC INTO @DATA(ld_act_istat). | ||||
| DATA(ld_act_istat) | = '1'. | |||
| "SELECT single SVECT FROM GDSTR INTO @DATA(ld_act_svect). | ||||
| DATA(ld_act_svect) | = '1'. | |||
| "SELECT single MAINT FROM T77FC INTO @DATA(ld_act_maint). | ||||
| DATA(ld_act_maint) | = ' '. | |||
| "SELECT single MAINT FROM T77FC INTO @DATA(ld_display_only). | ||||
| DATA(ld_display_only) | = ' '. | |||
Search for further information about these or an SAP related objects