SAP MS_CHECK_SINGLE_SERVICE Function Module for NOTRANSL: Prüfung einer Einzelleistung bei der Erfassung
MS_CHECK_SINGLE_SERVICE is a standard ms check single service 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: Prüfung einer Einzelleistung bei der Erfassung 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 check single service FM, simply by entering the name MS_CHECK_SINGLE_SERVICE 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): Remote-Enabled
Update:

Function MS_CHECK_SINGLE_SERVICE 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_CHECK_SINGLE_SERVICE'"NOTRANSL: Prüfung einer Einzelleistung bei der Erfassung.
EXPORTING
I_EBELN = "Purchase Order Number
I_EBELP = "Purchase Order Item
IMP_ESLL = "Service Line
IMPORTING
E_PLAN_SERVICE = "Planned Service
E_CONTRACT_SERVICE = "
E_UNPLANED_SERVICE = "Unplanned Service
E_ESLL = "Service Line
EXCEPTIONS
SERVICE_NOT_EXIST = 1 SERVICE_NOT_ALLOW = 2 PO_NOT_EXIST = 3
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
IMPORTING Parameters details for MS_CHECK_SINGLE_SERVICE
I_EBELN - Purchase Order Number
Data type: EKKO-EBELNOptional: No
Call by Reference: No ( called with pass by value option)
I_EBELP - Purchase Order Item
Data type: EKPO-EBELPOptional: No
Call by Reference: No ( called with pass by value option)
IMP_ESLL - Service Line
Data type: ESLLOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for MS_CHECK_SINGLE_SERVICE
E_PLAN_SERVICE - Planned Service
Data type: XFELDOptional: No
Call by Reference: No ( called with pass by value option)
E_CONTRACT_SERVICE -
Data type: XFELDOptional: No
Call by Reference: No ( called with pass by value option)
E_UNPLANED_SERVICE - Unplanned Service
Data type: XFELDOptional: No
Call by Reference: No ( called with pass by value option)
E_ESLL - Service Line
Data type: ESLLOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
SERVICE_NOT_EXIST -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SERVICE_NOT_ALLOW -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PO_NOT_EXIST - Purchase order does not exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MS_CHECK_SINGLE_SERVICE 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: | ||||
| lv_i_ebeln | TYPE EKKO-EBELN, " | |||
| lv_e_plan_service | TYPE XFELD, " | |||
| lv_service_not_exist | TYPE XFELD, " | |||
| lv_i_ebelp | TYPE EKPO-EBELP, " | |||
| lv_service_not_allow | TYPE EKPO, " | |||
| lv_e_contract_service | TYPE XFELD, " | |||
| lv_imp_esll | TYPE ESLL, " | |||
| lv_po_not_exist | TYPE ESLL, " | |||
| lv_e_unplaned_service | TYPE XFELD, " | |||
| lv_e_esll | TYPE ESLL. " |
|   CALL FUNCTION 'MS_CHECK_SINGLE_SERVICE' "NOTRANSL: Prüfung einer Einzelleistung bei der Erfassung |
| EXPORTING | ||
| I_EBELN | = lv_i_ebeln | |
| I_EBELP | = lv_i_ebelp | |
| IMP_ESLL | = lv_imp_esll | |
| IMPORTING | ||
| E_PLAN_SERVICE | = lv_e_plan_service | |
| E_CONTRACT_SERVICE | = lv_e_contract_service | |
| E_UNPLANED_SERVICE | = lv_e_unplaned_service | |
| E_ESLL | = lv_e_esll | |
| EXCEPTIONS | ||
| SERVICE_NOT_EXIST = 1 | ||
| SERVICE_NOT_ALLOW = 2 | ||
| PO_NOT_EXIST = 3 | ||
| . " MS_CHECK_SINGLE_SERVICE | ||
ABAP code using 7.40 inline data declarations to call FM MS_CHECK_SINGLE_SERVICE
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 EBELN FROM EKKO INTO @DATA(ld_i_ebeln). | ||||
| "SELECT single EBELP FROM EKPO INTO @DATA(ld_i_ebelp). | ||||
Search for further information about these or an SAP related objects