Manufacturing ERP Integration & Support Portal

Tester Guide / UAT Checklist Instructions only

Staff Testing

Done Reset Click Reset Demo Data. Expected: Dashboard returns to clean stock, sales, ERP sync, and ticket values. Demo data is ready.
Current Produce Open Manufacturing and complete WO-0001. Expected: Work order is completed, stock movement appears, production receipt is queued. Waiting for WO-0001 completion.
Next Sales Create a sales order, then queue it to Infor M3 or SYSPRO. Expected: Sales order becomes an ERP outbox transaction. Waiting for sales order creation.
Next ERP Sync Open ERP Monitor, click Send, then try Force fail. Expected: Success creates sync log; failure creates support ticket. Waiting for ERP send/failure test.
Next Support Add vendor reference, retry the failed transaction, then close the ticket. Expected: Failed sync becomes sent and dashboard support count updates. Waiting for failed ERP sync.
Done Report Open Docs & Reports. Expected: Staff can explain official references, SQL Server proof, UAT, and deployment. Docs & Reports opened.

System Work Area Use this area to operate the ERP demo. The guide above is for tester instructions.

Simple Reports

Reporting extension point

Report	Value	Purpose
Production output	0	Shopfloor performance
Stock balance	1240	Inventory support
ERP sync failures	0	Support priority
Open vendor tickets	0	Follow-up until closure

Official References

Legit sources only

Demo Boundary

This is a working ERP integration architecture demo. It uses mock Infor M3 and SYSPRO connectors because no live vendor tenant credentials are available. A real connector can replace the mock connector behind the same interface after access, mapping, security, and vendor test rules are provided.

The UI is Julie's-inspired in public biscuit manufacturing tone only. It is not an official Julie's system, does not copy protected brand assets, and does not claim Julie's uses Infor M3 or SYSPRO.

Database Runtime Boundary

Honest demo scope

The online demo uses dependency-free JSON / in-memory storage so staff can test the full workflow without SQL Server credentials, database setup, or vendor platform access. It does not claim that a live SQL Server database is connected to this public demo.

Database readiness is demonstrated through SQL Server proof scripts in the project. These scripts show the intended schema, seed data, stored procedures, views, functions, scheduler concept, and data warehouse reporting structure that can replace the demo store in a production implementation.

SQL Server Proof

Schema script: sql/001_schema.sql creates app, erp, dw, and admin.
Seed script: sql/002_seed_demo_data.sql prepares demo manufacturing and sales records.
Stored procedures: app.sp_CreateWorkOrder, app.sp_CompleteProduction, erp.sp_QueueOutbox, and dw.sp_LoadFactSales.
Views and functions: stock balance, ERP sync status, available stock, retry eligibility, and dashboard views.
Scheduler concept: SQL Server Agent-style outbox retry timing is documented as a proof concept, not installed in this public demo.

Deployment Proof

podman build -t localhost/manufacturing-erp-demo:latest .
podman save -o manufacturing-erp-demo.tar localhost/manufacturing-erp-demo:latest
scp ./manufacturing-erp-demo.tar [email protected]:~/manufacturing-erp-demo-update.tar