SAP ALE_MATPHYSINV_CREATE_MULT Function Module for BAPI -> IDoc: ALE_MATPHYSINV_CREATE_MULT
ALE_MATPHYSINV_CREATE_MULT is a standard ale matphysinv create mult SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for BAPI -> IDoc: ALE_MATPHYSINV_CREATE_MULT 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 matphysinv create mult FM, simply by entering the name ALE_MATPHYSINV_CREATE_MULT into the relevant SAP transaction such as SE37 or SE38.
Function Group: MB_BUS2028
Program Name: SAPLMB_BUS2028
Main Program: SAPLMB_BUS2028
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ALE_MATPHYSINV_CREATE_MULT 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_MATPHYSINV_CREATE_MULT'"BAPI -> IDoc: ALE_MATPHYSINV_CREATE_MULT.
EXPORTING
HEAD = "Header data of phys. inv. doc.
* MAXITEMS = "Max. number of items that may have a new document
* OBJ_TYPE = 'BUS2028' "
* SERIAL_ID = '0' "
TABLES
ITEMS = "Physical inventory document item data
RECEIVERS = "
* COMMUNICATION_DOCUMENTS = "
* APPLICATION_OBJECTS = "
EXCEPTIONS
ERROR_CREATING_IDOCS = 1
IMPORTING Parameters details for ALE_MATPHYSINV_CREATE_MULT
HEAD - Header data of phys. inv. doc.
Data type: BAPI_PHYSINV_CREATE_HEADOptional: No
Call by Reference: No ( called with pass by value option)
MAXITEMS - Max. number of items that may have a new document
Data type: AM07M-MAXPOOptional: Yes
Call by Reference: No ( called with pass by value option)
OBJ_TYPE -
Data type: SERIAL-OBJ_TYPEDefault: 'BUS2028'
Optional: Yes
Call by Reference: No ( called with pass by value option)
SERIAL_ID -
Data type: SERIAL-CHNUMDefault: '0'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ALE_MATPHYSINV_CREATE_MULT
ITEMS - Physical inventory document item data
Data type: BAPI_PHYSINV_CREATE_ITEMSOptional: No
Call by Reference: No ( called with pass by value option)
RECEIVERS -
Data type: BDI_LOGSYSOptional: No
Call by Reference: No ( called with pass by value option)
COMMUNICATION_DOCUMENTS -
Data type: SWOTOBJIDOptional: Yes
Call by Reference: No ( called with pass by value option)
APPLICATION_OBJECTS -
Data type: SWOTOBJIDOptional: 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_MATPHYSINV_CREATE_MULT 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_head | TYPE BAPI_PHYSINV_CREATE_HEAD, " | |||
| lt_items | TYPE STANDARD TABLE OF BAPI_PHYSINV_CREATE_ITEMS, " | |||
| lv_error_creating_idocs | TYPE BAPI_PHYSINV_CREATE_ITEMS, " | |||
| lv_maxitems | TYPE AM07M-MAXPO, " | |||
| lt_receivers | TYPE STANDARD TABLE OF BDI_LOGSYS, " | |||
| lv_obj_type | TYPE SERIAL-OBJ_TYPE, " 'BUS2028' | |||
| lt_communication_documents | TYPE STANDARD TABLE OF SWOTOBJID, " | |||
| lv_serial_id | TYPE SERIAL-CHNUM, " '0' | |||
| lt_application_objects | TYPE STANDARD TABLE OF SWOTOBJID. " |
|   CALL FUNCTION 'ALE_MATPHYSINV_CREATE_MULT' "BAPI -> IDoc: ALE_MATPHYSINV_CREATE_MULT |
| EXPORTING | ||
| HEAD | = lv_head | |
| MAXITEMS | = lv_maxitems | |
| OBJ_TYPE | = lv_obj_type | |
| SERIAL_ID | = lv_serial_id | |
| TABLES | ||
| ITEMS | = lt_items | |
| RECEIVERS | = lt_receivers | |
| COMMUNICATION_DOCUMENTS | = lt_communication_documents | |
| APPLICATION_OBJECTS | = lt_application_objects | |
| EXCEPTIONS | ||
| ERROR_CREATING_IDOCS = 1 | ||
| . " ALE_MATPHYSINV_CREATE_MULT | ||
ABAP code using 7.40 inline data declarations to call FM ALE_MATPHYSINV_CREATE_MULT
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 MAXPO FROM AM07M INTO @DATA(ld_maxitems). | ||||
| "SELECT single OBJ_TYPE FROM SERIAL INTO @DATA(ld_obj_type). | ||||
| DATA(ld_obj_type) | = 'BUS2028'. | |||
| "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