SAP PS Network Activity

You are an SAP PS (Project Systems) expert. The user wants to create network activities with relationships and scheduling using the SAP PS module.

What to check first

• Verify the project exists in transaction code /n/SAPC/CNS100 (Create Network) or check via SE16N table PROJ
• Confirm you have authorization for PS Network creation (check role SAP_PS_PROJECT_ADMIN or equivalent)
• Retrieve the project definition ID (PSPID) you'll use — run transaction SE16N > Table PROJ > Filter by project status

Steps

1. Open transaction code /n/SAPC/CNS100 (Create Network) or legacy /nCN01 to initiate a new network within an existing project
2. Enter the project ID (PSPID) and network header description in the Network Header dialog
3. Create activity nodes by clicking "New Activity" and assigning activity numbers, descriptions, and work center assignments
4. Define activity relationships by right-clicking activities and selecting "Create Relationship" — specify predecessor/successor links with lag time (start-to-start, finish-to-finish, start-to-finish)
5. Set activity scheduling parameters: enter planned duration (DAUER in days), earliest start date (FRUE_AN), and latest finish date (SPAE_EN)
6. Assign resource allocations by selecting an activity and entering personnel/equipment in the "Assignments" tab with planned hours and cost center
7. Calculate and schedule the network using "Schedule Network" button or transaction CN02 to compute critical path and float calculations
8. Save the network structure using Ctrl+S or menu path "Network > Save" — system validates relationships and dates before committing

Code

* SAP PS Network Activity Creation via ABAP
REPORT ZNET_ACTIVITY_CREATE.

DATA: ls_network TYPE cnhdr,
      ls_activity TYPE cnaop,
      ls_relation TYPE cnrel,
      lv_network_id TYPE cnpnum,
      lv_project_id TYPE pspid,
      lv_activity_id TYPE kalnr,
      lt_activities TYPE TABLE OF cnaop.

PARAMETERS: p_pspid TYPE pspid,
            p_netnr TYPE cnpnum,
            p_act1 TYPE kalnr,
            p_act2 TYPE kalnr.

PERFORM validate_project USING p_pspid.

* Create network header
ls_network-pspid = p_pspid.
ls_network-cnpnum = p_netnr.
ls_network-ktxt = 'Sample PS Network'.
ls_network-start = sy-datum.

CALL FUNCTION 'CNET_CREATE_NETWORK'
  EXPORTING
    is_cnhdr = ls_network
  IMPORTING
    ev_cnpnum = lv_network_id
  EXCEPTIONS
    invalid_input = 1
    error_saving =

Note: this example was truncated in the source. See the GitHub repo for the latest full version.

Common Pitfalls

• Treating this skill as a one-shot solution — most workflows need iteration and verification
• Skipping the verification steps — you don't know it worked until you measure
• Applying this skill without understanding the underlying problem — read the related docs first

When NOT to Use This Skill

• When a simpler manual approach would take less than 10 minutes
• On critical production systems without testing in staging first
• When you don't have permission or authorization to make these changes

How to Verify It Worked

• Run the verification steps documented above
• Compare the output against your expected baseline
• Check logs for any warnings or errors — silent failures are the worst kind

Production Considerations

• Test in staging before deploying to production
• Have a rollback plan — every change should be reversible
• Monitor the affected systems for at least 24 hours after the change