SAP HRPY_PUST_GET_STEP_STATUS Function Module for









HRPY_PUST_GET_STEP_STATUS is a standard hrpy pust get step status 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 hrpy pust get step status FM, simply by entering the name HRPY_PUST_GET_STEP_STATUS into the relevant SAP transaction such as SE37 or SE38.

Function Group: HRST2
Program Name: SAPLHRST2
Main Program: SAPLHRST2
Appliation area: P
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function HRPY_PUST_GET_STEP_STATUS 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 'HRPY_PUST_GET_STEP_STATUS'"
EXPORTING
P_PROCESSID = "
P_STEPID = "
* P_52SPS = "
* P_REFRESH_BUFFER = 'X' "

IMPORTING
P_STATUS = "
P_RUNID = "
.



IMPORTING Parameters details for HRPY_PUST_GET_STEP_STATUS

P_PROCESSID -

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

P_STEPID -

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

P_52SPS -

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

P_REFRESH_BUFFER -

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

EXPORTING Parameters details for HRPY_PUST_GET_STEP_STATUS

P_STATUS -

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

P_RUNID -

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

Copy and paste ABAP code example for HRPY_PUST_GET_STEP_STATUS 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_p_status  TYPE C, "   
lv_p_processid  TYPE T52SPS-PROCESSID, "   
lv_p_runid  TYPE T52SPS-RUNID, "   
lv_p_stepid  TYPE T52SPS-STEPID, "   
lv_p_52sps  TYPE PAY_PM_SET_TAB, "   
lv_p_refresh_buffer  TYPE RP_XFELD. "   'X'

  CALL FUNCTION 'HRPY_PUST_GET_STEP_STATUS'  "
    EXPORTING
         P_PROCESSID = lv_p_processid
         P_STEPID = lv_p_stepid
         P_52SPS = lv_p_52sps
         P_REFRESH_BUFFER = lv_p_refresh_buffer
    IMPORTING
         P_STATUS = lv_p_status
         P_RUNID = lv_p_runid
. " HRPY_PUST_GET_STEP_STATUS




ABAP code using 7.40 inline data declarations to call FM HRPY_PUST_GET_STEP_STATUS

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 PROCESSID FROM T52SPS INTO @DATA(ld_p_processid).
 
"SELECT single RUNID FROM T52SPS INTO @DATA(ld_p_runid).
 
"SELECT single STEPID FROM T52SPS INTO @DATA(ld_p_stepid).
 
 
DATA(ld_p_refresh_buffer) = 'X'.
 


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!