Built for SAP Business OneB1Nexus Lead Time Update
Real lead times. Reviewed, then written to SAP.
SAP Business One has a lead time field, but nothing keeps it true. B1Nexus Lead Time Update measures every purchase order to goods receipt, lets your buyers approve or reject each one, and writes the item's average lead time back to SAP.
A receipt only changes an average after a reviewer approves it.
Lead time is the GRPO date minus the purchase order date. Nothing reaches the item master until a person has looked at it.
01GRPO posted
A goods receipt is copied from a purchase order in SAP.
SAP
02Daily sync
Overnight, each receipt line gets its lead time in days.
overnight
03Pending
New receipts wait in the queue, and reviewers get a digest.
daily digest
04Reviewer decides
Approve it, or reject it with a reason that is kept.
approve / reject
05Average update
Preview the new averages, then confirm.
preview → confirm
06SAP item updated
The average is written to the item, and logged in SAP.
history in SAP
A closer look
Every number, with the receipts behind it.
Receipt detail
See why a receipt took 14 days
The purchase order and goods receipt side by side, how the days were counted, the item's current average and SAP lead time, and a chart of every approved lead time for the item.
GRPO 2001 · line 0
Average update
Preview first. Nothing is written yet.
Pick the items with newly approved receipts, compare the current and proposed averages and the receipts used, then confirm. Each item is updated in SAP all-or-nothing.
Average Update
Open POs by item
Know when it will really arrive
Open purchase order lines with how long they have been open and the expected receipt date from the item's average lead time. Late lines stand out.
Open POs by Item
In SAP Business One
The average lives on the item. The history lives in SAP too.
On the item master
Average lead time, number of receipts, shortest, longest and date of the last update, in their own item fields.
MRP, when you're ready
Optionally write the rounded average to the standard Lead Time field that MRP uses. Off until you switch it on.
History in SAP
Every review decision and every update run is stored in SAP, with the exact receipts each average used.
Service Layer only
Reads and writes go through the SAP Business One Service Layer. A one-time setup adds the fields and tables it needs, and never changes existing ones.
History & audit
Who decided, and what changed
A read-only record of every average lead time update (old and new value, method, receipts used, by whom and when) and every review decision with its reason.
History & Audit
Features
Built for buyers and planners.
Daily receipt sync
Reads new goods receipts from SAP every morning and measures each PO-based line in days. Receipts cancelled later drop out on their own.
Outlier flags
Negative times, receipts over a year and lines far outside the item's range are flagged, so a person decides.
Review queue
Filter by date, item, vendor or item group, sort, approve or reject in bulk, and export to CSV.
Reasons on record
Rejections need a reason, with codes such as Expedited, Vendor error or Data entry error. Admins can reopen a decision.
Your averaging rules
Simple or quantity-weighted, over all receipts or the last N receipts or days, in calendar or business days with your holidays.
Daily digest
An e-mail and an in-app notification list new receipts to review. Reviewers can be scoped to item groups or buyers.
Expected receipts
Open purchase orders by item, how long they have been open and when they should arrive, with late lines flagged.
Roles & audit
Viewer, Reviewer, Updater and Admin roles, and a read-only history of every decision and update, stored in SAP.
Requirements
What you need to get started.
SAP Business One
SAP Business One on SAP HANA, with the Service Layer. A one-time setup creates the item fields, tables and objects the app needs.
Server
Windows Server (x64) with PostgreSQL 15 or later, behind IIS for HTTPS. Delivered as an offline package: no internet or build tools needed on the server.
E-mail
An SMTP account for the daily digest, with a test e-mail from the admin screen.
Users
Any modern browser, down to phone width, in light or dark mode. Roles: Viewer, Reviewer, Updater and Admin.
FAQ
Frequently asked questions
Does it change lead times in SAP on its own?
No. Receipts only count once a reviewer approves them, and an average is only written after someone with the Updater role previews the new values and confirms. Each item is written all-or-nothing.
Does it overwrite the standard Lead Time field that MRP uses?
Only if you switch that on. By default the average goes into its own fields on the item (average, number of receipts, shortest, longest and last update), and the standard Lead Time field is left alone.
What about receipts that would distort the average?
Negative times, receipts over a year and, if you set a tolerance, receipts far outside the item's range are flagged as outliers. A reviewer decides: approve, or reject with a reason that stays on record.
How do reviewers know there is work?
A daily digest e-mail and an in-app notification list the new receipts to review. Reviewers can be limited to their own item groups or buyers.
Contact us
See your real lead times.
Book a walkthrough of the review queue and the average update, or tell us how your buyers keep lead times up to date today.
