Internal tool · SAP B1

Inventory Batch
Approval & Posting

Receive scanned batches from handheld terminals, review and approve them, then post as Purchase Orders, Goods Receipts or Stock Countings directly into SAP Business One.

Open App & Sign In API Reference
Two-app pipeline

App 1 (Windows desktop with Nordic ID scanners) collects items and uploads to this web app. Here you review, approve, and post batches to SAP B1 — without scanners ever touching SAP directly.

📡
App 1 · Windows

Scan & Accumulate

Nordic ID terminals scan barcodes. Items are resolved against SAP B1 and stored locally.

📤
App 1 → App 2

Upload via API

Batches are POSTed to /upload/batch with an API key. Idempotent upsert.

App 2 · Web

Review & Post to SAP

Approve the batch here, then post it as a single SAP document. Idempotent — safe to retry.

What this app does

Manage the full lifecycle from upload to SAP posting in one place.

📋

Batch Dashboard

Tiles for Purchase Orders, Goods Receipts, and Stock Counting — with pending counts and status at a glance.

🔍

Line Validation

Each scanned line shows OK, Unresolved, or Warning. Batches with unresolved lines cannot be approved.

🏭

Three SAP Doc Types

Post batches as Purchase Orders, Goods Receipt POs, or Inventory Countings with correct field mapping.

🔑

API Key Upload

App 1 authenticates with a static API key over HTTPS. No interactive login required for scanner terminals.

🔁

Idempotent Posting

Re-uploading or re-posting is safe. Duplicates are detected via idempotency key. SAP docs are never created twice.

🔒

Session Auth

Web users log in with email + password. HttpOnly session cookie with 8-hour sliding expiry.

Batch status lifecycle

⬆ Uploaded ✔ Approved ⏳ Posting ✅ Posted / ✗ PostFailed · ✗ Rejected · 📦 Archived

PostFailed batches can be re-posted. Rejected batches can be re-uploaded by App 1. Once Posted, the SAP doc number is stored and the batch is locked.

Where to go next