PrimeForce / Modules / Service Calls
Service Calls
A field-service front end for companies already running service in SAP Business One. Built for a technician on a site with no signal.
What it does
Field technicians log service calls that post into SAP Business One as service call documents. The only part of the product that captures offline — drafts queue on the device and upload when the connection returns.
- Offline capture, keyed so nothing duplicates
- Server-side queue, drained to SAP every 60s
- Progress re-sync, because SAP users edit remarks
- Location captured at submit
- Posting Monitor reads without calling SAP
Offline works for Service Calls only. Payroll, leave, HR and reports all require a live connection.
· Status
· Configuration
· Service Call Monitor
What that means in practice.
Offline capture with a client-side key
A draft is written to the device database with a client-generated request ID. It leaves the device only once the server has it — and because the key travels with it, a retry after a timeout cannot create a second call.
Queued, not posted synchronously
Submitting puts the call in a server-side staging queue. A background worker drains it to SAP on an interval, so a SAP outage delays posting instead of failing the technician’s submission.
Progress re-sync
SAP users keep editing a service call’s remarks long after it posts, so a background job re-reads that field on a longer interval and shows it on the Monitor.
A Monitor that does not hammer SAP
SAP lookups are cached locally, so the Monitor screen makes zero live SAP calls on its read path.
Location at submit
Coordinates are captured when the call is logged. The product stores them; it does not render a map.
See it against your own numbers.
Bring a payroll period you have already closed. We configure the components, run it, and show you the variance against your figures.
Other modules.
Human Resources
Every other module reads from the employee master. It holds the record, the salary card that values it, and the lifecycle events that change either one.
Organization
Ten master tables, every code unique per company. This is the structure payroll costs against and workflow routes through.
Payroll
Sixty-nine entities and the longest chain in the product: run plan, staged inputs, snapshot, pay line, component line, cost-centre split, journal entry.