SAP UMB_DETAIL_SCORE_GET Function Module for









UMB_DETAIL_SCORE_GET is a standard umb detail score get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 umb detail score get FM, simply by entering the name UMB_DETAIL_SCORE_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function UMB_DETAIL_SCORE_GET 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 'UMB_DETAIL_SCORE_GET'"
  EXPORTING
*  I_UNAME =  "
*  I_PERNR =  "
   I_DATBEG =  "
   I_DATEND =  "

 IMPORTING
   E_SCORE =  "
   E_VALIDFR =  "
   E_VALIDTO =  "
   E_SCALE_MIN =  "
   E_SCALE_MAX =  "
   E_RETURN =  "

TABLES
*  ET_SCORE_MATRIX =  "
*  ET_SCORE_MATRIX1 =  "
.



IMPORTING Parameters details for UMB_DETAIL_SCORE_GET

I_UNAME -

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

I_PERNR -

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

I_DATBEG -

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

I_DATEND -

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

EXPORTING Parameters details for UMB_DETAIL_SCORE_GET

E_SCORE -

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

E_VALIDFR -

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

E_VALIDTO -

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

E_SCALE_MIN -

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

E_SCALE_MAX -

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

E_RETURN -

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

TABLES Parameters details for UMB_DETAIL_SCORE_GET

ET_SCORE_MATRIX -

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

ET_SCORE_MATRIX1 -

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

Copy and paste ABAP code example for UMB_DETAIL_SCORE_GET 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_e_score  TYPE UMB_Y_SCORE, "   
lv_i_uname  TYPE SYUNAME, "   
lt_et_score_matrix  TYPE STANDARD TABLE OF UMB_YT_SCORE_MATRIX, "   
lv_i_pernr  TYPE BAS_PERNR, "   
lv_e_validfr  TYPE SYDATUM, "   
lt_et_score_matrix1  TYPE STANDARD TABLE OF UMB_YT_SCORE_MATRIX1, "   
lv_i_datbeg  TYPE SYDATUM, "   
lv_e_validto  TYPE SYDATUM, "   
lv_i_datend  TYPE SYDATUM, "   
lv_e_scale_min  TYPE UMB_Y_SCRLO, "   
lv_e_scale_max  TYPE UMB_Y_SCRHI, "   
lv_e_return  TYPE BAPIRET2. "   

  CALL FUNCTION 'UMB_DETAIL_SCORE_GET'  "
    EXPORTING
         I_UNAME = lv_i_uname
         I_PERNR = lv_i_pernr
         I_DATBEG = lv_i_datbeg
         I_DATEND = lv_i_datend
    IMPORTING
         E_SCORE = lv_e_score
         E_VALIDFR = lv_e_validfr
         E_VALIDTO = lv_e_validto
         E_SCALE_MIN = lv_e_scale_min
         E_SCALE_MAX = lv_e_scale_max
         E_RETURN = lv_e_return
    TABLES
         ET_SCORE_MATRIX = lt_et_score_matrix
         ET_SCORE_MATRIX1 = lt_et_score_matrix1
. " UMB_DETAIL_SCORE_GET




ABAP code using 7.40 inline data declarations to call FM UMB_DETAIL_SCORE_GET

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!