Primavera / MS Project Schedule Import to Network Activities Interface
Short answer: A custom interface program that transfers activity duration, work and constraint dates updated in the scheduling tool (Primavera P6, MS Project or Excel) to SAP network activities via a file. Project planners keep the schedule in one place, and cost planning, capacity and material requirement dates in SAP stay current.
- Estimated effort
- M · 5–7 working days
- System
- ECC and S/4HANA
- Tables
- 4
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
Why is the standard not enough?
CN22 and CJ20N change network activities one by one; there is no standard transaction that takes updates from an external scheduling tool from a file in a scheduled and controlled way. As a result the dates in the two systems quickly drift apart. The custom interface matches the activities, writes only changed values and keeps a log of every transfer.
Who uses it? Project schedulers, project control (PMO) teams and project managers.
Closest standard alternatives
Tables used
The tables the program reads and updates. ECC and S/4HANA differences are marked separately.
| Table | Role | Access | System |
|---|---|---|---|
| AFVVQuantities, Dates and Values of Order Operations | Activity quantities and dates: duration, work, constraint types and constraint dates | Write | ECC + S/4 |
| AFVCOperation within an Order | Network activity: activity number, description, WBS assignment | Read | ECC + S/4 |
| AFKOOrder Header Data for PP Orders | Network header: routing number | Read | ECC + S/4 |
| PRPSWBS Element Master Data | WBS element shown in the log | Read | ECC + S/4 |
BAPIs and functions used
- BAPI_PS_INITIALIZATIONInitialize PS BAPI Processing. Initializes the PS BAPI buffer for each network
- BAPI_BUS2002_ACT_CHANGE_MULTIChange Network Activities. Updates duration, work and constraint dates of the changed activities
- BAPI_PS_PRECOMMITPrecommit for PS BAPIs. Runs the PS consistency checks before saving
- BAPI_TRANSACTION_COMMITCommit a BAPI transaction. Saves successful networks 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/schedule/ |
| P_SERVER | Read from application server | Checkbox | — | No | X |
| P_ONLYCH | Write changed values only | Checkbox | — | No | X |
| P_TEST | Test mode (check without saving) | 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 | Network | AFKO-AUFNR | Yes |
| 2 | Activity | AFVC-VORNR | Yes |
| 3 | Activity description (for checking) | AFVC-LTXA1 | No |
| 4 | Normal duration | AFVV-DAUNO | No |
| 5 | Duration unit | AFVV-DAUNE | No |
| 6 | Work | AFVV-ARBEI | No |
| 7 | Work unit | AFVV-ARBEH | No |
| 8 | Start constraint type | AFVV-EINSA | No |
| 9 | Constrained start date | AFVV-NTANF | No |
| 10 | Finish constraint type | AFVV-EINSE | No |
| 11 | Constrained finish date | AFVV-NTEND | No |
Sample upload file
| 1 | Network * | Activity * | Activity description (for checking) | Normal duration | Duration unit | Work | Work unit | Start constraint type | Constrained start date | Finish constraint type | Constrained finish date |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 2 | 4000215 | 0010 | Basic design | 15 | DAY | 240 | H | 1 | 12/01/2026 | ||
| 3 | 4000215 | 0020 | Detailed engineering | 25 | DAY | 600 | H | ||||
| 4 | 4000215 | 0050 | Site installation | 30 | DAY | 1,440 | H | 1 | 03/01/2027 | 2 | 04/15/2027 |
Result list columns
| # | Column | Source |
|---|---|---|
| 1 | Row | Calculated Row number in the file |
| 2 | Network | AFKO-AUFNR |
| 3 | Activity | AFVC-VORNR |
| 4 | Activity description | AFVC-LTXA1 |
| 5 | New duration | AFVV-DAUNO |
| 6 | Constrained start | AFVV-NTANF |
| 7 | Changed fields | Calculated List of the fields that differ between file and AFVV |
| 8 | Status | Calculated Updated, no change or error |
| 9 | Message | Calculated First error or success message from the BAPI return table |
Sample result list
| Row | Network | Activity | Activity description | New duration | Constrained start | Changed fields | Status | Message |
|---|---|---|---|---|---|---|---|---|
| 2 | 4000215 | 0010 | Basic design | 15 | 12/01/2026 | Duration, constrained start | Updated | Activity 0010 changed |
| 3 | 4000215 | 0020 | Detailed engineering | 25 | No change | Values equal to SAP | ||
| 4 | 4000215 | 0050 | Site installation | 30 | 03/01/2027 | Work, constraint dates | Error | Activity partly confirmed; work cannot be reduced below confirmed work |
How does the program work?
- The file is read from the local PC or a folder on the application server; network and activity number are the mandatory key fields.
- The routing number (AUFPL) of the network is found in AFKO; the activity (VORNR) is matched in AFVC. Rows without a match become errors.
- The current duration (DAUNO/DAUNE), work (ARBEI/ARBEH), constraint types (EINSA/EINSE) and constraint dates (NTANF/NTEND) in AFVV are compared with the file; with “changed only” selected, rows without differences are skipped.
- For each network BAPI_PS_INITIALIZATION is called, changed activities are updated with BAPI_BUS2002_ACT_CHANGE_MULTI and BAPI_PS_PRECOMMIT is run.
- Without errors the changes are saved with BAPI_TRANSACTION_COMMIT; in test mode or on error BAPI_TRANSACTION_ROLLBACK runs. Old and new values are written to the log; a server file is moved to an archive folder after processing.
Performance notes
Read AFKO, AFVC and AFVV in one pass with the network numbers from the file. Call the BAPI once per network with all changed activities, not once per activity. When scheduled as a nightly job, choose hours when users are not changing the same networks.
Features
- Test mode (check without posting)
- Line-by-line result and error log
- Download failed lines as a separate file Failed rows are returned to the scheduler as a file for correction.
- Runs as a background job
- Send the result by email A summary of each transfer can be sent to the project scheduler.
Authorization objects
- C_AFKO_AWKChange authorization by network type
- C_PROJ_KOKProject authorization by controlling area
Frequently asked questions
How are activity codes in the scheduling tool matched to SAP?
The simplest way is to use a code field in the scheduling tool that holds the SAP network and activity number. If that is not possible, a mapping table is kept and the program translates the code in the file through it.
Is the network rescheduled after the transfer?
If scheduling on save is set in the network profile, SAP recalculates the dates when saving. If not, a separate scheduling job can be planned after the transfer; this step is optional.
Does it work on S/4HANA?
Yes. BAPI_BUS2002_ACT_CHANGE_MULTI and the network tables are supported in S/4HANA. For the read side, the CDS view I_NetworkActivityByInternalKey can be used for a clean core approach.
Packages that include this solution
Project Planning and Earned Value Pack
A four-component pack that brings the project plan into SAP and measures performance with earned value: WBS cost plan upload from Excel, transfer of …
Related reports
Critical Path and Low Float Network Activities Report
A custom ALV report that filters network activities by the total float from the last scheduling run and lists critical (zero float), negative float …
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 …
Project WBS Schedule Slippage Report (Basic, Forecast and Actual Dates)
A custom ALV report that compares the basic start and finish dates of each WBS element with the forecast and actual dates, calculates the slip in days …
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.