Network Activity Confirmation Upload from Weekly Timesheets Program
Short answer: A custom interface program that posts personnel, network, activity, date and hours rows from an external time tracking tool or an Excel timesheet as network activity confirmations in bulk. It skips rows already posted, checks in test mode and lists the confirmation number of every row.
- Estimated effort
- M · 4–6 working days
- System
- ECC and S/4HANA
- Tables
- 5
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
Why is the standard not enough?
CN25 enters each confirmation on screen one at a time; the CN27 collective confirmation screen also needs the rows typed in. CATS requires every employee to record in CATS and an approval process. Companies that keep time records in an external tool or Excel need an upload that reads a file and prevents duplicate postings to transfer the weekly hours to the network.
Who uses it? Project controllers, engineering team leads and project offices that keep time records outside SAP.
Closest standard alternatives
Tables used
The tables the program reads and updates. ECC and S/4HANA differences are marked separately.
| Table | Role | Access | System |
|---|---|---|---|
| AFRUOrder Confirmations | Confirmation record: personnel, hours, date, final flag; also read for the duplicate check | Write | ECC + S/4 |
| AFVVQuantities, Dates and Values of Order Operations | Activity actual work total (updated by the confirmation) | Write | ECC + S/4 |
| AFVCOperation within an Order | Activity existence and work center check | Read | ECC + S/4 |
| AUFKOrder Master Data | Network existence and plant | Read | ECC + S/4 |
| JESTIndividual Object Status | Network status (released, not technically completed) | Read | ECC + S/4 |
BAPIs and functions used
- BAPI_NETWORK_CONF_ADDAdd Network Confirmations. Posts network activity confirmations in bulk
- BAPI_TRANSACTION_COMMITCommit a BAPI transaction. Saves successful confirmations permanently
- BAPI_TRANSACTION_ROLLBACKRoll Back BAPI Transaction. Rolls back changes in test mode or on error
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| P_FILE | File or server folder | Single value | — | Yes | /interface/ps/timesheet/ |
| P_SERVER | Read from application server | Checkbox | — | No | X |
| P_TEST | Test mode (check without posting) | Checkbox | — | No | X |
| P_SKIPD | Skip rows already posted | 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 | Personnel no | AFRU-PERNR | No |
| 2 | Network | AFRU-AUFNR | Yes |
| 3 | Activity | AFRU-VORNR | Yes |
| 4 | Posting date | AFRU-BUDAT | Yes |
| 5 | Actual work | AFRU-ISMNW | Yes |
| 6 | Unit | AFRU-ISMNE | No |
| 7 | Activity type | AFRU-LEARR | No |
| 8 | Final confirmation (X) | AFRU-AUERU | No |
| 9 | Confirmation text | AFRU-LTXA1 | No |
Sample upload file
| 1 | Personnel no | Network * | Activity * | Posting date * | Actual work * | Unit | Activity type | Final confirmation (X) | Confirmation text |
|---|---|---|---|---|---|---|---|---|---|
| 2 | 10045 | 4000123 | 0020 | 11/13/2026 | 8 | H | MUH01 | Mechanical drawing revision | |
| 3 | 10052 | 4000131 | 0010 | 11/13/2026 | 10 | H | SAHA1 | Site setup | |
| 4 | 10045 | 4000123 | 0020 | 11/13/2026 | 8 | H | MUH01 | Mechanical drawing revision |
Result list columns
| # | Column | Source |
|---|---|---|
| 1 | Row | Calculated Row number in the file |
| 2 | Network | AFRU-AUFNR |
| 3 | Activity | AFRU-VORNR |
| 4 | Personnel no | AFRU-PERNR |
| 5 | Actual work | AFRU-ISMNW |
| 6 | Confirmation no | AFRU-RUECK |
| 7 | Confirmation counter | AFRU-RMZHL |
| 8 | Status | Calculated Posted, skipped (duplicate) or error |
| 9 | Message | Calculated First error or success message from the BAPI return table |
Sample result list
| Row | Network | Activity | Personnel no | Actual work | Confirmation no | Confirmation counter | Status | Message |
|---|---|---|---|---|---|---|---|---|
| 2 | 4000123 | 0020 | 10045 | 8 | 0000071842 | 00000014 | Posted | Confirmation saved |
| 3 | 4000131 | 0010 | 10052 | 10 | 0000071907 | 00000006 | Posted | Confirmation saved |
| 4 | 4000123 | 0020 | 10045 | 8 | Skipped | A confirmation already exists for the same person, activity and date |
How does the program work?
- The file is read from the user’s PC or, in a background job, from a folder on the application server; each row carries personnel number, network, activity, posting date, hours, unit, activity type, final confirmation flag and text.
- Checks: the network and activity must exist and be released and must not be technically completed; hours must be above zero; the activity type must fit the activity.
- Duplicate check: if a non-cancelled (STOKZ blank) AFRU confirmation already exists for the same personnel number, network, activity and date, the row is skipped.
- Rows are grouped by network and posted with BAPI_NETWORK_CONF_ADD; in test mode the BAPI is called with its test flag and BAPI_TRANSACTION_ROLLBACK follows.
- In a real run BAPI_TRANSACTION_COMMIT is done per network; the confirmation number and counter (RUECK, RMZHL) are written to the result list. The processed file is moved to an archive folder and failed rows are written to a separate file.
Performance notes
Weekly files are usually a few thousand rows and are processed in minutes as a nightly job. Committing per network is enough for locking and error isolation. Rows that fail because the same network is locked in CN25 at the same time can be retried.
Features
- Test mode (check without posting)
- Line-by-line result and error log
- Download failed lines as a separate file Failed rows can be corrected and uploaded again with the same template.
- Runs as a background job Files in the server folder are processed automatically by a nightly job.
Authorization objects
- C_AFRU_AWKConfirmation posting authorization by plant and order type
- C_AFKO_AWKNetwork authorization by plant and order type
Frequently asked questions
Is the personnel number mandatory?
No. If cost and capacity are not tracked per person, the confirmation can be posted with only network, activity, date and hours. If a personnel number is given, it is checked against the HR master data.
How are wrongly uploaded confirmations reversed?
They are cancelled with CN29 or BAPI_NETWORK_CONF_CANCEL using the confirmation number and counter in the result list. A mass cancel option can be added to the program if needed.
Can this program be used on S/4HANA?
Yes. BAPI_NETWORK_CONF_ADD is supported for classic networks on S/4HANA.
Related reports
Network Activity Planned vs Actual Work Hours Report
A custom ALV report that compares planned work with confirmed actual work on network activities and lists the remaining hours, completion percentage, …
Project Definition and WBS Structure Upload from Excel Program
A custom program that creates the project definition and a multi-level WBS structure in bulk from Excel rows, including descriptions, dates, …
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.