Kontakt

Ansicht
Dokumentation

BAPI_WAGE_COMP_EXT_CHANGE - Obsolete: Use BAPI_WAGECOMPEXT_CHANGE

BAPI_WAGE_COMP_EXT_CHANGE - Obsolete: Use BAPI_WAGECOMPEXT_CHANGE

Vendor Master (General Section)   BAL Application Log Documentation  
This documentation is copyright by SAP AG.
SAP E-Book

Functionality

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

To determine the key of the record to be changed, use the EEWageComponentExt.GetList BAPI before you use this BAPI.

This is the only method you can use for changing records for the Salary Elements infotype (0579). It is not possible to change them directly in HR.

The function module runs the following data checks and if the check has a negative result, 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 date of the salary element. If the employee is not active, the run payroll until date is set in the Payroll Status infotype (0003). This means that a retroactive run is triggered in the next payroll run. No errors are returned.

Example

Travel Management (TM) triggers a retroactive run in the TM system. This creates a new result that should replace the old result in HR.

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 the BapiService.TransactionRollback

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 use 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, for example, if 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 is set in the Payroll Status infotype (0003) so that a retroactive run is triggered.

Further information





Parameters

COSTASSIGNMENT
EMPLOYEENUMBER
EXTENSIONIN
LOCKINDICATOR
OBJECTID
RECORDNUMBER
RETURN
SUBTYPE
TESTRUN
VALIDITYBEGIN
VALIDITYEND
WAGECOMPDATA

Exceptions

Function Group

PCIF_EXTSALARY

Addresses (Business Address Services)   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 4795 Date: 20240523 Time: 163254     sap01-206 ( 84 ms )