# Network Activity Confirmation Upload from Weekly Timesheets Program

> 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.

- Type: Program, Custom development, Interface
- Module: PS
- Estimated effort: M (4–6 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/programs/network-activity-confirmation-upload-from-timesheets-program/


## 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.

### Closest standard alternatives

- CN25: Enters a single activity confirmation on screen; does not read a file.
- CAT2: Keeps time records in CATS; requires every employee to use CATS and a transfer/approval process.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| AFRU | Confirmation record: personnel, hours, date, final flag; also read for the duplicate check | Write | - | ECC + S/4 |
| AFVV | Activity actual work total (updated by the confirmation) | Write | - | ECC + S/4 |
| AFVC | Activity existence and work center check | Read | AFVC-AUFPL = AFRU-AUFPL AND AFVC-APLZL = AFRU-APLZL | ECC + S/4 |
| AUFK | Network existence and plant | Read | AUFK-AUFNR = AFRU-AUFNR | ECC + S/4 |
| JEST | Network status (released, not technically completed) | Read | JEST-OBJNR = AUFK-OBJNR | ECC + S/4 |

## BAPIs and functions used

- BAPI_NETWORK_CONF_ADD: Posts network activity confirmations in bulk
- BAPI_TRANSACTION_COMMIT: Saves successful confirmations permanently
- BAPI_TRANSACTION_ROLLBACK: Rolls back changes in test mode or on error

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| P_FILE | File or server folder | Single value | - | Yes |
| P_SERVER | Read from application server | Checkbox | - | No |
| P_TEST | Test mode (check without posting) | Checkbox | - | No |
| P_SKIPD | Skip rows already posted | Checkbox | - | No |

## Input file columns

| Column | Target field | Required |
|---|---|---|
| Personnel no | AFRU-PERNR | No |
| Network | AFRU-AUFNR | Yes |
| Activity | AFRU-VORNR | Yes |
| Posting date | AFRU-BUDAT | Yes |
| Actual work | AFRU-ISMNW | Yes |
| Unit | AFRU-ISMNE | No |
| Activity type | AFRU-LEARR | No |
| Final confirmation (X) | AFRU-AUERU | No |
| Confirmation text | AFRU-LTXA1 | No |

## Result list columns

| Column | Source |
|---|---|
| Row | Calculated: Row number in the file |
| Network | AFRU-AUFNR |
| Activity | AFRU-VORNR |
| Personnel no | AFRU-PERNR |
| Actual work | AFRU-ISMNW |
| Confirmation no | AFRU-RUECK |
| Confirmation counter | AFRU-RMZHL |
| Status | Calculated: Posted, skipped (duplicate) or error |
| Message | Calculated: First error or success message from the BAPI return table |

## How does the program work?

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.

## Authorization objects

- C_AFRU_AWK: Confirmation posting authorization by plant and order type
- C_AFKO_AWK: Network 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.

---
Let us build this program for your system: https://nekuhub.com/en/request-a-quote/?report=ps-network-confirmation-upload
