SAP CABA_HR_CHECK Function Module for
CABA_HR_CHECK is a standard caba hr check 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 caba hr check FM, simply by entering the name CABA_HR_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: CABA_HR
Program Name: SAPLCABA_HR
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function CABA_HR_CHECK 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 'CABA_HR_CHECK'".
TABLES
IM_CABA_CHECK_TAB = "
EX_RETURN_TAB = "
EXCEPTIONS
COMMUNICATION_FAILURE = 1 SYSTEM_FAILURE = 2
TABLES Parameters details for CABA_HR_CHECK
IM_CABA_CHECK_TAB -
Data type: BAPI_TIMESHEET_HR_ATTRIBUTESOptional: No
Call by Reference: Yes
EX_RETURN_TAB -
Data type: BAPIRET2Optional: No
Call by Reference: Yes
EXCEPTIONS details
COMMUNICATION_FAILURE -
Data type:Optional: No
Call by Reference: Yes
SYSTEM_FAILURE -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CABA_HR_CHECK 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_im_caba_check_tab | TYPE STANDARD TABLE OF BAPI_TIMESHEET_HR_ATTRIBUTES, " | |||
| lv_communication_failure | TYPE BAPI_TIMESHEET_HR_ATTRIBUTES, " | |||
| lt_ex_return_tab | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_system_failure | TYPE BAPIRET2. " |
|   CALL FUNCTION 'CABA_HR_CHECK' " |
| TABLES | ||
| IM_CABA_CHECK_TAB | = lt_im_caba_check_tab | |
| EX_RETURN_TAB | = lt_ex_return_tab | |
| EXCEPTIONS | ||
| COMMUNICATION_FAILURE = 1 | ||
| SYSTEM_FAILURE = 2 | ||
| . " CABA_HR_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM CABA_HR_CHECK
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