EmployeeAbsence

Warning! The API methods "Delete," "Approve," "Create," and "Request," and "Change," as well as their corresponding RFCs:

are no longer valid. Using these APIs can create inconsistencies in time data.

Instead, use the corresponding API Methods "ManageDelete," "ManageCreation," and "ManageChange" for the Business Object BUS7007,
as well as the following corresponding RFCs:

Available Methods

• Approve : Unlock absence [ BAPI_ABSENCE_APPROVE ] (Obsolete in 46A)
  
• Change : Change absence [ BAPI_ABSENCE_CHANGE ] (Obsolete in 46A)
  
• Create : Create absence [ BAPI_ABSENCE_CREATE ] (Obsolete in 46A)
  
• Delete : Delete absence [ BAPI_ABSENCE_DELETE ] (Obsolete in 46A)
  
• GetDetail : Read absence [ BAPI_ABSENCE_GETDETAIL ] (Obsolete in 46C)
  
• GetdetailedList : Read instances with data [ BAPI_ABSENCE_GETDETAILEDLIST ] (Obsolete in 46C)
  
• GetList : Read instances [ BAPI_ABSENCE_GETLIST ] (Obsolete in 46C)
  
• Request : Create locked absence [ BAPI_ABSENCE_REQUEST ] (Obsolete in 46A)
  
• SimulateCreation : Simulation: Create absence [ BAPI_ABSENCE_SIMULATECREATION ] (Obsolete in 46C)
  

Approve

Caution! This API method only writes the Absences infotype (2001). Itshould no longer be used as it can lead to inconsistent time data.

Instead, please use the corresponding API method for business object BUS7007.

This method can be used to unlock an Absences infotype record (2001).

Together with the REQUEST method, it allows you to implement the"double verification principle" whereby at least two users are involvedin writing an active data record to the database. One of the userscreates a locked infotype record using the REQUEST method. Another user
unlocks the record - that is, activates it using the APPROVE method.

Notes

Messages are returned in the RETURN parameter. The parameter documentation contains the return codes and their meanings.

The key fields used by the method are described under the parameters.

The method can only be used if the ENQUEUE method for the business object EMPLOYEE has already been called. For more information on the ENQUEUE method, please see the documentation on the function moduleBAPI_EMPLOYEE_ENQUEUE.

For more information on the REQUEST method, please see the documentation on function module BAPI_ABSENCE_REQUEST.

Change

Caution! This API method only changes the Absences infotype (2001). Itshould no longer be used as it can lead to inconsistent time data.

Instead, please use the corresponding 'ManageChange' API method for business object BUS7007.

Using this method, an Absences infotype record (2001) can be changed.

Notes

Messages are returned in the RETURN parameter. The parameter documentation contains the return codes and their meanings.

The key fields used by this method are described under the parameters.

This method can only be used if the ENQUEUE method has already been called up for the business object EMPLOYEE
. For more information on the ENQUEUE method, please see the documentation on the function module BAPI_EMPLOYEE_ENQUEUE.

Create

Caution! This API method only writes the Absences infotype (2001). Itshould no longer be used as it can lead to inconsistent time data.

Instead, please use the corresponding 'ManageCreation' API method for business object BUS7007.

Using this method, an Absences infotype record (2001) can be created.

Notes

Messages are returned in the RETURN parameter. The parameter documentation contains the return codes and their meanings.

The key fields used by this method are described under the parameters.

This method can only be used if the ENQUEUE method has already been called up for the business object EMPLOYEE
. For more information on the ENQUEUE method, please see the documentation on the function module BAPI_EMPLOYEE_ENQUEUE.

Delete

Caution! This API method only deletes the Absences infotype (2001). Itshould no longer be used as it can lead to inconsistent time data.

Instead, please use the corresponding 'ManageDelete' API method for business object BUS7007.

Using this method, an Absences infotype record (2001) can be deleted.

Notes

Messages are returned in the RETURN parameter. The parameter documentation contains the return codes and their meanings.

The key fields used by this method are described under the parameters.

This method can only be used if the ENQUEUE method has already been called up for the business object EMPLOYEE
. For more information on the ENQUEUE method, please see the documentation on the function module BAPI_EMPLOYEE_ENQUEUE.

GetDetail

This method can be used to read an Absences infotype record (2001).

Notes

Messages are returned in the RETURN parameter. The parameter documentation contains the return codes and their meanings.

The key fields used by the method are described under the parameters.

GetdetailedList

This method enables you to read the keys of the data records (instances) in the Absences infotype (2001) that are within the entered time period.

Notes

Messages are returned in the RETURN parameter. The parameter documentation contains information on confirmation values and their
meanings.

The key fields used in this method are described in section on parameters.

GetList

This method can be used to read the keys of data records (instances) for the Absences infotype (2001) that lie within the specified time interval.

Notes

Messages are returned in the RETURN parameter. The parameter documentation contains the return codes and their meanings.

The key fields used by the method are described under the parameters.

Request

Caution! This API method only writes the Absences infotype (2001). Itshould no longer be used as it can lead to inconsistent time data.

Instead, please use the corresponding API method for business object BUS7007.

This method can be used to create an Absences infotype record (2001).

Used together with the APPROVE method, it allows you to implement the"double verification principle" whereby at least two users are involvedin writing an active data record to the database. One of the userscreates a locked infotype record using the APPROVE method. Another
user unlocks the record, that is activates it using the APPROVE method.

Notes

Messages are returned in the RETURN parameter. The parameter documentation contains the return codes and their meanings.

The key fields used by the method are described under the parameters.

This method can only be used if the ENQUEUE method for the business object EMPLOYEE has already been called. For information on the ENQUEUE method, please see the documentation on the function moduleBAPI_EMPLOYEE_ENQUEUE.

For more information on the APPROVE method, please see the documentation on the function module BAPI_ABSENCE_APPROVE.

SimulateCreation

Using this method, the process of creating an Absences infotype record (2001) can be simulated.

All required consistency checks are carried out; the record is not written to the database, however.

Notes

Messages are returned in the RETURN parameter. The parameter documentation contains the return codes and their meanings.

The key fields used by this method are described under the parameters.