SAP SCWB_CINST_BUILD_QUEUE Function Module for









SCWB_CINST_BUILD_QUEUE is a standard scwb cinst build queue 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 cinst build queue FM, simply by entering the name SCWB_CINST_BUILD_QUEUE into the relevant SAP transaction such as SE37 or SE38.

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



Function SCWB_CINST_BUILD_QUEUE 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_CINST_BUILD_QUEUE'"
EXPORTING
* IV_ALL_CINSTS_NEEDED = ' ' "

IMPORTING
ET_QUEUE = "
ET_INCOMPLETE_NOTES = "
ET_FLAT_QUEUE = "
ET_NOTES_CHECKED = "
EV_CINST_NOT_MATCHING = "
EV_MERGE_IMPOSSIBLE = "

CHANGING
* CT_CORR_INSTRUCTIONS = "
* CT_TO_BE_DEIMPLEMENTED = "
* CT_PATCH_LEVELS = "

EXCEPTIONS
UNREADABLE_DATA = 1 CORR_INSTRUCTION_NOT_FOUND = 2 INCONSISTENT_DELIVERY_DATA = 3 UNDEFINED_MANUAL_ACTIVITY = 4
.



IMPORTING Parameters details for SCWB_CINST_BUILD_QUEUE

IV_ALL_CINSTS_NEEDED -

Data type: BOOLE_D
Default: SPACE
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for SCWB_CINST_BUILD_QUEUE

ET_QUEUE -

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

ET_INCOMPLETE_NOTES -

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

ET_FLAT_QUEUE -

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

ET_NOTES_CHECKED -

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

EV_CINST_NOT_MATCHING -

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

EV_MERGE_IMPOSSIBLE -

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

CHANGING Parameters details for SCWB_CINST_BUILD_QUEUE

CT_CORR_INSTRUCTIONS -

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

CT_TO_BE_DEIMPLEMENTED -

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

CT_PATCH_LEVELS -

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

EXCEPTIONS details

UNREADABLE_DATA -

Data type:
Optional: No
Call by Reference: Yes

CORR_INSTRUCTION_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

INCONSISTENT_DELIVERY_DATA -

Data type:
Optional: No
Call by Reference: Yes

UNDEFINED_MANUAL_ACTIVITY -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SCWB_CINST_BUILD_QUEUE 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_queue  TYPE BCWBN_CORR_INSTRUCTION_QUEUE, "   
lv_unreadable_data  TYPE BCWBN_CORR_INSTRUCTION_QUEUE, "   
lv_ct_corr_instructions  TYPE BCWBN_CORR_INSTRUCTIONS, "   
lv_iv_all_cinsts_needed  TYPE BOOLE_D, "   SPACE
lv_et_incomplete_notes  TYPE BCWBN_NOTES, "   
lv_ct_to_be_deimplemented  TYPE BCWBN_CORR_INSTRUCTIONS, "   
lv_corr_instruction_not_found  TYPE BCWBN_CORR_INSTRUCTIONS, "   
lv_et_flat_queue  TYPE BCWBN_CORR_INSTRUCTIONS, "   
lv_ct_patch_levels  TYPE BCWBN_DELIVERY_EVENTS, "   
lv_inconsistent_delivery_data  TYPE BCWBN_DELIVERY_EVENTS, "   
lv_et_notes_checked  TYPE SCWB_API_T_NOTENUMBER, "   
lv_undefined_manual_activity  TYPE SCWB_API_T_NOTENUMBER, "   
lv_ev_cinst_not_matching  TYPE BOOLE_D, "   
lv_ev_merge_impossible  TYPE BOOLE_D. "   

  CALL FUNCTION 'SCWB_CINST_BUILD_QUEUE'  "
    EXPORTING
         IV_ALL_CINSTS_NEEDED = lv_iv_all_cinsts_needed
    IMPORTING
         ET_QUEUE = lv_et_queue
         ET_INCOMPLETE_NOTES = lv_et_incomplete_notes
         ET_FLAT_QUEUE = lv_et_flat_queue
         ET_NOTES_CHECKED = lv_et_notes_checked
         EV_CINST_NOT_MATCHING = lv_ev_cinst_not_matching
         EV_MERGE_IMPOSSIBLE = lv_ev_merge_impossible
    CHANGING
         CT_CORR_INSTRUCTIONS = lv_ct_corr_instructions
         CT_TO_BE_DEIMPLEMENTED = lv_ct_to_be_deimplemented
         CT_PATCH_LEVELS = lv_ct_patch_levels
    EXCEPTIONS
        UNREADABLE_DATA = 1
        CORR_INSTRUCTION_NOT_FOUND = 2
        INCONSISTENT_DELIVERY_DATA = 3
        UNDEFINED_MANUAL_ACTIVITY = 4
. " SCWB_CINST_BUILD_QUEUE




ABAP code using 7.40 inline data declarations to call FM SCWB_CINST_BUILD_QUEUE

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_all_cinsts_needed) = ' '.
 
 
 
 
 
 
 
 
 
 
 


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!