SCWB_CINST_BUILD_QUEUE_N SAP Function module

SCWB_CINST_BUILD_QUEUE_N is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name SCWB_CINST_BUILD_QUEUE_N into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: SCWC
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM SCWB_CINST_BUILD_QUEUE_N - SCWB CINST BUILD QUEUE N

CALL FUNCTION 'SCWB_CINST_BUILD_QUEUE_N' "
* EXPORTING
*   iv_with_manual_activities = SPACE  " boole_d
*   iv_all_cinsts_needed = SPACE  " boole_d
*   iv_update = SPACE           " boole_d
  IMPORTING
    et_queue =                  " bcwbn_corr_instruction_queue
    et_incomplete_notes =       " bcwbn_notes
    et_flat_queue =             " bcwbn_corr_instructions
    et_notes_checked =          " scwb_api_t_notenumber
    ev_cinst_not_matching =     " boole_d
    ev_merge_impossible =       " boole_d
    es_failing_note =           " bcwbn_note
* CHANGING
*   ct_corr_instructions =      " bcwbn_corr_instructions
*   ct_to_be_deimplemented =    " bcwbn_corr_instructions
*   ct_patch_levels =           " bcwbn_delivery_events
  EXCEPTIONS
    UNREADABLE_DATA = 1         "
    CORR_INSTRUCTION_NOT_FOUND = 2  "
    INCONSISTENT_DELIVERY_DATA = 3  "
    UNDEFINED_MANUAL_ACTIVITY = 4  "
    .  "  SCWB_CINST_BUILD_QUEUE_N

ABAP code example for Function Module SCWB_CINST_BUILD_QUEUE_N

The ABAP code below is a full code listing to execute function module SCWB_CINST_BUILD_QUEUE_N including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_et_queue  
 
 TYPE BCWBN_CORR_INSTRUCTION_QUEUE
,
ld_et_incomplete_notes  
 
 TYPE BCWBN_NOTES
,
ld_et_flat_queue  
 
 TYPE BCWBN_CORR_INSTRUCTIONS
,
ld_et_notes_checked  
 
 TYPE SCWB_API_T_NOTENUMBER
,
ld_ev_cinst_not_matching  
 
 TYPE BOOLE_D
,
ld_ev_merge_impossible  
 
 TYPE BOOLE_D
,
ld_es_failing_note  
 
 TYPE BCWBN_NOTE
.


DATA(ld_ct_corr_instructions) = 'Check type of data required'.

DATA(ld_ct_to_be_deimplemented) = 'Check type of data required'.

DATA(ld_ct_patch_levels) = 'Check type of data required'.

DATA(ld_iv_with_manual_activities) = 'Check type of data required'.

DATA(ld_iv_all_cinsts_needed) = 'Check type of data required'.

DATA(ld_iv_update) = 'Check type of data required'.
.

CALL FUNCTION 'SCWB_CINST_BUILD_QUEUE_N'
* EXPORTING
*   iv_with_manual_activities =    ld_iv_with_manual_activities
*   iv_all_cinsts_needed =       ld_iv_all_cinsts_needed
*   iv_update =                  ld_iv_update
  IMPORTING
    et_queue =                   ld_et_queue
    et_incomplete_notes =        ld_et_incomplete_notes
    et_flat_queue =              ld_et_flat_queue
    et_notes_checked =           ld_et_notes_checked
    ev_cinst_not_matching =      ld_ev_cinst_not_matching
    ev_merge_impossible =        ld_ev_merge_impossible
    es_failing_note =            ld_es_failing_note
* CHANGING
*   ct_corr_instructions =       ld_ct_corr_instructions
*   ct_to_be_deimplemented =     ld_ct_to_be_deimplemented
*   ct_patch_levels =            ld_ct_patch_levels
  EXCEPTIONS
    UNREADABLE_DATA =            1
    CORR_INSTRUCTION_NOT_FOUND =    2
    INCONSISTENT_DELIVERY_DATA =    3
    UNDEFINED_MANUAL_ACTIVITY =    4
    .  "  SCWB_CINST_BUILD_QUEUE_N

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_ct_corr_instructions
 
 TYPE BCWBN_CORR_INSTRUCTIONS ,
ld_et_queue
 
 TYPE BCWBN_CORR_INSTRUCTION_QUEUE ,
ld_iv_with_manual_activities
 
 TYPE BOOLE_D ,
ld_ct_to_be_deimplemented
 
 TYPE BCWBN_CORR_INSTRUCTIONS ,
ld_et_incomplete_notes
 
 TYPE BCWBN_NOTES ,
ld_iv_all_cinsts_needed
 
 TYPE BOOLE_D ,
ld_ct_patch_levels
 
 TYPE BCWBN_DELIVERY_EVENTS ,
ld_et_flat_queue
 
 TYPE BCWBN_CORR_INSTRUCTIONS ,
ld_iv_update
 
 TYPE BOOLE_D ,
ld_et_notes_checked
 
 TYPE SCWB_API_T_NOTENUMBER ,
ld_ev_cinst_not_matching
 
 TYPE BOOLE_D ,
ld_ev_merge_impossible
 
 TYPE BOOLE_D ,
ld_es_failing_note
 
 TYPE BCWBN_NOTE .


ld_ct_corr_instructions = 'Check type of data required'.
ld_iv_with_manual_activities = 'Check type of data required'.
ld_ct_to_be_deimplemented = 'Check type of data required'.
ld_iv_all_cinsts_needed = 'Check type of data required'.
ld_ct_patch_levels = 'Check type of data required'.
ld_iv_update = 'Check type of data required'.