GCV2SQL · SAP HANA development quality

Static quality assessment

A bounded source review, not a certification of business correctness, database equivalence or performance. Findings are not evidence that fixes were applied. No uploaded SQL was executed and no live HANA connection was used.

Assessment identity and scope

Assessment: GCV-07c081e2ba699124
Generated: 2026-11-07T01:53:33+00:00
Project: Synthetic demonstration — no customer data
Artifact: Synthetic SQL quality example
Type: sql · Requested target: unknown (not version certification)
Application: 1.0.0-rc.1 · Revision: 0039
Finding schema: 1
Source SHA-256: 07c081e2ba699124f8d3612db39eee5abad83873be7f25cb63aecc9644db4464
Rule registry SHA-256: 691ab9fc2ed0dcade806c11301577a1fdbafa0660892723d319fe8b99923bfbb

Fingerprint convention: XML uses the server-normalized input (line endings, outer whitespace and any outer CDATA wrapper); SQL uses the exact submitted text. Keep the matching reviewed source with this report.

Summary

One source artifact analyzed. Coverage and unsupported constructs are recorded below. Counts separate authority classes; there is no generic quality score. Zero findings does not establish a clean or complete assessment.

0Scoped proven findings
0Human review
0Metadata required
0Data required
1Opportunities
0Unsupported findings

Findings and developer actions

IN list repeats identical literal values

OPTIMIZATION_OPPORTUNITY · info · DUPLICATE_IN_LITERAL

The membership list contains the same typed literal token more than once.

Finding identity
f-2e786d7bab091a6c3a80a11f
Affected node
SQL
Source location
{"sql": {"column": 52, "line": 1, "span": {"encoding": "unicode-codepoint", "end": 64, "start": 51}, "statement": 1}}
Evidence
{"predicate": ["X", "IN", "(", "1", ",", "1", ",", "NULL", ")"], "queryFingerprint": "1a0aa9c9a3b7e5eb7e5309db3ca8a0a153e16f5258ad404551fe4caa3ba02034", "values": ["1"]}
Next action
Remove only repeated identical literal entries; preserve NULL membership and the original predicate.
Proof / limits
{"authority": "LITERAL_MEMBERSHIP_IDEMPOTENCE_V1", "evidenceLevel": "E0", "nullSemanticsPreserved": true, "parameterOrderPreserved": true}
Candidate available, not applied
true

Coverage, skipped checks and limitations

{"coverage": [{"blockedBy": ["External table/view column existence, correlation, intended aggregation grain and arbitrary subquery equivalence need authoritative metadata and complete scoped/type analysis. No missing column or business key is guessed."], "check": "SQL source-column references", "coverage": "PARTIAL"}, {"blockedBy": ["No complete version-specific function/type catalog or live prepare was used."], "check": "HANA version compatibility", "coverage": "PARTIAL", "target": "unknown"}], "notice": "Static SELECT/SQLScript subset only. Source metadata, full HANA grammar, runtime behavior and performance are not validated. Nothing was executed."}

Next steps

  1. Review each finding and its source evidence with the responsible engineer.
  2. Supply authoritative metadata or business intent where required; do not count unknowns as defects.
  3. Preview only authorized source-bound candidates in the workbench. This report makes no change to the source or customer systems.
  4. Validate any approved change under a separately authorized test plan. Measure performance rather than infer savings.

The report omits the full raw source by default, but evidence and names may still be proprietary. Store and share only with authorized recipients. Browser Print / Save as PDF can produce a local printable copy.