SAP BAPI_WASTEORDERWEIGH_UPLOAD Function Module for Upload weighing data for waste disposal order









BAPI_WASTEORDERWEIGH_UPLOAD is a standard bapi wasteorderweigh upload SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Upload weighing data for waste disposal order 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 bapi wasteorderweigh upload FM, simply by entering the name BAPI_WASTEORDERWEIGH_UPLOAD into the relevant SAP transaction such as SE37 or SE38.

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



Function BAPI_WASTEORDERWEIGH_UPLOAD 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 'BAPI_WASTEORDERWEIGH_UPLOAD'"Upload weighing data for waste disposal order
EXPORTING
* X_GOODSMOVEMENT = 'X' "Indicator for Good Moevement
* X_STORNO = "Indicator for Cancellation
* X_MOVE_TYPE = '561' "Movement Type (Inventory Management)
* X_GOODSMVT_CODE = '05' "Assign code to transaction for BAPI goods movement
* X_GETGOODSMVTDATA = "

IMPORTING
Y_TMSEG = "
Y_MATERIALDOCUMENT = "
Y_MJAHR = "

TABLES
WASTEORDERWEIGHINGDATAUPL = "BAPI upload structure for weighing data
* RETURN = "Return Parameter
* EXTENSIONIN = "Reference structure for BAPI parameters EXTENSIONIN/EXTENSIONOUT
.



IMPORTING Parameters details for BAPI_WASTEORDERWEIGH_UPLOAD

X_GOODSMOVEMENT - Indicator for Good Moevement

Data type: KENNZX
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_STORNO - Indicator for Cancellation

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

X_MOVE_TYPE - Movement Type (Inventory Management)

Data type: BWART
Default: '561'
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_GOODSMVT_CODE - Assign code to transaction for BAPI goods movement

Data type: GM_CODE
Default: '05'
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_GETGOODSMVTDATA -

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

EXPORTING Parameters details for BAPI_WASTEORDERWEIGH_UPLOAD

Y_TMSEG -

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

Y_MATERIALDOCUMENT -

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

Y_MJAHR -

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

TABLES Parameters details for BAPI_WASTEORDERWEIGH_UPLOAD

WASTEORDERWEIGHINGDATAUPL - BAPI upload structure for weighing data

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

RETURN - Return Parameter

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

EXTENSIONIN - Reference structure for BAPI parameters EXTENSIONIN/EXTENSIONOUT

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

Copy and paste ABAP code example for BAPI_WASTEORDERWEIGH_UPLOAD 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_y_tmseg  TYPE TY_T_MSEG, "   
lv_x_goodsmovement  TYPE KENNZX, "   'X'
lt_wasteorderweighingdataupl  TYPE STANDARD TABLE OF BAPIEORDERWEIGHINGDATAUPL_TAB, "   
lt_return  TYPE STANDARD TABLE OF EWA_BAPIRETURN1_TAB, "   
lv_x_storno  TYPE KENNZX, "   
lv_y_materialdocument  TYPE BAPI2017_GM_HEAD_RET-MAT_DOC, "   
lv_y_mjahr  TYPE MJAHR, "   
lt_extensionin  TYPE STANDARD TABLE OF BAPIPAREXTAB, "   
lv_x_move_type  TYPE BWART, "   '561'
lv_x_goodsmvt_code  TYPE GM_CODE, "   '05'
lv_x_getgoodsmvtdata  TYPE CHAR1. "   

  CALL FUNCTION 'BAPI_WASTEORDERWEIGH_UPLOAD'  "Upload weighing data for waste disposal order
    EXPORTING
         X_GOODSMOVEMENT = lv_x_goodsmovement
         X_STORNO = lv_x_storno
         X_MOVE_TYPE = lv_x_move_type
         X_GOODSMVT_CODE = lv_x_goodsmvt_code
         X_GETGOODSMVTDATA = lv_x_getgoodsmvtdata
    IMPORTING
         Y_TMSEG = lv_y_tmseg
         Y_MATERIALDOCUMENT = lv_y_materialdocument
         Y_MJAHR = lv_y_mjahr
    TABLES
         WASTEORDERWEIGHINGDATAUPL = lt_wasteorderweighingdataupl
         RETURN = lt_return
         EXTENSIONIN = lt_extensionin
. " BAPI_WASTEORDERWEIGH_UPLOAD




ABAP code using 7.40 inline data declarations to call FM BAPI_WASTEORDERWEIGH_UPLOAD

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_x_goodsmovement) = 'X'.
 
 
 
 
"SELECT single MAT_DOC FROM BAPI2017_GM_HEAD_RET INTO @DATA(ld_y_materialdocument).
 
 
 
DATA(ld_x_move_type) = '561'.
 
DATA(ld_x_goodsmvt_code) = '05'.
 
 


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!