K.2Bloom · UNot started

Key-user (in-app) extensibility

Reading depth

What you'll learn

The in-app (key-user) tools let business users add fields, views, and simple logic through released, supported extension points — no classic development.

  • Key-user tools are built into the Fiori apps — changes are made through screens, not code.
  • You can add custom fields, custom views of data, and simple custom logic.
  • You only ever extend at released (SAP-supported, stable) extension points.

Key-user extensibility is a set of tools built right into the SAP Fiori apps you already use. (Fiori is SAP's modern, web-style user interface.) These tools let business power users adapt the system without any classic programming — the changes are made through screens, not code.

Through them you can add custom fields to standard apps, build custom views of data (SAP calls these CDS views, which are essentially saved, reusable queries), and attach simple custom logic at points SAP has deliberately opened up for this purpose. Those opening points are called released extension points — SAP has marked them as safe and stable to build on.

The important word is 'released.' Because you are only ever extending where SAP has published a stable, supported hook, your additions are upgrade-safe by design. You get genuine flexibility without taking on the upgrade risk that classic development used to carry.

Key points

  • Key-user tools are built into the Fiori apps — changes are made through screens, not code.
  • You can add custom fields, custom views of data, and simple custom logic.
  • You only ever extend at released (SAP-supported, stable) extension points.
  • Because the hooks are released, the changes are upgrade-safe by design.

Examples

A field added the supported way

A purchasing lead adds a 'Preferred Carrier' field to a standard app using the in-app tool. It appears for everyone, reports correctly, and is still there after the next upgrade — no developer involved.

Source notes: clean-core-curriculum (business synthesis)

Ask Claude

Build a prompt from this lesson + your question and open a fresh Claude chat with it pre-filled — handy for adapting a before/after pattern to your own object.