SAP OXDEP_ELEMENT_GET Function Module for NOTRANSL: element get
OXDEP_ELEMENT_GET is a standard oxdep element get 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: element get 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 element get FM, simply by entering the name OXDEP_ELEMENT_GET 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_ELEMENT_GET 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_ELEMENT_GET'"NOTRANSL: element get.
EXPORTING
ISELF = "Instance
CHAR = "Characteristic
IMPORTING
OPERAND = "DE-EN-LANG-SWITCH-NO-TRANSLATION
CELL = "Cell
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_ELEMENT_GET
ISELF - Instance
Data type: COCOM_INSTSOptional: No
Call by Reference: Yes
CHAR - Characteristic
Data type: CO003_ATNAMOptional: No
Call by Reference: Yes
EXPORTING Parameters details for OXDEP_ELEMENT_GET
OPERAND - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: OMDEP_CELL-OPERANDOptional: No
Call by Reference: Yes
CELL - Cell
Data type: OMDEP_CELL-STRINGOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for OXDEP_ELEMENT_GET 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_iself | TYPE COCOM_INSTS, " | |||
| lv_operand | TYPE OMDEP_CELL-OPERAND, " | |||
| lv_cell | TYPE OMDEP_CELL-STRING, " | |||
| lv_char | TYPE CO003_ATNAM. " |
|   CALL FUNCTION 'OXDEP_ELEMENT_GET' "NOTRANSL: element get |
| EXPORTING | ||
| ISELF | = lv_iself | |
| CHAR | = lv_char | |
| IMPORTING | ||
| OPERAND | = lv_operand | |
| CELL | = lv_cell | |
| . " OXDEP_ELEMENT_GET | ||
ABAP code using 7.40 inline data declarations to call FM OXDEP_ELEMENT_GET
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.| "SELECT single OPERAND FROM OMDEP_CELL INTO @DATA(ld_operand). | ||||
| "SELECT single STRING FROM OMDEP_CELL INTO @DATA(ld_cell). | ||||
Search for further information about these or an SAP related objects