SAP POWL_EXT_STATUS Function Module for set external status for gen. selection screen
POWL_EXT_STATUS is a standard powl ext status SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for set external status for gen. selection screen 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 powl ext status FM, simply by entering the name POWL_EXT_STATUS into the relevant SAP transaction such as SE37 or SE38.
Function Group: POWL_V_QUERY
Program Name: SAPLPOWL_V_QUERY
Main Program: SAPLPOWL_V_QUERY
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function POWL_EXT_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 'POWL_EXT_STATUS'"set external status for gen. selection screen.
EXPORTING
* P_SUBMIT_MODE = "
TABLES
* P_EXCLUDE = "Table structure for 'SET PF-STATUS EXCLUDING ...'
IMPORTING Parameters details for POWL_EXT_STATUS
P_SUBMIT_MODE -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for POWL_EXT_STATUS
P_EXCLUDE - Table structure for 'SET PF-STATUS EXCLUDING ...'
Data type:Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for POWL_EXT_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: | ||||
| lt_p_exclude | TYPE STANDARD TABLE OF STRING, " | |||
| lv_p_submit_mode | TYPE STRING. " |
|   CALL FUNCTION 'POWL_EXT_STATUS' "set external status for gen. selection screen |
| EXPORTING | ||
| P_SUBMIT_MODE | = lv_p_submit_mode | |
| TABLES | ||
| P_EXCLUDE | = lt_p_exclude | |
| . " POWL_EXT_STATUS | ||
ABAP code using 7.40 inline data declarations to call FM POWL_EXT_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.Search for further information about these or an SAP related objects