Lunica for SAP Business One
Lunica runs beside Business One the way your reports do: read from the same data, in the same terms, with nothing posted back without a person.
SAP’s small-business ERP, run by manufacturers and distributors with a few hundred users or fewer.
How Lunica connects to Business One.
Lunica reads SAP Business One through a read-only login to the Business One database on SQL Server or HANA: the business partner 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 Business One has them, so an account on Net 30 ages on that, not on a flat net-30.
Nothing is written to Business One by Lunica. Work that belongs in Business One goes back as the DI API or an import where one exists, or keyed by your team from what Lunica prepared. Invoice copies and signed tickets come from the attachments on the document, which keeps working exactly as before. Lunica runs on one Windows server inside your network, or beside your hosted instance.
51 workflows for SAP Business One.
Every workflow in the directory, written in Business One’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 instance, set up and maintained by Lunica. It reads SAP Business One through a read-only login to the Business One database on SQL Server or HANA. There is no inbound connection from outside your network.
What does Lunica read in Business One?
The business partner 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 Business One?
Nothing lands in Business One without a person. What belongs in Business One goes back as the DI API or an import where one exists, or keyed by your team from what Lunica prepared.
What about our documents?
Invoice copies and scans keep living in the attachments on the document. Lunica reads them when a workflow needs one and never writes to them.
See it on your Business One data.
Thirty minutes. We walk a workflow on Business One data, then map it to yours.