SAP BAPI_ISUSMORDER_CREATEMULTIPLE Function Module for Create service orders
BAPI_ISUSMORDER_CREATEMULTIPLE is a standard bapi isusmorder createmultiple SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create service orders 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 isusmorder createmultiple FM, simply by entering the name BAPI_ISUSMORDER_CREATEMULTIPLE into the relevant SAP transaction such as SE37 or SE38.
Function Group: EEWM_SV_ORD
Program Name: SAPLEEWM_SV_ORD
Main Program: SAPLEEWM_SV_ORD
Appliation area: E
Release date: 21-Jul-1998
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_ISUSMORDER_CREATEMULTIPLE 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_ISUSMORDER_CREATEMULTIPLE'"Create service orders.
EXPORTING
* NO_APPL_LOG = "No Application Log, RETURN Table Used Instead
TABLES
ORDERDATA = "Data for order creation
RETURN = "Return Code
* OBJECTLIST = "Object list
* LONGTEXT = "Long Text
* PERMITS = "Permits
* OBJECTRELATION = "Object links
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_SAPLEEWM_SV_ORD_001 IS-U: User Exit - Display Service Orders in Customer Overview
EXIT_SAPLEEWM_SV_ORD_002 IS-U: User Exit - Display Notifications in Customer Overview
EXIT_SAPLEEWM_SV_ORD_003 IS-U: Enhancement for Displaying Notifs and Orders in Customer Overview
IMPORTING Parameters details for BAPI_ISUSMORDER_CREATEMULTIPLE
NO_APPL_LOG - No Application Log, RETURN Table Used Instead
Data type: FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_ISUSMORDER_CREATEMULTIPLE
ORDERDATA - Data for order creation
Data type: BAPI_SEWOCRTOptional: No
Call by Reference: No ( called with pass by value option)
RETURN - Return Code
Data type: BAPIRETURN1Optional: No
Call by Reference: No ( called with pass by value option)
OBJECTLIST - Object list
Data type: BAPI_OBJECTLISTOptional: Yes
Call by Reference: No ( called with pass by value option)
LONGTEXT - Long Text
Data type: BAPI_LONGTEXTOptional: Yes
Call by Reference: No ( called with pass by value option)
PERMITS - Permits
Data type: BAPI_PERMITSOptional: Yes
Call by Reference: No ( called with pass by value option)
OBJECTRELATION - Object links
Data type: BAPI_OBJRELOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BAPI_ISUSMORDER_CREATEMULTIPLE 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_orderdata | TYPE STANDARD TABLE OF BAPI_SEWOCRT, " | |||
| lv_no_appl_log | TYPE FLAG, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRETURN1, " | |||
| lt_objectlist | TYPE STANDARD TABLE OF BAPI_OBJECTLIST, " | |||
| lt_longtext | TYPE STANDARD TABLE OF BAPI_LONGTEXT, " | |||
| lt_permits | TYPE STANDARD TABLE OF BAPI_PERMITS, " | |||
| lt_objectrelation | TYPE STANDARD TABLE OF BAPI_OBJREL. " |
|   CALL FUNCTION 'BAPI_ISUSMORDER_CREATEMULTIPLE' "Create service orders |
| EXPORTING | ||
| NO_APPL_LOG | = lv_no_appl_log | |
| TABLES | ||
| ORDERDATA | = lt_orderdata | |
| RETURN | = lt_return | |
| OBJECTLIST | = lt_objectlist | |
| LONGTEXT | = lt_longtext | |
| PERMITS | = lt_permits | |
| OBJECTRELATION | = lt_objectrelation | |
| . " BAPI_ISUSMORDER_CREATEMULTIPLE | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_ISUSMORDER_CREATEMULTIPLE
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.Search for further information about these or an SAP related objects