SAP RSDU_PSA_POST_ACTIVATION2_DB4 Function Module for PSA Post activation activities
RSDU_PSA_POST_ACTIVATION2_DB4 is a standard rsdu psa post activation2 db4 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for PSA Post activation activities 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 rsdu psa post activation2 db4 FM, simply by entering the name RSDU_PSA_POST_ACTIVATION2_DB4 into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSDU_PART_DB4
Program Name: SAPLRSDU_PART_DB4
Main Program: SAPLRSDU_PART_DB4
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RSDU_PSA_POST_ACTIVATION2_DB4 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 'RSDU_PSA_POST_ACTIVATION2_DB4'"PSA Post activation activities.
EXPORTING
I_TABLNM = "PSA Table Name
I_USERAPP = ".
CHANGING
C_PROCESSED = "Boolean
EXCEPTIONS
PSA_POST_ACTIVATION2_FAILED = 1
IMPORTING Parameters details for RSDU_PSA_POST_ACTIVATION2_DB4
I_TABLNM - PSA Table Name
Data type: RSD_TABLNMOptional: No
Call by Reference: Yes
I_USERAPP - .
Data type: RSTSODS-USERAPPOptional: No
Call by Reference: Yes
CHANGING Parameters details for RSDU_PSA_POST_ACTIVATION2_DB4
C_PROCESSED - Boolean
Data type: RS_BOOLOptional: No
Call by Reference: Yes
EXCEPTIONS details
PSA_POST_ACTIVATION2_FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RSDU_PSA_POST_ACTIVATION2_DB4 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_tablnm | TYPE RSD_TABLNM, " | |||
| lv_c_processed | TYPE RS_BOOL, " | |||
| lv_psa_post_activation2_failed | TYPE RS_BOOL, " | |||
| lv_i_userapp | TYPE RSTSODS-USERAPP. " |
|   CALL FUNCTION 'RSDU_PSA_POST_ACTIVATION2_DB4' "PSA Post activation activities |
| EXPORTING | ||
| I_TABLNM | = lv_i_tablnm | |
| I_USERAPP | = lv_i_userapp | |
| CHANGING | ||
| C_PROCESSED | = lv_c_processed | |
| EXCEPTIONS | ||
| PSA_POST_ACTIVATION2_FAILED = 1 | ||
| . " RSDU_PSA_POST_ACTIVATION2_DB4 | ||
ABAP code using 7.40 inline data declarations to call FM RSDU_PSA_POST_ACTIVATION2_DB4
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 USERAPP FROM RSTSODS INTO @DATA(ld_i_userapp). | ||||
Search for further information about these or an SAP related objects