SAP IW_C_CONTEXT_GET Function Module for IWB: Read context values from context table
IW_C_CONTEXT_GET is a standard iw c context 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 IWB: Read context values from context table 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 iw c context get FM, simply by entering the name IW_C_CONTEXT_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: SI63
Program Name: SAPLSI63
Main Program: SAPLSI63
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function IW_C_CONTEXT_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 'IW_C_CONTEXT_GET'"IWB: Read context values from context table.
IMPORTING
LANGUAGE = "
IWB_STATE = "
COUNTRY = "
INDUSTRY = "
SOURCE_LANGUAGE = "
TARGET_LANGUAGE = "
RELEASE = "
TASK = "
STRUCTURE_CLASS = "Document Class
STRUCTURE_OBJID = "
TABLES
CONTEXT = "
EXPORTING Parameters details for IW_C_CONTEXT_GET
LANGUAGE -
Data type: SY-LANGUOptional: No
Call by Reference: No ( called with pass by value option)
IWB_STATE -
Data type: SDOKPROPTY-VALUEOptional: No
Call by Reference: No ( called with pass by value option)
COUNTRY -
Data type: T005-LAND1Optional: No
Call by Reference: No ( called with pass by value option)
INDUSTRY -
Data type: IWEXTEND-IDOptional: No
Call by Reference: No ( called with pass by value option)
SOURCE_LANGUAGE -
Data type: SY-LANGUOptional: No
Call by Reference: No ( called with pass by value option)
TARGET_LANGUAGE -
Data type: SY-LANGUOptional: No
Call by Reference: No ( called with pass by value option)
RELEASE -
Data type: IWEXTEND-RELOptional: No
Call by Reference: No ( called with pass by value option)
TASK -
Data type: SDOKR3LLST-TASK_NAMEOptional: No
Call by Reference: No ( called with pass by value option)
STRUCTURE_CLASS - Document Class
Data type: SDOKOBJECT-CLASSOptional: No
Call by Reference: No ( called with pass by value option)
STRUCTURE_OBJID -
Data type: SDOKOBJECT-OBJIDOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for IW_C_CONTEXT_GET
CONTEXT -
Data type: SDOKPROPTYOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for IW_C_CONTEXT_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: | ||||
lt_context | TYPE STANDARD TABLE OF SDOKPROPTY, " | |||
lv_language | TYPE SY-LANGU, " | |||
lv_iwb_state | TYPE SDOKPROPTY-VALUE, " | |||
lv_country | TYPE T005-LAND1, " | |||
lv_industry | TYPE IWEXTEND-ID, " | |||
lv_source_language | TYPE SY-LANGU, " | |||
lv_target_language | TYPE SY-LANGU, " | |||
lv_release | TYPE IWEXTEND-REL, " | |||
lv_task | TYPE SDOKR3LLST-TASK_NAME, " | |||
lv_structure_class | TYPE SDOKOBJECT-CLASS, " | |||
lv_structure_objid | TYPE SDOKOBJECT-OBJID. " |
  CALL FUNCTION 'IW_C_CONTEXT_GET' "IWB: Read context values from context table |
IMPORTING | ||
LANGUAGE | = lv_language | |
IWB_STATE | = lv_iwb_state | |
COUNTRY | = lv_country | |
INDUSTRY | = lv_industry | |
SOURCE_LANGUAGE | = lv_source_language | |
TARGET_LANGUAGE | = lv_target_language | |
RELEASE | = lv_release | |
TASK | = lv_task | |
STRUCTURE_CLASS | = lv_structure_class | |
STRUCTURE_OBJID | = lv_structure_objid | |
TABLES | ||
CONTEXT | = lt_context | |
. " IW_C_CONTEXT_GET |
ABAP code using 7.40 inline data declarations to call FM IW_C_CONTEXT_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 LANGU FROM SY INTO @DATA(ld_language). | ||||
"SELECT single VALUE FROM SDOKPROPTY INTO @DATA(ld_iwb_state). | ||||
"SELECT single LAND1 FROM T005 INTO @DATA(ld_country). | ||||
"SELECT single ID FROM IWEXTEND INTO @DATA(ld_industry). | ||||
"SELECT single LANGU FROM SY INTO @DATA(ld_source_language). | ||||
"SELECT single LANGU FROM SY INTO @DATA(ld_target_language). | ||||
"SELECT single REL FROM IWEXTEND INTO @DATA(ld_release). | ||||
"SELECT single TASK_NAME FROM SDOKR3LLST INTO @DATA(ld_task). | ||||
"SELECT single CLASS FROM SDOKOBJECT INTO @DATA(ld_structure_class). | ||||
"SELECT single OBJID FROM SDOKOBJECT INTO @DATA(ld_structure_objid). | ||||
Search for further information about these or an SAP related objects