SAP HR_ECM_DEFAULT_PROCESS_FREQU Function Module for Evaluates the time unit for a compensation process
HR_ECM_DEFAULT_PROCESS_FREQU is a standard hr ecm default process frequ SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Evaluates the time unit for a compensation process 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 default process frequ FM, simply by entering the name HR_ECM_DEFAULT_PROCESS_FREQU into the relevant SAP transaction such as SE37 or SE38.
Function Group: HRECM00ADMFREQUENCY
Program Name: SAPLHRECM00ADMFREQUENCY
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function HR_ECM_DEFAULT_PROCESS_FREQU 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_DEFAULT_PROCESS_FREQU'"Evaluates the time unit for a compensation process.
EXPORTING
CITEM = "Compensation Review Item
CAREA = "Compensation Area
PERNR = "Personnel Number
EFFDT = "Default Effective Date
MESSAGE_HANDLER = "HR Master Data: Messages
IMPORTING
PROCESS_FREQU = "Unit of Time Including Hourly
IS_OK = "Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
IMPORTING Parameters details for HR_ECM_DEFAULT_PROCESS_FREQU
CITEM - Compensation Review Item
Data type: ECM_CITEMOptional: No
Call by Reference: Yes
CAREA - Compensation Area
Data type: ECM_CAREAOptional: No
Call by Reference: Yes
PERNR - Personnel Number
Data type: PERNR_DOptional: No
Call by Reference: Yes
EFFDT - Default Effective Date
Data type: ECM_EFFDTOptional: No
Call by Reference: Yes
MESSAGE_HANDLER - HR Master Data: Messages
Data type: IF_HRPA_MESSAGE_HANDLEROptional: No
Call by Reference: Yes
EXPORTING Parameters details for HR_ECM_DEFAULT_PROCESS_FREQU
PROCESS_FREQU - Unit of Time Including Hourly
Data type: ECM_FREQHOptional: No
Call by Reference: Yes
IS_OK - Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
Data type: BOOLE_DOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for HR_ECM_DEFAULT_PROCESS_FREQU 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_citem | TYPE ECM_CITEM, " | |||
| lv_process_frequ | TYPE ECM_FREQH, " | |||
| lv_carea | TYPE ECM_CAREA, " | |||
| lv_is_ok | TYPE BOOLE_D, " | |||
| lv_pernr | TYPE PERNR_D, " | |||
| lv_effdt | TYPE ECM_EFFDT, " | |||
| lv_message_handler | TYPE IF_HRPA_MESSAGE_HANDLER. " |
|   CALL FUNCTION 'HR_ECM_DEFAULT_PROCESS_FREQU' "Evaluates the time unit for a compensation process |
| EXPORTING | ||
| CITEM | = lv_citem | |
| CAREA | = lv_carea | |
| PERNR | = lv_pernr | |
| EFFDT | = lv_effdt | |
| MESSAGE_HANDLER | = lv_message_handler | |
| IMPORTING | ||
| PROCESS_FREQU | = lv_process_frequ | |
| IS_OK | = lv_is_ok | |
| . " HR_ECM_DEFAULT_PROCESS_FREQU | ||
ABAP code using 7.40 inline data declarations to call FM HR_ECM_DEFAULT_PROCESS_FREQU
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