SAP SWF_GET_CONTAINER_INST Function Module for Workflow Interfaces: Read Container

Search SAP Function Modules

SWF_GET_CONTAINER_INST is a standard swf get container inst SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Workflow Interfaces: Read 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 swf get container inst FM, simply by entering the name SWF_GET_CONTAINER_INST into the relevant SAP transaction such as SE37 or SE38.

Function Group: SWF_WSC_RFC
Program Name: SAPLSWF_WSC_RFC
Main Program: SAPLSWF_WSC_RFC
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function SWF_GET_CONTAINER_INST 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 'SWF_GET_CONTAINER_INST'"Workflow Interfaces: Read Container
  EXPORTING
   WORKITEM_ID =  "Work Item ID
*  LANGUAGE = SY-LANGU "SAP R/3 System, Current Language

 IMPORTING
   RETURN_CODE =  "Return Value (0 - 1)
   XML_CONTAINER =  "Container as XML Stream of Fixed Width
   XML_SIZE =  "Size in Bytes
   XML_DEFEXTENSION =  "Container as XML Stream of Fixed Width
   XML_DEFEXT_SIZE =  "Size in Bytes

TABLES
*  MESSAGE_LINES =  "Message Lines
*  MESSAGE_STRUCT =  "Message Structure

.

IMPORTING Parameters details for SWF_GET_CONTAINER_INST

WORKITEM_ID - Work Item ID

Data type: SWR_STRUCT-WORKITEMID
Optional: No
Call by Reference: No ( called with pass by value option)

LANGUAGE - SAP R/3 System, Current Language

Data type: SYLANGU
Default: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for SWF_GET_CONTAINER_INST

RETURN_CODE - Return Value (0 - 1)

Data type: SY-SUBRC
Optional: No
Call by Reference: No ( called with pass by value option)

XML_CONTAINER - Container as XML Stream of Fixed Width

Data type: SWF_XMLCNT
Optional: No
Call by Reference: No ( called with pass by value option)

XML_SIZE - Size in Bytes

Data type: SWF_XMLSIZ
Optional: No
Call by Reference: No ( called with pass by value option)

XML_DEFEXTENSION - Container as XML Stream of Fixed Width

Data type: SWF_XMLCNT
Optional: No
Call by Reference: No ( called with pass by value option)

XML_DEFEXT_SIZE - Size in Bytes

Data type: SWF_XMLSIZ
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for SWF_GET_CONTAINER_INST

MESSAGE_LINES - Message Lines

Data type: SWR_MESSAG
Optional: Yes
Call by Reference: No ( called with pass by value option)

MESSAGE_STRUCT - Message Structure

Data type: SWR_MSTRUC
Optional: Yes
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for SWF_GET_CONTAINER_INST 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.

ABAP code using 7.40 inline data declarations to call FM SWF_GET_CONTAINER_INST

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