Everything you need to know about ConfiDoq
Answers to common questions about automated SAP transport documentation, ConfiDoq features, and data privacy.
What is ConfiDoq?
ConfiDoq is a SaaS tool that automatically generates structured documentation for SAP transport requests. It takes a transport export from SAP S/4HANA or ECC as input and produces complete, audit-ready documentation enriched with contextual SAP knowledge — without any manual writing effort.
Who is ConfiDoq designed for?
ConfiDoq is built for SAP consultants, Basis administrators, project managers, and IT departments that manage SAP transports as part of their change management process. It is especially useful for teams undergoing S/4HANA migrations, teams subject to compliance requirements (SOX, GxP, internal audit), and any organization where documentation quality is a bottleneck.
What SAP systems does ConfiDoq support?
ConfiDoq currently supports SAP S/4HANA (on-premise and private cloud) and SAP ECC. Documentation is generated from standard transport request exports produced via our ConfiDoq report.
How do I export transport requests for ConfiDoq?
You export your transport requests from SAP using our ABAP report. ConfiDoq accepts the exported file, analyzes all included objects, and generates the documentation automatically. No SAP system access or RFC connection is required from ConfiDoq's side.
What does ConfiDoq include in the generated documentation?
Each generated document includes: a structured overview of the transport request, a list of all contained objects with type and technical name, a plain-language explanation of what each object does and its business context, change management metadata, and a version history. The output is designed to be immediately usable in reviews, audits, and stakeholder handovers.
What data is sent to ConfiDoq?
Only the technical SAP configuration data contained in your transport export is processed. This typically includes object names, types, and transport metadata — no transactional data, no personal data, and no business content. ConfiDoq does not require access to your live SAP system.
Where is my data processed and stored?
All data is processed and stored on EU-based infrastructure. ConfiDoq is fully GDPR-compliant. Input data is retained for a limited time after documentation generation is complete. For enterprise customers, a Data Processing Agreement (DPA) is available.
Does ConfiDoq sell or share my data?
No. ConfiDoq never sells, shares, or monetizes customer data with third parties. Data is processed solely for the purpose of generating your documentation.
What is a credit and what does it cover?
One credit equals one generated documentation for one transport request. Credits are consumed when you generate a document. A single transport request may contain dozens of SAP objects — the credit covers the full documentation of the entire request, regardless of its complexity.
Is there a free trial?
Yes. Every new account receives 3 free credits upon registration, with no credit card required. This allows you to generate three complete transport documentation outputs and evaluate the quality before purchasing.
What output formats are available?
ConfiDoq generates documentation in two formats: Markdown — the default output, ideal for embedding in wikis, Confluence, or any Markdown-compatible tool; and Word (.docx) — a polished, editable document suitable for stakeholder reviews, audits, and archiving. Both formats are available for download from your dashboard immediately after processing.
Can ConfiDoq integrate with my CI/CD or release management toolchain?
API-based integration is on the ConfiDoq roadmap. For current availability and enterprise integration options, contact the ConfiDoq team at sales@confidoq.ai.
How is ConfiDoq different from writing documentation manually?
Manual documentation of a single SAP transport request typically takes 1–3 hours depending on complexity. The quality depends on the individual consultant's SAP knowledge and available time. ConfiDoq generates equivalent or better documentation in seconds, with consistent structure, SAP-specific context enrichment, and no knowledge dependency. It also eliminates the risk of documentation being skipped under time pressure.