Skip to main content

๐Ÿ–ฅ๏ธ App Tab

The AI@KB Cloud Application is organised into three main tab pages: App, Setup, and Admin. This page covers the App tab, which is the primary workspace for all users.

The App tab provides three interconnected panels:

PanelPurpose
Process ViewerVisual exploration of SAP end-to-end business process flows
ChatConversational AI for querying SAP configuration and extracted data
Documentation GenerationGenerate structured, data-validated documentation from your SAP system

AI@KB App Tab โ€” three-panel overview


Process Viewerโ€‹

The Process Viewer renders SAP business processes as interactive, structured flow diagrams โ€” sourced directly from your system's configuration and transactional data. It gives teams an immediate visual understanding of how key end-to-end processes are configured in their specific SAP landscape.

Selecting a Processโ€‹

Use the three dropdowns to navigate to the process you want to view:

  1. System / Customer โ€” select the SAP system or customer context
  2. Module โ€” choose the functional area (e.g. Sales & Distribution, Finance, Logistics)
  3. Process โ€” pick the specific end-to-end process (e.g. O2C Returns, Standard Order-to-Cash)

Once selected, click โšก Load to render the diagram. The status bar below the dropdowns confirms the process name and the number of steps it contains.

Process Viewer โ€” selecting a process flow

Viewing the Process Flowโ€‹

The diagram renders each step of the business process as a colour-coded block, connected by directional arrows that represent the document or movement flow between them. Each block displays the relevant SAP document type, transaction codes, tables, and real transactional examples extracted from the system.

Process Viewer โ€” Returns Order-to-Cash flow diagram

The diagram is structured in layers:

LayerContent
Process stepsEach SAP document type in sequence (e.g. Sales Order โ†’ Delivery โ†’ Goods Issue โ†’ Invoice โ†’ FI posting)
PartnersThe partner functions involved at each step (Sold-to, Ship-to, Payer, etc.)
OutputOutput types generated at each step (order confirmation, delivery note, invoice, etc.)
PricingPricing procedures and key condition types active in the flow
Real data, not diagrams

Every example shown in the Process Viewer โ€” document numbers, quantities, amounts โ€” is extracted directly from your SAP system. You are looking at how your system actually runs, not a generic template.


Chatโ€‹

The Chat panel provides a conversational AI interface that understands your SAP system's configuration, SPRO settings, pricing schemas, document types, and extracted transactional data. Ask questions in plain language and receive context-aware, evidence-backed answers.

Asking a Questionโ€‹

Type your question in the input area and click Send โ†’. The placeholder text summarises the scope of what the Chat understands:

Ask questions about SAP SD processes, SPRO configuration, pricing schemas, document types, and extracted SAP data.

Chat โ€” entering a question about return document types

Structured Answers with Source Referencesโ€‹

The Chat returns structured answers that reference the exact source files and configuration tables from which the information was drawn. Answers are formatted for clarity โ€” tables, code blocks, and section references are used where appropriate.

Chat โ€” answer showing Return Sales Document Types table

For more complex questions, the Chat provides layered responses: a summary finding followed by the underlying configuration evidence and process-level context.

Chat โ€” answer detail with standard O2C Returns flow and source reference

Example questions you can ask:

  • "Which sales document types are used for return flows?"
  • "What pricing procedure is active for Sales Org 1710?"
  • "How is free-of-charge delivery handled in this system?"
  • "What EDI/IDoc types are configured for outbound delivery?"
  • "Which delivery types are active in transactional data?"
Source transparency

Every answer includes a reference to the specific configuration file or data extract it was derived from (e.g. sd-spro-report.md, sd-retro-config.md ยง12). This makes it straightforward to verify findings and trace them back to the raw extracted data.


Documentation Generationโ€‹

The Documentation Generation panel produces structured, data-validated documentation of your SAP system's configuration โ€” automatically, based on the data extracted from your ERP. The output is a professional-grade reference document that combines SPRO configuration settings with evidence from real transactional data.

Selecting Content Sectionsโ€‹

Choose which sections to include in the generated document by ticking the relevant checkboxes:

SectionContent
Configuration of your SAP systemSPRO settings, customising tables, and configuration objects
Existing SAP dataTransactional data counts, key figures, and data-validated findings
Integration flowEDI/IDoc configuration, output determination, and warehouse integration
Output managementOutput types, NAST configuration, and print/EDI routing

Click โ–ถ Start generation to trigger the document build.

Documentation Generation โ€” selecting content sections

Generation Confirmationโ€‹

Once started, the application confirms that document preparation is underway and that the finished document will be delivered by email.

Documentation Generation โ€” confirmation message


Generated Document โ€” Illustrationโ€‹

The following screenshots illustrate the structure and content of a generated AI@KB document. This example covers the SAP S/4HANA Sales & Distribution module for a customer system running S/4HANA 2023 FPS03.

Cover Pageโ€‹

The document opens with a structured cover page identifying the system, client, extraction date, primary organisational unit, and the method used to produce the documentation.

Generated document โ€” cover page

Document metadata

The cover page records the extraction method: SPRO table extraction + transactional data via AI@CDS / MCP connector. This ensures full auditability of how the configuration was captured and when.

Approach and Key Findingsโ€‹

The opening section explains the documentation methodology โ€” combining SPRO configuration data with live transactional evidence โ€” and presents a summary of key findings at a glance: transaction volumes, unique customers, and active document counts drawn directly from the system.

Generated document โ€” approach and key findings summary

Standard Order-to-Cash Processโ€‹

The document includes process-specific sections that combine the configured document flow with real transactional examples. The Standard Order-to-Cash section shows the complete document chain with actual document numbers, movement types, partner functions, and output types observed in the extracted data.

Generated document โ€” Standard Order-to-Cash flow with data evidence

Free of Charge Deliveryโ€‹

Process variants such as Free of Charge Delivery are documented automatically, with the item category configuration, billing relevance settings, and a data table showing how many items and orders were processed under this variant.

Generated document โ€” Free of Charge Delivery configuration and data evidence

Integration Patterns and Output Configurationโ€‹

The Integration section maps the three layers of the output and integration landscape โ€” IDoc/ALE for document exchange, NAST for output determination, and EWM/WM for warehouse integration โ€” together with the actual counts and error rates observed in the extracted data.

Generated document โ€” integration architecture and output configuration

A dedicated Gaps section identifies areas where configuration was present in SPRO but no corresponding transactional evidence was found, or where configuration objects were incomplete. Each gap is assigned a priority level (High / Medium / Low) to guide the follow-up review.

Generated document โ€” gaps and recommended follow-up table

Configuration Detail Tablesโ€‹

The document concludes with detailed configuration tables for all relevant objects โ€” delivery types, billing types, item categories, pricing conditions, and more. Each table shows the full configured set alongside an Active flag derived from transactional data, making it immediately clear which objects are live and which are unused.

Generated document โ€” Delivery Types configuration table with active status

Configuration vs. reality

The Active status column is one of the most powerful features of AI@KB documentation. It distinguishes between what is configured in SPRO and what is actually used in practice โ€” giving project teams a clear view of the effective system footprint without manual cross-referencing.