Runs inside SAP GUIread-only
Reads your Z code and live SAP data, and answers inside the SAP screen, with its sources.
ANIMATION · SAMPLE PROGRAM AND DATA
User: I can't post to cost center 4100; I'm getting error ZFI 004. Why?
Verity, with SAP data: Cost center 4100 has used up its 2026 budget, so ZFI_MASRAF is blocking the posting. Controlling raises the budget; until then you can post to a different cost center. Figures: budget TL 250,000, spent TL 251,420, remaining TL −1,420.
Would you like me to prepare an e-mail to pass this on to the right person?
Sources (3): ZFI_BUTCE, ZFI_MASRAF_F01, Message ZFI 004
CAPABILITIES
It reads your Z programs, messages and tables, and grounds every answer in those records.
Z PROGRAM ANALYSIS
It studies each Z program in eight passes: reading the code, tables and messages, and testing the queries it builds against SAP. Your administrator approves the resulting program profile; if the code later changes, Verity says so in its answer.
LIVE DATA
Only from the tables of the program you ask about, read-only. Copy the table or export it to Excel in one click.
ERROR RESOLUTION
It reads the message's long text in SAP and the code condition that raised it, then writes what happened, why, the fix and who does it. If enabled, it also reads ST22 short dumps.
INSIDE SAP GUI
You type /nZVERITY in the command field; Verity opens with your SAP session, with no separate password. Those without authorization can’t open it.
APPROVED ANSWER FIRST
Each question is first looked up in your company's approved question set; on a match the answer comes without using AI. AI steps in when needed, SAP data when needed.
WRITTEN FOR THE ROLE
You choose the role: a business user learns what to forward and to whom; a consultant sees the master data and customizing work to do, ready to do it themselves. The choice opens no new data access.
SUPPORT TOOLS
Most SAP tickets are a few recurring types: missing master data, a missing authorization, “it worked yesterday”, a job that failed overnight, why a setting behaves the way it does. Verity solves these inside the chat by looking at your own system: what’s missing, whose job it is, and which transaction fixes it.
I can't create an order for customer 100482 in VA01.
Opens the record for the customer, vendor, material, account and cost center, and finds what is missing or blocked.
I get a “no authorization” error in VA01.
Finds the missing authorization in your own session and drafts the request to send to the security team.
It worked last week, today it doesn’t.
Shows what changed in the program and master data since that date — what, by whom and with which transport.
Which jobs failed last night?
Without going through SM37 one by one, it finds the canceled jobs and the ones that finished without errors but produced no list, and shows each step’s program and variant.
Why does order type ZOR run a credit check?
Reads the setting in this system and explains it in business terms, naming the SPRO path and the maintenance transaction.
I want to add my own check before saving in VA01. Which exit?
Shows the point that best fits your need and at most one alternative, and marks the ones your company already uses. You write the code.
Compare this report for company codes 1000 and 2000.
Without running the program, it traces the data work in its code and gives the result and the differences as a table.
Prepare the user guide for this transaction.
Compiles an end-user Word guide from the approved program profile: selection screen, step-by-step use, result screen, messages. No AI is used and nothing is made up.
They are all read-only and run with your own SAP authorizations: you see in chat only what you can already see in SAP.
DEBUG ASSISTANT · FOR CONSULTANTS
The consultant types the error message and the transaction. Verity replays the path to where the error was raised in a real debugger window, step by step, with your own system’s code and data: which condition, which value, whose job.
I get error ZSD 012 saving a ZOR order for customer 100482 in VA01, payment term Z030. Why?
SELECT SINGLE * FROM zsd_payt_rules INTO ls_ruleLS_RULE-ZTERM = Z060 WHERE kunnr = vbak-kunnr.IF vbak-auart = 'ZOR'.VBAK-AUART = ZOR IF vbkd-zterm <> ls_rule-zterm.VBKD-ZTERM = Z030 MESSAGE e012(zsd).E ZSD 012Root cause: The order's payment term Z030 doesn't match Z060 in the customer's ZSD_PAYT_RULES rule, so the user exit blocks the posting.
Problem: The order can't be saved because its payment term differs from the one defined for this customer.
Solution:
Who fixes it: Master data.
ANIMATION · SAMPLE PROGRAM AND DATA · CLICK THE STEPS
It shows the path to the message with the value read from SAP at each condition. Standard SAP or your own code — clear at a glance.
It counts the report’s reads one by one with your selections, and finds at which condition the data was cut off and what is really in that field.
It reads the ST22 dump: shows the path to the line where the program stopped and the record that caused the error, explained in business terms.
Nothing is written to SAP and no debugger is opened. If you wish, you can step through the same spot in your own debugger.
SPEC · ABAP
Next to Chat, the left panel has two more areas. Both look at your own system; neither writes anything to SAP.
You describe the need in your own words. Verity asks about the points that must not go wrong, verifies tables and fields in the system and gives you the TS as an Excel file in the template. It works the same for users and consultants.
Anything that can’t be verified is listed as an “open point”. Solutions such as writing directly to standard tables never go into a TS; the safe way (BAPI, maintenance table) is proposed.
You describe the request or attach the TS Excel file. Verity inspects the system and explains the development step by step with sample code. The sample code is checked against the coding standard and security rules.
Verity does not write code to the system, create objects or run programs; you carry out the steps. For work that needs approval (posting with a BAPI, enhancements) it asks first.
SECURITY
Verity connects to your SAP with read-only access. It writes no data and posts no records.
Read-only isn't left to a single setting. Verity's request passes through four separate layers before it reaches SAP.
Verity signs a data processing agreement (KVKK/GDPR) with you. If you prefer, you connect your own AI account; then your agreement applies.
Personal and confidential values in the SAP data an answer needs are replaced with a placeholder before they leave your network. The real value behind it stays only on your server; the AI writes its answer with placeholders and the user sees the real value on screen.
If masking can’t be completed, the request never goes to the AI. Screenshots, PDFs and audio can’t be masked, so they aren’t sent while the shield is on.
HOW IT WORKS
Verity is made of the chat screen in SAP GUI, the server on your network and the admin portal. SAP data it reads is processed on your server; only the part needed for the answer goes to the AI, with personal and confidential values masked.
A user types /nZVERITY in the command field; the chat opens with the SAP session — in Turkish for a Turkish logon, in English for any other language. The SAP role decides who can open it — no separate account or password.
Runs on a virtual machine on your network. It only reads SAP, studies your code and data, and prepares the answer with its sources.
Manage your programs, the approved program profiles and question sets here, and track usage. Chat text reaches the portal only if you want it to.
The program profile is re-analyzed regularly; if the code hasn't changed, no analysis runs.
NEXT STEP
The pilot is installed on your existing on-premise S/4HANA; no SAP cloud commitment is required.1
PRICING · DURATION · SCOPE
Pricing, pilot duration and scope are prepared from your number of systems, your programs and your number of users. All of it is discussed in the pilot meeting, with your data.