Kontakt

Ansicht
Dokumentation

BAPI_WAGE_COMP_EXT_DELETE - Obsolete: Use BAPI_WAGECOMPEXT_DELETE

BAPI_WAGE_COMP_EXT_DELETE - Obsolete: Use BAPI_WAGECOMPEXT_DELETE

PERFORM Short Reference   PERFORM Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

Functionality

This function module deletes an existing record of the External Salary Elements infotype (0579) in HR.

Before you use this BAPI, use the EEWageComponentExt.GetList BAPI to determine the key of the record to be deleted.

This is the only method you can use for deleting transferred records. You cannot delete transferred records in HR.

The function module runs the following data checks. If the check is negative, it returns an error:

  • The personnel number exists in HR.
  • The date on which the salary elements are transferred to Payroll is later than the earliest personal retroactive accounting date in the Payroll Status infotype (0003) for the employee and is also later than the earliest retroactive accounting date in the control record for the employee's payroll area.
  • The account assignment object (account assignment block, posting information) is valid.
  • The HR wage type exists for the employee's country and is permitted for transfer from the application.
  • The employee is actively employed on the validity end date of the salary element. If the employee is not active, the run payroll to date in the Payroll Status infotype (0003) is set. No errors are returned.

Notes

Database update

The BAPI does not execute a Commit Work operation. This avoids database updates for each created record. You can control database updates using the BapiService.TransactionCommit or BapiService.TransactionRollback methods. We recommend several BAPI calls (20 to 100) before you set a Commit.

The personnel number is locked from the point when the BAPI is called to the point when infotypes 0579 and 0003 are updated. The number of personnel numbers processed between two Commits should be chosen accordingly:

  • If the personnel number lock is critical, you should set a Commit more frequently.
  • If the performance is critical, you should process as many personnel numbers as possible between two Commits.

Locked personnel numbers

  • Personnel numbers are rejected if they are locked at the time of the transfer. This is the case if, for example, master data is edited for a personnel number.

Payroll status

  • If the payroll area for a personnel number has the status Released for Payroll, you cannot make any changes to the infotype records for this personnel number for the current and past payroll periods. The personnel number is then not rejected but it is stored in matchcode W so that it can be processed in the correction run for Payroll.

Retroactive changes

If salary elements are transferred and they were due in a period for which payroll has already been run, the earliest master data change date is set in the Payroll Status infotype (0003) so that a retroactive run is triggered.

Further information





Parameters

EMPLOYEENUMBER
LOCKINDICATOR
OBJECTID
RECORDNUMBER
RETURN
SUBTYPE
TESTRUN
VALIDITYBEGIN
VALIDITYEND

Exceptions

Function Group

PCIF_EXTSALARY

CL_GUI_FRONTEND_SERVICES - Frontend Services   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 4079 Date: 20240523 Time: 152417     sap01-206 ( 72 ms )