Mass Additional Payment (Infotype 0015) Upload Program
Short answer: A custom program that posts bonuses, sales commissions, premiums and similar one-time payments from an Excel or CSV file to infotype 0015 in bulk. It checks that the wage type is permitted, the payroll period is open and the same payment has not been entered before; it runs in test mode first.
- Estimated effort
- M · 3–5 working days
- System
- ECC and S/4HANA
- Tables
- 4
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
Why is the standard not enough?
PA70 fast entry creates records for many employees on screen, but it does not read a file and its field layout is fixed. PA30 is for one employee. When payment lists with hundreds of rows from a sales or bonus system are keyed manually, there is a risk of wrong wage types, duplicate payments or postings into a closed period.
Who uses it? Payroll specialists and finance teams that calculate sales commissions and bonuses.
Closest standard alternatives
Tables used
The tables the program reads and updates. ECC and S/4HANA differences are marked separately.
| Table | Role | Access | System |
|---|---|---|---|
| PA0015HR Master Record: Infotype 0015 (Additional Payments) | Additional payments: wage type, amount, currency, payment date, assignment number | Write | ECC + S/4 |
| PA0001HR Master Record: Infotype 0001 (Organizational Assignment) | Check of the active assignment and payroll area on the payment date | Read | ECC + S/4 |
| PA0003HR Master Record: Infotype 0003 (Payroll Status) | Payroll accounted-to date; postings into closed periods are blocked | Read | ECC + S/4 |
| T512ZPermissibility of Wage Types per Infotype | Whether the wage type is permitted for infotype 0015 | Read | ECC + S/4 |
BAPIs and functions used
- BAPI_EMPLOYEE_ENQUEUELock Employee. Locks the employee before posting
- HR_INFOTYPE_OPERATIONMaintain HR Infotype Record. Creates the infotype 0015 record; called without commit in test mode
- BAPI_EMPLOYEE_DEQUEUEUnlock Employee. Releases the lock after posting
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| P_FILE | Upload file (XLSX or CSV) | Single value | — | Yes | C:\temp\kasim_primleri.xlsx |
| P_ABKRS | Payroll area | Single value | PA0001-ABKRS | Yes | TM |
| P_TEST | Test mode (check without posting) | Checkbox | — | No | X |
| P_DUPL | Reject duplicate records | Checkbox | — | No | X |
Input file columns
The columns of the upload template and the SAP fields they are written to. Columns with an asterisk are mandatory.
| # | Column | Target field | Required |
|---|---|---|---|
| 1 | Pers. no. | PA0015-PERNR | Yes |
| 2 | Wage type | PA0015-LGART | Yes |
| 3 | Amount | PA0015-BETRG | Yes |
| 4 | Currency | PA0015-WAERS | Yes |
| 5 | Payment date | PA0015-BEGDA | Yes |
| 6 | Number | PA0015-ANZHL | No |
| 7 | Unit | PA0015-ZEINH | No |
| 8 | Assignment no. | PA0015-ZUORD | No |
Sample upload file
| 1 | Pers. no. * | Wage type * | Amount * | Currency * | Payment date * | Number | Unit | Assignment no. |
|---|---|---|---|---|---|---|---|---|
| 2 | 00001024 | 3100 | 4,250 | TRY | 11/30/2026 | PRIM-2026-11 | ||
| 3 | 00001057 | 3100 | 3,800 | TRY | 11/30/2026 | PRIM-2026-11 | ||
| 4 | 00001092 | 3150 | 12,500 | TRY | 10/31/2026 | KOM-2026-Q3 |
Result list columns
| # | Column | Source |
|---|---|---|
| 1 | Row | Calculated Row number in the file |
| 2 | Pers. no. | PA0015-PERNR |
| 3 | Wage type | PA0015-LGART |
| 4 | Status | Calculated From the checks and posting: posted, test OK or error |
| 5 | Message | Calculated Check error or HR_INFOTYPE_OPERATION return message |
Sample result list
| Row | Pers. no. | Wage type | Status | Message |
|---|---|---|---|---|
| 2 | 00001024 | 3100 | Posted | Infotype 0015 record created |
| 3 | 00001057 | 3100 | Error | A record with the same wage type and assignment number already exists |
| 4 | 00001092 | 3150 | Error | Payment date is not after the payroll accounted-to date (31.10.2026) |
How does the program work?
- The file (XLSX or CSV) is read from the user’s PC or the application server; the first row is skipped as the header.
- Each row is checked: is the employee active on the payment date and in the selected payroll area (PA0001), is the wage type permitted for infotype 0015 (T512Z), are amount and currency filled, is the payment date after the payroll accounted-to date (PA0003-ABRDT).
- Duplicate check: if PA0015 already has a record with the same employee, wage type, date and assignment number, the row is rejected.
- The employee is locked with BAPI_EMPLOYEE_ENQUEUE; the record is created with HR_INFOTYPE_OPERATION (operation INS) and the lock is released with BAPI_EMPLOYEE_DEQUEUE. In test mode the function is called without commit (no-commit) and the change is rolled back.
- Result and message are listed per row; failed rows can be downloaded as a separate file. The program does not write file contents or amounts to a permanent log.
Performance notes
Locking and posting happen per employee; processing rows of the same employee consecutively reduces the number of locks. Run files above a few thousand rows as a background job and do not upload while payroll is running (while the payroll control record is released for payroll).
Features
- Test mode (check without posting)
- Line-by-line result and error log
- Download failed lines as a separate file Corrected rows can be uploaded again with the same template.
- Export to Excel An empty upload template can be downloaded as Excel.
- Runs as a background job
Authorization objects
- P_ORGINWrite authorization for personnel data, infotype 0015
- P_PERNRCheck that prevents users from posting to their own personnel number
Frequently asked questions
Does payroll recalculate retroactively after the upload?
As long as the payment date is after the payroll accounted-to date, the record is calculated normally in the next payroll period. Posting into a past period is blocked by default; a separate option can be enabled for deliberate retroactive payments.
Are amounts stored in the program log?
No. The result list contains only row number, personnel number, wage type and message; file contents and amounts are not stored permanently.
Can it also be used for infotype 0014 (recurring payments)?
Yes. The same structure can be adapted to recurring payments with start and end dates in infotype 0014; the template and checks are defined separately and increase the effort range slightly.
Packages that include this solution
Pre-Payroll Check and Upload Pack
A pack that brings together the work done before every payroll run: bulk upload of additional payments and absence and attendance records from Excel, …
Related reports
Mass Absence and Attendance Upload Program
A custom program that posts absence (infotype 2001) and attendance (infotype 2002) records coming from time clocks, shift planning tools or Excel into …
Employee Bank Details Changed Since Last Payroll Report
A custom ALV control report that lists employees whose bank details (infotype 0009) were created or changed after the last payroll run or within a …
Let us build this program for your system
Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.