SAP ALE_MOSRVAPS_SAVEMULTI3 Function Module for BAPI -> IDoc: ALE_MOSRVAPS_SAVEMULTI3
ALE_MOSRVAPS_SAVEMULTI3 is a standard ale mosrvaps savemulti3 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_MOSRVAPS_SAVEMULTI3 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 mosrvaps savemulti3 FM, simply by entering the name ALE_MOSRVAPS_SAVEMULTI3 into the relevant SAP transaction such as SE37 or SE38.
Function Group: 10503
Program Name: SAPL10503
Main Program: SAPL10503
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ALE_MOSRVAPS_SAVEMULTI3 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_MOSRVAPS_SAVEMULTI3'"BAPI -> IDoc: ALE_MOSRVAPS_SAVEMULTI3.
EXPORTING
LOGICALSYSTEM = "
* EVENTCONTROL = ' ' "
* OBJ_TYPE = 'BUS10503' "
* SERIAL_ID = '0' "
* ORDERTYPE = '6' "
* EXTNUMBERASSIGNMENT = 'X' "
* COMMITCONTROL = 'E' "
* PLNGVERSION = '000' "
* STRATEGYPROFILE = "
* NOCREATE = "
* CHECKSOURCEEXISTENCE = 'X' "
* PLANNINGMODEUSAGE = "
TABLES
ORDERHEAD = "
* MAPPINGDATA = "
* EXTENSIONIN = "
RECEIVERS = "
* COMMUNICATION_DOCUMENTS = "
* APPLICATION_OBJECTS = "
* ORDERHEADX = "
* CFGHEADERS = "
* CFGINSTANCES = "
* CFGPARTOF = "
* CFGVALUES = "
* CFGVARKEYS = "
* CFGBLOB = "
* CFGREFOBJECT = "
EXCEPTIONS
ERROR_CREATING_IDOCS = 1
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPL10503_001 User Exit Inbound Processing of Orders with SNP PPMs
EXIT_SAPL10503_002 User Exit for Method 'SaveMultiple' of Business Object BUS10503
EXIT_SAPL10503_003 User Exit for Method 'CreateFromTemplate' of Business Object BUS10503
EXIT_SAPL10503_004 User Exit for Method 'GetList' of Business Objects BUS10503
EXIT_SAPL10503_005 User Exit for Method 'DeleteMultiple' of Business Object BUS10503
IMPORTING Parameters details for ALE_MOSRVAPS_SAVEMULTI3
LOGICALSYSTEM -
Data type: BAPIGENFIELDS-LOGSYSTEMOptional: No
Call by Reference: No ( called with pass by value option)
EVENTCONTROL -
Data type: BAPI10503GENFIELDS-EVENT_CONTROLDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
OBJ_TYPE -
Data type: SERIAL-OBJ_TYPEDefault: 'BUS10503'
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)
ORDERTYPE -
Data type: BAPI10503GENFIELDS-ORDER_TYPEDefault: '6'
Optional: No
Call by Reference: No ( called with pass by value option)
EXTNUMBERASSIGNMENT -
Data type: BAPI10503GENFIELDS-EXT_NR_FLAGDefault: 'X'
Optional: No
Call by Reference: No ( called with pass by value option)
COMMITCONTROL -
Data type: BAPI10503GENFIELDS-COMMCTRLDefault: 'E'
Optional: No
Call by Reference: No ( called with pass by value option)
PLNGVERSION -
Data type: BAPIGENFIELDS-VRSIOEXDefault: '000'
Optional: No
Call by Reference: No ( called with pass by value option)
STRATEGYPROFILE -
Data type: BAPI10503ORDSTRATPROFSETOptional: Yes
Call by Reference: No ( called with pass by value option)
NOCREATE -
Data type: BAPI10503GENFIELDS-NO_CREATEOptional: Yes
Call by Reference: No ( called with pass by value option)
CHECKSOURCEEXISTENCE -
Data type: BAPI10503GENFIELDS-CHECK_PPMDefault: 'X'
Optional: No
Call by Reference: No ( called with pass by value option)
PLANNINGMODEUSAGE -
Data type: BAPI10503GENFIELDS-PLANNING_MODEOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ALE_MOSRVAPS_SAVEMULTI3
ORDERHEAD -
Data type: BAPI10503ORDHEADINOptional: No
Call by Reference: No ( called with pass by value option)
MAPPINGDATA -
Data type: BAPI10503ORDMAPRETOOptional: Yes
Call by Reference: No ( called with pass by value option)
EXTENSIONIN -
Data type: BAPIPAREXOptional: Yes
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)
ORDERHEADX -
Data type: BAPI10503ORDHEADINXOptional: Yes
Call by Reference: No ( called with pass by value option)
CFGHEADERS -
Data type: BAPIAPOCUCFGINOptional: Yes
Call by Reference: No ( called with pass by value option)
CFGINSTANCES -
Data type: BAPIAPOCUINSINOptional: Yes
Call by Reference: No ( called with pass by value option)
CFGPARTOF -
Data type: BAPIAPOCUPRTINOptional: Yes
Call by Reference: No ( called with pass by value option)
CFGVALUES -
Data type: BAPIAPOCUVALINOptional: Yes
Call by Reference: No ( called with pass by value option)
CFGVARKEYS -
Data type: BAPIAPOCUVKINOptional: Yes
Call by Reference: No ( called with pass by value option)
CFGBLOB -
Data type: BAPIAPOCUBLBINOptional: Yes
Call by Reference: No ( called with pass by value option)
CFGREFOBJECT -
Data type: BAPI10500REFOBJECTOptional: 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_MOSRVAPS_SAVEMULTI3 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_orderhead | TYPE STANDARD TABLE OF BAPI10503ORDHEADIN, " | |||
| lv_logicalsystem | TYPE BAPIGENFIELDS-LOGSYSTEM, " | |||
| lv_error_creating_idocs | TYPE BAPIGENFIELDS, " | |||
| lt_mappingdata | TYPE STANDARD TABLE OF BAPI10503ORDMAPRETO, " | |||
| lv_eventcontrol | TYPE BAPI10503GENFIELDS-EVENT_CONTROL, " SPACE | |||
| lv_obj_type | TYPE SERIAL-OBJ_TYPE, " 'BUS10503' | |||
| lt_extensionin | TYPE STANDARD TABLE OF BAPIPAREX, " | |||
| lt_receivers | TYPE STANDARD TABLE OF BDI_LOGSYS, " | |||
| lv_serial_id | TYPE SERIAL-CHNUM, " '0' | |||
| lt_communication_documents | TYPE STANDARD TABLE OF SWOTOBJID, " | |||
| lt_application_objects | TYPE STANDARD TABLE OF SWOTOBJID, " | |||
| lv_ordertype | TYPE BAPI10503GENFIELDS-ORDER_TYPE, " '6' | |||
| lt_orderheadx | TYPE STANDARD TABLE OF BAPI10503ORDHEADINX, " | |||
| lt_cfgheaders | TYPE STANDARD TABLE OF BAPIAPOCUCFGIN, " | |||
| lv_extnumberassignment | TYPE BAPI10503GENFIELDS-EXT_NR_FLAG, " 'X' | |||
| lt_cfginstances | TYPE STANDARD TABLE OF BAPIAPOCUINSIN, " | |||
| lv_commitcontrol | TYPE BAPI10503GENFIELDS-COMMCTRL, " 'E' | |||
| lt_cfgpartof | TYPE STANDARD TABLE OF BAPIAPOCUPRTIN, " | |||
| lv_plngversion | TYPE BAPIGENFIELDS-VRSIOEX, " '000' | |||
| lt_cfgvalues | TYPE STANDARD TABLE OF BAPIAPOCUVALIN, " | |||
| lv_strategyprofile | TYPE BAPI10503ORDSTRATPROFSET, " | |||
| lv_nocreate | TYPE BAPI10503GENFIELDS-NO_CREATE, " | |||
| lt_cfgvarkeys | TYPE STANDARD TABLE OF BAPIAPOCUVKIN, " | |||
| lt_cfgblob | TYPE STANDARD TABLE OF BAPIAPOCUBLBIN, " | |||
| lv_checksourceexistence | TYPE BAPI10503GENFIELDS-CHECK_PPM, " 'X' | |||
| lt_cfgrefobject | TYPE STANDARD TABLE OF BAPI10500REFOBJECT, " | |||
| lv_planningmodeusage | TYPE BAPI10503GENFIELDS-PLANNING_MODE. " |
|   CALL FUNCTION 'ALE_MOSRVAPS_SAVEMULTI3' "BAPI -> IDoc: ALE_MOSRVAPS_SAVEMULTI3 |
| EXPORTING | ||
| LOGICALSYSTEM | = lv_logicalsystem | |
| EVENTCONTROL | = lv_eventcontrol | |
| OBJ_TYPE | = lv_obj_type | |
| SERIAL_ID | = lv_serial_id | |
| ORDERTYPE | = lv_ordertype | |
| EXTNUMBERASSIGNMENT | = lv_extnumberassignment | |
| COMMITCONTROL | = lv_commitcontrol | |
| PLNGVERSION | = lv_plngversion | |
| STRATEGYPROFILE | = lv_strategyprofile | |
| NOCREATE | = lv_nocreate | |
| CHECKSOURCEEXISTENCE | = lv_checksourceexistence | |
| PLANNINGMODEUSAGE | = lv_planningmodeusage | |
| TABLES | ||
| ORDERHEAD | = lt_orderhead | |
| MAPPINGDATA | = lt_mappingdata | |
| EXTENSIONIN | = lt_extensionin | |
| RECEIVERS | = lt_receivers | |
| COMMUNICATION_DOCUMENTS | = lt_communication_documents | |
| APPLICATION_OBJECTS | = lt_application_objects | |
| ORDERHEADX | = lt_orderheadx | |
| CFGHEADERS | = lt_cfgheaders | |
| CFGINSTANCES | = lt_cfginstances | |
| CFGPARTOF | = lt_cfgpartof | |
| CFGVALUES | = lt_cfgvalues | |
| CFGVARKEYS | = lt_cfgvarkeys | |
| CFGBLOB | = lt_cfgblob | |
| CFGREFOBJECT | = lt_cfgrefobject | |
| EXCEPTIONS | ||
| ERROR_CREATING_IDOCS = 1 | ||
| . " ALE_MOSRVAPS_SAVEMULTI3 | ||
ABAP code using 7.40 inline data declarations to call FM ALE_MOSRVAPS_SAVEMULTI3
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 LOGSYSTEM FROM BAPIGENFIELDS INTO @DATA(ld_logicalsystem). | ||||
| "SELECT single EVENT_CONTROL FROM BAPI10503GENFIELDS INTO @DATA(ld_eventcontrol). | ||||
| DATA(ld_eventcontrol) | = ' '. | |||
| "SELECT single OBJ_TYPE FROM SERIAL INTO @DATA(ld_obj_type). | ||||
| DATA(ld_obj_type) | = 'BUS10503'. | |||
| "SELECT single CHNUM FROM SERIAL INTO @DATA(ld_serial_id). | ||||
| DATA(ld_serial_id) | = '0'. | |||
| "SELECT single ORDER_TYPE FROM BAPI10503GENFIELDS INTO @DATA(ld_ordertype). | ||||
| DATA(ld_ordertype) | = '6'. | |||
| "SELECT single EXT_NR_FLAG FROM BAPI10503GENFIELDS INTO @DATA(ld_extnumberassignment). | ||||
| DATA(ld_extnumberassignment) | = 'X'. | |||
| "SELECT single COMMCTRL FROM BAPI10503GENFIELDS INTO @DATA(ld_commitcontrol). | ||||
| DATA(ld_commitcontrol) | = 'E'. | |||
| "SELECT single VRSIOEX FROM BAPIGENFIELDS INTO @DATA(ld_plngversion). | ||||
| DATA(ld_plngversion) | = '000'. | |||
| "SELECT single NO_CREATE FROM BAPI10503GENFIELDS INTO @DATA(ld_nocreate). | ||||
| "SELECT single CHECK_PPM FROM BAPI10503GENFIELDS INTO @DATA(ld_checksourceexistence). | ||||
| DATA(ld_checksourceexistence) | = 'X'. | |||
| "SELECT single PLANNING_MODE FROM BAPI10503GENFIELDS INTO @DATA(ld_planningmodeusage). | ||||
Search for further information about these or an SAP related objects