Lunica for Dancik Navigator
Lunica runs beside Dancik the way your reports do: read from the same data, in the same terms, with nothing posted back without a person.
The IBM i system for flooring, tile and lumber distributors, now part of Kerridge Commercial Systems.
How Lunica connects to Dancik.
Lunica reads Dancik Navigator through ODBC to the Dancik database on IBM i, under a profile that can only read: 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 Dancik has them, so an account on Net 30 EOM ages on that, not on a flat net-30.
Nothing is written to Dancik by Lunica. Work that belongs in Dancik goes back as a Dancik import where one exists, or keyed by your team from what Lunica prepared. Invoice copies and signed tickets come from Dancik’s document attachments, which keeps working exactly as before. Lunica runs on one Windows server inside your network, beside the IBM i.
51 workflows for Dancik Navigator.
Every workflow in the directory, written in Dancik’s terms, with a demo in its formats.
Questions
Does it need a server?
Lunica runs on one Windows server inside your network, beside the IBM i, set up and maintained by Lunica. It reads Dancik Navigator through ODBC to the Dancik database on IBM i, under a profile that can only read. There is no inbound connection from outside your network.
What does Lunica read in Dancik?
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 Dancik?
Nothing lands in Dancik without a person. What belongs in Dancik goes back as a Dancik import where one exists, or keyed by your team from what Lunica prepared.
What about our documents?
Invoice copies and scans keep living in Dancik’s document attachments. Lunica reads them when a workflow needs one and never writes to them.
See it on your Dancik data.
Thirty minutes. We walk a workflow on Dancik data, then map it to yours.