SAP HRTMC_READ_POTENTIAL Function Module for

Search SAP Function Modules

HRTMC_READ_POTENTIAL is a standard hrtmc read potential 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 hrtmc read potential FM, simply by entering the name HRTMC_READ_POTENTIAL into the relevant SAP transaction such as SE37 or SE38.

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

Function HRTMC_READ_POTENTIAL 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 'HRTMC_READ_POTENTIAL'"
  EXPORTING
   IV_CENTRAL_PERSON =  "Object ID
   IV_BEGDA =  "Valid-From Date
   IV_ENDDA =  "Valid To Date

 IMPORTING
   EV_POTENTIAL =  "Potential Value
   EV_STATUS =  "Status of Performance or Potential Record
   EV_SCALE_ID =  "Scale ID
   EV_MAX_SCALE_VALUE =  "Potential Value

EXCEPTIONS
   NO_DATE = 1    INTERNAL_ERROR = 2 

.

IMPORTING Parameters details for HRTMC_READ_POTENTIAL

IV_CENTRAL_PERSON - Object ID

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

IV_BEGDA - Valid-From Date

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

IV_ENDDA - Valid To Date

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

EXPORTING Parameters details for HRTMC_READ_POTENTIAL

EV_POTENTIAL - Potential Value

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

EV_STATUS - Status of Performance or Potential Record

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

EV_SCALE_ID - Scale ID

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

EV_MAX_SCALE_VALUE - Potential Value

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

EXCEPTIONS details

NO_DATE -

Data type:
Optional: No
Call by Reference: Yes

INTERNAL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

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

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