SAP PRGN_USER_ASSIGNMENT_CHANGE Function Module for
PRGN_USER_ASSIGNMENT_CHANGE is a standard prgn user assignment change 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 prgn user assignment change FM, simply by entering the name PRGN_USER_ASSIGNMENT_CHANGE into the relevant SAP transaction such as SE37 or SE38.
Function Group: PRGN_EXCHANGE
Program Name: SAPLPRGN_EXCHANGE
Main Program: SAPLPRGN_EXCHANGE
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PRGN_USER_ASSIGNMENT_CHANGE 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 'PRGN_USER_ASSIGNMENT_CHANGE'".
EXPORTING
* SHOW_ERROR_MESSAGES = ' ' "Display error messages
* ENQUEUE_ACTIVITY_GROUP = 'X' "
* AUTHORITY_CHECK = 'X' "Execute authorization check
* CHECK_ZBV_IS_ACTIVE = 'X' "
* NO_COMMIT = ' ' "Customized ('C') or standard menu ('S') flag
IMPORTING
NUMBER_NOT_AUTHORIZED = "
NUMBER_ENQUEUED = "
NUMBER_NOT_EXISTING = "
TABLES
* ADD_USERS_TO_ACTGROUPS = "
* DELETE_USERS_FROM_ACTGROUPS = "
* NOT_AUTHORIZED = "
* ENQUEUED = "
* NOT_EXISTING = "
* IT_BAPIRET2 = "Return Parameters
IMPORTING Parameters details for PRGN_USER_ASSIGNMENT_CHANGE
SHOW_ERROR_MESSAGES - Display error messages
Data type: CHAR01Default: SPACE
Optional: Yes
Call by Reference: Yes
ENQUEUE_ACTIVITY_GROUP -
Data type: CHAR01Default: 'X'
Optional: Yes
Call by Reference: Yes
AUTHORITY_CHECK - Execute authorization check
Data type: CHAR01Default: 'X'
Optional: Yes
Call by Reference: Yes
CHECK_ZBV_IS_ACTIVE -
Data type: CHAR01Default: 'X'
Optional: Yes
Call by Reference: Yes
NO_COMMIT - Customized ('C') or standard menu ('S') flag
Data type: CHAR01Default: SPACE
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for PRGN_USER_ASSIGNMENT_CHANGE
NUMBER_NOT_AUTHORIZED -
Data type: SYTABIXOptional: No
Call by Reference: Yes
NUMBER_ENQUEUED -
Data type: SYTABIXOptional: No
Call by Reference: Yes
NUMBER_NOT_EXISTING -
Data type: SYTABIXOptional: No
Call by Reference: Yes
TABLES Parameters details for PRGN_USER_ASSIGNMENT_CHANGE
ADD_USERS_TO_ACTGROUPS -
Data type: STR_AGRSOptional: Yes
Call by Reference: Yes
DELETE_USERS_FROM_ACTGROUPS -
Data type: STR_AGRSOptional: Yes
Call by Reference: Yes
NOT_AUTHORIZED -
Data type: STR_AGRSOptional: Yes
Call by Reference: Yes
ENQUEUED -
Data type: STR_AGRSOptional: Yes
Call by Reference: Yes
NOT_EXISTING -
Data type: STR_AGRSOptional: Yes
Call by Reference: Yes
IT_BAPIRET2 - Return Parameters
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for PRGN_USER_ASSIGNMENT_CHANGE 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_show_error_messages | TYPE CHAR01, " SPACE | |||
| lv_number_not_authorized | TYPE SYTABIX, " | |||
| lt_add_users_to_actgroups | TYPE STANDARD TABLE OF STR_AGRS, " | |||
| lv_number_enqueued | TYPE SYTABIX, " | |||
| lv_enqueue_activity_group | TYPE CHAR01, " 'X' | |||
| lt_delete_users_from_actgroups | TYPE STANDARD TABLE OF STR_AGRS, " | |||
| lt_not_authorized | TYPE STANDARD TABLE OF STR_AGRS, " | |||
| lv_authority_check | TYPE CHAR01, " 'X' | |||
| lv_number_not_existing | TYPE SYTABIX, " | |||
| lt_enqueued | TYPE STANDARD TABLE OF STR_AGRS, " | |||
| lv_check_zbv_is_active | TYPE CHAR01, " 'X' | |||
| lv_no_commit | TYPE CHAR01, " SPACE | |||
| lt_not_existing | TYPE STANDARD TABLE OF STR_AGRS, " | |||
| lt_it_bapiret2 | TYPE STANDARD TABLE OF BAPIRET2. " |
|   CALL FUNCTION 'PRGN_USER_ASSIGNMENT_CHANGE' " |
| EXPORTING | ||
| SHOW_ERROR_MESSAGES | = lv_show_error_messages | |
| ENQUEUE_ACTIVITY_GROUP | = lv_enqueue_activity_group | |
| AUTHORITY_CHECK | = lv_authority_check | |
| CHECK_ZBV_IS_ACTIVE | = lv_check_zbv_is_active | |
| NO_COMMIT | = lv_no_commit | |
| IMPORTING | ||
| NUMBER_NOT_AUTHORIZED | = lv_number_not_authorized | |
| NUMBER_ENQUEUED | = lv_number_enqueued | |
| NUMBER_NOT_EXISTING | = lv_number_not_existing | |
| TABLES | ||
| ADD_USERS_TO_ACTGROUPS | = lt_add_users_to_actgroups | |
| DELETE_USERS_FROM_ACTGROUPS | = lt_delete_users_from_actgroups | |
| NOT_AUTHORIZED | = lt_not_authorized | |
| ENQUEUED | = lt_enqueued | |
| NOT_EXISTING | = lt_not_existing | |
| IT_BAPIRET2 | = lt_it_bapiret2 | |
| . " PRGN_USER_ASSIGNMENT_CHANGE | ||
ABAP code using 7.40 inline data declarations to call FM PRGN_USER_ASSIGNMENT_CHANGE
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.| DATA(ld_show_error_messages) | = ' '. | |||
| DATA(ld_enqueue_activity_group) | = 'X'. | |||
| DATA(ld_authority_check) | = 'X'. | |||
| DATA(ld_check_zbv_is_active) | = 'X'. | |||
| DATA(ld_no_commit) | = ' '. | |||
Search for further information about these or an SAP related objects