Dateiformate je Engine
Welche Exporte und Dateien jede Analyse-Engine akzeptiert — aus den deklarierten Eingabeverträgen der Engines.
Inhalt geprüft am 26. September 2026
Upload-Regeln für alle Engines
- Laden Sie
.xml,.json,.csv,.zipoder.abapbis je 100 MB hoch (Betreibereinstellung). - Archive: höchstens Kompressionsverhältnis 100:1, insgesamt 500 MB entpackt, 10 000 Einträge und 2 Ebenen verschachtelter Archive; Einträge mit absoluten Pfaden oder
../werden abgewiesen. - XML wird mit deaktivierten DTDs, Entity-Deklarationen und externen Referenzen geparst.
- Geheimnisse in Textdateien (XML, XSD, WSDL, EDMX, XDP, JSON, CSV, ABAP und Klartextquellen) werden vor dem Speichern geschwärzt, und die Anzahl der Schwärzungen wird mit dem Upload gespeichert. ZIP- und PDF-Dateien werden nicht umgeschrieben; Evidenz-Ausschnitte werden bei der Analyse geschwärzt. Details: Datenverarbeitung im Detail.
Dateiformate je Engine
Formate, die jede Engine laut Eingabevertrag akzeptiert. Uploads werden zusätzlich anhand von Magic Bytes, Archivgrenzen und einem Malware-Scan geprüft, bevor eine Engine sie sieht.
| Engine | Akzeptierte Formate | Eingabevertrag |
|---|---|---|
| OPD Guard | JSON, XML, CSV, XLSX | BRFplus output-determination decision tables (CSV with a Step column or '# Step:' sections, XML <Table name=...> export, XLSX with one sheet per step, or JSON {'tables': {step: [rows]}}) plus an optional document 'scenario' with 'expected_determination', a batch 'scenarios' list ([{id, scenario, expected}]), 'baseline_tables' (previous version, for the before/after diff) and a FormDoctor 'form_handoff' block. XML carries batch scenarios as <Scenarios><Scenario id=...>, expectations as <Expected> and the previous version as <BaselineDecisionTables>.Erforderliche Eingabe: At least one decision table (CSV/XML/XLSX/JSON) |
| FormDoctor | XML, TEXT | Adobe Form XDP template together with the form's runtime data XML and/or the form interface schema (XSD) (as artifacts, or data XML in raw_content + configuration.xdp_content / xsd_content), or a SAPscript / Smart Forms source (XML export or text). Optional configuration: business_source_fields, custom_fields [{name, form_enabled, context_supports_forms}], data_source {name, extensible}, form_template, output_type.Erforderliche Eingabe: XDP template AND runtime data XML or form interface XSD (binding verification); or a SAPscript / Smart Forms source (legacy form audit) |
| Custom Field Flow Doctor | JSON | Custom field registry JSON: {'field_name': 'YY1_…', 'hops': [{source_context, target_context, min_release?}], 'field_definitions': {context: {type, length, usages: ['UI', 'FORM', 'API', ...]}}, 'required_exposures': {context: ['FORM', 'API', 'ANALYTICS', 'UI', 'EMAIL']} (or a list for the final context), 'active_scenarios': [...], 'badi_implementations': [...]}.Erforderliche Eingabe: field_name; hops or field_definitions |
| Extension Impact Guard | JSON | Extension inventory JSON: {'extensions': [{object_name, object_type, status, dependencies, data_type, length, software_collection}], 'dependencies': {object: [consumers]}, 'target_object': '…', 'action': 'DELETE'|'MODIFY'|'CHANGE_TYPE'|'CHANGE_LENGTH'|'TRANSPORT', 'change': {new_type, new_length}}. Deletion / change / transport verdicts require an explicit target_object.Erforderliche Eingabe: extensions or dependencies/graph adjacency map; target_object for deletion/impact verdicts |
| SPRO2Cloud | CSV, JSON, TEXT, XLSX | SPRO / IMG activity export: CSV (comma, semicolon, tab or pipe separated) with an activity (ActivityID / IMG activity / node), activity name, SPRO path or table column; JSON rows {'activity_id', 'activity_name', 'spro_path', 'table_name', 'module', 'country', 'source_release'} (list or {'activities': [...]}); an XLSX workbook (base64) whose worksheets start with such a header row; or a plain list of IMG activity IDs / table names, one per line.Erforderliche Eingabe: At least one IMG activity ID, activity name, SPRO / IMG path or configuration table name |
| ECC2Cloud Navigator | CSV, JSON, TEXT, ZIP | Legacy landscape inventory: ST03N / SUIM usage CSV (TCode / Transaction / object_name column, optional ExecutionCount, AvgResponseTimeMs, UserCount, Module, Process, Owner), TADIR export (OBJECT, OBJ_NAME, DEVCLASS, AUTHOR), JSON rows {name, type, executions, module, process, owner} or typed lists {'img_items', 'tables', 'abap_objects', 'custom_objects', 'requirements'}, 'TCODE [count]' lines, or an abapGit repository ZIP (base64).Erforderliche Eingabe: At least one transaction, interface, IMG activity, table, ABAP / custom object or requirement |
| SAP Gap Radar | JSON, TEXT | Business / technical requirement statements: JSON {'requirements': [{'requirement': '…', 'scope_items': [...]}]}, {'requirement': '…'}, a JSON list, or plain text (one statement, or a bulleted / numbered / ID-prefixed list with one requirement per item).Erforderliche Eingabe: At least one non-empty requirement statement; Every statement must be an SAP business or technical requirement (SAP process, object, configuration or extensibility term); unrelated prose is rejected as GAP_RADAR_INVALID_INPUT |
| Migration Template Intelligence | XML, CSV, TEXT | SAP data migration template (Migration Cockpit 'Migrate Your Data' load file): the Excel 2003 XML spreadsheet as downloaded from SAP (all sheets, document properties OBJECT_NAME / VERSION / LANGUAGE, field list) or the CSV of one data sheet including its header rows (as converted from an XLSX by the upload): title row, SAP structure names, SAP field names, the type-specification row ('ETE;80;0;C;80;0'), group names ('Schlüssel' / 'Key') and field descriptions ('*' = mandatory), then the data rows. EN and DE templates.Erforderliche Eingabe: A migration template data sheet with its type-specification row (XML spreadsheet or CSV) |
| Clean Core Object Guard | ABAP, ZIP, JSON | Custom ABAP source (report, class, function group include), an abapGit repository ZIP containing *.abap files, or an object list JSON {'objects': [{'name', 'type': TABL|FUNC|CLAS|DDLS}]} for release-status lookup.Erforderliche Eingabe: ABAP source with at least one statement, an abapGit ZIP, or an object list |
| Change Pointer Coverage Auditor | JSON, CSV, TEXT | ALE change pointer configuration: JSON {'target_message_type', 'bd61_active', 'bd50_msg_types', 'bd52_fields', 'expected_fields', 'dd04l_metadata', 'bdcp2_samples', 'change_documents', 'bd53_reduced_fields'} or a record-type CSV (BD61/BD50/BD52/DD04L/BDCP2/CDPOS rows).Erforderliche Eingabe: message type (target_message_type or active BD50 entry); BD52 field configuration |
| API Change Guard | JSON, XML, TEXT | Two API specifications of the same service — baseline (current) and candidate (target release): OpenAPI 2/3 (JSON or YAML) or OData EDMX V2/V4 XML — supplied as {'baseline': …, 'candidate': …} in raw_content / configuration or as artifacts named *baseline* / *candidate*; optional 'integrations' registry for consumer impact.Erforderliche Eingabe: baseline specification; candidate specification |
| Software Collection Dependency Guard | JSON, XML, ZIP | Key-User Software Collection export: JSON {'collections': [{collection_id, items: [{item_id, type, status, dependencies}], dependencies}], 'target_system_collections': [...], 'import_order': [collection ids]}, XML <software_collections> (optional <import_order><step collection="…"/></import_order>), or a ZIP (nested up to 2 levels) containing manifest.json / manifest.xml.Erforderliche Eingabe: At least one software collection |
| Transport Dependency Analyzer | JSON, CSV, XML | CTS transport metadata: CSV export of E070/E071/E071K with a TRKORR header row, JSON {'transports': {TRKORR: ['TABL ZTAB', …]}, 'e070': [...], 'e071': [...], 'call_references': [...], 'seometarel': [...], 'wbcrossgt': [...], 'planned_sequence': [...]}, XML with <E070>/<E071> sections, or the cloud-aware gCTS / abapGit adapter JSON {'adapter': 'GCTS', 'commits': [{id, parents, timestamp, objects | files}], 'planned_sequence': [commit ids]}.Erforderliche Eingabe: At least one transport request (or gCTS / abapGit commit) with its object list |
| Safe Decommission Preflight | JSON, CSV, TEXT | Decommissioning extract: JSON {'target_type' (USER | TECHNICAL_USER | SERVICE_USER | COMMUNICATION_USER | JOB_STEP_USER | RFC_DESTINATION), 'target_user' or 'target_destination', 'evaluation_date', 'usr02': [...], 'tbtco': [...], 'tbtcp': [...], 'rfcdes': [...], 'swwwihead': [...], 'agr_users': [...], 'sm20': [...], 'scheduled_integrations': [...], 'ownership': [...]} or a sectioned CSV ([TARGET], [USR02], [TBTCO], [TBTCP], [AGR_USERS], [INTEGRATIONS], [OWNERSHIP], ...). Time-based rules require 'evaluation_date' (extract date); it is never taken from the system clock.Erforderliche Eingabe: target_user or target_destination; per target type: USR02, TBTCO, RFCDES, SWWWIHEAD (users); + TBTCP (technical / job-step users); RFCDES + scheduled integration inventory (service / communication users, RFC destinations); evaluation_date for recency rules |
| Fiori 403 Root-Cause Doctor | JSON, CSV, TEXT | 403 diagnostic telemetry: JSON {'http_response': {status_code, method, url, headers, body}, 'su53': [...], 'iwfnd_error_log': [...], 'icf_services': [...], 'ucon_rules': [...], 'cloud_connector_logs': [...], 'btp_destination': {name, url, proxy_type, authentication, check_status}}, a browser network export (HAR JSON {'log': {'entries': [...]}}), an HTTP request/response text dump or SU53 text export, or SICF/SU53 CSV artifacts.Erforderliche Eingabe: At least one telemetry source (HTTP trace or HAR, SU53, /IWFND/ERROR_LOG, SICF, UCON, BTP destination, Cloud Connector) |
| Workflow Stuck Explainer | JSON, CSV | Workflow runtime extracts: JSON {'swwwihead': [{wi_id, wi_type, wi_stat, wi_rh_task}], 'swwloghist': [...], 'agent_traces': [...], 'swetypv': [...], 'containers': [...], 'deadlines': [...]} or CSV exports of SWWWIHEAD / SWWLOGHIST / SWETYPV with their column headers.Erforderliche Eingabe: SWWWIHEAD work items (or other workflow runtime tables) |
| IAM Cost Optimizer | JSON, CSV | Role composition and assignments: JSON {'roles': [{role_name, catalogs, authorizations, assigned_users}], 'users': [...], 'catalogs': [...], 'price_categories': {...}, 'usage_records': [...], 'read_only_alternatives': {app_id: read_only_app_id}} or CSV exports AGR_USERS (UNAME, AGR_NAME), AGR_1251 (AGR_NAME, OBJECT, FIELD, LOW), catalog/app, ST03N usage and read-only alternatives (APP_ID, READ_ONLY_APP_ID).Erforderliche Eingabe: business roles or user role assignments |
| Account Determination Preflight | JSON, CSV | Automatic account determination: JSON {'chart_of_accounts', 'company_code', 'obyc_rules': [...], 'vkoa_rules': [...], 'fi_rules': [...], 'ska1_accounts': [...], 'skb1_accounts': [...], 'valuation_classes': [...], 'movement_types': [{movement_type, transaction_key, account_modifier}], 'plants': [{plant, valuation_grouping_code}], 'expected_combinations': [{model, ..., expected_account}]} or CSV exports of T030 (KTOPL, KTOSL, BKLAS, KONTS/KONTU), C001/VKOA (VKORG, KTOSL, SAKNR), SKA1, SKB1. Company-code checks run only for an explicitly supplied company code.Erforderliche Eingabe: OBYC, VKOA and/or FI determination entries |
| System Refresh Delta Guard | JSON, CSV, TEXT | Post-refresh extracts of the target system: JSON {'sid', 'client', 'rfc_destinations', 'scot', 'logical_systems', 'jobs', 'printers', 'endpoints', 'integration_destinations', 'queues', 'custom_config', 'isolation_policy'} - optionally as {'pre_refresh': {...}, 'post_refresh': {...}, 'ignore_policy': [{section, key, reason}]} for the before / after comparison - or a sectioned CSV export.Erforderliche Eingabe: target SID; RFC / SCOT / logical system / job / printer sections for a full verdict |
| Error Log Root Cause | CSV, TEXT, JSON | SAP message log export: Migration Cockpit message log (including the Fiori 'SAPUI5-Export' with Typ, Nachrichtentitel, Nachrichtenklasse, Nachrichtennummer, Datum und Uhrzeit), SLG1 application log or any message table as CSV / TSV / semicolon / pipe (ALV list) text with a header row containing a message type column (Type, Msg Type, Typ, Meldungstyp, MSGTY) and a message class + number (ID / Message Class / Nachrichtenklasse / Arbeitsgebiet + Number / No. / Nummer) or a combined message column (Message: 'CNIF_PI 076'); optional object (Instance, Object Key, Source Record, WBS Element / PSP-Element, Project, Material, Customer, Supplier, Order …), parent (Parent, Superior, Higher-Level, Übergeordnet), migration object and timestamp columns. Without an object column the objects are read from the message texts (source-record groups, framework / wrapper message roles). JSON: an array of message objects or {'messages': [...]} with the same keys.Erforderliche Eingabe: A message log with a message type column and a message id (class + number or combined) |
| MFS BlackBox | JSON, CSV, XLSX | MFS telegram log: CSV/TSV/pipe log with a header row (type, hu_id, cp, to_cp, seq_no, sender_plc, receiver_plc, status, time_sec/timestamp, wt_id, plc_release; EDGE,<from>,<to> rows declare conveyor topology), the same table as the first worksheet of an XLSX workbook, or JSON {'telegrams': [...], 'conveyor_edges': [[from, to]], 'configuration': {ack_timeout_seconds, max_retries, heartbeat_timeout_seconds, completion_timeout_seconds, recurrence_threshold}}. Inline payloads are bounded by the service payload limit; delimited logs of any size (multi-GB) are streamed through POST /api/v1/analyze/stream and processed line by line with bounded memory.Erforderliche Eingabe: At least one telegram with a 'type' |