SAP SWA_CHECK_PD_CONTAINER_DATA Function Module for









SWA_CHECK_PD_CONTAINER_DATA is a standard swa check pd container data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 swa check pd container data FM, simply by entering the name SWA_CHECK_PD_CONTAINER_DATA into the relevant SAP transaction such as SE37 or SE38.

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



Function SWA_CHECK_PD_CONTAINER_DATA 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 'SWA_CHECK_PD_CONTAINER_DATA'"
  EXPORTING
   PDOBJECT =  "Concatenated ID for org. object
*  LANGUAGE = SY-LANGU "Message language
*  DATAFLOW = 'E' "Binding direction
*  INTERNAL_DATE_N_TIME =  "Date and time entries in internal format

 IMPORTING
   RESULT =  "Return code (0,1,2,3)

TABLES
   CONTAINER_INSTANCE =  "<-> Created container instance
*  MESSAGES =  "<- Messages
   CONTAINER_VALUES =  "-> Values for container instance to be created
*  CONTAINER_VALUES_NO_CHECK =  "
*  STRUCTURED_MESSAGES =  "
.



IMPORTING Parameters details for SWA_CHECK_PD_CONTAINER_DATA

PDOBJECT - Concatenated ID for org. object

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

LANGUAGE - Message language

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

DATAFLOW - Binding direction

Data type: SWABINDEF-DATAFLOW
Default: 'E'
Optional: Yes
Call by Reference: No ( called with pass by value option)

INTERNAL_DATE_N_TIME - Date and time entries in internal format

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

EXPORTING Parameters details for SWA_CHECK_PD_CONTAINER_DATA

RESULT - Return code (0,1,2,3)

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

TABLES Parameters details for SWA_CHECK_PD_CONTAINER_DATA

CONTAINER_INSTANCE - <-> Created container instance

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

MESSAGES - <- Messages

Data type: SWA_MSGLIN
Optional: Yes
Call by Reference: Yes

CONTAINER_VALUES - -> Values for container instance to be created

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

CONTAINER_VALUES_NO_CHECK -

Data type: SWACONEXTV
Optional: Yes
Call by Reference: Yes

STRUCTURED_MESSAGES -

Data type: SWR_MSTRUC
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for SWA_CHECK_PD_CONTAINER_DATA 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_result  TYPE SY-SUBRC, "   
lv_pdobject  TYPE RHOBJECTS-OBJECT, "   
lt_container_instance  TYPE STANDARD TABLE OF SWCONT, "   
lv_language  TYPE SY-LANGU, "   SY-LANGU
lt_messages  TYPE STANDARD TABLE OF SWA_MSGLIN, "   
lv_dataflow  TYPE SWABINDEF-DATAFLOW, "   'E'
lt_container_values  TYPE STANDARD TABLE OF SWACONEXTV, "   
lv_internal_date_n_time  TYPE SY-INPUT, "   
lt_container_values_no_check  TYPE STANDARD TABLE OF SWACONEXTV, "   
lt_structured_messages  TYPE STANDARD TABLE OF SWR_MSTRUC. "   

  CALL FUNCTION 'SWA_CHECK_PD_CONTAINER_DATA'  "
    EXPORTING
         PDOBJECT = lv_pdobject
         LANGUAGE = lv_language
         DATAFLOW = lv_dataflow
         INTERNAL_DATE_N_TIME = lv_internal_date_n_time
    IMPORTING
         RESULT = lv_result
    TABLES
         CONTAINER_INSTANCE = lt_container_instance
         MESSAGES = lt_messages
         CONTAINER_VALUES = lt_container_values
         CONTAINER_VALUES_NO_CHECK = lt_container_values_no_check
         STRUCTURED_MESSAGES = lt_structured_messages
. " SWA_CHECK_PD_CONTAINER_DATA




ABAP code using 7.40 inline data declarations to call FM SWA_CHECK_PD_CONTAINER_DATA

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 SUBRC FROM SY INTO @DATA(ld_result).
 
"SELECT single OBJECT FROM RHOBJECTS INTO @DATA(ld_pdobject).
 
 
"SELECT single LANGU FROM SY INTO @DATA(ld_language).
DATA(ld_language) = SY-LANGU.
 
 
"SELECT single DATAFLOW FROM SWABINDEF INTO @DATA(ld_dataflow).
DATA(ld_dataflow) = 'E'.
 
 
"SELECT single INPUT FROM SY INTO @DATA(ld_internal_date_n_time).
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!