SAP HRHAP_C_CATEGORY_MODIFY Function Module for
HRHAP_C_CATEGORY_MODIFY is a standard hrhap c category modify 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 hrhap c category modify FM, simply by entering the name HRHAP_C_CATEGORY_MODIFY into the relevant SAP transaction such as SE37 or SE38.
Function Group: HRHAP_C_IF_CATEGORY
Program Name: SAPLHRHAP_C_IF_CATEGORY
Main Program: SAPLHRHAP_C_IF_CATEGORY
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function HRHAP_C_CATEGORY_MODIFY 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 'HRHAP_C_CATEGORY_MODIFY'".
EXPORTING
CATEGORY_ID = "Appraisal Category ID
T_T77HAP_ROLE = "Roles
T_T77HAP_VALTY = "Value Types
T_C_STATUS = "
T_C_RULES = "
T_C_EVENTS = "
S_CAT_TYPE_SELECT = "Selected Header Types
S_T77HAP_C_T = "Appraisal Category - Text Table
T_APPER = "Appraiser object types
T_APPEE = "Appraisee object types
T_P_APPER = "Part Appraiser Types
T_OTHER = "Other object types
T_T77HAP_COL = "Columns
T_T77HAP_EX = "Exits
IMPORTING
S_RETURN = "Application Log: Message Data
IMPORTING Parameters details for HRHAP_C_CATEGORY_MODIFY
CATEGORY_ID - Appraisal Category ID
Data type: HAP_CATEGORY_IDOptional: No
Call by Reference: Yes
T_T77HAP_ROLE - Roles
Data type: HAP_T_T77HAP_ROLEOptional: No
Call by Reference: Yes
T_T77HAP_VALTY - Value Types
Data type: HAP_T_T77HAP_VALTYOptional: No
Call by Reference: Yes
T_C_STATUS -
Data type: HAP_T_C_STATUSOptional: No
Call by Reference: Yes
T_C_RULES -
Data type: HAP_T_C_WFROptional: No
Call by Reference: Yes
T_C_EVENTS -
Data type: HAP_T_C_WFEOptional: No
Call by Reference: Yes
S_CAT_TYPE_SELECT - Selected Header Types
Data type: HAP_S_CAT_TYPE_SELECTOptional: No
Call by Reference: Yes
S_T77HAP_C_T - Appraisal Category - Text Table
Data type: T77HAP_C_TOptional: No
Call by Reference: Yes
T_APPER - Appraiser object types
Data type: HAP_T_APPEROptional: No
Call by Reference: Yes
T_APPEE - Appraisee object types
Data type: HAP_T_APPEEOptional: No
Call by Reference: Yes
T_P_APPER - Part Appraiser Types
Data type: HAP_T_P_APPEROptional: No
Call by Reference: Yes
T_OTHER - Other object types
Data type: HAP_T_OTHEROptional: No
Call by Reference: Yes
T_T77HAP_COL - Columns
Data type: HAP_T_T77HAP_COLOptional: No
Call by Reference: Yes
T_T77HAP_EX - Exits
Data type: HAP_T_T77HAP_EXOptional: No
Call by Reference: Yes
EXPORTING Parameters details for HRHAP_C_CATEGORY_MODIFY
S_RETURN - Application Log: Message Data
Data type: BAL_S_MSGOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for HRHAP_C_CATEGORY_MODIFY 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_s_return | TYPE BAL_S_MSG, " | |||
| lv_category_id | TYPE HAP_CATEGORY_ID, " | |||
| lv_t_t77hap_role | TYPE HAP_T_T77HAP_ROLE, " | |||
| lv_t_t77hap_valty | TYPE HAP_T_T77HAP_VALTY, " | |||
| lv_t_c_status | TYPE HAP_T_C_STATUS, " | |||
| lv_t_c_rules | TYPE HAP_T_C_WFR, " | |||
| lv_t_c_events | TYPE HAP_T_C_WFE, " | |||
| lv_s_cat_type_select | TYPE HAP_S_CAT_TYPE_SELECT, " | |||
| lv_s_t77hap_c_t | TYPE T77HAP_C_T, " | |||
| lv_t_apper | TYPE HAP_T_APPER, " | |||
| lv_t_appee | TYPE HAP_T_APPEE, " | |||
| lv_t_p_apper | TYPE HAP_T_P_APPER, " | |||
| lv_t_other | TYPE HAP_T_OTHER, " | |||
| lv_t_t77hap_col | TYPE HAP_T_T77HAP_COL, " | |||
| lv_t_t77hap_ex | TYPE HAP_T_T77HAP_EX. " |
|   CALL FUNCTION 'HRHAP_C_CATEGORY_MODIFY' " |
| EXPORTING | ||
| CATEGORY_ID | = lv_category_id | |
| T_T77HAP_ROLE | = lv_t_t77hap_role | |
| T_T77HAP_VALTY | = lv_t_t77hap_valty | |
| T_C_STATUS | = lv_t_c_status | |
| T_C_RULES | = lv_t_c_rules | |
| T_C_EVENTS | = lv_t_c_events | |
| S_CAT_TYPE_SELECT | = lv_s_cat_type_select | |
| S_T77HAP_C_T | = lv_s_t77hap_c_t | |
| T_APPER | = lv_t_apper | |
| T_APPEE | = lv_t_appee | |
| T_P_APPER | = lv_t_p_apper | |
| T_OTHER | = lv_t_other | |
| T_T77HAP_COL | = lv_t_t77hap_col | |
| T_T77HAP_EX | = lv_t_t77hap_ex | |
| IMPORTING | ||
| S_RETURN | = lv_s_return | |
| . " HRHAP_C_CATEGORY_MODIFY | ||
ABAP code using 7.40 inline data declarations to call FM HRHAP_C_CATEGORY_MODIFY
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