Connecting ThingWorx CWC to SAP: From Work Order to Finished Stock
By PSPTechHub ·

Summary
PSPTechHub connected ThingWorx Connected Work Cell (CWC) 9.7 to SAP across the whole life of a production order. Orders now arrive in CWC from SAP on their own and are scheduled for each work cell. Operators see the order's live SAP details at the top of their screen, record the parts they use, and finish each step. CWC then tells SAP the step is done, and when the order is complete it books the finished products into stock. Nobody types the same information into SAP twice.
The Problem: SAP and the Shop Floor Were Out of Step
Production orders were planned in SAP, but the work happened in CWC. Every order had to be set up by hand in CWC, and everything that happened on the line had to be typed back into SAP afterwards.
Orders set up by hand
Planners had to recreate each SAP order in CWC before operators could start.
Operators couldn't see the full picture
The work screen showed only basic order details, not the quantities and status held in SAP.
Double entry of parts and progress
Parts used and steps finished were recorded in CWC and then again in SAP.
Stock that didn't match
Late or missing entries meant SAP showed stock that wasn't really on the shelf, and finished products weren't booked in on time.
Using too much by mistake
Nothing stopped someone recording more of a part than the order needed.
The Solution: SAP Connected at Every Step of the Order
PSPTechHub connected CWC to SAP at every point where an order changes hands: when it is planned, while it is built and when it is finished. Everything happens on the screens operators already use.
Orders arrive automatically
Released SAP orders are brought into CWC with their product and route, ready to schedule — no retyping.
Scheduling for each work cell
Planners see orders with their status, edit details, and load serial numbers so several jobs can run in parallel.
Live order details on screen
The top of the work screen shows the SAP order number, process plan and revision, target, delivered and confirmed quantities, and SAP status.
Needed vs used, at a glance
For each part, operators see how many the order needs and how many have been used.
Record parts, with no over-use
Operators enter batch or serial numbers and press Consume; the button locks once the needed amount is reached.
Only the parts that matter
Parts SAP records automatically are hidden; bulk parts and pick-and-place machine files are recorded in one go.
Tell SAP when a step is done
Pressing Complete confirms the operation in SAP, so order progress stays current.
Book finished products into stock
When every step is done, the operator enters the serial or batch numbers and confirms, and SAP records the goods receipt.
Clear answers from SAP
Every action shows SAP's own success or error message, so operators know where they stand.
How It Works: From Work Order to SAP
- 1
Order released in SAP
CWC picks up the order, finds its route and makes it ready to schedule.
- 2
Schedule and start
The planner schedules it to a work cell and the operator starts the job.
- 3
See the live order
The work screen shows the order's SAP details and its parts list.
- 4
Record parts used
The operator records batch or serial parts, bulk parts or the machine file, and SAP is updated.
- 5
Finish each step
Pressing Complete confirms the operation in SAP.
- 6
Deliver the order
After the last step, the operator enters serial or batch numbers and SAP books the finished products into stock.
For IT Teams: How It Is Built
CWC handles the operator screen; SAP stays the official record for stock and order progress. ThingWorx services connect the two in real time.
- CWC work screenMaterial Consumption area added to the operator's execution screen
- ValidationBlocks empty entries and use beyond the needed quantity
- Helper servicesRead the SAP parts list and send consumption and confirmations
- SAP connectorLive link to SAP for parts lists, goods movements and operation confirmation
- SAPKeeps the official record of stock and order progress
ThingWorx services built
| Service | Purpose |
|---|---|
| Parts list from SAP | Read live at runtime — no separate copy of SAP data is stored |
| Goods movement to SAP | Posts each consumption against the work order |
| Order import and scheduling | Brings released SAP orders into CWC, finds the route and creates the product |
| Order header details | Reads live order quantities and status from SAP for the work screen |
| Operation confirmation | Confirms finished operations in SAP |
| Goods receipt | Books finished products into SAP stock with serial or batch numbers |
| Pick-and-place file reader | Reads machine files and posts parts in bulk, with an audit log |
| Consumption table | Keeps a record of what was used on each order |
Design decisions
- SAP data is read live, so operators always see the current parts list
- Built into the CWC screen operators already know — no new app to learn
- Standard CWC screens are customized through copies wired in by the menu configuration, so PTC upgrades stay clean
- Each feature tested against SAP: order details matched field by field, missing SAP data handled on screen
- Every consumption attempt shows SAP's real answer, success or failure
- Over-use is stopped on screen before anything reaches SAP
- Machine-file uploads are logged so every bulk posting can be traced
Outcomes
No manual order setup
SAP orders appear in CWC ready to schedule.
One place to work
Operators build, record parts and finish orders on the same screen.
Stock you can trust
Parts used and finished products reach SAP the moment they happen.
No over-use
Recording more than an order needs is blocked.
Live order progress
SAP knows when each step and each order is done.
Easier upgrades
Customizations sit on copies of standard screens, so the standard product stays untouched.
This solution fits if you need to…
- Record material consumption in ThingWorx CWC and post it to SAP
- Stop over-consumption of parts on a work order
- Record batch and serial numbered parts at the workstation
- Post pick-and-place machine usage to SAP automatically
- Confirm SAP operations when work is completed in CWC
- Import SAP production orders into ThingWorx CWC automatically
- Post goods receipt to SAP from ThingWorx CWC with serial or batch numbers
Frequently Asked Questions
Can ThingWorx CWC post material consumption to SAP?
Yes. In this solution operators record the parts they use in CWC and each entry is sent straight to SAP against the work order.
What is ThingWorx Connected Work Cell (CWC)?
CWC is PTC's ThingWorx app that guides operators through their work at the workstation, with digital instructions and data capture.
How do you stop operators using more parts than needed?
The Consume button only works once details are entered, and it locks as soon as the used amount reaches the amount the order needs.
What happens if SAP rejects a consumption?
The operator sees SAP's own error message on screen, so they know why and can fix it.
Can pick-and-place machine usage be sent to SAP?
Yes. The machine's file is read and all the parts it placed are recorded in SAP in one go, with an audit log of each upload.
Does CWC keep a separate copy of SAP data?
No. The parts list is read live from SAP each time, so it is always current.
Can SAP production orders be loaded into CWC automatically?
Yes. Released SAP orders are brought into CWC with their product and route, then shown on a scheduling screen for each work cell.
Can CWC book finished products into SAP stock?
Yes. When every step is complete, the operator enters the serial or batch numbers and CWC posts the goods receipt to SAP, then closes the order.
Can CWC tell SAP when an operation is finished?
Yes. Pressing Complete on the work screen sends an operation confirmation to SAP.
