14 Sep

Context Engineering


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

Context Engineering refers to the targeted selection, structuring and preparation of the information that an AI model receives for a query. It is not about the formulation of the instruction itself, but about what knowledge, examples and data are provided to the model before it even answers.

A language model only processes what is in the context window. If the relevant excerpt from the customer history or product documentation is missing, no matter how well-formulated the prompt is, the answer will remain vague or incorrect. Context engineering therefore comprises several building blocks: retrieval-augmented generation for accessing documents, a memory for previous interactions, system instructions that set the framework, and the selection of which information actually fits given limited context windows. This selection is not a technical detail. It determines whether an AI assistant answers from a company's context or from generic training knowledge.

Reference to SAP Business One

Context engineering plays a concrete role in the SAP Business One world as soon as an AI assistant is required to answer questions about documents, master data or reports. A model that has only been trained generally knows neither a client's chart of accounts nor the payment terms of a specific business partner. Only the preparation of master data and document context, for instance via an MCP server or a retrieval pipeline, enables the model to work with the client's actual data instead of guesswork.

Demarcation

Context engineering is not identical to prompt engineering. Prompt engineering optimises the phrasing of the instruction. Context engineering optimises the information available to the model. Retrieval-augmented generation, in turn, is a single technique within context engineering, not a synonym for it. Anyone who only uses RAG, but neglects memory, system instructions and selection criteria, is only doing half of context engineering.


 

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...".
Generative AI in ERP

AI in ERP – but under control: What Versino AI means for SAP Business One users

AI can do a lot today – but without control, it often creates more problems than it solves. Versino AI connects AI models...
Wird geladen …