Lunica for Epicor Eclipse
Lunica runs beside Eclipse the way your reports do: read from the same data, in the same terms, with nothing posted back without a person.
Epicor’s ERP for electrical, plumbing and HVAC distributors, built around the order and the branch.
How Lunica connects to Eclipse.
Lunica reads Epicor Eclipse through Eclipse’s reporting database or ODBC, under an account that can only read: the customer file and open items for aging and statements, open purchase orders and receipts for AP matching, the product file for counts and pricing, quotes and order history for the sales desk. Terms are read as Eclipse has them, so an account on 2% 10 Net 30 ages on that, not on a flat net-30.
Nothing is written to Eclipse by Lunica. Work that belongs in Eclipse goes back as an Eclipse import where one exists, or keyed by your team from what Lunica prepared. Invoice copies and signed tickets come from Eclipse Imaging, which keeps working exactly as before. Lunica runs on one Windows server inside your network.
51 workflows for Epicor Eclipse.
Every workflow in the directory, written in Eclipse’s terms, with a demo in its formats.
Questions
Does it need a server?
Lunica runs on one Windows server inside your network, set up and maintained by Lunica. It reads Epicor Eclipse through Eclipse’s reporting database or ODBC, under an account that can only read. There is no inbound connection from outside your network.
What does Lunica read in Eclipse?
The customer file, open items and terms, purchase orders and receipts, the product file, quotes and order history, as each workflow needs them. Read-only, and only the rows a task is about.
Can it post to Eclipse?
Nothing lands in Eclipse without a person. What belongs in Eclipse goes back as an Eclipse import where one exists, or keyed by your team from what Lunica prepared.
What about our documents?
Invoice copies and scans keep living in Eclipse Imaging. Lunica reads them when a workflow needs one and never writes to them.
See it on your Eclipse data.
Thirty minutes. We walk a workflow on Eclipse data, then map it to yours.