SAP BAPI_ABSENCE_GETDETAIL Function Module for Read absence
BAPI_ABSENCE_GETDETAIL is a standard bapi absence getdetail 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 absence 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 bapi absence getdetail FM, simply by entering the name BAPI_ABSENCE_GETDETAIL into the relevant SAP transaction such as SE37 or SE38.
Function Group: ABSE
Program Name: SAPLABSE
Main Program:
Appliation area: H
Release date: 29-Aug-1997
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function BAPI_ABSENCE_GETDETAIL 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 'BAPI_ABSENCE_GETDETAIL'"Read absence.
EXPORTING
EMPLOYEENUMBER = "Personnel number
SUBTYPE = "Subtype
OBJECTID = "Object identification
LOCKINDICATOR = "Lock indicator for HR master record
VALIDITYBEGIN = "Valid from date
VALIDITYEND = "Valid to date
RECORDNUMBER = "Number of Infotype Record
IMPORTING
RETURN = "Structure for return code
START = "Start time
END = "End time
ABSENCETYPE = "Attendance or absence type
ABSENCEDAYS = "Absence or attendance days
ABSENCEHOURS = "Absence hours
NAMEOFABSENCETYPE = "
IMPORTING Parameters details for BAPI_ABSENCE_GETDETAIL
EMPLOYEENUMBER - Personnel number
Data type: BAPIP2001-PERNROptional: No
Call by Reference: No ( called with pass by value option)
SUBTYPE - Subtype
Data type: BAPIP2001-SUBTYOptional: No
Call by Reference: No ( called with pass by value option)
OBJECTID - Object identification
Data type: BAPIP2001-OBJPSOptional: No
Call by Reference: No ( called with pass by value option)
LOCKINDICATOR - Lock indicator for HR master record
Data type: BAPIP2001-SPRPSOptional: No
Call by Reference: No ( called with pass by value option)
VALIDITYBEGIN - Valid from date
Data type: BAPIP2001-BEGDAOptional: No
Call by Reference: No ( called with pass by value option)
VALIDITYEND - Valid to date
Data type: BAPIP2001-ENDDAOptional: No
Call by Reference: No ( called with pass by value option)
RECORDNUMBER - Number of Infotype Record
Data type: BAPIP2001-SEQNROptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_ABSENCE_GETDETAIL
RETURN - Structure for return code
Data type: BAPIRETURN1Optional: No
Call by Reference: No ( called with pass by value option)
START - Start time
Data type: BAPIP2001-BEGUZOptional: No
Call by Reference: No ( called with pass by value option)
END - End time
Data type: BAPIP2001-ENDUZOptional: No
Call by Reference: No ( called with pass by value option)
ABSENCETYPE - Attendance or absence type
Data type: BAPIP2001-AWARTOptional: No
Call by Reference: No ( called with pass by value option)
ABSENCEDAYS - Absence or attendance days
Data type: BAPIP2001-ABWTGOptional: No
Call by Reference: No ( called with pass by value option)
ABSENCEHOURS - Absence hours
Data type: BAPIP2001-STDAZOptional: No
Call by Reference: No ( called with pass by value option)
NAMEOFABSENCETYPE -
Data type: BAPIP2001-NAMEOFAWARTOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BAPI_ABSENCE_GETDETAIL 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_return | TYPE BAPIRETURN1, " | |||
lv_employeenumber | TYPE BAPIP2001-PERNR, " | |||
lv_start | TYPE BAPIP2001-BEGUZ, " | |||
lv_subtype | TYPE BAPIP2001-SUBTY, " | |||
lv_end | TYPE BAPIP2001-ENDUZ, " | |||
lv_objectid | TYPE BAPIP2001-OBJPS, " | |||
lv_absencetype | TYPE BAPIP2001-AWART, " | |||
lv_lockindicator | TYPE BAPIP2001-SPRPS, " | |||
lv_absencedays | TYPE BAPIP2001-ABWTG, " | |||
lv_validitybegin | TYPE BAPIP2001-BEGDA, " | |||
lv_validityend | TYPE BAPIP2001-ENDDA, " | |||
lv_absencehours | TYPE BAPIP2001-STDAZ, " | |||
lv_recordnumber | TYPE BAPIP2001-SEQNR, " | |||
lv_nameofabsencetype | TYPE BAPIP2001-NAMEOFAWART. " |
  CALL FUNCTION 'BAPI_ABSENCE_GETDETAIL' "Read absence |
EXPORTING | ||
EMPLOYEENUMBER | = lv_employeenumber | |
SUBTYPE | = lv_subtype | |
OBJECTID | = lv_objectid | |
LOCKINDICATOR | = lv_lockindicator | |
VALIDITYBEGIN | = lv_validitybegin | |
VALIDITYEND | = lv_validityend | |
RECORDNUMBER | = lv_recordnumber | |
IMPORTING | ||
RETURN | = lv_return | |
START | = lv_start | |
END | = lv_end | |
ABSENCETYPE | = lv_absencetype | |
ABSENCEDAYS | = lv_absencedays | |
ABSENCEHOURS | = lv_absencehours | |
NAMEOFABSENCETYPE | = lv_nameofabsencetype | |
. " BAPI_ABSENCE_GETDETAIL |
ABAP code using 7.40 inline data declarations to call FM BAPI_ABSENCE_GETDETAIL
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 PERNR FROM BAPIP2001 INTO @DATA(ld_employeenumber). | ||||
"SELECT single BEGUZ FROM BAPIP2001 INTO @DATA(ld_start). | ||||
"SELECT single SUBTY FROM BAPIP2001 INTO @DATA(ld_subtype). | ||||
"SELECT single ENDUZ FROM BAPIP2001 INTO @DATA(ld_end). | ||||
"SELECT single OBJPS FROM BAPIP2001 INTO @DATA(ld_objectid). | ||||
"SELECT single AWART FROM BAPIP2001 INTO @DATA(ld_absencetype). | ||||
"SELECT single SPRPS FROM BAPIP2001 INTO @DATA(ld_lockindicator). | ||||
"SELECT single ABWTG FROM BAPIP2001 INTO @DATA(ld_absencedays). | ||||
"SELECT single BEGDA FROM BAPIP2001 INTO @DATA(ld_validitybegin). | ||||
"SELECT single ENDDA FROM BAPIP2001 INTO @DATA(ld_validityend). | ||||
"SELECT single STDAZ FROM BAPIP2001 INTO @DATA(ld_absencehours). | ||||
"SELECT single SEQNR FROM BAPIP2001 INTO @DATA(ld_recordnumber). | ||||
"SELECT single NAMEOFAWART FROM BAPIP2001 INTO @DATA(ld_nameofabsencetype). | ||||
Search for further information about these or an SAP related objects