28 apr

Patch Level versus Feature Package


E-invoicing in Germany: How to implement the obligation with SAP Business One

SAP delivers updates for SAP Business One in two release types: Feature Packages (FP) and Patch Levels (PL or Service Pack SP). The current version number is under Help → About SAP Business One visible in the top line, for example 10.0 FP 2508 PL 04.

Context

On Feature Package (e.g. FP 2405, FP 2502, FP 2508) brings new functionalities: new OData entities in the Service Layer, new processes, UI enhancements, additional localisations, changed data models. The numbering follows the year and month (FP 2508 = August 2025) and marks a major development stage. Between two Feature Packages, SAP releases Patch Levels resp. Service packs — smaller releases with bug fixes, security patches, and minor adjustments without functional enhancements. Multiple PLs can follow the same FP release, for example FP 2508 PL 00, PL 01, PL 02. The FP release is particularly relevant for integrations and add-ons: it determines which service layer APIs are available (see change logs per FP). Add-ons such as B1UP, Coresuite, CKS.DMS, and Versino Financial Suite maintain their own FP compatibility matrices and typically need to be updated to a compatible version after an FP upgrade.

Demarcation

Patch levels are not technically major changes – nevertheless, they should not be skipped because they close security vulnerabilities and can be a prerequisite for later FP updates. FPs, on the other hand, are not mandatory jumps: customers often stay one or two FP generations behind to ensure add-on stability. Compared to a Major Release The upgrade from SAP B1 9.x to 10.0 is significantly less risky and without migration the Database Possible. A clean B1 upgrade strategy specifies how often FPs are applied, when PLs are installed, and who carries out which test runs before going live.


ReAct and RLEF

ReAct and RLEF: How Artificial Intelligence Learns from Real Mistakes — and What Automated Bank Reconciliation in SAP Business One Has to Do with It

This is the fourth instalment in a series on this blog dealing with AI fundamentals in conjunction with SAP Business One...
Service Layer AI as a transactional layer

SAP B1 10.0 FP2608: Service Layer AI as a transactional layer

The SAP Business One Service Layer has previously served predominantly as a passive data provider: applications requested data via OData, each ...
Process Reward Model

Process Reward Models: Why a correct result does not yet prove a correct method

This series continuously examines individual AI basic terms and methods such as the Process Reward Model. The previous episode has ...
Test-Time-Compute-Scaling

Test-Time Compute Scaling: Why a Smaller AI Model Can End Up Winning — and What Supplier Comparison in SAP Business One Has to Do With It

This is a continuation of the series on this blog, which deals with Artificial Intelligence in combination with SAP Business One...
RLHF

RLHF and reward models: AI hype or what the approval process in SAP Business One has to do with it

Key takeaways: The article covers the application of artificial intelligence in the context of SAP Business One and fundamental AI topics. Thanks to ...
AI Webinar

AI – Answers from SAP Business One – without SQL, without IT ticket

Live webinar on 30 July 2026, 14:00–14:30 | Live demo via Microsoft Teams | Duration: 30 minutes „How were the sales...".
Wird geladen …