SAP BAPI_GOODSMVT_SAPCREATE Function Module for SAP Internal Cross-System Flow of Goods
BAPI_GOODSMVT_SAPCREATE is a standard bapi goodsmvt sapcreate SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for SAP Internal Cross-System Flow of Goods 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 goodsmvt sapcreate FM, simply by entering the name BAPI_GOODSMVT_SAPCREATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: MB_BAPI2017_SAP
Program Name: SAPLMB_BAPI2017_SAP
Main Program: SAPLMB_BAPI2017_SAP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_GOODSMVT_SAPCREATE 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_GOODSMVT_SAPCREATE'"SAP Internal Cross-System Flow of Goods.
EXPORTING
IS_HEADER = "SAP Internal! Header Data
IMPORTING
MATERIALDOCUMENT = "Number of Material Document
MATDOCUMENTYEAR = "Material Doc. Year
TABLES
* IT_IMSEG = "SAP Internal! Call Data MB_CREATE_GOODS_MOVEMENT for CSFG
* IT_ITEM = "SAP Internal! Item Data from MSEG for CSFG
* IT_VALUE = "SAP Internal! Valuation Data
* IT_CSL_TOKEN = "SAP Internal! CSL Token for CSFG
* IT_DATASTORE = "SAP Internal! Enhancement GOODSMVT_SAPCREATE
* UPSLINK = "
RETURN = "Return Parameter
* IT_XIFORCE = "
IMPORTING Parameters details for BAPI_GOODSMVT_SAPCREATE
IS_HEADER - SAP Internal! Header Data
Data type: BAPI2017_SAP_HEADEROptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_GOODSMVT_SAPCREATE
MATERIALDOCUMENT - Number of Material Document
Data type: BAPI2017_SAP_KEY-MBLNROptional: No
Call by Reference: No ( called with pass by value option)
MATDOCUMENTYEAR - Material Doc. Year
Data type: BAPI2017_SAP_KEY-MJAHROptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_GOODSMVT_SAPCREATE
IT_IMSEG - SAP Internal! Call Data MB_CREATE_GOODS_MOVEMENT for CSFG
Data type: BAPI2017_SAP_IMSEGOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_ITEM - SAP Internal! Item Data from MSEG for CSFG
Data type: BAPI2017_SAP_ITEMOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_VALUE - SAP Internal! Valuation Data
Data type: BAPI2017_SAP_VALUEOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_CSL_TOKEN - SAP Internal! CSL Token for CSFG
Data type: BAPI2017_SAP_CSL_TOKENOptional: Yes
Call by Reference: Yes
IT_DATASTORE - SAP Internal! Enhancement GOODSMVT_SAPCREATE
Data type: BAPI2017_SAP_DATASTOREOptional: Yes
Call by Reference: No ( called with pass by value option)
UPSLINK -
Data type: BAPI_UPSLINK_COREOptional: Yes
Call by Reference: Yes
RETURN - Return Parameter
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
IT_XIFORCE -
Data type: BAPI_XI_FORCEOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_GOODSMVT_SAPCREATE 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: | ||||
| lt_it_imseg | TYPE STANDARD TABLE OF BAPI2017_SAP_IMSEG, " | |||
| lv_is_header | TYPE BAPI2017_SAP_HEADER, " | |||
| lv_materialdocument | TYPE BAPI2017_SAP_KEY-MBLNR, " | |||
| lt_it_item | TYPE STANDARD TABLE OF BAPI2017_SAP_ITEM, " | |||
| lv_matdocumentyear | TYPE BAPI2017_SAP_KEY-MJAHR, " | |||
| lt_it_value | TYPE STANDARD TABLE OF BAPI2017_SAP_VALUE, " | |||
| lt_it_csl_token | TYPE STANDARD TABLE OF BAPI2017_SAP_CSL_TOKEN, " | |||
| lt_it_datastore | TYPE STANDARD TABLE OF BAPI2017_SAP_DATASTORE, " | |||
| lt_upslink | TYPE STANDARD TABLE OF BAPI_UPSLINK_CORE, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lt_it_xiforce | TYPE STANDARD TABLE OF BAPI_XI_FORCE. " |
|   CALL FUNCTION 'BAPI_GOODSMVT_SAPCREATE' "SAP Internal Cross-System Flow of Goods |
| EXPORTING | ||
| IS_HEADER | = lv_is_header | |
| IMPORTING | ||
| MATERIALDOCUMENT | = lv_materialdocument | |
| MATDOCUMENTYEAR | = lv_matdocumentyear | |
| TABLES | ||
| IT_IMSEG | = lt_it_imseg | |
| IT_ITEM | = lt_it_item | |
| IT_VALUE | = lt_it_value | |
| IT_CSL_TOKEN | = lt_it_csl_token | |
| IT_DATASTORE | = lt_it_datastore | |
| UPSLINK | = lt_upslink | |
| RETURN | = lt_return | |
| IT_XIFORCE | = lt_it_xiforce | |
| . " BAPI_GOODSMVT_SAPCREATE | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_GOODSMVT_SAPCREATE
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 MBLNR FROM BAPI2017_SAP_KEY INTO @DATA(ld_materialdocument). | ||||
| "SELECT single MJAHR FROM BAPI2017_SAP_KEY INTO @DATA(ld_matdocumentyear). | ||||
Search for further information about these or an SAP related objects