1. Prepare
Describe edition, transaction boundary, trigger, interaction and evidence. Example: a local S/4HANA adaptation without an independent process, with extension-point availability unverified.
Practical usage guide
Build one evidence-led SAP extension architecture hypothesis with a primary runtime, component flow, governance gates, one fallback and explicit human confirmation.
Describe edition, transaction boundary, trigger, interaction and evidence. Example: a local S/4HANA adaptation without an independent process, with extension-point availability unverified.
Review the deterministic pattern and runtime recommendation, alternatives, discarded options, questions and gates. Check which conclusions depend on missing release or extension evidence.
This does not verify actual API availability or certify clean core compliance. Confirm released extension points and transaction constraints in the target edition before choosing an implementation.