HANA Readiness: the DB Mindset

• QuestionWhat is "What actually changed when you moved to HANA"?Tap to revealAnswerHANA changed the storage and execution model — columnar, no implicit sort, snapshot reads, transparent pool/cluster tables — so old assumptions about order and locking no longer hold.
• QuestionIn "What actually changed when you moved to HANA", explain:Tap to revealAnswerColumnar by default — no implicit physical row order to rely on.
• QuestionIn "What actually changed when you moved to HANA", explain:Tap to revealAnswerNo implicit sort: order must be requested, or it is arbitrary.
• QuestionIn "What actually changed when you moved to HANA", explain:Tap to revealAnswerSELECT takes no row lock; reads come from an MVCC snapshot.
• QuestionIn "What actually changed when you moved to HANA", explain:Tap to revealAnswerPool/cluster tables are now transparent — same SQL, different cardinality.
• QuestionAnalogy for "What actually changed when you moved to HANA":Tap to revealAnswerAnyDB was a filing cabinet that kept folders in a fixed order; HANA is a warehouse of loose cards it re-shuffles for speed, so you must label the order you want.
• QuestionWhat is "Common HANA pitfalls"?Tap to revealAnswerThe classic traps: ORDER BY is no longer free, partial-key SELECT SINGLE is arbitrary, and an empty FOR ALL ENTRIES driver returns every row — so guard it.
• QuestionIn "Common HANA pitfalls", explain:Tap to revealAnswerORDER BY is not free — request it explicitly when you depend on order.
• QuestionIn "Common HANA pitfalls", explain:Tap to revealAnswerSELECT SINGLE on a partial key returns an arbitrary row; supply the full key.
• QuestionIn "Common HANA pitfalls", explain:Tap to revealAnswerFOR ALL ENTRIES de-duplicates the driver AND returns ALL rows on an empty driver — guard it.
• QuestionIn "Common HANA pitfalls", explain:Tap to revealAnswerImplicit type conversion in WHERE can cost the index; match the field's type.
• QuestionAnalogy for "Common HANA pitfalls":Tap to revealAnswerFOR ALL ENTRIES with an empty driver is like an unfiltered search box returning the entire catalog instead of nothing.
• QuestionWhat is "Less-obvious pitfalls"?Tap to revealAnswerThese less-obvious pitfalls corrupt results silently: BINARY SEARCH and DELETE ADJACENT DUPLICATES both assume a prior SORT, and UP TO 1 ROWS needs an explicit ORDER BY.
• QuestionIn "Less-obvious pitfalls", explain:Tap to revealAnswerPACKAGE SIZE issues separate DB calls and can break consistent-read; use cursoring deliberately.
• QuestionIn "Less-obvious pitfalls", explain:Tap to revealAnswerMODIFY into a HASHED table reallocates buckets — prefer INSERT INTO a SORTED table on hot paths.
• QuestionIn "Less-obvious pitfalls", explain:Tap to revealAnswerDELETE ADJACENT DUPLICATES needs a prior SORT by the same fields, or it misses non-adjacent dups.
• QuestionIn "Less-obvious pitfalls", explain:Tap to revealAnswerREAD TABLE BINARY SEARCH on an unsorted table is undefined — no dump, just wrong results.
• QuestionAnalogy for "Less-obvious pitfalls":Tap to revealAnswerBINARY SEARCH on an unsorted table is like using a dictionary's binary lookup on pages that were shuffled — you confidently land on the wrong page.
• QuestionWhat is "What to actually do: SCMON → ATC → baseline"?Tap to revealAnswerScope live code with SCMON/UPL, quality-scan it with the Custom Code Migration app, freeze today's debt under an ATC baseline, and re-run after every FPS.
• QuestionIn "What to actually do: SCMON → ATC → baseline", explain:Tap to revealAnswerScope with SCMON/UPL for 1–3 months so you fix live code, not dead code.
• QuestionIn "What to actually do: SCMON → ATC → baseline", explain:Tap to revealAnswerQuality-scan with the Custom Code Migration app or SYCM against the Simplification DB.
• QuestionIn "What to actually do: SCMON → ATC → baseline", explain:Tap to revealAnswerBaseline the findings so only new debt raises alerts; then chip away at the baseline.
• QuestionIn "What to actually do: SCMON → ATC → baseline", explain:Tap to revealAnswerRe-run after every FPS — readiness checks gain rules each release.
• QuestionAnalogy for "What to actually do: SCMON → ATC → baseline":Tap to revealAnswerIt is triage then a debt freeze: find out which patients are actually in the building, stop the bleeding for new injuries, and work down the old caseload.
• QuestionWhat is "The Simplification Database"?Tap to revealAnswerThe Simplification Database is SAP's catalog of what changed in S/4; check against it with the release-matched S4HANA_READINESS_2023 variant via SYCM or 'Analyze Custom Code.'
• QuestionIn "The Simplification Database", explain:Tap to revealAnswerThe Simplification DB catalogs what S/4 removed or changed; readiness checks compare against it.
• QuestionIn "The Simplification Database", explain:Tap to revealAnswerReach it via SYCM or the 'Analyze Custom Code' app.
• QuestionIn "The Simplification Database", explain:Tap to revealAnswerUse the release-aligned variant S4HANA_READINESS_2023.
• QuestionIn "The Simplification Database", explain:Tap to revealAnswerOne DB per target release — always load the target's, not an older one.
• QuestionAnalogy for "The Simplification Database":Tap to revealAnswerIt is the official 'what moved or was discontinued' list for a given release — use the edition that matches where you are going, not last year's.

1. 1Outline the core idea

   Analyse~10 min

   In your own words, outline the central idea of "What actually changed when you moved to HANA". Aim for one paragraph, no jargon you haven't earned.

   Done when: A non-expert could read your paragraph and explain it back to you.

   Re-read the source concept

2. 2Translate it to a real situation

   Apply~15 min

   Find a real situation from your own work / life where "The Simplification Database" applies. Translate the idea — describe the situation, the move you'd make, and the alternative you considered first.

   Done when: You can name a specific situation (not a hypothetical), state your move, and explain the trade-off in one paragraph.

   Re-read the source concept

3. 3Teach it back

   Evaluate~5 min

   Pick someone (a colleague, a peer, a rubber duck) and explain the section to them in under 5 minutes. Use your own example, not the one from the lesson.

   Done when: Your listener can repeat the core idea + the trade-off back to you without prompting.

Why this matters. Reading + quizzing prove recall; applying it in a real situation is the only evidence of transfer. Treat at least one of these as non-negotiable before you move on.