SAP MDM_PIC_BUPA_DATA_SENT Function Module for
MDM_PIC_BUPA_DATA_SENT is a standard mdm pic bupa data sent 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 mdm pic bupa data sent FM, simply by entering the name MDM_PIC_BUPA_DATA_SENT into the relevant SAP transaction such as SE37 or SE38.
Function Group: MDM_BUPA_EXTRACTOR_PI
Program Name: SAPLMDM_BUPA_EXTRACTOR_PI
Main Program: SAPLMDM_BUPA_EXTRACTOR_PI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MDM_PIC_BUPA_DATA_SENT 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 'MDM_PIC_BUPA_DATA_SENT'".
TABLES
I_T_MSG = "
EXCEPTIONS
INVALID = 1 DUPLICATE = 2 UNKNOWN_ERROR = 3
TABLES Parameters details for MDM_PIC_BUPA_DATA_SENT
I_T_MSG -
Data type: MDM01_T_MESSNUMOptional: No
Call by Reference: Yes
EXCEPTIONS details
INVALID -
Data type:Optional: No
Call by Reference: Yes
DUPLICATE -
Data type:Optional: No
Call by Reference: Yes
UNKNOWN_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for MDM_PIC_BUPA_DATA_SENT 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_invalid | TYPE STRING, " | |||
| lt_i_t_msg | TYPE STANDARD TABLE OF MDM01_T_MESSNUM, " | |||
| lv_duplicate | TYPE MDM01_T_MESSNUM, " | |||
| lv_unknown_error | TYPE MDM01_T_MESSNUM. " |
|   CALL FUNCTION 'MDM_PIC_BUPA_DATA_SENT' " |
| TABLES | ||
| I_T_MSG | = lt_i_t_msg | |
| EXCEPTIONS | ||
| INVALID = 1 | ||
| DUPLICATE = 2 | ||
| UNKNOWN_ERROR = 3 | ||
| . " MDM_PIC_BUPA_DATA_SENT | ||
ABAP code using 7.40 inline data declarations to call FM MDM_PIC_BUPA_DATA_SENT
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