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