How RF-SMART Manufacturing Data Collection connects to Oracle JD Edwards EnterpriseOne
Native barcode and RF transactions on E1 workflows
Transactions are built on EnterpriseOne workflows, so a scan on the floor results in the same inventory and work order updates as the standard JDE screens. The vendor states both online and offline operation; offline transactions queue on the device and post when the connection returns.
What data moves
| From | To | Data | When |
|---|---|---|---|
| JD Edwards | RF-SMART | Open work orders, parts lists, routing steps, items and lots | Scan of work order barcode |
| RF-SMART | JD Edwards | Work order completion quantities, with lot and serial numbers | Operator confirms completion |
| RF-SMART | JD Edwards | Labor hours by employee and operation | Swipe on/off or elapsed time entry |
| RF-SMART | Label printer | Shop floor labels for lots, containers and serials | Completion or issue |
Setting it up
- 1List transactions neededDecide between completions, issues, labor, scrap and moves, and which work centers use each.
- 2Clean JDE manufacturing dataVerify routings, work centers, lot control flags and serial settings, since scans will expose any gaps.
- 3Set up labor identitiesIssue badges or IDs mapped to employees or addresses so labor lands on the right person.
- 4Design labelsCreate lot and serial label formats and test them with the printers on the floor.
- 5Configure offline behaviorDefine what can be done offline, such as completions, and how conflicts are handled when syncing.
- 6Pilot and trainRun one cell for a week, reconcile with JDE reports and train supervisors on exceptions.
What usually breaks
- !Operators who forget to swipe off leave open labor records that inflate hours and cost.
- !Offline transactions applied after a work order has closed are rejected, creating reconciliation work.
- !Serial or lot numbers entered twice generate duplicate errors or false traceability.
- !Label templates that do not match the downstream customer requirement force rework at shipping.
- !Routing steps that differ from actual practice leave reports of operation progress misleading.
A private AI layer across both systems
Open labor cleanup
A private assistant reading labor records can list open or overlong entries and suggest corrected end times for a supervisor to approve.
Sync exception summary
Group failed or queued offline transactions by cause and explain what to fix on each work order.
Traceability answers
Answer which components went into a serial number or lot from JDE records during a customer complaint.
Throughput questions
Let managers ask where work orders stall by operation and shift, from live JDE data.
Try it here, free
JD Edwards EnterpriseOne AI Assistant Sizing and Value Calculator
Estimate peak load, GPUs, index size, hours saved and payback for an on-prem AI assistant on JD Edwards EnterpriseOne.
When something else fits better
- JDE's standard Work Order Time Entry and Completion screens are enough where there are few operators and terminals at the cell.
- RFgen's mobile apps are another option validated by Oracle for JDE; compare scope and support.
- A full MES is worth considering if you need real-time machine data, not just barcode transactions.
Frequently asked questions
Does it work if the network drops?
The vendor describes online and offline data collection. Offline transactions are stored on the device and sent to JDE later. Test your own rules for conflicts, such as a work order closed in the meantime. Always test an offline scenario in your own plant, with a real work order closed or changed while a device is disconnected.
Can it track labor as well as completions?
Yes. The vendor lists labor tracking by swipe on and off or elapsed time, alongside lot and serial tracking and shop floor labels. Setting the swipe rules and shift boundaries carefully is important, since labor cost accuracy depends on operators using them consistently.
Where does AI add value on the shop floor?
Mainly in cleanup and answers: finding open labor, explaining failed syncs and tracing lots. A model on your own servers reads JDE data, shows its sources, and proposes corrections that a person approves before anything is written. Pilot with a few cells first, so you can tune labels, prompts and exception handling before every operator depends on it daily.
Pairing documented at rfsmart.com/jd-edwards-enterpriseone/solutions/enterpriseone-manufacturing-data- . RF-SMART Manufacturing Data Collection is a product of RF-SMART; Netray is independent and not affiliated with either vendor.