SAP MS_SERVICE_PACKAGE_PAI Function Module for NOTRANSL: Rückgabe vom Service-Paket mit Subscreen

Search SAP Function Modules

MS_SERVICE_PACKAGE_PAI is a standard ms service package pai SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Rückgabe vom Service-Paket mit Subscreen 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 ms service package pai FM, simply by entering the name MS_SERVICE_PACKAGE_PAI into the relevant SAP transaction such as SE37 or SE38.

Function Group: MLSP
Program Name: SAPLMLSP
Main Program: SAPLMLSP
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MS_SERVICE_PACKAGE_PAI 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 'MS_SERVICE_PACKAGE_PAI'"NOTRANSL: Rückgabe vom Service-Paket mit Subscreen
 IMPORTING
   COMSRV =  "
   E_DIRTY_PACKAGE =  "
   E_EMPTY_PACKAGE =  "
   E_FUNCTION =  "
   E_CURSOR =  "Internal Tables, Current Row Index
   E_CURSOR_FIELD =  "Name of a Screen Element

TABLES
*  E_ACC_TAB =  "

.

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_SAPLMLSP_001 *** As of 4.0 in Standard SAP System *** Formula Calculation
EXIT_SAPLMLSP_002 ** As of 4.0 in Std. SAP System ** User Exit: Query Whether Formula Exists
EXIT_SAPLMLSP_010 Query Whether Selection of Services from Other Systems is Allowed
EXIT_SAPLMLSP_011 Call Foreign Selection for Services
EXIT_SAPLMLSP_020 *** As of 3.1G in Standard SAP System *** Unplanned Portion/Entry Sheet
EXIT_SAPLMLSP_030 User Exit: Fill ESLL Structure Before Checks (After Entry)
EXIT_SAPLMLSP_031 Check ESLL Datat After Checking
EXIT_SAPLMLSP_040 Transfer of Data to Detail User Screen
EXIT_SAPLMLSP_041 Adoption of Data from User Screen
EXIT_SAPLMLSP_043

EXPORTING Parameters details for MS_SERVICE_PACKAGE_PAI

COMSRV -

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

E_DIRTY_PACKAGE -

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

E_EMPTY_PACKAGE -

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

E_FUNCTION -

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

E_CURSOR - Internal Tables, Current Row Index

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

E_CURSOR_FIELD - Name of a Screen Element

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

TABLES Parameters details for MS_SERVICE_PACKAGE_PAI

E_ACC_TAB -

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

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

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