Helios One · buyer workflow
Epicor Prophet 21 contract manufacturing PO acknowledgment
The decision for this workflow
Request acknowledgment by customer program and outside-process milestone rather than one pooled date. The page uses sample/fictional data so a team can challenge the rule before sharing a real export. It is aimed at a buyer deciding what to ask, what to hold, and what to leave for a human.
Prophet 21 program acknowledgment sheet
This page’s working artifact is a Prophet 21 program acknowledgment sheet. It is intentionally narrower than a full ERP rollout: the buyer supplies a reviewed export or copies a supplier message, then checks the proposed state before anything is sent or written back.
Worked fictional example: Fictional Prophet 21 PO P21-CM-88
| Field | Fictional value |
|---|---|
| Program | Orchid / 60 housings |
| Internal process | CNC complete 2026-12-05 |
| Outside process | Anodize slot 2026-12-08 |
| Decision | Final ship 2026-12-10; keep both milestones |
The useful decision is request acknowledgment by customer program and outside-process milestone rather than one pooled date. In a real review, record the source file, message date, reviewer, and any redaction before treating a value as operational.
What Helios does directly
Helios can generate the field set and local sample for review; it does not read or write a Prophet 21 tenant. P1 stores status records 0 live-tested integrations. Helios keeps the distinction between a draft, an extracted value, and a buyer-approved decision visible. A supplier reply is not sent automatically from this page, and no ERP record is changed by this artifact.
Evidence boundary
Epicor product and partner pages provide ecosystem context only and do not support a live Helios integration claim. The three sources below provide industry or vendor context; they do not establish a Helios customer result, certification, or live integration. The p1-stores status is the controlling integration boundary for this wave: 0 live-tested integrations.
Use the related workflow links to prepare the minimum export, draft an acknowledgment, or review a supplier reply. Keep real purchase orders and controlled documents in the approved environment.
Working artifact · fictional sample data
Open-PO export validator
| po_number | supplier | line | promise_date | qty_open |
|---|---|---|---|---|
| PO-1042 | Northstar Plating | 10 | 2026-11-06 | 20 |
| PO-1043 | Acme Machining | 20 | 2026-11-08 | 0 |
| PO-1044 | Example Supplier | 10 | not-a-date | 12 |
Sources and verification
- Epicor Prophet 21 product page (primary; accessed 2026-10-23) — Epicor describes Prophet 21; this page does not claim a Helios connector.
- Epicor ISV partners (primary; accessed 2026-10-23) — Epicor describes its ISV ecosystem; it does not validate this workflow.
- SourceDay PO collaboration datasheet (primary; accessed 2026-10-23) — SourceDay provides category context; its product is not attributed to Helios.
Frequently asked questions
Why include the customer program in the acknowledgment?
It prevents a shared supplier from applying one date to the wrong build. The example uses a fictional program code for that reason.