SAP BAPI_ABSENCE_SIMULATECREATION Function Module for Simulation: Create absence









BAPI_ABSENCE_SIMULATECREATION is a standard bapi absence simulatecreation SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Simulation: Create 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 simulatecreation FM, simply by entering the name BAPI_ABSENCE_SIMULATECREATION into the relevant SAP transaction such as SE37 or SE38.

Function Group: ABSE
Program Name: SAPLABSE
Main Program:
Appliation area: H
Release date: 11-Sep-1997
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_ABSENCE_SIMULATECREATION 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_SIMULATECREATION'"Simulation: Create absence
EXPORTING
EMPLOYEENUMBER = "Personnel number
VALIDITYBEGIN = "Valid from date
VALIDITYEND = "Valid to date
* START = "Start time
* END = "End time
ABSENCETYPE = "Attendance or absence type
* ABSENCEHOURS = "Absence hours

IMPORTING
RETURN = "Structure for return code
EMPLOYEENUMBER = "Personnel number
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 Parameters details for BAPI_ABSENCE_SIMULATECREATION

EMPLOYEENUMBER - Personnel number

Data type: BAPIP2001-PERNR
Optional: No
Call by Reference: No ( called with pass by value option)

VALIDITYBEGIN - Valid from date

Data type: BAPIP2001-BEGDA
Optional: No
Call by Reference: No ( called with pass by value option)

VALIDITYEND - Valid to date

Data type: BAPIP2001-ENDDA
Optional: No
Call by Reference: No ( called with pass by value option)

START - Start time

Data type: BAPIP2001-BEGUZ
Optional: Yes
Call by Reference: No ( called with pass by value option)

END - End time

Data type: BAPIP2001-ENDUZ
Optional: Yes
Call by Reference: No ( called with pass by value option)

ABSENCETYPE - Attendance or absence type

Data type: BAPIP2001-AWART
Optional: No
Call by Reference: No ( called with pass by value option)

ABSENCEHOURS - Absence hours

Data type: BAPIP2001-STDAZ
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BAPI_ABSENCE_SIMULATECREATION

RETURN - Structure for return code

Data type: BAPIRETURN1
Optional: No
Call by Reference: No ( called with pass by value option)

EMPLOYEENUMBER - Personnel number

Data type: BAPIP2001-PERNR
Optional: No
Call by Reference: No ( called with pass by value option)

SUBTYPE -

Data type: BAPIP2001-SUBTY
Optional: No
Call by Reference: No ( called with pass by value option)

OBJECTID - Object identification

Data type: BAPIP2001-OBJPS
Optional: No
Call by Reference: No ( called with pass by value option)

LOCKINDICATOR - Lock indicator for HR master record

Data type: BAPIP2001-SPRPS
Optional: No
Call by Reference: No ( called with pass by value option)

VALIDITYBEGIN - Valid from date

Data type: BAPIP2001-BEGDA
Optional: No
Call by Reference: No ( called with pass by value option)

VALIDITYEND - Valid to date

Data type: BAPIP2001-ENDDA
Optional: No
Call by Reference: No ( called with pass by value option)

RECORDNUMBER - Number of Infotype Record

Data type: BAPIP2001-SEQNR
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for BAPI_ABSENCE_SIMULATECREATION 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_validitybegin  TYPE BAPIP2001-BEGDA, "   
lv_employeenumber  TYPE BAPIP2001-PERNR, "   
lv_subtype  TYPE BAPIP2001-SUBTY, "   
lv_validityend  TYPE BAPIP2001-ENDDA, "   
lv_start  TYPE BAPIP2001-BEGUZ, "   
lv_objectid  TYPE BAPIP2001-OBJPS, "   
lv_end  TYPE BAPIP2001-ENDUZ, "   
lv_lockindicator  TYPE BAPIP2001-SPRPS, "   
lv_absencetype  TYPE BAPIP2001-AWART, "   
lv_validitybegin  TYPE BAPIP2001-BEGDA, "   
lv_validityend  TYPE BAPIP2001-ENDDA, "   
lv_absencehours  TYPE BAPIP2001-STDAZ, "   
lv_recordnumber  TYPE BAPIP2001-SEQNR. "   

  CALL FUNCTION 'BAPI_ABSENCE_SIMULATECREATION'  "Simulation: Create absence
    EXPORTING
         EMPLOYEENUMBER = lv_employeenumber
         VALIDITYBEGIN = lv_validitybegin
         VALIDITYEND = lv_validityend
         START = lv_start
         END = lv_end
         ABSENCETYPE = lv_absencetype
         ABSENCEHOURS = lv_absencehours
    IMPORTING
         RETURN = lv_return
         EMPLOYEENUMBER = lv_employeenumber
         SUBTYPE = lv_subtype
         OBJECTID = lv_objectid
         LOCKINDICATOR = lv_lockindicator
         VALIDITYBEGIN = lv_validitybegin
         VALIDITYEND = lv_validityend
         RECORDNUMBER = lv_recordnumber
. " BAPI_ABSENCE_SIMULATECREATION




ABAP code using 7.40 inline data declarations to call FM BAPI_ABSENCE_SIMULATECREATION

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 BEGDA FROM BAPIP2001 INTO @DATA(ld_validitybegin).
 
"SELECT single PERNR FROM BAPIP2001 INTO @DATA(ld_employeenumber).
 
"SELECT single SUBTY FROM BAPIP2001 INTO @DATA(ld_subtype).
 
"SELECT single ENDDA FROM BAPIP2001 INTO @DATA(ld_validityend).
 
"SELECT single BEGUZ FROM BAPIP2001 INTO @DATA(ld_start).
 
"SELECT single OBJPS FROM BAPIP2001 INTO @DATA(ld_objectid).
 
"SELECT single ENDUZ FROM BAPIP2001 INTO @DATA(ld_end).
 
"SELECT single SPRPS FROM BAPIP2001 INTO @DATA(ld_lockindicator).
 
"SELECT single AWART FROM BAPIP2001 INTO @DATA(ld_absencetype).
 
"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).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!