SAP UPSCU_CHECK_PROCESS_ALLOWED Function Module for
UPSCU_CHECK_PROCESS_ALLOWED is a standard upscu check process allowed 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 upscu check process allowed FM, simply by entering the name UPSCU_CHECK_PROCESS_ALLOWED into the relevant SAP transaction such as SE37 or SE38.
Function Group: UPSCU
Program Name: SAPLUPSCU
Main Program: SAPLUPSCU
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function UPSCU_CHECK_PROCESS_ALLOWED 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 'UPSCU_CHECK_PROCESS_ALLOWED'".
EXPORTING
IM_INSTID = "ALE Distribution Packet: ID for Instantiation
IM_VRGNG = "Business Transaction
EXCEPTIONS
FAILING_INSTANCE = 1 NOT_ALLOWED = 2
IMPORTING Parameters details for UPSCU_CHECK_PROCESS_ALLOWED
IM_INSTID - ALE Distribution Packet: ID for Instantiation
Data type: UPS_INSTIDOptional: No
Call by Reference: Yes
IM_VRGNG - Business Transaction
Data type: TJ01-VRGNGOptional: No
Call by Reference: Yes
EXCEPTIONS details
FAILING_INSTANCE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_ALLOWED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for UPSCU_CHECK_PROCESS_ALLOWED 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_im_instid | TYPE UPS_INSTID, " | |||
| lv_failing_instance | TYPE UPS_INSTID, " | |||
| lv_im_vrgng | TYPE TJ01-VRGNG, " | |||
| lv_not_allowed | TYPE TJ01. " |
|   CALL FUNCTION 'UPSCU_CHECK_PROCESS_ALLOWED' " |
| EXPORTING | ||
| IM_INSTID | = lv_im_instid | |
| IM_VRGNG | = lv_im_vrgng | |
| EXCEPTIONS | ||
| FAILING_INSTANCE = 1 | ||
| NOT_ALLOWED = 2 | ||
| . " UPSCU_CHECK_PROCESS_ALLOWED | ||
ABAP code using 7.40 inline data declarations to call FM UPSCU_CHECK_PROCESS_ALLOWED
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 VRGNG FROM TJ01 INTO @DATA(ld_im_vrgng). | ||||
Search for further information about these or an SAP related objects