SAP SWC_ELEMENT_GET Function Module for Read element from container
SWC_ELEMENT_GET is a standard swc 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 Read element from container 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 swc element get FM, simply by entering the name SWC_ELEMENT_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: SWCD
Program Name: SAPLSWCD
Main Program: SAPLSWCD
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function SWC_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 'SWC_ELEMENT_GET'"Read element from container.
EXPORTING
ELEMENT = "Container element
IMPORTING
FIELD = "ABAP/4 field
TABLES
CONTAINER = "Container instance
EXCEPTIONS
IS_NULL = 1 NOT_FOUND = 2 TYPE_CONFLICT = 3
IMPORTING Parameters details for SWC_ELEMENT_GET
ELEMENT - Container element
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SWC_ELEMENT_GET
FIELD - ABAP/4 field
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SWC_ELEMENT_GET
CONTAINER - Container instance
Data type: SWCONTOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
IS_NULL -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_FOUND - Element not found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TYPE_CONFLICT - Type or length conflict
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SWC_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_field | TYPE STRING, " | |||
| lv_element | TYPE STRING, " | |||
| lv_is_null | TYPE STRING, " | |||
| lt_container | TYPE STANDARD TABLE OF SWCONT, " | |||
| lv_not_found | TYPE SWCONT, " | |||
| lv_type_conflict | TYPE SWCONT. " |
| CALL FUNCTION 'SWC_ELEMENT_GET' "Read element from container |
| EXPORTING | ||
| ELEMENT | = lv_element | |
| IMPORTING | ||
| FIELD | = lv_field | |
| TABLES | ||
| CONTAINER | = lt_container | |
| EXCEPTIONS | ||
| IS_NULL = 1 | ||
| NOT_FOUND = 2 | ||
| TYPE_CONFLICT = 3 | ||
| . " SWC_ELEMENT_GET | ||
ABAP code using 7.40 inline data declarations to call FM SWC_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.Search for further information about these or an SAP related objects