SAP HR_CA_GET_CLASSIFICATION_GROUP Function Module for Read the classification group for WCB
HR_CA_GET_CLASSIFICATION_GROUP is a standard hr ca get classification group SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read the classification group for WCB 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 ca get classification group FM, simply by entering the name HR_CA_GET_CLASSIFICATION_GROUP into the relevant SAP transaction such as SE37 or SE38.
Function Group: HRPAYCA01
Program Name: SAPLHRPAYCA01
Main Program: SAPLHRPAYCA01
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function HR_CA_GET_CLASSIFICATION_GROUP 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_CA_GET_CLASSIFICATION_GROUP'"Read the classification group for WCB.
EXPORTING
PLANS = "Position
STELL = "Job
ORGEH = "Organizational Unit
ENDDA = "End Date
IMPORTING
OTYPE = "Object Type
OBJID = "Object ID
TABLES
WCB1 = "Payroll results - Workers' compensation information
EXCEPTIONS
NO_ASSIGNMENT = 1 NO_DATE_PROVIDED = 2 NO_ACTIVE_PLVAR = 3 OBJ_NOT_MAINTAINED_IN_PD = 4 NO_PARENT_FOUND = 5 OBJ_NOT_FOUND = 6
IMPORTING Parameters details for HR_CA_GET_CLASSIFICATION_GROUP
PLANS - Position
Data type: T528B-PLANSOptional: No
Call by Reference: Yes
STELL - Job
Data type: T513-STELLOptional: No
Call by Reference: Yes
ORGEH - Organizational Unit
Data type: T527X-ORGEHOptional: No
Call by Reference: Yes
ENDDA - End Date
Data type: ENDDAOptional: No
Call by Reference: Yes
EXPORTING Parameters details for HR_CA_GET_CLASSIFICATION_GROUP
OTYPE - Object Type
Data type: HRP1000-OTYPEOptional: No
Call by Reference: Yes
OBJID - Object ID
Data type: HRP1000-OBJIDOptional: No
Call by Reference: Yes
TABLES Parameters details for HR_CA_GET_CLASSIFICATION_GROUP
WCB1 - Payroll results - Workers' compensation information
Data type: PC2WCB1Optional: No
Call by Reference: Yes
EXCEPTIONS details
NO_ASSIGNMENT - No assignment has been found
Data type:Optional: No
Call by Reference: Yes
NO_DATE_PROVIDED - No evaluation date has been provided
Data type:Optional: No
Call by Reference: Yes
NO_ACTIVE_PLVAR - No active plan variant has been found
Data type:Optional: No
Call by Reference: Yes
OBJ_NOT_MAINTAINED_IN_PD - Object was not created in PD
Data type:Optional: No
Call by Reference: Yes
NO_PARENT_FOUND - Object does not have a parent org unit
Data type:Optional: No
Call by Reference: Yes
OBJ_NOT_FOUND - Object does not exist in table T527X
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for HR_CA_GET_CLASSIFICATION_GROUP 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: | ||||
| lt_wcb1 | TYPE STANDARD TABLE OF PC2WCB1, " | |||
| lv_otype | TYPE HRP1000-OTYPE, " | |||
| lv_plans | TYPE T528B-PLANS, " | |||
| lv_no_assignment | TYPE T528B, " | |||
| lv_objid | TYPE HRP1000-OBJID, " | |||
| lv_stell | TYPE T513-STELL, " | |||
| lv_no_date_provided | TYPE T513, " | |||
| lv_orgeh | TYPE T527X-ORGEH, " | |||
| lv_no_active_plvar | TYPE T527X, " | |||
| lv_endda | TYPE ENDDA, " | |||
| lv_obj_not_maintained_in_pd | TYPE ENDDA, " | |||
| lv_no_parent_found | TYPE ENDDA, " | |||
| lv_obj_not_found | TYPE ENDDA. " |
|   CALL FUNCTION 'HR_CA_GET_CLASSIFICATION_GROUP' "Read the classification group for WCB |
| EXPORTING | ||
| PLANS | = lv_plans | |
| STELL | = lv_stell | |
| ORGEH | = lv_orgeh | |
| ENDDA | = lv_endda | |
| IMPORTING | ||
| OTYPE | = lv_otype | |
| OBJID | = lv_objid | |
| TABLES | ||
| WCB1 | = lt_wcb1 | |
| EXCEPTIONS | ||
| NO_ASSIGNMENT = 1 | ||
| NO_DATE_PROVIDED = 2 | ||
| NO_ACTIVE_PLVAR = 3 | ||
| OBJ_NOT_MAINTAINED_IN_PD = 4 | ||
| NO_PARENT_FOUND = 5 | ||
| OBJ_NOT_FOUND = 6 | ||
| . " HR_CA_GET_CLASSIFICATION_GROUP | ||
ABAP code using 7.40 inline data declarations to call FM HR_CA_GET_CLASSIFICATION_GROUP
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.| "SELECT single OTYPE FROM HRP1000 INTO @DATA(ld_otype). | ||||
| "SELECT single PLANS FROM T528B INTO @DATA(ld_plans). | ||||
| "SELECT single OBJID FROM HRP1000 INTO @DATA(ld_objid). | ||||
| "SELECT single STELL FROM T513 INTO @DATA(ld_stell). | ||||
| "SELECT single ORGEH FROM T527X INTO @DATA(ld_orgeh). | ||||
Search for further information about these or an SAP related objects