Orchestrate

Last year's activity rate

Break-fix drill · Finance · about 5 minutes · starts after stage 11 of 11, "Pay and close the month", and the Who made the margin chapter through "Plan 2027" (the assembly hall, the test bench and plant administration planned for 2027, the rates not yet set), with the lab date moved to 2027-01-05, January open beside December for the year-end close, and a production order for four ES-200 released with its parts issued

What the user reports

First week of the year at Calder, 2027-01-05. In December the controller planned 2027 for the assembly hall, the test bench and plant administration and worked out the new activity rates on Activity rate planning. She emailed them to the plant manager, he said yes over the holidays, and she meant to set them when she was back. This morning the floor finished assembling and pressure testing January's first four ES-200, and the production supervisor confirms the order.

The error: The confirmation of January's order for four ES-200 is refused: CP11-410 is planned for 2027 (540 h) but has no activity rate for 2027, so its hours would be charged at last year's 140.00. Nothing posts; the order waits with its parts issued.

What you'll do

  1. See the problem as the production supervisor: On Production orders, find the order for 4 ES-200 starting 2027-01-05 and confirm its work as planned (8 h assembly, 4 h pressure test).
  2. Find the cause: The cost centers still have their activity rates (140.00 and 180.00), and the 2027 plans are in. Why is the confirmation refused, and what is the right repair?
  3. Fix it as the cost controller.
  4. Prove it: run the step that failed again.

Start the drill

The drill runs in the lab on its own prepared copy of the fictional Calder Pumpworks, saved in this browser apart from your company. All codes and values are fictional course labels.

Answer and explanation (open after the drill)

The fix: The plans for 2027 carry no rate: the calculation was done but never set. Set the rates from the plans on Activity rate planning, so January's hours charge 185.00 and 223.00.

The message names the cost center, the year and the missing rate. In the lab a cost center's own rate is the first year's (2026); a year that is planned charges the rate set on its plan, and a planned year without one is refused, so no order is quietly charged last year's rate. The rate comes from the plan with administration's share in it (185.00 and 223.00), which Set the rates writes. Changing the cost centers' own rates rewrites 2026's, which the year's plan still overrides; copying last year's rate onto the plan charges January the wrong amount on purpose. The period is open: the parts were received and issued today.

Why it broke

The year's rates were calculated and approved but never written onto the plans. In the lab a cost center planned for a year charges that year's rate; with none set, the hours would have gone out at last year's rate, so the confirmation stops instead.

How teams prevent it

Put Set the rates on the year-end checklist with an owner and a date before the first working day, and check Activity rate planning for the new year before the floor confirms anything: every planned cost center should show Set.

Across teams

The production supervisor couldn't confirm January's first order, the pumps waited for their goods receipt, and the planner's schedule slipped; had the hours gone through at last year's rate, every January order would have been undercosted by 45.00 an assembly hour and 43.00 a test hour, the cost centers would have looked under-absorbed by the same, and the variances and margins built on them would have been wrong until someone found it at month-end.

Where AI fits

Plain automation: a check on the year-end checklist that every cost center planned for the new year has its rate set finds this with no model. An assistant could draft the reminder to the controller in December; setting the rates stays the controller's decision, because they are the approved plan.

Learn more: Record to report, end to end

All drills · Back to the lab

Sign in to track your progress

We'll email you a one-time sign-in link. No password needed.

or

Tell us a little about you

Optional, every field. It helps us pitch answers to your questions at the right level and decide which topics to write next. It is never shown publicly, and you can change or clear it anytime from the account menu.

SAP areas you work in