SAP EXIT_RPCEUDI0_002 Function Module for CUD 2002: user exit for part C section 4
EXIT_RPCEUDI0_002 is a standard exit rpceudi0 002 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 2002: user exit for part C section 4 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 rpceudi0 002 FM, simply by entering the name EXIT_RPCEUDI0_002 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XUI1
Program Name: SAPLXUI1
Main Program:
Appliation area: P
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function EXIT_RPCEUDI0_002 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_RPCEUDI0_002'"CUD 2002: user exit for part C section 4.
EXPORTING
P_TABENTE = "
P_C_PREV4 = "
P_BREAK = "
P_BREAKAI = "
P_PERNR = "
P_WAERS = "
P_ENDDA = "
P_BEGDA = "
TABLES
P_CUDTABPREV1 = "
P_CUDTABPREV2 = "
P_I_PAYROLL_RESULT = "
P_I_PC_RESULT = "
P_I_TM_RESULTS = "
P_RT_TAB = "
P_P0001 = "
P_P0016 = "
P_P0154 = "
EXCEPTIONS
USED_USER_EXIT = 1
IMPORTING Parameters details for EXIT_RPCEUDI0_002
P_TABENTE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
P_C_PREV4 -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
P_BREAK -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
P_BREAKAI -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
P_PERNR -
Data type:Optional: No
Call by Reference: Yes
P_WAERS -
Data type:Optional: No
Call by Reference: Yes
P_ENDDA -
Data type:Optional: No
Call by Reference: Yes
P_BEGDA -
Data type:Optional: No
Call by Reference: Yes
TABLES Parameters details for EXIT_RPCEUDI0_002
P_CUDTABPREV1 -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
P_CUDTABPREV2 -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
P_I_PAYROLL_RESULT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
P_I_PC_RESULT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
P_I_TM_RESULTS -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
P_RT_TAB -
Data type:Optional: No
Call by Reference: Yes
P_P0001 -
Data type:Optional: No
Call by Reference: Yes
P_P0016 -
Data type:Optional: No
Call by Reference: Yes
P_P0154 -
Data type:Optional: No
Call by Reference: Yes
EXCEPTIONS details
USED_USER_EXIT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EXIT_RPCEUDI0_002 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_p_tabente | TYPE STRING, " | |||
lt_p_cudtabprev1 | TYPE STANDARD TABLE OF STRING, " | |||
lv_used_user_exit | TYPE STRING, " | |||
lv_p_c_prev4 | TYPE STRING, " | |||
lt_p_cudtabprev2 | TYPE STANDARD TABLE OF STRING, " | |||
lv_p_break | TYPE STRING, " | |||
lt_p_i_payroll_result | TYPE STANDARD TABLE OF STRING, " | |||
lv_p_breakai | TYPE STRING, " | |||
lt_p_i_pc_result | TYPE STANDARD TABLE OF STRING, " | |||
lv_p_pernr | TYPE STRING, " | |||
lt_p_i_tm_results | TYPE STANDARD TABLE OF STRING, " | |||
lv_p_waers | TYPE STRING, " | |||
lt_p_rt_tab | TYPE STANDARD TABLE OF STRING, " | |||
lv_p_endda | TYPE STRING, " | |||
lt_p_p0001 | TYPE STANDARD TABLE OF STRING, " | |||
lv_p_begda | TYPE STRING, " | |||
lt_p_p0016 | TYPE STANDARD TABLE OF STRING, " | |||
lt_p_p0154 | TYPE STANDARD TABLE OF STRING. " |
  CALL FUNCTION 'EXIT_RPCEUDI0_002' "CUD 2002: user exit for part C section 4 |
EXPORTING | ||
P_TABENTE | = lv_p_tabente | |
P_C_PREV4 | = lv_p_c_prev4 | |
P_BREAK | = lv_p_break | |
P_BREAKAI | = lv_p_breakai | |
P_PERNR | = lv_p_pernr | |
P_WAERS | = lv_p_waers | |
P_ENDDA | = lv_p_endda | |
P_BEGDA | = lv_p_begda | |
TABLES | ||
P_CUDTABPREV1 | = lt_p_cudtabprev1 | |
P_CUDTABPREV2 | = lt_p_cudtabprev2 | |
P_I_PAYROLL_RESULT | = lt_p_i_payroll_result | |
P_I_PC_RESULT | = lt_p_i_pc_result | |
P_I_TM_RESULTS | = lt_p_i_tm_results | |
P_RT_TAB | = lt_p_rt_tab | |
P_P0001 | = lt_p_p0001 | |
P_P0016 | = lt_p_p0016 | |
P_P0154 | = lt_p_p0154 | |
EXCEPTIONS | ||
USED_USER_EXIT = 1 | ||
. " EXIT_RPCEUDI0_002 |
ABAP code using 7.40 inline data declarations to call FM EXIT_RPCEUDI0_002
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