SAP FRML957_GUIDSETS_UNION Function Module for NOTRANSL: RMS-FRM: Vereinigung zweier GUID-Mengen
FRML957_GUIDSETS_UNION is a standard frml957 guidsets union SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: RMS-FRM: Vereinigung zweier GUID-Mengen 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 frml957 guidsets union FM, simply by entering the name FRML957_GUIDSETS_UNION into the relevant SAP transaction such as SE37 or SE38.
Function Group: FRML957
Program Name: SAPLFRML957
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FRML957_GUIDSETS_UNION 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 'FRML957_GUIDSETS_UNION'"NOTRANSL: RMS-FRM: Vereinigung zweier GUID-Mengen.
EXPORTING
I_SET_1 = "
I_SET_2 = "
IMPORTING
E_SET_RES = "
IMPORTING Parameters details for FRML957_GUIDSETS_UNION
I_SET_1 -
Data type: FRM51_SET_TYPEOptional: No
Call by Reference: Yes
I_SET_2 -
Data type: FRM51_SET_TYPEOptional: No
Call by Reference: Yes
EXPORTING Parameters details for FRML957_GUIDSETS_UNION
E_SET_RES -
Data type: FRM51_SET_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FRML957_GUIDSETS_UNION 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_set_1 | TYPE FRM51_SET_TYPE, " | |||
| lv_e_set_res | TYPE FRM51_SET_TYPE, " | |||
| lv_i_set_2 | TYPE FRM51_SET_TYPE. " |
|   CALL FUNCTION 'FRML957_GUIDSETS_UNION' "NOTRANSL: RMS-FRM: Vereinigung zweier GUID-Mengen |
| EXPORTING | ||
| I_SET_1 | = lv_i_set_1 | |
| I_SET_2 | = lv_i_set_2 | |
| IMPORTING | ||
| E_SET_RES | = lv_e_set_res | |
| . " FRML957_GUIDSETS_UNION | ||
ABAP code using 7.40 inline data declarations to call FM FRML957_GUIDSETS_UNION
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