Consulting roles
The Consulting product groups read-only advisory roles. They read your system for evidence and produce client-facing deliverables — assessments, reviews, inventories, and a final report — but they change nothing in SAP. Every Consulting role is handed only the read set of tools and physically cannot write, lock, or activate.
You pick these roles in the Chat composer, and they pair naturally with the Requests queue, where consulting work is organized. For the permission model, see How roles work.
The Migration Map and Clean-core check roles also appear under Consulting. They are documented on the CDS, RAP, Fiori & migration page.
At a glance#
| Role | Read/Write | Use it to… |
|---|---|---|
| Assessment | Read-only | Assess the current state of a scoped custom-code area. |
| Authorization Review | Read-only | Derive required auth objects from code and report gaps. |
| Interface Inventory | Read-only | Inventory RFC, ALE/IDoc, and Gateway interfaces from config and code. |
| Delivery Report | Read-only | Assemble the client deliverable with a GO / GO-WITH-WARNINGS / NO-GO verdict. |
Assessment#
Read/Write: Read-only.
Assessment produces a current-state assessment of a scoped custom-code area. Its methodology is read-only evidence → findings → summary, where each finding follows a consistent shape: symptom → evidence → impact → recommendation → effort/risk → confidence. The deliverable is an executive summary, a findings table, and — importantly — a "not checked" section that states what was out of scope or could not be examined.
When to use it: as the evidence-gathering backbone of a consulting engagement on a defined area of custom code.
Authorization Review#
Read/Write: Read-only.
Authorization Review derives the required authorization objects from code — explicit AUTHORITY-CHECK statements plus the implicit ones (S_TCODE, S_PROGRAM, S_RFC) — and, where access is readable, compares them against what is actually granted. It reports MISSING authorizations versus OVER-GRANT. It is advisory only and makes no PFCG changes.
When to use it: to understand what a piece of custom code actually needs to run, and where granted access is too tight or too broad — without touching roles.
Interface Inventory#
Read/Write: Read-only.
Interface Inventory builds a read-only inventory of interfaces from both configuration and code: RFC destinations, ALE/IDoc partner setup, RFC-enabled function modules, and OData/Gateway services. It is static only — it does not check runtime health. Runtime interface health is Support's job; see Support roles.
When to use it: to map what integrations exist in a system as a planning or documentation input, distinct from checking whether they are currently working.
Delivery Report#
Read/Write: Read-only.
Delivery Report assembles the client-facing consulting deliverable from the evidence gathered by the other Consult roles. It produces a prioritized roadmap, an overall GO / GO-WITH-WARNINGS / NO-GO verdict, and a mandatory "missing evidence" section that is honest about what could not be established.
When to use it: at the end of an engagement, to turn the individual Consult outputs into one coherent report a client can act on.
Related pages#
- How roles work — why every Consulting role is read-only.
- Requests — the queue where consulting work is organized.
- CDS, RAP, Fiori & migration — home of Migration Map and Clean-core check, which also appear under Consulting.
- Support roles — runtime interface health lives here, not in Interface Inventory.
- Chat — pick a role and send a task.