C_ACT sample questions & answers

Fjordmaelk, a Nordic dairy cooperative serving 4,000 member farms, runs a heavily modified SAP ECC system for milk procurement, batch traceability, and member settlement. The board has approved a move to SAP S/4HANA with three firm expectations: retire a large backlog of obsolete custom developments and adopt standard procurement processes wherever possible; preserve several years of batch-traceability history required by food-safety regulators; and complete the transition within a 14-month window tied to the cooperative's annual settlement cycle. A recent audit flagged that many existing customizations no longer reflect how the business actually operates. Finance has also signalled that the project budget cannot absorb a full ground-up reimplementation of processes that already work well, so any redesign must focus on the areas that genuinely need it. The CIO is attracted to the lowest-disruption route but is wary of carrying technical debt into the new platform. Two workstream leads disagree: one favours an in-place conversion to protect the schedule, while the other pushes a clean rebuild to escape the legacy clutter. As the project manager advising the steering committee, you must recommend the SAP Activate transition path that best satisfies all three expectations together.

Which transition path should you recommend so that the cooperative's combined goals are met?

AgroNexo, a Brazilian agritech logistics company, is launching an SAP S/4HANA programme with two distinct workstreams. The company is expanding rapidly across several Brazilian states and treats the programme as foundational to that growth. The first delivers standard finance and procurement on largely unchanged best-practice processes, governed by fixed statutory reporting deadlines that cannot move. The second builds a new grower-settlement capability whose requirements are still emerging; product owners expect to learn from grower feedback every few weeks and to reshape priorities frequently. Early discovery has already shown that grower payment rules vary by region and crop and will keep changing as new cooperatives are signed. The executive sponsor has read about agile transformation and wants "one agile method applied everywhere" so the programme presents a single modern delivery story to the board. The delivery leads are uneasy: the finance team values predictability and a clear milestone path, while the settlement team needs room to iterate. You are the project manager and must advise how to structure delivery within SAP Activate so each workstream is set up appropriately without fragmenting governance.

What delivery approach should you recommend across the two workstreams?

Rheinwerk Components, a German automotive supplier on SAP S/4HANA, faces a late request from one plant: a specialized surcharge must be applied to certain customer pricing conditions before a contractual go-live in three weeks. The surcharge reflects a genuine commercial agreement with a major customer, and missing it would breach a contract clause that carries financial penalties. A developer has proposed editing a standard pricing object directly because it is the fastest way to meet the date. The architecture lead objects, reminding the team that the programme committed to keeping the core clean so that future upgrades remain low-effort. The company upgrades on a regular cadence and has already felt the cost of legacy modifications carried over from its previous system. The plant controller counters that the business need is real and cannot simply be refused. Several other plants have similar pricing variations and are watching to see how this one is handled. The CIO has asked you, as project manager, to recommend an approach that delivers the surcharge while honouring the clean-core commitment the programme made at the outset.

Which approach should you recommend to deliver the surcharge requirement?

Northwater Energy, a Canadian utility, is early in an SAP S/4HANA implementation and the workstreams disagree on sequencing. The utility serves several regulated jurisdictions, so its billing and asset processes carry compliance requirements that make late rework especially costly. One stream lead wants to begin detailed configuration and build immediately to maximize throughput, arguing that requirements are "well enough understood." Another insists the team should first validate how standard processes meet the utility's needs before any build begins. That lead stresses that no one has yet confirmed how closely the utility's actual needs align with the standard processes. A third proposes freezing all requirements up front and locking scope before exploring what the standard solution offers. They argue this would give the plan certainty, even though it commits the team before the standard capabilities are understood. The programme has committed to minimizing rework and to adopting standard processes wherever possible. As project manager, you must decide which sequencing aligns with the SAP Activate methodology so that the team confirms standard-process fit at the right point and avoids building on unvalidated assumptions.

Which sequencing should you direct the team to follow?

Southern Cross Health, an Australian hospital network, is implementing SAP S/4HANA across finance and supply functions that touch patient-safety-critical workflows. The network spans several hospitals and thousands of shift-working staff, which makes coordinated communication and engagement genuinely difficult to do well. Clinical and ward staff have been openly resistant, citing earlier system rollouts that disrupted care. Union representatives have asked to be consulted, and several senior clinicians have real influence over whether their teams embrace or quietly bypass new processes. The executive sponsor's current plan is a single intensive week of training immediately before go-live, on the assumption that adoption is essentially a training event. Department heads warn that resistance is rooted in trust and workflow concerns, not lack of instruction. They note the changes will alter familiar ordering and approval steps that staff lean on under time pressure. The programme's success measures include safe, sustained adoption after go-live, not just system availability. As project manager, you must recommend how organizational change management should be approached so that adoption risk is genuinely reduced.

Which change-management approach should you recommend?

Tsukimi Instruments, a Japanese precision-measurement manufacturer, is building an SAP extension using agile delivery. The extension will feed calibration data into regulated quality records, so defects reaching production could undermine the very measurements customers depend on. To protect a high sprint velocity, the team has been pulling backlog items into sprints before acceptance criteria are agreed and marking items complete without verifying that agreed completion checks pass. The result is steadily climbing defect leakage into the downstream testing-and-deploy stage, where release readiness is now slipping. Two recent increments were reported as done but failed when assembled end to end, eroding the sponsor's confidence in the team's status reporting. The delivery lead's instinct is to add testers at the end to catch the defects, while another voice wants to lengthen sprints so more items "finish." The programme's objective is a predictable, quality-assured release rather than raw output. A third voice suggests simply accepting the current defect rate and fixing issues after release to protect the cadence. As project manager, you must recommend the corrective action that addresses the root cause.

Which corrective action should you recommend to restore release predictability and quality?