SAP HRTMC_WRITE_POTENTIAL Function Module for









HRTMC_WRITE_POTENTIAL is a standard hrtmc write 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 write potential FM, simply by entering the name HRTMC_WRITE_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_WRITE_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_WRITE_POTENTIAL'"
  EXPORTING
   IV_CENTRAL_PERSON =  "Object ID
*  IV_TESTRUN =  "
*  IV_NO_LOCK =  "
*  IV_NO_FLUSH =  "
   IV_POTENTIAL =  "Potential Value
   IV_STATUS =  "Status of Performance or Potential Record
   IV_SCALE_ID =  "Scale ID
*  IV_MAX_SCALE_VALUE =  "Potential Value
   IV_BEGDA =  "Valid-From Date
   IV_ENDDA =  "Valid To Date
*  IV_NO_COMMIT =  "Data Element for Domain BOOLE: TRUE (='X') and FALSE (=' ')
*  IV_APPRAISAL_ID =  "

EXCEPTIONS
   NO_DATE = 1    INTERNAL_ERROR = 2    INCOMPATIBLE_SCALES = 3
.



IMPORTING Parameters details for HRTMC_WRITE_POTENTIAL

IV_CENTRAL_PERSON - Object ID

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

IV_TESTRUN -

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

IV_NO_LOCK -

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

IV_NO_FLUSH -

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

IV_POTENTIAL - Potential Value

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

IV_STATUS - Status of Performance or Potential Record

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

IV_SCALE_ID - Scale ID

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

IV_MAX_SCALE_VALUE - Potential Value

Data type: HRTMC_POTENTIAL
Optional: Yes
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)

IV_NO_COMMIT - Data Element for Domain BOOLE: TRUE (='X') and FALSE (=' ')

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

IV_APPRAISAL_ID -

Data type: HAP_APPRAISAL_ID
Optional: Yes
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

INCOMPATIBLE_SCALES -

Data type:
Optional: No
Call by Reference: Yes

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

DATA:
lv_no_date  TYPE STRING, "   
lv_iv_central_person  TYPE HROBJID, "   
lv_iv_testrun  TYPE BOOLE_D, "   
lv_iv_no_lock  TYPE BOOLE_D, "   
lv_iv_no_flush  TYPE BOOLE_D, "   
lv_iv_potential  TYPE HRTMC_POTENTIAL, "   
lv_internal_error  TYPE HRTMC_POTENTIAL, "   
lv_iv_status  TYPE HRTMC_P_STATUS, "   
lv_incompatible_scales  TYPE HRTMC_P_STATUS, "   
lv_iv_scale_id  TYPE SCALE_ID, "   
lv_iv_max_scale_value  TYPE HRTMC_POTENTIAL, "   
lv_iv_begda  TYPE BEGDA, "   
lv_iv_endda  TYPE ENDDA, "   
lv_iv_no_commit  TYPE BOOLE_D, "   
lv_iv_appraisal_id  TYPE HAP_APPRAISAL_ID. "   

  CALL FUNCTION 'HRTMC_WRITE_POTENTIAL'  "
    EXPORTING
         IV_CENTRAL_PERSON = lv_iv_central_person
         IV_TESTRUN = lv_iv_testrun
         IV_NO_LOCK = lv_iv_no_lock
         IV_NO_FLUSH = lv_iv_no_flush
         IV_POTENTIAL = lv_iv_potential
         IV_STATUS = lv_iv_status
         IV_SCALE_ID = lv_iv_scale_id
         IV_MAX_SCALE_VALUE = lv_iv_max_scale_value
         IV_BEGDA = lv_iv_begda
         IV_ENDDA = lv_iv_endda
         IV_NO_COMMIT = lv_iv_no_commit
         IV_APPRAISAL_ID = lv_iv_appraisal_id
    EXCEPTIONS
        NO_DATE = 1
        INTERNAL_ERROR = 2
        INCOMPATIBLE_SCALES = 3
. " HRTMC_WRITE_POTENTIAL




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



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!