Orchestrate

The new part nobody declared

Break-fix drill · Sales · about 5 minutes · starts after stage 11 of 11, "Pay and close the month", and the Product compliance chapter up to "Date the impellers on ES-200's bill" in *The redesign meets the rule* (Germany's lead rules, the sales check refusing unknown, Auental with a credit profile, and the redesign EC-1001 with the lead-free impeller CP-IMP210)

What the user reports

Monday 21 December at Rockford. Auental heard that Calder's redesigned ES-200 impeller is lead-free and wants one pump for a booster station, delivered in the middle of February (its purchase order AWV-PO-3120). Customer service enters the order for 2027-02-15 and it is refused, although the redesign was made for exactly this market.

The error: Sales order for Auental (10000044) refused on Sales orders: ES-200's compliance in DE on 2027-02-15, the requested delivery date, is unknown: no declaration for CP-IMP210.

What you'll do

  1. See the problem as the customer service representative: On Sales orders, create the order for 10000044 in CPUS / 10 / PU, customer reference AWV-PO-3120, requested delivery 2027-02-15: 1 ES-200.
  2. Find the cause: The redesign took the lead out of the impeller, so why is ES-200's status unknown in Germany for February?
  3. Fix it as the product compliance specialist.
  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: From the change date the bill uses CP-IMP210, and nobody recorded Tamsfield's declaration for it: a part without a declaration makes the pump unknown.

The status reads the bill valid on the requested delivery date, and from 1 February that bill has CP-IMP210 instead of CP-IMP200. A part's contents are only known from its supplier's declaration, and nobody has asked Tamsfield for one, so ES-200 is unknown from that date and the settings refuse unknown. The old impeller would make it not compliant, not unknown; the March rule applies only from its date; credit blocks look different.

Why it broke

Engineering's change was right and dated; the hand-off was missing. A new part entered a product sold into a regulated market, and the change record went to purchasing and production but not to compliance, so nobody asked Tamsfield what the new impeller contains. The sales check did its job: it wouldn't promise a pump nobody could vouch for.

How teams prevent it

Make compliance a step of every change record that adds a bought part to a product sold where rules apply: the change raises a request for the supplier's declaration, with the change date as the deadline, and the change isn't released until the declaration is in or the date moves. A weekly list of parts on dated bill lines without a declaration catches the rest.

Across teams

Engineering changed the bill, purchasing set up the source, compliance owns the declaration, customer service holds Auental's order, and Tamsfield has the answer. The gap sat between engineering and compliance; customer service found it.

Where AI fits

Plain automation is enough to find the gap: a rule lists every part a change record starts on a bill without a declaration for the markets the product is sold into. A model can help read the declaration Tamsfield sends and draft the record with the passage it read, which the specialist confirms.

Learn more: Master data that every module depends on

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