SAP BAPI_SERVICE_CHANGE Function Module for BAPI to Change a Service Master Record

Search SAP Function Modules

BAPI_SERVICE_CHANGE is a standard bapi service change 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 to Change a Service Master Record 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 service change FM, simply by entering the name BAPI_SERVICE_CHANGE into the relevant SAP transaction such as SE37 or SE38.

Function Group: BASB
Program Name: SAPLBASB
Main Program: SAPLBASB
Appliation area:
Release date: 31-Jan-2005
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_SERVICE_CHANGE 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_SERVICE_CHANGE'"BAPI to Change a Service Master Record
  EXPORTING
   SERVICENUMBER =  "Service Number
*  IM_SERVICE_DATA =  "General Data for Service, Import
*  IM_SERVICE_DATAX =  "Change Parameter for Service Data, Import
*  TESTRUN =  "Test Indicator

 IMPORTING
   EX_SERVICE_DATA =  "General Data for Service, Export
   EX_SERVICE_DATAX =  "Change Parameter for Service Data, Export

TABLES
   RETURN =  "Return Parameter(s)
   SERVICE_DESCRIPTION =  "Short Texts for Service
*  SERVICE_LONG_TEXTS =  "Long Texts for Service
*  EXTENSION_IN =  "Customer's Own Fields (Import Parameters)
*  EXTENSION_OUT =  "Customer's Own Fields (Export Parameters)

.

IMPORTING Parameters details for BAPI_SERVICE_CHANGE

SERVICENUMBER - Service Number

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

IM_SERVICE_DATA - General Data for Service, Import

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

IM_SERVICE_DATAX - Change Parameter for Service Data, Import

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

TESTRUN - Test Indicator

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

EXPORTING Parameters details for BAPI_SERVICE_CHANGE

EX_SERVICE_DATA - General Data for Service, Export

Data type: BAPISRV_ASMD
Optional: No
Call by Reference: No ( called with pass by value option)

EX_SERVICE_DATAX - Change Parameter for Service Data, Export

Data type: BAPISRV_ASMDX
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BAPI_SERVICE_CHANGE

RETURN - Return Parameter(s)

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

SERVICE_DESCRIPTION - Short Texts for Service

Data type: BAPISRV_ASMDT
Optional: No
Call by Reference: Yes

SERVICE_LONG_TEXTS - Long Texts for Service

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

EXTENSION_IN - Customer's Own Fields (Import Parameters)

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

EXTENSION_OUT - Customer's Own Fields (Export Parameters)

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

Copy and paste ABAP code example for BAPI_SERVICE_CHANGE 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 BAPI_SERVICE_CHANGE

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