SAP EXIT_RPCDUDI0_038 Function Module for CUD 2001: user exit for box 2, social security
EXIT_RPCDUDI0_038 is a standard exit rpcdudi0 038 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for CUD 2001: user exit for box 2, social security 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 exit rpcdudi0 038 FM, simply by entering the name EXIT_RPCDUDI0_038 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XUI0
Program Name: SAPLXUI0
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EXIT_RPCDUDI0_038 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 'EXIT_RPCDUDI0_038'"CUD 2001: user exit for box 2, social security.
EXPORTING
DATA_ASSUNZIONE = "Date and time, current date (Application server)
TABLES
BREAK = "
EXCEPTIONS
USED_USER_EXIT = 1
IMPORTING Parameters details for EXIT_RPCDUDI0_038
DATA_ASSUNZIONE - Date and time, current date (Application server)
Data type: SY-DATUMOptional: No
Call by Reference: Yes
TABLES Parameters details for EXIT_RPCDUDI0_038
BREAK -
Data type:Optional: No
Call by Reference: Yes
EXCEPTIONS details
USED_USER_EXIT -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for EXIT_RPCDUDI0_038 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_break | TYPE STANDARD TABLE OF STRING, " | |||
| lv_used_user_exit | TYPE STRING, " | |||
| lv_data_assunzione | TYPE SY-DATUM. " |
|   CALL FUNCTION 'EXIT_RPCDUDI0_038' "CUD 2001: user exit for box 2, social security |
| EXPORTING | ||
| DATA_ASSUNZIONE | = lv_data_assunzione | |
| TABLES | ||
| BREAK | = lt_break | |
| EXCEPTIONS | ||
| USED_USER_EXIT = 1 | ||
| . " EXIT_RPCDUDI0_038 | ||
ABAP code using 7.40 inline data declarations to call FM EXIT_RPCDUDI0_038
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 DATUM FROM SY INTO @DATA(ld_data_assunzione). | ||||
Search for further information about these or an SAP related objects