SAP SCWB_GET_COMPL_REQUESTS Function Module for









SCWB_GET_COMPL_REQUESTS is a standard scwb get compl requests 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 scwb get compl requests FM, simply by entering the name SCWB_GET_COMPL_REQUESTS into the relevant SAP transaction such as SE37 or SE38.

Function Group: SCWL
Program Name: SAPLSCWL
Main Program: SAPLSCWL
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function SCWB_GET_COMPL_REQUESTS 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 'SCWB_GET_COMPL_REQUESTS'"
  EXPORTING
*  IV_MERGE_OBJECT_LISTS = ' ' "
*  IV_PROGRESS_INDICATOR = ' ' "
*  IV_READ_FROM_CACHE = ' ' "
*  IV_REFILL_CACHE = ' ' "

 IMPORTING
   ET_REQUESTS_WD =  "

TABLES
   IT_REQUEST_NUMBERS =  "Request Number with Original System
*  ET_NON_EXISTING_REQUESTS =  "Request Number with Original System
*  ET_RFC_MESSAGES =  "RFC Call Message
*  ET_REQUESTS_NOT_IN_CACHE =  "
*  ET_UNREADABLE_REQUESTS =  "
.



IMPORTING Parameters details for SCWB_GET_COMPL_REQUESTS

IV_MERGE_OBJECT_LISTS -

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

IV_PROGRESS_INDICATOR -

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

IV_READ_FROM_CACHE -

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

IV_REFILL_CACHE -

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

EXPORTING Parameters details for SCWB_GET_COMPL_REQUESTS

ET_REQUESTS_WD -

Data type: STRHI_REQUESTS_WD
Optional: No
Call by Reference: Yes

TABLES Parameters details for SCWB_GET_COMPL_REQUESTS

IT_REQUEST_NUMBERS - Request Number with Original System

Data type: SCWBTRKORR
Optional: No
Call by Reference: Yes

ET_NON_EXISTING_REQUESTS - Request Number with Original System

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

ET_RFC_MESSAGES - RFC Call Message

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

ET_REQUESTS_NOT_IN_CACHE -

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

ET_UNREADABLE_REQUESTS -

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

Copy and paste ABAP code example for SCWB_GET_COMPL_REQUESTS 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_et_requests_wd  TYPE STRHI_REQUESTS_WD, "   
lt_it_request_numbers  TYPE STANDARD TABLE OF SCWBTRKORR, "   
lv_iv_merge_object_lists  TYPE C, "   SPACE
lv_iv_progress_indicator  TYPE C, "   SPACE
lt_et_non_existing_requests  TYPE STANDARD TABLE OF SCWBTRKORR, "   
lt_et_rfc_messages  TYPE STANDARD TABLE OF SCWBRFCMSG, "   
lv_iv_read_from_cache  TYPE C, "   SPACE
lv_iv_refill_cache  TYPE C, "   SPACE
lt_et_requests_not_in_cache  TYPE STANDARD TABLE OF SCWBTRKORR, "   
lt_et_unreadable_requests  TYPE STANDARD TABLE OF SCWBTRKORR. "   

  CALL FUNCTION 'SCWB_GET_COMPL_REQUESTS'  "
    EXPORTING
         IV_MERGE_OBJECT_LISTS = lv_iv_merge_object_lists
         IV_PROGRESS_INDICATOR = lv_iv_progress_indicator
         IV_READ_FROM_CACHE = lv_iv_read_from_cache
         IV_REFILL_CACHE = lv_iv_refill_cache
    IMPORTING
         ET_REQUESTS_WD = lv_et_requests_wd
    TABLES
         IT_REQUEST_NUMBERS = lt_it_request_numbers
         ET_NON_EXISTING_REQUESTS = lt_et_non_existing_requests
         ET_RFC_MESSAGES = lt_et_rfc_messages
         ET_REQUESTS_NOT_IN_CACHE = lt_et_requests_not_in_cache
         ET_UNREADABLE_REQUESTS = lt_et_unreadable_requests
. " SCWB_GET_COMPL_REQUESTS




ABAP code using 7.40 inline data declarations to call FM SCWB_GET_COMPL_REQUESTS

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.

 
 
DATA(ld_iv_merge_object_lists) = ' '.
 
DATA(ld_iv_progress_indicator) = ' '.
 
 
 
DATA(ld_iv_read_from_cache) = ' '.
 
DATA(ld_iv_refill_cache) = ' '.
 
 
 


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!