SAP PS Progress Tracking

You are an SAP Project Systems (PS) consultant. The user wants to track project progress using earned value analysis (EVA) and generate comprehensive status reports.

What to check first

• Run transaction CN40 to verify that project planning data exists and WBS elements have planned costs and dates
• Run transaction CJPA to confirm actual costs and commitments are being posted to the project
• Check that your user role includes authorization object C_PRPS_PRJ with relevant project codes

Steps

1. Open transaction CJ20N to access the project planning screen and review your WBS structure and scheduling baseline
2. Navigate to transaction CJI3 to view the current project status overview including actual vs. planned spend
3. Run transaction CJI4 to access Earned Value Analysis, which calculates planned value (PV), earned value (EV), and actual cost (AC)
4. In the EVA report, configure the analysis date and select the progress measurement method (e.g., percentage of completion, milestone-based) using the MESSPRINZIP field
5. Generate the variance report by selecting "Variances" in CJI4 to see schedule variance (SV = EV - PV) and cost variance (CV = EV - AC)
6. Use transaction CJI7 to create a formal project status report snapshot, specifying the reporting period and organizational level
7. Export the report data to Excel via the ALV grid toolbar for distribution and further analysis
8. Set up a recurring variant in CJI4 using menu path Tools > Batch variant to automate weekly or monthly EVA runs

Code

REPORT z_sap_ps_eva_tracking.

DATA: lt_projects TYPE TABLE OF proj,
      lt_wbs TYPE TABLE OF prps,
      lt_eva_data TYPE TABLE OF zeva_result,
      ls_eva TYPE zeva_result,
      lv_planned_value TYPE p DECIMALS 2,
      lv_earned_value TYPE p DECIMALS 2,
      lv_actual_cost TYPE p DECIMALS 2,
      lv_sched_var TYPE p DECIMALS 2,
      lv_cost_var TYPE p DECIMALS 2.

TYPES: BEGIN OF zeva_result,
         project_id TYPE projn,
         wbs_element TYPE prps,
         planned_value TYPE p DECIMALS 2,
         earned_value TYPE p DECIMALS 2,
         actual_cost TYPE p DECIMALS 2,
         schedule_variance TYPE p DECIMALS 2,
         cost_variance TYPE p DECIMALS 2,
         cpi TYPE p DECIMALS 2,
         spi TYPE p DECIMALS 2,
       END OF zeva_result.

SELECT * INTO TABLE lt_projects
  FROM proj
  WHERE pstat = 'A'.

LOOP AT lt_projects INTO DATA(ls_project).
  SELECT * INTO TABLE lt_wbs
    FROM pr

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