14 Sep

Context Engineering

Versino Financial Suite

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.


 

AI in everyday work: Person starts with their own task instead of the learning pile

AI in everyday work: Here's how to find the right start

Anyone who wants to use AI in their daily work is familiar with this: You read an article about prompts. A new model appears in it ...
AI-SHOP

AI assistant meets SAP Business One: Two paths out of the Versino AI shop

AI assistants like Claude or Copilot write emails, compile documents, and explain technical terms. But when you ask them about the open-source code...
SPRINT & SWIRL

Sprint and Swirl: How an AI agent divides work and learns from trials

This series deals with artificial intelligence in conjunction with SAP Business One. It takes a close look at fundamental AI principles...
LATS

LATS: Considering several paths simultaneously with AI — and the availability check in SAP B1

This series focuses on artificial intelligence in conjunction with SAP Business One. Not as a collection of product announcements, but as...
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 ...
Wird geladen …