SAP MS_READ_SERVICE_OBJECT Function Module for NOTRANSL: Lesen einer Service-Best. bzw. eines Kontrakts

Search SAP Function Modules

MS_READ_SERVICE_OBJECT is a standard ms read service object 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: Lesen einer Service-Best. bzw. eines Kontrakts 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 read service object FM, simply by entering the name MS_READ_SERVICE_OBJECT into the relevant SAP transaction such as SE37 or SE38.

Function Group: MLSH
Program Name: SAPLMLSH
Main Program: SAPLMLSH
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function MS_READ_SERVICE_OBJECT 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_READ_SERVICE_OBJECT'"NOTRANSL: Lesen einer Service-Best. bzw. eines Kontrakts
  EXPORTING
   I_EBELN =  "Purchasing Document Number
   I_EBELP =  "Item Number of Purchasing Document

 IMPORTING
   E_ESUH =  "Ext. Services Management: Unpl. Service Limits: Header Data
   E_SRV_MDRV =  "Generated Table for View

TABLES
   T_ML_ESLL =  "Generated Table for View
   T_ESUC =  "Ext. Services Management: Unplanned Limits on Contract Item

EXCEPTIONS
   FATAL_ERROR = 1    NOT_FOUND = 2    NO_SERVICES = 3 

.

IMPORTING Parameters details for MS_READ_SERVICE_OBJECT

I_EBELN - Purchasing Document Number

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

I_EBELP - Item Number of Purchasing Document

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

EXPORTING Parameters details for MS_READ_SERVICE_OBJECT

E_ESUH - Ext. Services Management: Unpl. Service Limits: Header Data

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

E_SRV_MDRV - Generated Table for View

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

TABLES Parameters details for MS_READ_SERVICE_OBJECT

T_ML_ESLL - Generated Table for View

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

T_ESUC - Ext. Services Management: Unplanned Limits on Contract Item

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

EXCEPTIONS details

FATAL_ERROR -

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

NOT_FOUND -

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

NO_SERVICES -

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

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

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