SAP ALE_GOODSMVT_CANCEL Function Module for NOTRANSL: BAPI -> IDoc: ALE_GOODSMVT_CANCEL









ALE_GOODSMVT_CANCEL is a standard ale goodsmvt cancel SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: BAPI -> IDoc: ALE_GOODSMVT_CANCEL 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 ale goodsmvt cancel FM, simply by entering the name ALE_GOODSMVT_CANCEL into the relevant SAP transaction such as SE37 or SE38.

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



Function ALE_GOODSMVT_CANCEL 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 'ALE_GOODSMVT_CANCEL'"NOTRANSL: BAPI -> IDoc: ALE_GOODSMVT_CANCEL
EXPORTING
MATERIALDOCUMENT = "Number of a Material Document
MATDOCUMENTYEAR = "Material Document Year
* GOODSMVTPSTNGDATE = "
* GOODSMVTPRUNAME = "
* OBJ_TYPE = 'BUS2017' "
* SERIAL_ID = '0' "

TABLES
* GOODSMVTMATDOCITEM = "
RECEIVERS = "
* COMMUNICATION_DOCUMENTS = "
* APPLICATION_OBJECTS = "

EXCEPTIONS
ERROR_CREATING_IDOCS = 1
.



IMPORTING Parameters details for ALE_GOODSMVT_CANCEL

MATERIALDOCUMENT - Number of a Material Document

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

MATDOCUMENTYEAR - Material Document Year

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

GOODSMVTPSTNGDATE -

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

GOODSMVTPRUNAME -

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

OBJ_TYPE -

Data type: SERIAL-OBJ_TYPE
Default: 'BUS2017'
Optional: Yes
Call by Reference: No ( called with pass by value option)

SERIAL_ID -

Data type: SERIAL-CHNUM
Default: '0'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for ALE_GOODSMVT_CANCEL

GOODSMVTMATDOCITEM -

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

RECEIVERS -

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

COMMUNICATION_DOCUMENTS -

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

APPLICATION_OBJECTS -

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

EXCEPTIONS details

ERROR_CREATING_IDOCS -

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

Copy and paste ABAP code example for ALE_GOODSMVT_CANCEL 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_materialdocument  TYPE BAPI2017_GM_HEAD_02-MAT_DOC, "   
lt_goodsmvtmatdocitem  TYPE STANDARD TABLE OF BAPI2017_GM_ITEM_04, "   
lv_error_creating_idocs  TYPE BAPI2017_GM_ITEM_04, "   
lt_receivers  TYPE STANDARD TABLE OF BDI_LOGSYS, "   
lv_matdocumentyear  TYPE BAPI2017_GM_HEAD_02-DOC_YEAR, "   
lv_goodsmvtpstngdate  TYPE BAPI2017_GM_HEAD_02-PSTNG_DATE, "   
lt_communication_documents  TYPE STANDARD TABLE OF SWOTOBJID, "   
lv_goodsmvtpruname  TYPE BAPI2017_GM_HEAD_01-PR_UNAME, "   
lt_application_objects  TYPE STANDARD TABLE OF SWOTOBJID, "   
lv_obj_type  TYPE SERIAL-OBJ_TYPE, "   'BUS2017'
lv_serial_id  TYPE SERIAL-CHNUM. "   '0'

  CALL FUNCTION 'ALE_GOODSMVT_CANCEL'  "NOTRANSL: BAPI -> IDoc: ALE_GOODSMVT_CANCEL
    EXPORTING
         MATERIALDOCUMENT = lv_materialdocument
         MATDOCUMENTYEAR = lv_matdocumentyear
         GOODSMVTPSTNGDATE = lv_goodsmvtpstngdate
         GOODSMVTPRUNAME = lv_goodsmvtpruname
         OBJ_TYPE = lv_obj_type
         SERIAL_ID = lv_serial_id
    TABLES
         GOODSMVTMATDOCITEM = lt_goodsmvtmatdocitem
         RECEIVERS = lt_receivers
         COMMUNICATION_DOCUMENTS = lt_communication_documents
         APPLICATION_OBJECTS = lt_application_objects
    EXCEPTIONS
        ERROR_CREATING_IDOCS = 1
. " ALE_GOODSMVT_CANCEL




ABAP code using 7.40 inline data declarations to call FM ALE_GOODSMVT_CANCEL

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.

"SELECT single MAT_DOC FROM BAPI2017_GM_HEAD_02 INTO @DATA(ld_materialdocument).
 
 
 
 
"SELECT single DOC_YEAR FROM BAPI2017_GM_HEAD_02 INTO @DATA(ld_matdocumentyear).
 
"SELECT single PSTNG_DATE FROM BAPI2017_GM_HEAD_02 INTO @DATA(ld_goodsmvtpstngdate).
 
 
"SELECT single PR_UNAME FROM BAPI2017_GM_HEAD_01 INTO @DATA(ld_goodsmvtpruname).
 
 
"SELECT single OBJ_TYPE FROM SERIAL INTO @DATA(ld_obj_type).
DATA(ld_obj_type) = 'BUS2017'.
 
"SELECT single CHNUM FROM SERIAL INTO @DATA(ld_serial_id).
DATA(ld_serial_id) = '0'.
 


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!