SAP UPS_SEND_NEW_MAIL Function Module for Broadcast-mail for re-set version
UPS_SEND_NEW_MAIL is a standard ups send new mail SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Broadcast-mail for re-set version 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 ups send new mail FM, simply by entering the name UPS_SEND_NEW_MAIL into the relevant SAP transaction such as SE37 or SE38.
Function Group: UPS_C
Program Name: SAPLUPS_C
Main Program: SAPLUPS_C
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function UPS_SEND_NEW_MAIL 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 'UPS_SEND_NEW_MAIL'"Broadcast-mail for re-set version.
EXPORTING
I_VERSION = "Planning Session/Version
I_TEILPLAN = "Subplan in STS
EXCEPTIONS
FAILED = 1
IMPORTING Parameters details for UPS_SEND_NEW_MAIL
I_VERSION - Planning Session/Version
Data type: UPS_Y_VERSIONOptional: No
Call by Reference: Yes
I_TEILPLAN - Subplan in STS
Data type: UPS_Y_TEILPLANOptional: No
Call by Reference: Yes
EXCEPTIONS details
FAILED - Error
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for UPS_SEND_NEW_MAIL 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_failed | TYPE STRING, " | |||
| lv_i_version | TYPE UPS_Y_VERSION, " | |||
| lv_i_teilplan | TYPE UPS_Y_TEILPLAN. " |
|   CALL FUNCTION 'UPS_SEND_NEW_MAIL' "Broadcast-mail for re-set version |
| EXPORTING | ||
| I_VERSION | = lv_i_version | |
| I_TEILPLAN | = lv_i_teilplan | |
| EXCEPTIONS | ||
| FAILED = 1 | ||
| . " UPS_SEND_NEW_MAIL | ||
ABAP code using 7.40 inline data declarations to call FM UPS_SEND_NEW_MAIL
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