SAP ROPC_WORKFLOW_STATUS Function Module for









ROPC_WORKFLOW_STATUS is a standard ropc workflow 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 ropc workflow status FM, simply by entering the name ROPC_WORKFLOW_STATUS into the relevant SAP transaction such as SE37 or SE38.

Function Group: ROPC_WF
Program Name: SAPLROPC_WF
Main Program: SAPLROPC_WF
Appliation area: B
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function ROPC_WORKFLOW_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 'ROPC_WORKFLOW_STATUS'"
EXPORTING
I_WIID = "

IMPORTING
E_WI_STAT = "

EXCEPTIONS
READ_FAILED = 1
.



IMPORTING Parameters details for ROPC_WORKFLOW_STATUS

I_WIID -

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

EXPORTING Parameters details for ROPC_WORKFLOW_STATUS

E_WI_STAT -

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

EXCEPTIONS details

READ_FAILED -

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

Copy and paste ABAP code example for ROPC_WORKFLOW_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_i_wiid  TYPE SWWWIHEAD-WI_ID, "   
lv_e_wi_stat  TYPE SWWWIHEAD-WI_STAT, "   
lv_read_failed  TYPE SWWWIHEAD. "   

  CALL FUNCTION 'ROPC_WORKFLOW_STATUS'  "
    EXPORTING
         I_WIID = lv_i_wiid
    IMPORTING
         E_WI_STAT = lv_e_wi_stat
    EXCEPTIONS
        READ_FAILED = 1
. " ROPC_WORKFLOW_STATUS




ABAP code using 7.40 inline data declarations to call FM ROPC_WORKFLOW_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 WI_ID FROM SWWWIHEAD INTO @DATA(ld_i_wiid).
 
"SELECT single WI_STAT FROM SWWWIHEAD INTO @DATA(ld_e_wi_stat).
 
 


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!