SAP HR_ECM_READ_OBJECT Function Module for Read compensation budgeting object









HR_ECM_READ_OBJECT is a standard hr ecm read 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 Read compensation budgeting object 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 hr ecm read object FM, simply by entering the name HR_ECM_READ_OBJECT into the relevant SAP transaction such as SE37 or SE38.

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



Function HR_ECM_READ_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 'HR_ECM_READ_OBJECT'"Read compensation budgeting object
  EXPORTING
   PLVAR =  "Plan Version
   OTYPE =  "Object Type
*  OBJID =  "Object ID
*  REALO = ' ' "Extended Object ID
*  BEGDA = SY-DATUM "Date
*  ENDDA = SY-DATUM "Date
*  READ_DB = 'X' "Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
   MESSAGE_HANDLER =  "HR Master Data: Messages

 IMPORTING
   OBEG =  "Date
   OEND =  "Date
   SHORT =  "Object Abbreviation
   STEXT =  "Object Name
   IS_OK =  "Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
.



IMPORTING Parameters details for HR_ECM_READ_OBJECT

PLVAR - Plan Version

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

OTYPE - Object Type

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

OBJID - Object ID

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

REALO - Extended Object ID

Data type: REALO
Default: SPACE
Optional: Yes
Call by Reference: Yes

BEGDA - Date

Data type: DATUM
Default: SY-DATUM
Optional: Yes
Call by Reference: Yes

ENDDA - Date

Data type: DATUM
Default: SY-DATUM
Optional: Yes
Call by Reference: Yes

READ_DB - Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')

Data type: BOOLE_D
Default: 'X'
Optional: Yes
Call by Reference: Yes

MESSAGE_HANDLER - HR Master Data: Messages

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

EXPORTING Parameters details for HR_ECM_READ_OBJECT

OBEG - Date

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

OEND - Date

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

SHORT - Object Abbreviation

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

STEXT - Object Name

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

IS_OK - Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')

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

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

DATA:
lv_obeg  TYPE DATUM, "   
lv_plvar  TYPE PLVAR, "   
lv_oend  TYPE DATUM, "   
lv_otype  TYPE OTYPE, "   
lv_objid  TYPE OBJEKTID, "   
lv_short  TYPE SHORT_D, "   
lv_realo  TYPE REALO, "   SPACE
lv_stext  TYPE STEXT, "   
lv_begda  TYPE DATUM, "   SY-DATUM
lv_is_ok  TYPE BOOLE_D, "   
lv_endda  TYPE DATUM, "   SY-DATUM
lv_read_db  TYPE BOOLE_D, "   'X'
lv_message_handler  TYPE IF_HRPA_MESSAGE_HANDLER. "   

  CALL FUNCTION 'HR_ECM_READ_OBJECT'  "Read compensation budgeting object
    EXPORTING
         PLVAR = lv_plvar
         OTYPE = lv_otype
         OBJID = lv_objid
         REALO = lv_realo
         BEGDA = lv_begda
         ENDDA = lv_endda
         READ_DB = lv_read_db
         MESSAGE_HANDLER = lv_message_handler
    IMPORTING
         OBEG = lv_obeg
         OEND = lv_oend
         SHORT = lv_short
         STEXT = lv_stext
         IS_OK = lv_is_ok
. " HR_ECM_READ_OBJECT




ABAP code using 7.40 inline data declarations to call FM HR_ECM_READ_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.

 
 
 
 
 
 
DATA(ld_realo) = ' '.
 
 
DATA(ld_begda) = SY-DATUM.
 
 
DATA(ld_endda) = SY-DATUM.
 
DATA(ld_read_db) = 'X'.
 
 


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!