SAP HR_ECM_ADAPT_PROCDATA_FOR_UI Function Module for Adapt process preparation data into format for user interface
HR_ECM_ADAPT_PROCDATA_FOR_UI is a standard hr ecm adapt procdata for ui SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Adapt process preparation data into format for user interface 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 adapt procdata for ui FM, simply by entering the name HR_ECM_ADAPT_PROCDATA_FOR_UI into the relevant SAP transaction such as SE37 or SE38.
Function Group: HRECM00HANDLER
Program Name: SAPLHRECM00HANDLER
Main Program: SAPLHRECM00HANDLER
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function HR_ECM_ADAPT_PROCDATA_FOR_UI 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_ADAPT_PROCDATA_FOR_UI'"Adapt process preparation data into format for user interface.
EXPORTING
PROC_PLANNED_TAB = "Table of compensation processes planned in current review
PROC_ADMIN_TAB = "Table of administration data for compensation processes
BUDGET_DATA_TAB = "Table of budget data for Compensation Administration
BUDGET_LINK_TAB = "Table of links between employee and budget unit (sorted)
PLAN_TAB = "Table of compensation plan data
MESSAGE_HANDLER = "HR Master Data: Messages
IMPORTING
BUDGET_TAB = "Table of Budget Data Passed to User Interface
COMP_DATA_TAB = "Table of Compensation Data Passed to User Interface
IS_OK = "Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
IMPORTING Parameters details for HR_ECM_ADAPT_PROCDATA_FOR_UI
PROC_PLANNED_TAB - Table of compensation processes planned in current review
Data type: HRECM00PROC_INFO_TABOptional: No
Call by Reference: Yes
PROC_ADMIN_TAB - Table of administration data for compensation processes
Data type: HRECM00PROC_ADMIN_TABOptional: No
Call by Reference: Yes
BUDGET_DATA_TAB - Table of budget data for Compensation Administration
Data type: HRECM00BUDGET_ADMIN_TABOptional: No
Call by Reference: Yes
BUDGET_LINK_TAB - Table of links between employee and budget unit (sorted)
Data type: HRECM00BUDGET_LINK_TABOptional: No
Call by Reference: Yes
PLAN_TAB - Table of compensation plan data
Data type: HRECM00COMP_PLAN_TABOptional: 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_ADAPT_PROCDATA_FOR_UI
BUDGET_TAB - Table of Budget Data Passed to User Interface
Data type: HRECM00BUDGET_TABOptional: No
Call by Reference: Yes
COMP_DATA_TAB - Table of Compensation Data Passed to User Interface
Data type: HRECM00COMP_DATA_TABOptional: 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_ADAPT_PROCDATA_FOR_UI 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_budget_tab | TYPE HRECM00BUDGET_TAB, " | |||
| lv_proc_planned_tab | TYPE HRECM00PROC_INFO_TAB, " | |||
| lv_comp_data_tab | TYPE HRECM00COMP_DATA_TAB, " | |||
| lv_proc_admin_tab | TYPE HRECM00PROC_ADMIN_TAB, " | |||
| lv_is_ok | TYPE BOOLE_D, " | |||
| lv_budget_data_tab | TYPE HRECM00BUDGET_ADMIN_TAB, " | |||
| lv_budget_link_tab | TYPE HRECM00BUDGET_LINK_TAB, " | |||
| lv_plan_tab | TYPE HRECM00COMP_PLAN_TAB, " | |||
| lv_message_handler | TYPE IF_HRPA_MESSAGE_HANDLER. " |
|   CALL FUNCTION 'HR_ECM_ADAPT_PROCDATA_FOR_UI' "Adapt process preparation data into format for user interface |
| EXPORTING | ||
| PROC_PLANNED_TAB | = lv_proc_planned_tab | |
| PROC_ADMIN_TAB | = lv_proc_admin_tab | |
| BUDGET_DATA_TAB | = lv_budget_data_tab | |
| BUDGET_LINK_TAB | = lv_budget_link_tab | |
| PLAN_TAB | = lv_plan_tab | |
| MESSAGE_HANDLER | = lv_message_handler | |
| IMPORTING | ||
| BUDGET_TAB | = lv_budget_tab | |
| COMP_DATA_TAB | = lv_comp_data_tab | |
| IS_OK | = lv_is_ok | |
| . " HR_ECM_ADAPT_PROCDATA_FOR_UI | ||
ABAP code using 7.40 inline data declarations to call FM HR_ECM_ADAPT_PROCDATA_FOR_UI
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