Key Takeaways

● Clean core extensibility is when we, as a design choice, decide to go that way per use case: synchronous OData for transactional use cases that require immediate response, asynchronous events for all other use cases.

● At the beginning of each CAPM project, multi-tenancy issues should be addressed; retrofitting tenant isolation in a single-tenant already deployed extension is a much more disruptive affair than to include the feature from the word go.

● Principal propagation does not feature in the design of which extensions preserve core system authorization and audit trails’ integrity versus which ones allow them to degrade silently.

● In CAPM extensions the great production risk is not in the framework at all but in the peripheral issues: destination config, XSUAA scope mapping, CDS to core field mapping which go out of sync across environments.

● Clean core, which reduces upgrade risk in the ERP core but does not remove operational burden; it shifts versioning, monitoring, and…