- Service Layer
- The standard web interface SAP Business One exposes so external systems can read and write data using OData over HTTPS. Every call authenticates first, and the system’s business logic runs exactly as it would for a document entered on screen.
- DI API
- The programming interface used to integrate with SAP Business One before the Service Layer existed. It runs on a machine where the components are installed, which suits background work on an internal network better than requests arriving over the web.
- Company database
- One SAP Business One database holding an organisation’s master data, documents and configuration. Groups with several legal entities typically run more than one, and each is configured independently.
- Business partner
- The master record for anyone you trade with — customers, suppliers and general contacts. It carries addresses, payment terms, credit limits and the history of related documents.
- Item master data
- The master record for a product or service. It defines the code, units of measure, item group, costing method and the settings that determine how the item behaves in inventory.
- Sales order
- A document recording what a customer has asked to buy. It creates no accounting entries but commits stock and acts as the starting point for the delivery and the invoice that follow.
- Delivery
- The document recording goods leaving the warehouse for a customer. It reduces stock on hand and is normally the reference used when the invoice is raised.
- A/R invoice
- The customer invoice that takes a sale into the accounts. It creates the receivable and recognises revenue according to your configuration, usually based on a sales order or a delivery.
- Purchase order
- A document sent to a supplier confirming what you intend to buy. It does not affect stock or the ledger, but it is the reference used when goods arrive and when the supplier invoice is checked.
- Goods receipt PO
- The document recording goods received against a purchase order. It increases stock on hand and creates an accrual that stands until the supplier invoice is posted against it.
- Inventory transfer
- A movement of stock between warehouses or storage locations. The total quantity across the company is unchanged, but each location’s balance moves, which affects planning and stock counts.
- UDF
- A user-defined field added to a standard table or document to hold information the system does not provide out of the box. External systems only see these fields when the integration is explicitly configured to include them.
- UDT
- A user-defined table created to hold data that has no home in the standard structure, such as an internal reference list or supporting records for a customised process.
- Approval procedure
- Configuration that determines which documents, under which conditions, must pass through which approvers before they are added to the system.
- RBAC
- Role-based access control: granting permissions to roles that describe jobs, then assigning people to roles, rather than granting rights to individuals one at a time.
- Idempotency
- The property that sending the same request more than once has the same effect as sending it once. It is what prevents duplicate documents when a user presses the button twice or a client retries after a timeout.
- Audit log
- A record of who did what, when, and from where. It exists to answer questions after the fact, so it should be tamper-resistant and have a clearly defined retention period.
- Reverse proxy
- An intermediate server that receives requests on behalf of a backend service. It is commonly used to terminate TLS, restrict which origins may connect, distribute load, and keep access logs in one place.
