Functionality
This function module changes an existing record for the ExternalSalary Elements infotype (0579) in HR.
To determine the key of the record to be changed, use theEEWageComponentExt.GetList BAPI before you use this BAPI.
This is the only method you can use for changing records for theSalary Elements infotype (0579). It is not possible to changethem directly in HR.
The function module runs the following data checks and if the check hasa 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 inthe Payroll Status infotype (0003) for the employee and is alsolater than the earliest retroactive accounting date in thecontrol 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 untildate is set in the Payroll Status infotype (0003). This meansthat a retroactive run is triggered in the next payroll run. No errorsare 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 avoidsdatabase updates for each created record. You can control databaseupdates using the BapiService.TransactionCommit or theBapiService.TransactionRollbackThe personnel number is locked from the point when the BAPI is calledto the point when infotypes 0579 and 0003 are updated. The number ofpersonnel numbers processed between two commits should be chosenaccordingly:


• 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 apersonnel 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 forthis personnel number for the current and past payroll periods. Thepersonnel number is then not rejected but it is stored in matchcode Wso 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 forwhich payroll has already been run, the earliest master data change
is set in the Payroll Status infotype (0003) so that aretroactive run is triggered.

Description
The cost assignment of the salary element is optional.

Default
If no cost assignment is specified, the payroll system gives the salaryelement the same cost assignment as the employee (from infotypes 0001and 0027 - Organizational Assignment and Cost Distribution).

Description
If you want to perform a test run, set TestRun to 'X'.

Value range
'X' - Test run
SPACE - Update (the module does not perform a Commit)

Default
SPACE
The function module generally performs a database update (defaultsettings). This can be triggered with the BapiService.TransactionCommitor reset with the BapiService.Transactionollback.

Description
General data for salary element (origin, reference number in originalapplication, logical system for original application, wage type, andamount).

Description
Structure for enhancements by customer or partner - the additionalinformation is entered here. To process the information, a BusinessAdd-In, which is contained in the implementation of this BAPI must beused.

Description
Structure in which all error and success messages are returned.