SAP holds the operational truth of the business — purchase orders, postings, stock, production — and getting an answer out of it has always cost either a transaction code you have memorised or a favour from someone who has. Most people who need the number do not have access, and most people with access still find it slow. The SAP connector is part of askFinz Knowledge, which is still rolling out; here is what it will do, and what it will not.
Ask for a record without knowing the transaction code
Describe what you are looking for — a supplier, a purchase order, a material — and get the record, without learning the screen it lives behind.
Read the text fields nobody reports on
Long texts, notes and rejection reasons attached to a document carry the explanation that a field code does not. Those are matched by meaning.
Expose a defined slice of the system
You choose the modules and objects to include. The right first step is a narrow one — vendors and purchase orders, say — not the whole landscape.
What is read, and what is never posted
What crosses, and what stays in SAP
Read
the fields and long texts of the objects your administrator exposes.
Written back
nonenothing. No documents created, posted, released or changed.
Stored
a searchable copy of that text, plus the reference needed to open the record in SAP.
Never read
objects not exposed, and anything the connecting user is not authorised for.
What you will be granting
A read-only service user with authorisation for the specific objects you expose — the same discipline you would apply to any reporting interface, and nothing that can post a document.
Setting it up
Planned — not available yetWhat connecting it will look like once the connector arrives.
- 01
Your Basis team creates a read-only user and exposes the objects to include.
- 02
Connect from Knowledge and confirm the object list.
- 03
Decide the mode: a full read on a schedule, or only documents changed since the last pass.
- 04
Set the refresh interval.
Limits, honestly
- One-way and read-only. SAP remains the system of record, and no posting is ever made.
- Answers reflect the last refresh, not the live document.
- SAP landscapes vary enormously. Which objects are reachable depends on your version, modules and interface, and cannot be promised generically here.
- Authorisation objects are respected by exposing less, not by reproducing SAP's own checks.
- Custom Z-tables need to be exposed explicitly, one at a time.