SAP /SCMTMS/BAPI_SCHEDULE_SAVEMULT Function Module for Create and Change TM Schedules

Search SAP Function Modules

/SCMTMS/BAPI_SCHEDULE_SAVEMULT is a standard /scmtms/bapi schedule savemult 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 and Change TM Schedules 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 /scmtms/bapi schedule savemult FM, simply by entering the name /SCMTMS/BAPI_SCHEDULE_SAVEMULT into the relevant SAP transaction such as SE37 or SE38.

Function Group: /SCMTMS/BAPI_SCHEDULE
Program Name: /SCMTMS/SAPLBAPI_SCHEDULE
Main Program: /SCMTMS/SAPLBAPI_SCHEDULE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function /SCMTMS/BAPI_SCHEDULE_SAVEMULT 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 '/SCMTMS/BAPI_SCHEDULE_SAVEMULT'"Create and Change TM Schedules
  EXPORTING
   LOGICAL_SYSTEM =  "Logical System
*  BUSINESS_SYSTEM_GROUP =  "Business System Group
*  DETERMINE_DISTANCES = ABAP_FALSE "If true ('X'), the distance between locations is calculated
*  DEPARTURE_GENERATION =  "BAPI Structure for Departure Generation Parameter

TABLES
*  SCHEDULE_ROOT =  "BAPI structure for TM Schedule Root
*  SCHEDULE_ID_CREATED =  "BAPI Structure for TM Schedule Description
*  SCHEDULE_ID_UPDATED =  "BAPI Structure for TM Schedule Description
*  RETURN =  "Return Parameter
*  SCHEDULE_DEP =  "BAPI Structure for TM Schedule Departure
*  SCHEDULE_DEP_LOC =  "BAPI Structure for TM Schedule Location
*  SCHEDULE_DEP_RULES =  "BAPI Structure for TM Schedule Departure Rule
*  SCHEDULE_DEP_RL_STG =  "BAPI Structure for TM Schedule Departure Rule Stage
*  SCHEDULE_DESC =  "BAPI Structure for TM Schedule Description
*  SCHEDULE_LOC =  "BAPI Structure for TM Schedule Location
*  EXTENSION_IN =  "Ref. structure for BAPI parameter ExtensionIn/ExtensionOut
*  EXTENSION_OUT =  "Ref. structure for BAPI parameter ExtensionIn/ExtensionOut

.

IMPORTING Parameters details for /SCMTMS/BAPI_SCHEDULE_SAVEMULT

LOGICAL_SYSTEM - Logical System

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

BUSINESS_SYSTEM_GROUP - Business System Group

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

DETERMINE_DISTANCES - If true ('X'), the distance between locations is calculated

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

DEPARTURE_GENERATION - BAPI Structure for Departure Generation Parameter

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

TABLES Parameters details for /SCMTMS/BAPI_SCHEDULE_SAVEMULT

SCHEDULE_ROOT - BAPI structure for TM Schedule Root

Data type: /SCMTMS/S_SCH_BAPI_ROOT
Optional: Yes
Call by Reference: Yes

SCHEDULE_ID_CREATED - BAPI Structure for TM Schedule Description

Data type: /SCMTMS/S_SCH_BAPI_DESCRIPTION
Optional: Yes
Call by Reference: Yes

SCHEDULE_ID_UPDATED - BAPI Structure for TM Schedule Description

Data type: /SCMTMS/S_SCH_BAPI_DESCRIPTION
Optional: Yes
Call by Reference: Yes

RETURN - Return Parameter

Data type: BAPIRET2
Optional: Yes
Call by Reference: Yes

SCHEDULE_DEP - BAPI Structure for TM Schedule Departure

Data type: /SCMTMS/S_SCH_BAPI_DEP
Optional: Yes
Call by Reference: Yes

SCHEDULE_DEP_LOC - BAPI Structure for TM Schedule Location

Data type: /SCMTMS/S_SCH_BAPI_DEP_LOC
Optional: Yes
Call by Reference: Yes

SCHEDULE_DEP_RULES - BAPI Structure for TM Schedule Departure Rule

Data type: /SCMTMS/S_SCH_BAPI_DEP_RULES
Optional: Yes
Call by Reference: Yes

SCHEDULE_DEP_RL_STG - BAPI Structure for TM Schedule Departure Rule Stage

Data type: /SCMTMS/S_SCH_BAPI_DEP_RL_STG
Optional: Yes
Call by Reference: Yes

SCHEDULE_DESC - BAPI Structure for TM Schedule Description

Data type: /SCMTMS/S_SCH_BAPI_DESCRIPTION
Optional: Yes
Call by Reference: Yes

SCHEDULE_LOC - BAPI Structure for TM Schedule Location

Data type: /SCMTMS/S_SCH_BAPI_LOCATION
Optional: Yes
Call by Reference: Yes

EXTENSION_IN - Ref. structure for BAPI parameter ExtensionIn/ExtensionOut

Data type: BAPIPAREX
Optional: Yes
Call by Reference: Yes

EXTENSION_OUT - Ref. structure for BAPI parameter ExtensionIn/ExtensionOut

Data type: BAPIPAREX
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for /SCMTMS/BAPI_SCHEDULE_SAVEMULT 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.

ABAP code using 7.40 inline data declarations to call FM /SCMTMS/BAPI_SCHEDULE_SAVEMULT

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