SAP OXDEP_WU_ELEMENT_SET Function Module for NOTRANSL: where used list: element set
OXDEP_WU_ELEMENT_SET is a standard oxdep wu element set 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: where used list: element set 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 oxdep wu element set FM, simply by entering the name OXDEP_WU_ELEMENT_SET into the relevant SAP transaction such as SE37 or SE38.
Function Group: OXDEP
Program Name: SAPLOXDEP
Main Program: SAPLOXDEP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OXDEP_WU_ELEMENT_SET 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 'OXDEP_WU_ELEMENT_SET'"NOTRANSL: where used list: element set.
EXPORTING
ATTRIBUT = "Characteristic
VALUE = "Value
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLOXDEP_001
IMPORTING Parameters details for OXDEP_WU_ELEMENT_SET
ATTRIBUT - Characteristic
Data type: CO003_ATNAMOptional: No
Call by Reference: Yes
VALUE - Value
Data type: CO003_ATWRTOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for OXDEP_WU_ELEMENT_SET 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_attribut | TYPE CO003_ATNAM, " | |||
| lv_value | TYPE CO003_ATWRT. " |
|   CALL FUNCTION 'OXDEP_WU_ELEMENT_SET' "NOTRANSL: where used list: element set |
| EXPORTING | ||
| ATTRIBUT | = lv_attribut | |
| VALUE | = lv_value | |
| . " OXDEP_WU_ELEMENT_SET | ||
ABAP code using 7.40 inline data declarations to call FM OXDEP_WU_ELEMENT_SET
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