SAP HR_E_CONTRACT_CLASSIF Function Module for
HR_E_CONTRACT_CLASSIF is a standard hr e contract classif 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 hr e contract classif FM, simply by entering the name HR_E_CONTRACT_CLASSIF into the relevant SAP transaction such as SE37 or SE38.
Function Group: 34CS
Program Name: SAPL34CS
Main Program: SAPL34CS
Appliation area: P
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function HR_E_CONTRACT_CLASSIF 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_E_CONTRACT_CLASSIF'".
EXPORTING
P_DATE = "
* P_METO3 = "
* P_METO4 = "
P_IDSEG = "
* P_GRAMI = "
* P_FERED = "
* P_GBDAT = "
P_METOD = "
P_METO2 = "
* P_TPARC = "
* P_TPCCC = "
IMPORTING
P_CLASSIF = "
EXCEPTIONS
ERROR = 1
IMPORTING Parameters details for HR_E_CONTRACT_CLASSIF
P_DATE -
Data type: DOptional: No
Call by Reference: Yes
P_METO3 -
Data type: P0061-METO3Optional: Yes
Call by Reference: Yes
P_METO4 -
Data type: P0061-METO4Optional: Yes
Call by Reference: Yes
P_IDSEG -
Data type: Q0061-IDSEGOptional: No
Call by Reference: Yes
P_GRAMI -
Data type: PC226-FAMNUOptional: Yes
Call by Reference: Yes
P_FERED -
Data type: PC225-FEREDOptional: Yes
Call by Reference: Yes
P_GBDAT -
Data type: P0002-GBDATOptional: Yes
Call by Reference: Yes
P_METOD -
Data type: P0061-METODOptional: No
Call by Reference: Yes
P_METO2 -
Data type: P0061-METO2Optional: No
Call by Reference: Yes
P_TPARC -
Data type: COptional: Yes
Call by Reference: Yes
P_TPCCC -
Data type: PES_TPCCCOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for HR_E_CONTRACT_CLASSIF
P_CLASSIF -
Data type: PESS0_CONTRACT_CLASSIFOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for HR_E_CONTRACT_CLASSIF 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_error | TYPE STRING, " | |||
| lv_p_date | TYPE D, " | |||
| lv_p_classif | TYPE PESS0_CONTRACT_CLASSIF, " | |||
| lv_p_meto3 | TYPE P0061-METO3, " | |||
| lv_p_meto4 | TYPE P0061-METO4, " | |||
| lv_p_idseg | TYPE Q0061-IDSEG, " | |||
| lv_p_grami | TYPE PC226-FAMNU, " | |||
| lv_p_fered | TYPE PC225-FERED, " | |||
| lv_p_gbdat | TYPE P0002-GBDAT, " | |||
| lv_p_metod | TYPE P0061-METOD, " | |||
| lv_p_meto2 | TYPE P0061-METO2, " | |||
| lv_p_tparc | TYPE C, " | |||
| lv_p_tpccc | TYPE PES_TPCCC. " |
|   CALL FUNCTION 'HR_E_CONTRACT_CLASSIF' " |
| EXPORTING | ||
| P_DATE | = lv_p_date | |
| P_METO3 | = lv_p_meto3 | |
| P_METO4 | = lv_p_meto4 | |
| P_IDSEG | = lv_p_idseg | |
| P_GRAMI | = lv_p_grami | |
| P_FERED | = lv_p_fered | |
| P_GBDAT | = lv_p_gbdat | |
| P_METOD | = lv_p_metod | |
| P_METO2 | = lv_p_meto2 | |
| P_TPARC | = lv_p_tparc | |
| P_TPCCC | = lv_p_tpccc | |
| IMPORTING | ||
| P_CLASSIF | = lv_p_classif | |
| EXCEPTIONS | ||
| ERROR = 1 | ||
| . " HR_E_CONTRACT_CLASSIF | ||
ABAP code using 7.40 inline data declarations to call FM HR_E_CONTRACT_CLASSIF
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 METO3 FROM P0061 INTO @DATA(ld_p_meto3). | ||||
| "SELECT single METO4 FROM P0061 INTO @DATA(ld_p_meto4). | ||||
| "SELECT single IDSEG FROM Q0061 INTO @DATA(ld_p_idseg). | ||||
| "SELECT single FAMNU FROM PC226 INTO @DATA(ld_p_grami). | ||||
| "SELECT single FERED FROM PC225 INTO @DATA(ld_p_fered). | ||||
| "SELECT single GBDAT FROM P0002 INTO @DATA(ld_p_gbdat). | ||||
| "SELECT single METOD FROM P0061 INTO @DATA(ld_p_metod). | ||||
| "SELECT single METO2 FROM P0061 INTO @DATA(ld_p_meto2). | ||||
Search for further information about these or an SAP related objects