SAP /SCWM/WAVE_SPLIT_EXT Function Module for Split Waves









/SCWM/WAVE_SPLIT_EXT is a standard /scwm/wave split ext SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Split Waves 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 /scwm/wave split ext FM, simply by entering the name /SCWM/WAVE_SPLIT_EXT into the relevant SAP transaction such as SE37 or SE38.

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



Function /SCWM/WAVE_SPLIT_EXT 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 '/SCWM/WAVE_SPLIT_EXT'"Split Waves
EXPORTING
IV_LGNUM = "Lagernummer/Lagerkomplex
IV_RDOCCAT = "Belegtyp für Belegreferenz und belegbezogene Bestände
IV_WAVE = "Welle
* IT_WAVE_SPLIT = "Wellen Positionen mit Mengen
* IS_ATTR_SPLIT = "Wellenattribute für abgespaltene Welle
* IV_UPDATE_TASK = 'X' "Verbuchung asynchron über Verbuchung durchführen
* IV_COMMIT_WORK = ' ' "Verarbeitung mit COMMIT WORK

IMPORTING
ET_WAVEHDR = "Interne Tabelle: Wellenköpfe
ET_WAVEITM = "Interner Tabellentyp: Wellenpositionen
ET_DLV_HEADER = "Lieferungskopf (PRD) für Leseoperationen
ET_DLV_ITEM = "Lieferungsposition (PRD) für Leseoperationen
ET_BAPIRET = "Returntabelle
EV_SEVERITY = "Meldungstyp: S Success, E Error, W Warning, I Info, A Abort
.



IMPORTING Parameters details for /SCWM/WAVE_SPLIT_EXT

IV_LGNUM - Lagernummer/Lagerkomplex

Data type: /SCWM/LGNUM
Optional: No
Call by Reference: Yes

IV_RDOCCAT - Belegtyp für Belegreferenz und belegbezogene Bestände

Data type: /SCWM/DE_DOCCAT
Optional: No
Call by Reference: Yes

IV_WAVE - Welle

Data type: /SCWM/DE_WAVE
Optional: No
Call by Reference: Yes

IT_WAVE_SPLIT - Wellen Positionen mit Mengen

Data type: /SCWM/TT_WAVE_ITM
Optional: Yes
Call by Reference: Yes

IS_ATTR_SPLIT - Wellenattribute für abgespaltene Welle

Data type: /SCWM/S_WAVEATT_CH
Optional: Yes
Call by Reference: Yes

IV_UPDATE_TASK - Verbuchung asynchron über Verbuchung durchführen

Data type: /SCWM/RL03AVERBU
Default: 'X'
Optional: Yes
Call by Reference: Yes

IV_COMMIT_WORK - Verarbeitung mit COMMIT WORK

Data type: /SCWM/RL03ACOMIT
Default: SPACE
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for /SCWM/WAVE_SPLIT_EXT

ET_WAVEHDR - Interne Tabelle: Wellenköpfe

Data type: /SCWM/TT_WAVEHDR_INT
Optional: No
Call by Reference: Yes

ET_WAVEITM - Interner Tabellentyp: Wellenpositionen

Data type: /SCWM/TT_WAVEITM_INT
Optional: No
Call by Reference: Yes

ET_DLV_HEADER - Lieferungskopf (PRD) für Leseoperationen

Data type: /SCWM/DLV_HEADER_OUT_PRD_TAB
Optional: No
Call by Reference: Yes

ET_DLV_ITEM - Lieferungsposition (PRD) für Leseoperationen

Data type: /SCWM/DLV_ITEM_OUT_PRD_TAB
Optional: No
Call by Reference: Yes

ET_BAPIRET - Returntabelle

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

EV_SEVERITY - Meldungstyp: S Success, E Error, W Warning, I Info, A Abort

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

Copy and paste ABAP code example for /SCWM/WAVE_SPLIT_EXT 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_iv_lgnum  TYPE /SCWM/LGNUM, "   
lv_et_wavehdr  TYPE /SCWM/TT_WAVEHDR_INT, "   
lv_et_waveitm  TYPE /SCWM/TT_WAVEITM_INT, "   
lv_iv_rdoccat  TYPE /SCWM/DE_DOCCAT, "   
lv_iv_wave  TYPE /SCWM/DE_WAVE, "   
lv_et_dlv_header  TYPE /SCWM/DLV_HEADER_OUT_PRD_TAB, "   
lv_et_dlv_item  TYPE /SCWM/DLV_ITEM_OUT_PRD_TAB, "   
lv_it_wave_split  TYPE /SCWM/TT_WAVE_ITM, "   
lv_et_bapiret  TYPE BAPIRET2_T, "   
lv_is_attr_split  TYPE /SCWM/S_WAVEATT_CH, "   
lv_ev_severity  TYPE BAPI_MTYPE, "   
lv_iv_update_task  TYPE /SCWM/RL03AVERBU, "   'X'
lv_iv_commit_work  TYPE /SCWM/RL03ACOMIT. "   SPACE

  CALL FUNCTION '/SCWM/WAVE_SPLIT_EXT'  "Split Waves
    EXPORTING
         IV_LGNUM = lv_iv_lgnum
         IV_RDOCCAT = lv_iv_rdoccat
         IV_WAVE = lv_iv_wave
         IT_WAVE_SPLIT = lv_it_wave_split
         IS_ATTR_SPLIT = lv_is_attr_split
         IV_UPDATE_TASK = lv_iv_update_task
         IV_COMMIT_WORK = lv_iv_commit_work
    IMPORTING
         ET_WAVEHDR = lv_et_wavehdr
         ET_WAVEITM = lv_et_waveitm
         ET_DLV_HEADER = lv_et_dlv_header
         ET_DLV_ITEM = lv_et_dlv_item
         ET_BAPIRET = lv_et_bapiret
         EV_SEVERITY = lv_ev_severity
. " /SCWM/WAVE_SPLIT_EXT




ABAP code using 7.40 inline data declarations to call FM /SCWM/WAVE_SPLIT_EXT

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_update_task) = 'X'.
 
DATA(ld_iv_commit_work) = ' '.
 


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!